Escalated to Bugzilla from IssueTracker
Indicate the platform(s) (architectures) the problem is being reported against. >> RHEL5 32bit and 64bit Provide clear and concise problem description as it is understood at the time of escalation >> Installing RHBA-2008:0362 causes logwatch to find unmatched entries in /var/log/up2date It complains --------------------- up2date Begin ------------------------ **Unmatched Entries** updateLoginInfo() login info updateLoginInfo() login info updateLoginInfo() login info ---------------------- up2date End ------------------------- Steps to reproduce >> - On a RHEL5 U1 system install packages associated with RHBA-2008:0362 - Register the system against RHN Hosted/Satellite - Install or upgrade few packages - Execute rhn-profile-sync - Let logwatch scan /var/log/up2date log file Observed behavior >> On executing rhn-profile-sync it would log [Thu Oct 9 16:45:57 2008] up2date updateLoginInfo() login info [Thu Oct 9 16:45:57 2008] up2date logging into up2date server [Thu Oct 9 16:45:57 2008] up2date successfully retrieved authentication token from up2date server [Thu Oct 9 16:45:57 2008] up2date Updating package profile On this logwatch reports --------------------- up2date Begin ------------------------ **Unmatched Entries** updateLoginInfo() login info ---------------------- up2date End ------------------------- Desired behavior >> Either the information logged through up2date should be [Thu Oct 9 16:45:52 2008] up2date logging into up2date server [Thu Oct 9 16:45:52 2008] up2date successfully retrieved authentication token from up2date server [Thu Oct 9 16:45:52 2008] up2date Updating package profile OR the logwatch filters should be edited to ignore "updateLoginInfo() login info" State specific action requested of SEG >> Would like SEG to review this and decide whether a change is to be done in information logged in /var/log/up2date revert the message "updateLoginInfo() login info" to "up2date logging into up2date server" or the filters mentioned under /usr/share/logwatch/scripts/services/up2date Attach sosreport >> Have attached the sosreport of the system on which this issue is seen. Refer /var/log/up2date. List any customer applied changes from the last 30 days >> Upgraded/Installed RHBA-2008:0362 on the system. This event sent from IssueTracker by mpoole [Support Engineering Group] issue 228117
Under /usr/share/logwatch/scripts/services/up2date it has : if ( ( $ThisLine =~ /^updating login info$/ ) or This is the old string. It doesn't have the new string. Issue escalated to Support Engineering Group by: pmutha. pmutha assigned to issue for Production Support (Pune). Category set to: RHN::up2date Internal Status set to 'Waiting on SEG' Status set to: Waiting on Tech This event sent from IssueTracker by mpoole [Support Engineering Group] issue 228117
Proposed fix is here: http://linux.derkeiler.com/Mailing-Lists/RedHat/2008-07/msg00085.html Basically it would on your end amount to adding this line: ( $ThisLine =~ /^updateLoginInfo\(\) login info/ ) or to /usr/share/logwatch/scripts/services/up2date instead of the end user having to copy that file to /etc/logwatch/scripts/services/up2date and add that line her/himself. I have done the latter and will post back if it fixes for tonight's logwatch runs. Diff for what I did: --- /usr/share/logwatch/scripts/services/up2date 2008-01-03 08:59:00.000000000 -0600 +++ /etc/logwatch/scripts/services/up2date 2009-02-26 10:19:37.000000000 -0600 @@ -25,6 +25,7 @@ $DebugCounter++; } if ( ( $ThisLine =~ /^updating login info$/ ) or + ( $ThisLine =~ /^updateLoginInfo\(\) login info/ ) or ( $ThisLine =~ /^Opening rpmdb in \/var\/lib\/rpm\/ with option .$/ ) or ( $ThisLine =~ /^successfully retrieved authentication token from up2date server$/ ) or ( $ThisLine =~ /^(getA|a)vailablePackageList from network$/ ) or
(In reply to comment #3) > I have done the latter and will post back if it fixes for > tonight's logwatch runs. The change did fix the issue. Please commit this or have upstream commit.
I have sent an email to eric.moret, the maintainer listed in the file in question.
Could you please send your patch and bug report to the upstream mailing lists shown on the logwatch main page: http://www.logwatch.org/index.html # logwatch-bugs: Report a bug # logwatch-patches: Submit a patch (unified diff format please (diff -u)) Thank you, __ Eric
This request was evaluated by Red Hat Product Management for inclusion, but this component is not scheduled to be updated in the current Red Hat Enterprise Linux release. If you would like this request to be reviewed for the next minor release, ask your support representative to set the next rhel-x.y flag to "?".
An advisory has been issued which should help the problem described in this bug report. This report is therefore being closed with a resolution of ERRATA. For more information on therefore solution and/or where to find the updated files, please follow the link below. You may reopen this bug report if the solution does not work for you. http://rhn.redhat.com/errata/RHBA-2010-0033.html
*** Bug 548117 has been marked as a duplicate of this bug. ***