Red Hat Bugzilla – Bug 169057
nightly yum cron updates not shown by logwatch
Last modified: 2007-11-30 17:11:13 EST
From Bugzilla Helper:
User-Agent: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.7.10) Gecko/20050909 Fedora/1.7.10-1.5.2
Description of problem:
I have the nightly yum update cron job turned on. Many times it shows updates applied in /var/log/yum.log. In FC4 these updates show up in the output from logwatch that is sent out daily. In FC3 these updates never appear to show up in the logwatch output.
Version-Release number of selected component (if applicable):
Steps to Reproduce:
1. chkconfig yum on
2. wait until yum updates something during the nightly run
Actual Results: I get logwatch reports but nothing about yum updates is included in those.
Expected Results: As I get in FC4 I should see what yum did overnight.
Thank you for your notice.
The fixed version is on
could you please test it?
This version will probably be in update soon.
This bug is fixed in the last fc3 logwatch update (logwatch-5.2.2-1.FC3.2).
If these problem is still present in this version please open this bug.
Hmm, it didn't appear to work with logwatch-5.2.2-1.FC3.2.test. Sorry it took
so long, I finally had some yum nightly updates go through. I'll install
logwatch-5.2.2-1.FC3.2 but I'm guessing it is the same package so it still won't
show the nightly yum updates.
I notice that the yum filter is configured to use the US date ("%m/%d/%y").
However my yum.log looks like:
Nov 29 04:26:32 Updated: selinux-policy-targeted-sources.noarch 1.17.30-3.19
Shouldn't the yum filter be using std date ("%b %d")?
Please could you send me the log files (or the germane part of them), which
demonstrate this problem?
Created attachment 121770 [details]
Here's the fix, put this in /etc/log.d/scripts/logfiles/yum/applyupdate and
give it execute permission. Seems to work for me (i.e. logwatch now shows the
nightly automatic yum updates).
Thank you for bug report.
This is another problem - logwatch don't process yum logs at all. It is fixed in
If there is any problem please reopen this bug.