How do I generate a crm_report from a RHEL 6 or 7 High Availability cluster node using pacemaker?

Solution Verified - Updated

Environment

  • Red Hat Enterprise Linux (RHEL) 6 or 7 with the High Availability Add On
  • pacemaker

Issue

  • How is a crm_report generated?
  • What data do I gather for a Pacemaker cluster?

Resolution

Collecting crm_report via

sosreport
The sosreport utility will automatically collect a crm_report via the cluster plugin, and as such is the recommended method for gathering cluster-related data for providing to Red Hat Global Support Services.

NOTE: Certain releases of sos contain an issue which may prevent collection of crm_report, which may necessitate either updating the sos package, or running crm_report manually as described below.

Collecting crm_report manually


`crm_report` requires specifying a start time for the data to be collected, in the format `"YYYY-M-D H:M:S"` using the -f flag. For example: 
# crm_report -f "2014-04-10 12:00:00"

NOTE: When collecting a crm_report to provide to Red Hat Global Support Services during an investigation, it is important that the date specified is earlier than the known occurrences of the problems or behavior in question, ideally by at least a day or more. If it is unknown when the issue occurred, then going back one week or more is a good strategy. The following command will collect exactly 7 days prior to the current date/time. Please run this on each node:

# crm_report -f "`date --date='7 days ago' +%Y-%m-%d' '%H:%M:%S`"  -S

For more about what crm_report collects and it's options, please see:

# man crm_report
SBR
Product(s)
Components
Tags

This solution is part of Red Hat’s fast-track publication program, providing a huge library of solutions that Red Hat engineers have created while supporting our customers. To give you the knowledge you need the instant it becomes available, these articles may be presented in a raw and unedited form.