#321: Store test logs for at least a month
------------------------+---------------------------------------------------
Reporter: kparal | Owner:
Type: task | Status: new
Priority: major | Milestone: Nice to have soon
Component: production | Resolution:
Keywords: |
------------------------+---------------------------------------------------
Comment (by jlaska):
tflink suspects that tmpwatch in RHEL5 isn't honoring the time argument of
"15d". Using a `find` command, we've confirmed that there are no result
logs older than 1 day on the system. Per Tim's suggestion, I've adjusted
the tmpwatch command used in /etc/cron.d/autoqa to the following ...
{{{
0 13 * * * autotest /usr/sbin/tmpwatch -vv --dirmtime -umc -f 360
/usr/share/autotest/results/ -X README
}}}
This should tell us the timestamp of files being removed (-vv) and only
remove files older than 360 hours (15 days). Hopefully with the above
change, this will give us a good sense for what is happening. That's
certainly not expected. Hopefully this is Investigation continues.
I'd love to adjust to 30 days as a long-term goal, but it's just not
practical given our current storage constraints. Our storage needs are
definitely longer sufficient since autoqa-0.4.4 increased the number of
test cases, events ... and results. As we start to collect more results
longer than 1 day ... I'll gather some average per day numbers.
We also have some jobs that have *enormous* test results (3.0G). We'll
also need to explore why those logs are obscenely huge.
--
Ticket URL: <
https://fedorahosted.org/autoqa/ticket/321#comment:1>
AutoQA <
http://autoqa.fedorahosted.org>
Automated QA project