Bug 1190723

Summary:	crm_report not being collected with sosreport
Product:	Red Hat Enterprise Linux 6	Reporter:	Shane Bradley <sbradley>
Component:	sos	Assignee:	Shane Bradley <sbradley>
Status:	CLOSED ERRATA	QA Contact:	Miroslav Hradílek <mhradile>
Severity:	medium	Docs Contact:
Priority:	medium
Version:	6.5	CC:	agk, bmr, dkutalek, gavin, mhradile, plambri, pmoravec, sbradley
Target Milestone:	alpha
Target Release:	6.7
Hardware:	Unspecified
OS:	Unspecified
Whiteboard:
Fixed In Version:	sos-3.2-15.el6	Doc Type:	Rebase: Enhancements Only
Doc Text:	Important: if this rebase also contains bug fixes (or contains only bug fixes), select the correct option from the Doc Type drop-down list. Rebase package(s) to version: sos-3.2 Highlights and notable enhancements: The timeout is longer for commands with the rebase and should address the command crm_report that took long time to complete.	Story Points:	---
Clone Of:		Environment:
Last Closed:	2015-07-22 06:33:37 UTC	Type:	Bug
Regression:	---	Mount Type:	---
Documentation:	---	CRM:
Verified Versions:		Category:	---
oVirt Team:	---	RHEL 7.3 requirements from Atomic Host:
Cloudforms Team:	---	Target Upstream Version:
Embargoed:

Comment 20 Bryn M. Reeves 2015-06-03 08:49:32 UTC

I wouldn't bother with strace as a first step. Start by just capturing ps and top data once per second, e.g.:

  # top -d 1 -b > /tmp/top &
  # while true; do (date; ps ax --forest)>> /tmp/ps; sleep 1; done

And run "sosreport -v --batch -o cluster" or whatever.

Comment 22 Bryn M. Reeves 2015-06-04 08:48:52 UTC

I saw similar things testing the original crm_report patch (with artificially inflated log sizes).

In some ways it would be helpful if crm_report either had a "--everything" option (but with a better name ;), or an option to say grab the last N-thousand messages. That's generally a lot cheaper than parsing out dates.

Comment 25 errata-xmlrpc 2015-07-22 06:33:37 UTC

Since the problem described in this bug report should be
resolved in a recent advisory, it has been closed with a
resolution of ERRATA.

For information on the advisory, and where to find the updated
files, follow the link below.

If the solution does not work for you, open a new bug report.

https://rhn.redhat.com/errata/RHBA-2015-1323.html