crm_simulate - Man Page

Part of the Pacemaker cluster resource manager


crm_simulate <data source> <operation> [options]


crm_simulate - simulate a Pacemaker cluster's response to events


Help Options

-h,  --help

Show help options


Show all help options


Show output help


Show operations options


Show synthetic cluster event options


Show artifact options


Show data source options

Output Options


Specify output format as one of: text (default), xml


Specify file name for output (or "-" for stdout)


Use more highly formatted output (requires --output-as=text)


-R,  --run

Process the supplied input and show what actions the cluster will take in response

-S,  --simulate

Like --run, but also simulate taking those actions and show the resulting new status

-X,  --in-place

Like --simulate, but also store the results back to the input file

-A,  --show-attrs

Show node attributes

-c,  --show-failcounts

Show resource fail counts

-s,  --show-scores

Show allocation scores

-U,  --show-utilization

Show utilization information

-P,  --profile=DIR

Process all the XML files in the named directory to create profiling data

-N,  --repeat=N

With --profile, repeat each test N times and print timings

Synthetic Cluster Events

-u,  --node-up=NODE

Simulate bringing a node online

-d,  --node-down=NODE

Simulate taking a node offline

-f,  --node-fail=NODE

Simulate a node failing

-i,  --op-inject=OPSPEC

Generate a failure for the cluster to react to in the simulation. See `Operation Specification` help for more information.

-F,  --op-fail=OPSPEC

If the specified task occurs during the simulation, have it fail with return code ${rc}. The transition will normally stop at the failed action. Save the result with --save-output and re-run with --xml-file. See `Operation Specification` help for more information.

-t,  --set-datetime=DATETIME

Set date/time (ISO 8601 format, see

-q,  --quorum=QUORUM

Set to '1' (or 'true') to indicate cluster has quorum

-w,  --watchdog=DEVICE

Set to '1' (or 'true') to indicate cluster has an active watchdog device

-g,  --ticket-grant=TICKET

Simulate granting a ticket

-r,  --ticket-revoke=TICKET

Simulate revoking a ticket

-b,  --ticket-standby=TICKET

Simulate making a ticket standby

-e,  --ticket-activate=TICKET

Simulate activating a ticket

Artifact Options

-I,  --save-input=FILE

Save the input configuration to the named file

-O,  --save-output=FILE

Save the output configuration to the named file

-G,  --save-graph=FILE

Save the transition graph (XML format) to the named file

-D,  --save-dotfile=FILE

Save the transition graph (DOT format) to the named file

-a,  --all-actions

Display all possible actions in DOT graph (even if not part of transition)

Data Source

-L,  --live-check

Connect to CIB manager and use the current CIB contents as input

-x,  --xml-file=FILE

Retrieve XML from the named file

-p,  --xml-pipe

Retrieve XML from stdin

Application Options

-$,  --version

Display software version and exit

-V,  --verbose

Increase debug output (may be specified multiple times)

-Q,  --quiet

Display only essential output

Operation Specification

The OPSPEC in any command line option is of the form ${resource}_${task}_${interval_in_ms}@${node}=${rc} (, for example). ${rc} is an OCF return code.  For more information on these return codes, refer to


Pretend a recurring monitor action found memcached stopped on node and, during recovery, that the memcached stop action failed:

crm_simulate -LS --op-inject --op-fail --save-output /tmp/memcached-test.xml

Now see what the reaction to the stop failed would be:

crm_simulate -S --xml-file /tmp/memcached-test.xml


Written by Andrew Beekhof and the Pacemaker project contributors

Referenced By


January 2024 Pacemaker 2.1.7-4.fc40.2 System Administration Utilities