PACEMAKER(8)
π PACEMAKER β the cluster resource manager's chaotic little sibling
okay so real talk, bestie, this whole page is about PACEMAKER(8), one beautiful piece of the Pacemaker cluster resource manager situation. Buckle up π
β¨ NAME β¨
Pacemaker β literally a whole part of the Pacemaker cluster resource manager, no cap π
πΈ SYNOPSIS πΈ
cibadmin [<command>] [options]
π¦ DESCRIPTION π¦
bestie. it queries. it edits. it's giving "the Pacemaker configuration is my personal playground" energy. that's the whole vibe check β¨
π OPTIONS π
π Help Options:
these are the "help me help you" girlies π«Ά
-h,--helpβ shows the help options, obviously πββοΈ--help-allβ shows all the help options, the full buffet--help-outputβ shows the output help--help-commandsβ shows the command help--help-dataβ shows the data help--help-additionalβ shows the additional options help
π Output Options:
where the results go, and what they look like π«
--output-as=FORMATβ pick your output format, eithertext(that's the default, iconique) orxml--output-to=DESTβ name the file the output goes to (or pass-to yeet it to stdout)
π Commands:
the main character energy section, ngl π₯
-u,--upgradeβ upgrades the configuration to the latest syntax, glow-up era β¨-Q,--queryβ queries the contents of the CIB-E,--eraseβ erases the contents of the whole CIB π like all of it, gone-B,--bumpβ increases the CIB's epoch value by1-C,--createβ creates an object in the CIB (it will fail if the object already exists, rude but fair π)-M,--modifyβ finds an object somewhere in the CIB's XML tree and updates it (fails if the object doesn't exist, unless-cis also specified)-P,--patchβ supplies an update in the form of an XML diff (peepcrm_diff(8))-R,--replaceβ recursively replaces an object in the CIB-D,--deleteβ deletes the first object matching your criteria (for example,<op id="rsc1_op1" name="monitor"/>). the XML element name and all attributes must match for the element to actually get deleted, no half-matches allowed π ββοΈ-d,--delete-allβ when used with--xpath, removes all matching objects in the configuration instead of just the first one. it's giving "no survivors" π-a,--empty=[schema]β outputs an empty CIB. accepts an optional schema name argument to use as thevalidate-withvalue. if no schema is given, the latest one gets used π§-5,--md5-sumβ calculates the on-disk CIB digest-6,--md5-sum-versionedβ calculates the on-the-wire versioned CIB digest
π Data:
where your XML comes from, bestie π₯
-x,--xml-file=FILEβ retrieves XML from the named file. currently this takes precedence over--xml-textand--xml-pipe. in a future release, the last one specified will be used. keeping it real about the roadmap π«Ά-X,--xml-text=STRINGβ retrieves XML from the supplied string. currently this takes precedence over--xml-pipe, but--xml-fileoverrides this. in a future release, the last one specified will be used.-p,--xml-pipeβ retrieves XML from stdin. currently--xml-fileand--xml-textoverride this. in a future release, the last one specified will be used.
π Additional Options:
the extra-flavor section, iykyk π
-f,--forceβ forces the action to be performed. do it. don't ask. π€-t,--timeout=valueβ time (in seconds) to wait before declaring the operation failed β³-U,--user=valueβ runs the command with the permissions of the named user (valid only for therootandhaclusteraccounts, so don't get cute)-o,--scope=valueβ limits the scope of the operation to a specific section of the CIB. valid values:configuration,nodes,resources,constraints,crm_config,rsc_defaults,op_defaults,acls,fencing-topology,tags,alerts,status. if both--scope/-oand--xpath/-aare specified, the last one to appear takes effect π-A,--xpath=valueβ a valid XPath to use instead of--scope/-o. if both--scope/-oand--xpath/-aare specified, the last one to appear takes effect-S,--show-access=[value]β whether to use syntax highlighting for ACLs (with-Q/--queryand-U/--user). allowed values:'color'(the default for a terminal),'text'(plain text, the default for a non-terminal),'namespace', or'auto'(use the default value). default value:'auto'π¨--scoreβ treats new attribute values as atomic score updates where possible (with--modify/-M). this currently happens by default and cannot be disabled, but this default behavior is deprecated and will be removed in a future release. set this flag if this behavior is desired. this option takes effect when updating XML attributes. for an attribute named"name", if the new value is"name++"or"name+=X"for some scoreX, the new value is set as follows: if attribute"name"is not already set to some value in the element being updated, the new value is set as a literal string. if the new value is"name++", then the attribute is set to its existing value (parsed as a score) plus1. if the new value is"name+=X"for some scoreX, then the attribute is set to its existing value plusX, where the existing value andXare parsed and added as scores. scores are integer values capped atINFINITYand-INFINITY. refer to Pacemaker Explained for more details on scores, including how they are parsed and added π-c,--allow-createβ (Advanced) allows the target of--modify/-Mto be created if it does not exist π£-n,--no-childrenβ (Advanced) when querying an object, does not include its children in the result--update-statusβ (Advanced) applies the CIB update without triggering a controller refresh
β Application Options:
-$,--versionβ displays the software version and exits, and then dips βοΈ-V,--verboseβ increases debug output (may be specified multiple times, go off queen)
π₯ EXAMPLES π₯
query the configuration:
# cibadmin --query
or just:
# cibadmin
query just the cluster options configuration:
# cibadmin --query --scope crm_config
query all 'target-role' settings:
# cibadmin --query --xpath "//nvpair[@name='target-role']"
remove all 'is-managed' settings:
# cibadmin --delete-all --xpath "//nvpair[@name='is-managed']"
remove the resource named 'old':
# cibadmin --delete --xml-text '<primitive id="old"/>'
remove all resources from the configuration:
# cibadmin --replace --scope resources --xml-text '<resources/>'
replace the complete configuration with the contents of $HOME/pacemaker.xml:
# cibadmin --replace --xml-file $HOME/pacemaker.xml
replace the constraints section of the configuration with the contents of $HOME/constraints.xml:
# cibadmin --replace --scope constraints --xml-file $HOME/constraints.xml
increase the configuration version so old configurations can't get loaded by accident:
# cibadmin --modify --score --xml-text '<cib admin_epoch="admin_epoch++"/>'
edit the configuration with your favorite $EDITOR:
# cibadmin --query > $HOME/local.xml
# $EDITOR $HOME/local.xml
# cibadmin --replace --xml-file $HOME/local.xml
assuming a terminal, render the configuration in color (green for writable, blue for readable, red for denied) so you can visualize permissions for user tony:
# cibadmin --show-access=color --query --user tony | less -r
π SEE ALSO: π
crm(8), pcs(8), crm_shadow(8), crm_diff(8) β go read those too, bestie, they're part of the lore π¦
π AUTHOR π
Written by Andrew Beekhof and the Pacemaker project contributors π«Ά
that's a wrap, gorgeous π this page came from Pacemaker 3.0.3+20260728.7052..., dated September 2026, and it's filed under PACEMAKER(8) β slay, go forth and cluster πβ¨
π¦ where this page comes from
- opensuse-leap 16.0: pacemaker-cli 3.0.3+20260728.7052efa194-160000.1.1 Β· GPL-2.0-only AND GPL-2.0-or-later AND LGPL-2.1-or-later
- opensuse-leap 16.0: pacemaker-cli 3.0.3+20260728.7052efa194-160000.1.1 Β· GPL-2.0-only AND GPL-2.0-or-later AND LGPL-2.1-or-later
- opensuse-leap 16.0: pacemaker-cli 3.0.3+20260728.7052efa194-160000.1.1 Β· GPL-2.0-only AND GPL-2.0-or-later AND LGPL-2.1-or-later
- opensuse-leap 16.0: pacemaker-cli 3.0.3+20260728.7052efa194-160000.1.1 Β· GPL-2.0-only AND GPL-2.0-or-later AND LGPL-2.1-or-later
- π girlified by deepseek-ai/DeepSeek-V4.1-Flash-1017 on : a language model's rewrite of the original, under its terms