PACEMAKER(8)

💅 PACEMAKER (section 8) — the vibe check era of cluster config

okay bestie so first things first: this page is about Pacemaker, which is part of the Pacemaker cluster resource manager. the actual star of the show here is the command crm_verify — that's the one you're gonna run. section 8 of the manual, system administration utilities territory, we love to see it 🫶

---

✨ NAME ✨

Pacemaker — it's literally part of the Pacemaker cluster resource manager. that's the whole name entry. iconic, brief, no notes 💅

---

✨ SYNOPSIS ✨

crm_verify [<options>]

---

🦋 DESCRIPTION 🦋

so what does it do? it checks a Pacemaker configuration for errors. yep, that's the job. 🎀

it checks the well-formedness of a complete Pacemaker XML configuration, checks that it conforms to the configured schema, and checks for the presence of common misconfigurations. three vibe checks in one, honestly.

here's the serious part though, no cap: problems that get reported as errors must be fixed before the cluster will work properly. like, actually must. and whether you fix the stuff reported as warnings? that's left to the administrator to decide. your call, bestie 🌸

---

✨ OPTIONS ✨

🎀 Help Options:

• -h, --help — show help options. the classic cry for help, but make it documentation.
• --help-all — show all help options. the whole buffet 🍓
• --help-output — show output help. help, but specifically about output.
• --help-data — show data options. help for the data side of things.
• --help-additional — show additional options. help for the extra bits.

🌈 Output Options:

• --output-as=FORMAT — specify the output format as one of: text (the default, naturally) or xml. pick your fighter.
• --output-to=DEST — specify the file name for output (or use - for stdout). old-school dash means "just put it on my screen" 💖

🧚 Data sources:

• -L, --live-check — check the configuration used by the running cluster. the real one, live, no rehearsal 👑
• -x, --xml-file=FILE — check the configuration in the named file. point at a file, she'll read it.
• -p, --xml-pipe — check the configuration piped in via stdin. for the pipe girlies 💜
• -X, --xml-text=XML — check the configuration in the supplied string. XML right there in the argument, handheld mode.

⭐ Additional options:

• -S, --save-xml=FILE — save verified XML to the named file (most useful with -L). like a little souvenir of your verified config 🎀

🔥 Application Options:

• -$, --version — display software version and exit. yes the flag is literally a dollar sign, we stan a rich icon 💅
• -V, --verbose — increase debug output, and you may specify it multiple times. more -V, more words. go off.
• -q, --quiet — don't print verify information. silence is golden, shhh 🙈

---

💀 EXAMPLES 💀

check the consistency of the configuration in the running cluster:

crm_verify --live-check

check the consistency of the configuration in a given file and produce quiet output:

crm_verify --xml-file file.xml --quiet

check the consistency of the configuration in a given file and produce verbose output:

crm_verify --xml-file file.xml --verbose

three examples, all consistency checks, all slaying in their own way ✨

---

🫶 AUTHOR 🫶

written by Andrew Beekhof and the Pacemaker project contributors. we love a collaborative king 👑

---

and that's the whole page, bestie!! before you go — the footer tea ☕: this is Pacemaker 3.0.3+20260728.7052..., dated September 2026, from the Pacemaker 3.0.3+20260728.7052... release. okay now go fix those errors, fr fr 🔥🌷