Bug 516551

Summary:	sosreport -k general.syslogsize=15 doesn't work
Product:	Red Hat Enterprise Linux 5	Reporter:	Issue Tracker <tao>
Component:	sos	Assignee:	Adam Stokes <astokes>
Status:	CLOSED ERRATA	QA Contact:	BaseOS QE <qe-baseos-auto>
Severity:	medium	Docs Contact:
Priority:	medium
Version:	5.5	CC:	agk, ahecox, azelinka, bmr, cward, james.brown, joshua, tao
Target Milestone:	rc
Target Release:	---
Hardware:	All
OS:	Linux
Whiteboard:
Fixed In Version:		Doc Type:	Bug Fix
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:	2010-03-30 08:07:27 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:

Comment 2 James G. Brown III 2009-08-25 15:39:46 UTC

Only messages.* and secure.* adhere to a size limit when running an sosreport. messages and secure themselves or any other /var/log/ file are not as the output of sosreport -l suggests with the general.syslogsize option

general.syslogsize    15 max size (MiB) to collect per syslog file

This is leading to huge sosreports and wasted space in /tmp

Comment 4 joshua 2009-10-28 20:56:35 UTC

Not wasted space in /tmp... it is worse than that.  The issue is that if there isn't so much space available in /tmp, and we have a 5+gig /var/log/messages file, sosreport will never complete.  It fills up /tmp, and dies.

As I understand it, this is because the limits are applied to /var/log/messages.*, not to /var/log/messages itself!  Should take about, what, 10 minutes to fix?

Comment 9 Chris Ward 2010-02-11 10:12:13 UTC

~~ Attention Customers and Partners - RHEL 5.5 Beta is now available on RHN ~~

RHEL 5.5 Beta has been released! There should be a fix present in this 
release that addresses your request. Please test and report back results 
here, by March 3rd 2010 (2010-03-03) or sooner.

Upon successful verification of this request, post your results and update 
the Verified field in Bugzilla with the appropriate value.

If you encounter any issues while testing, please describe them and set 
this bug into NEED_INFO. If you encounter new defects or have additional 
patch(es) to request for inclusion, please clone this bug per each request
and escalate through your support representative.

Comment 13 errata-xmlrpc 2010-03-30 08:07:27 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 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-0201.html