1CRM_REPORT(8) System Administration Utilities CRM_REPORT(8)
2
3
4
6 crm_report - Part of the Pacemaker cluster resource manager
7
9 crm_report [options] [DEST]
10
12 crm_report - Create archive of everything needed when reporting cluster
13 problems
14
15 Required option:
16 -f, --from TIME
17 time prior to problems beginning (as "YYYY-M-D H:M:S" including
18 the quotes)
19
21 -V increase verbosity (may be specified multiple times)
22
23 -h, --help
24 display this message
25
26 -v, --version
27 display software version
28
29 --features
30 display software features
31
32 -t, --to TIME
33 time at which all problems were resolved (as "YYYY-M-D H:M:S"
34 including the quotes; default "now")
35
36 -T, --cts TEST
37 CTS test or set of tests to extract
38
39 --cts-log
40 CTS master logfile
41
42 -n, --nodes NODES
43 node names for this cluster (only needed if cluster is not
44 active on this host; accepts -n "a b" or -n a -n b)
45
46 -M do not search for cluster logs
47
48 -l, --logfile FILE
49 log file to collect (in addition to detected logs if -M is not
50 specified; may be specified multiple times)
51
52 -p PATT
53 additional regular expression to match variables to be masked in
54 output (default: "passw.*")
55
56 -L PATT
57 additional regular expression to match in log files for analysis
58 (default: CRIT: ERROR:)
59
60 -S, --single-node
61 don't attempt to collect data from other nodes
62
63 -c, --cluster TYPE
64 force the cluster type instead of detecting (currently only
65 corosync is supported)
66
67 -C, --corosync
68 force the cluster type to be corosync
69
70 -u, --user USER
71 username to use when collecting data from other nodes (default
72 root)
73
74 -D, --max-depth
75 search depth to use when attempting to locate files
76
77 -e, --rsh
78 command to use to run commands on other nodes (default ssh -T)
79
80 -d, --as-directory
81 leave result as a directory tree instead of archiving
82
83 --sos-mode
84 use defaults suitable for being called by sosreport tool (behav‐
85 ior subject to change and not useful to end users)
86
87 DEST, --dest DEST
88 custom destination directory or file name
89
90 crm_report works best when run from a cluster node on a running clus‐
91 ter, but can be run from a stopped cluster node or a Pacemaker Remote
92 node.
93
94 If neither --nodes nor --single-node is given, crm_report will guess
95 the node list, but may have trouble detecting Pacemaker Remote nodes.
96 Unless --single-node is given, the node names (whether specified by
97 --nodes or detected automatically) must be resolvable and reachable via
98 the command specified by -e/--rsh using the user specified by
99 -u/--user.
100
102 crm_report -f "2011-12-14 13:05:00" unexplained-apache-failure
103 crm_report -f 2011-12-14 -t 2011-12-15 something-that-took-mul‐
104 tiple-days crm_report -f 13:05:00 -t 13:12:00 brief-outage
105
106
107
108crm_report 2.0.3-4b1f869f0f November 2019 CRM_REPORT(8)