Note: This bug is displayed in read-only format because the product is no longer active in Red Hat Bugzilla.
For bugs related to Red Hat Enterprise Linux 4 product line. The current stable release is 4.9. For Red Hat Enterprise Linux 6 and above, please visit Red Hat JIRA https://issues.redhat.com/secure/CreateIssue!default.jspa?pid=12332745 to report new issues.

Bug 184363

Summary: Logwatch looks for wrong service name for cron
Product: Red Hat Enterprise Linux 4 Reporter: Håvard Lygre <hklygre>
Component: logwatchAssignee: Ivana Varekova <varekova>
Status: CLOSED ERRATA QA Contact:
Severity: medium Docs Contact:
Priority: medium    
Version: 4.0   
Target Milestone: ---   
Target Release: ---   
Hardware: All   
OS: Linux   
Whiteboard:
Fixed In Version: RHBA-2006-0631 Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2006-09-06 13:54:53 UTC Type: ---
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Embargoed:
Bug Depends On:    
Bug Blocks: 189992, 201655    

Description Håvard Lygre 2006-03-08 08:38:56 UTC
Description of problem:

Logwatch (service pam_unix) expects output from cron to begin with "cron:" while
it begins with "crond:".

This causes the following output in the daily security mails:

 --------------------- pam_unix Begin ------------------------ 

crond:
   Unknown Entries:
      session closed for user root: 170 Time(s)
      session opened for user root by (uid=0): 170 Time(s)

 ---------------------- pam_unix End ------------------------- 


Version-Release number of selected component (if applicable):

Red Hat Enterprise Linux ES release 4 (Nahant Update 3)
logwatch-5.2.2-1.EL4.1
vixie-cron-4.1-36.EL4

How reproducible:

Run logwatch on a system which runs cron-jobs.


  
Actual results:

Output as above.


Expected results:

No output.


Additional info:


Simple fix.

--- pam_unix.old        2006-03-08 09:41:56.000000000 +0100
+++ pam_unix    2006-03-08 09:42:02.000000000 +0100
@@ -133,7 +133,7 @@
       if ($line =~ s/^authentication failure; .*uid=(\d+) euid=(\d+) tty=(.+)
ruser= rhost=  user=(.+)$/$4($1,$2) on display $3/) {
          $data{$service}{'Authentication Failures'}{$line}++;
       }
-   } elsif ($service eq 'cron') {
+   } elsif ($service eq 'crond') {
           if ($line =~ s/^session opened for user (.+) by \(uid=\d+\)/$1/) {
                   ($Detail >= 5) && $data{$service}{'Sessions Opened'}{$line}++;
           } elsif ($line =~ /session closed for user/) {

Comment 3 Ivana Varekova 2006-04-27 13:50:05 UTC
Thank you for your bug report.
The fixed version is on
http://people.redhat.com/varekova/logwatch-5.2.2-2.EL4.test.src.rpm
Could you please test this version?
There are fixed other 5 bugs (the complete list of fixed bugs is on
http://people.redhat.com/varekova/work.html).

Comment 8 Red Hat Bugzilla 2006-09-06 13:54:54 UTC
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 the 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-2006-0631.html