Red Hat Bugzilla – Bug 159567
Logwatch doesn't recongnize routine mailman access
Last modified: 2007-11-30 17:07:18 EST
From Bugzilla Helper:
User-Agent: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.7.8) Gecko/20050513 Fedora/1.0.4-1.3.1 Firefox/1.0.4
Description of problem:
Logwatch reports routine access to mailman listinfo and archive pages as "unidentified 'other' records"
Version-Release number of selected component (if applicable):
Steps to Reproduce:
1. Standard RHEL 4 installation with mailman.
2. Access various pages under http://www.myserver.com/pipermail or http://www.myserver.com/mailman.
3. Wait for next day's logwatch report.
Actual Results: Lots of "unidentified 'other' records" in httpd section of logwatch report, all "GET /pipermail/..." or "GET /mailman/..." with code 200 responses.
Expected Results: The code 200 responses are normal accesses and should be filtered out by logwatch.
Created attachment 118292 [details]
This problem is fixed in the attached patch. Logwatch should ignore most of
mailx and pipermail log messages, but logwatch should not ignore (not only
mailman and pipermail) log messages with error response codes >400 (see
upstream version). The attached patch fixes this problem too.
logwatch seems to report all files without suffix. Mailman uses cgi files
Chances are, the patch attached is good enough.
Created attachment 118387 [details]
suppress the file list of no suffixes.
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.