CRM_REPORT(8)

CRM_REPORT(8) πŸ’… the cluster-reporting bestie era

okay so this is crm_report, part of the Pacemaker cluster resource manager ✨ like the glow-up your cluster reports have been waiting for.


✨ SYNOPSIS ✨

crm_report [options] [DEST]

🌸 DESCRIPTION 🌸

crm_report β€” Create archive of everything needed when reporting cluster problems πŸŽ€

ngl bestie, that's the whole vibe: your cluster is being weird, so you scoop up literally everything a human would need to figure out why, and you put it in one archive. iconic behavior.

πŸ’– Required option: πŸ’–

  • -f, --from TIME β€” the time prior to the problems beginning (as "YYYY-M-D H:M:S" including the quotes, dontcha dare forget them πŸ™ˆ)
yes bestie, it's required. no -f, no archive. periodt.

πŸ‘‘ OPTIONS πŸ‘‘

  • -V β€” increase verbosity, and yes you can specify it multiple times β€” stack that verbosity like your fave lip gloss ✨
  • -h, --help β€” display this message (the classic "help me help you" move)
  • -v, --version β€” display software version
  • --features β€” display software features
  • -t, --to TIME β€” the time at which all problems were resolved (as "YYYY-M-D H:M:S" including the quotes; default "now")
  • -n, --nodes NODES β€” node names for this cluster (only needed if the cluster is not active on this host; accepts -n "a b" or -n a -n b β€” both slay, pick your vibe)
  • -M β€” do not search for cluster logs πŸš«πŸ”
  • -l, --logfile FILE β€” log file to collect (in addition to detected logs if -M is not specified; may be specified multiple times β€” so you can list your faves)
  • -p PATT β€” an additional regular expression to match variables to be masked in output (default: "passw.*") 🫣
  • -L PATT β€” an additional regular expression to match in log files for analysis (default: CRIT: ERROR:)
  • -S, --single-node β€” don't attempt to collect data from other nodes, main character energy only πŸ’…
  • -c, --cluster TYPE β€” force the cluster type instead of detecting (currently only corosync is supported)
  • -C, --corosync β€” force the cluster type to corosync, no detection needed
  • -u, --user USER β€” username to use when collecting data from other nodes (default root)
  • -D, --max-depth β€” search depth to use when attempting to locate files 🌊
  • -e, --rsh β€” command to use to run commands on other nodes (default ssh -T)
  • -d, --as-directory β€” leave result as a directory tree instead of archiving (for the girlies who like to browse)
  • --sos-mode β€” use defaults suitable for being called by sosreport tool (behavior subject to change and not useful to end users) πŸ™ˆ
  • DEST, --dest DEST β€” custom destination directory or file name ✨

crm_report works best when run from a cluster node on a running cluster, but (good news!!) it can be run from a stopped cluster node or a Pacemaker Remote node too 🫢

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. like they have to actually answer the phone, yk?


🌈 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

and that's the whole page bestie, go forth and collect those logs πŸ¦‹

sign-off time ✨ β€” this iconic piece of documentation is brought to you by crm_report 3.0.3+20260728.705..., dated September 2026. mwah πŸ’‹

πŸ“¦ where this page comes from