Scroll to navigation

CRM_REPORT(8) System Administration Utilities CRM_REPORT(8)

NAME

crm_report - Part of the Pacemaker cluster resource manager

SYNOPSIS

crm_report [options] [DEST]

DESCRIPTION

crm_report - Create archive of everything needed when reporting cluster problems

Required option:

time prior to problems beginning (as "YYYY-M-D H:M:S" including the quotes)

OPTIONS

increase verbosity (may be specified multiple times)
display software version
display software features
time at which all problems were resolved (as "YYYY-M-D H:M:S" including the quotes; default "now")
CTS test or set of tests to extract
CTS master logfile
node names for this cluster (only needed if cluster is not active on this host; accepts -n "a b" or -n a -n b)
do not search for cluster logs
log file to collect (in addition to detected logs if -M is not specified; may be specified multiple times)
additional regular expression to match variables to be masked in output (default: "passw.*")
additional regular expression to match in log files for analysis (default: CRIT: ERROR:)
don't attempt to collect data from other nodes
force the cluster type instead of detecting (one of corosync, cman, openais, heartbeat)
force the cluster type to be openais
force the cluster type to be corosync
force the cluster type to be heartbeat
username to use when collecting data from other nodes (default root)
search depth to use when attempting to locate files
command to use to run commands on other nodes (default ssh -T)
use defaults suitable for being called by sosreport tool (behavior subject to change and not useful to end users)
custom destination directory or file name

crm_report works best when run from a cluster node on a running cluster, but can be run from a stopped cluster node or a Pacemaker Remote node.

If neither --nodes nor --single-node is given, crm_report will guess the node list, but may have trouble detecting Pacemaker Remote nodes. Unless --single-node is given, the node names (whether specified by --nodes or detected automatically) must be resolvable and reachable via the command specified by -e/--rsh using the user specified by -u/--user.

EXAMPLES

crm_report -f "2011-12-14 13:05:00" unexplained-apache-failure crm_report -f 2011-12-14 -t 2011-12-15 something-that-took-multiple-days crm_report -f 13:05:00 -t 13:12:00 brief-outage
June 2018 crm_report 1.1.18-bfe4e80420