Bug 187149 - Logwatch samba config doesn't account for gzipped log files
Logwatch samba config doesn't account for gzipped log files
Status: CLOSED ERRATA
Product: Red Hat Enterprise Linux 3
Classification: Red Hat
Component: logwatch (Show other bugs)
3.0
All Linux
medium Severity medium
: ---
: ---
Assigned To: Ivana Varekova
:
Depends On:
Blocks: 187539
  Show dependency treegraph
 
Reported: 2006-03-28 15:09 EST by Craig Miskell
Modified: 2007-11-30 17:07 EST (History)
0 users

See Also:
Fixed In Version: RHBA-2006-0333
Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of:
Environment:
Last Closed: 2006-05-10 17:43:30 EDT
Type: ---
Regression: ---
Mount Type: ---
Documentation: ---
CRM:
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:


Attachments (Terms of Use)

  None (edit)
Description Craig Miskell 2006-03-28 15:09:13 EST
Description of problem:
Default samba logfile config (/etc/log.d/conf/logfiles/samba.conf) doesn't 
account for the fact that logfiles might be gzipped (if logrotate is so 
configured).  It then attempts to parse gzip files, which occasionally have 
lines which match the date searches and spew binary garbage into the logwatch 
report.  Can be fixed by changing
LogFile = samba/*
to 
LogFile = samba/*.log

Version-Release number of selected component (if applicable):
logwatch-4.3.2-2.noarch

How reproducible:
Reliably, although depends on the precise contents of the gzip files

Steps to Reproduce:
1. Install logwatch, samba, and logrotate
2. Config logrotate to compress rotated logs
3. Wait for logwatch to find appropriate lines in compressed samba logs
  
Actual results:
Binary garbage (parts of gzip files) in logwatch reports

Expected results:
No garbage

Additional info:
Comment 4 Red Hat Bugzilla 2006-05-10 17:43:31 EDT
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-0333.html

Note You need to log in before you can comment on or make changes to this bug.