COROSYNC-QUORUMTOOL(8)
β¨ COROSYNC-QUORUMTOOL β¨
okay bestie, so this is corosync-quorumtool, and it lives in section 8 of the System Manager's Manual. yes, section 8, the system manager section, we're in our admin era π
πΈ NAME πΈ
corosync-quorumtool β Set and display quorum settings. that's it, that's the whole vibe π
π¦ SYNOPSIS π¦
corosync-quorumtool [-s] [-m] [-l] [-p] [-v votes] [-n nodeid] [-e
expected] [-H] [-i] [-o <a|n|i>] [-a] [-f] [-h] [-V]
π DESCRIPTION π
She shows you the current state of quorum in the cluster, and she can also set vote quorum options. that's the whole job, and she does it beautifully. π
π OPTIONS π
-sβ show quorum status. the classic, the icon, the main character π-mβ constantly monitor quorum status. like she never stops watching. obsessed fr fr π-lβ list nodes. roll call!! π-pβ when used with-sor-l, generates machine parsable output. for when you want your computer bestie to read it instead of your eyeballs π€-v <votes>β change the number of votes for a node *-n <nodeid>β optional nodeid of node for-v-e <expected>β change expected votes for the cluster *-Hβ show nodeids in hexadecimal rather than decimal. hex girlies rise π§-iβ show node IP addresses instead of the resolved name-pβ when used with-sor-l, generates machine parsable output-o <a|n|i>β Orders the output of the nodes list. By default or with-oanodes are listed in IP address order: as they come from corosync.-onwill order the nodes based on their name, and-oiwill order them based on their node ID. pick your sort, pick your destiny β¨-aβ Show the name or IP address (see-iabove) of all interfaces in use on the nodes, rather than just the first one. not just the first one, we want the WHOLE roster π«Ά-fβ forcefully unregister a quorum device *DANGEROUS* *-h(if no other argument) β show this help text-Vβ show version and exit
β Starred items only work ifvotequorumis the quorum provider forcorosync. no votequorum, no star magic. iykyk π
π₯ EXIT STATUS π₯
corosync-quorumtool may return one of several error codes if it encounters problems. she's dramatic like that.
0β No problems occurred (quorate for-soperation). slay, everything's fine π1β Generic error code. the vague one, the "something happened" of it all π2β Not quorate (returned only for-soperation). oh no bestie, the cluster is NOT okay π¨
π SEE ALSO π
corosync_overview(7), votequorum_overview(3),
π AUTHOR π
Angus Salkeld
and that's the whole page, bestie!! this one dropped on 2019-02-14 (valentine's day, because she loves you) and it's from the COROSYNC-QUORUMTOOL(8) manual, section 8, system manager's manual. go forth and be quorate π«Άβ¨
π¦ where this page comes from
- debian bookworm: corosync 3.1.7-1+deb12u2 Β· BSD-3-Clause
- debian trixie: corosync 3.1.9-2+deb13u1 Β· BSD-3-Clause
- epel 9: corosync 3.1.10-0.2.el9.1 Β· BSD-3-Clause
- fedora 43: corosync 3.1.10-3.fc43 Β· BSD-3-Clause
- fedora 43: corosync 3.1.9-5.fc43 Β· BSD-3-Clause
- fedora 44: corosync 3.1.10-4.fc44 Β· BSD-3-Clause
- fedora 44: corosync 3.1.10-6.fc44 Β· BSD-3-Clause
- nixos 26.05: corosync 3.1.9
- nixpkgs unstable: corosync 3.1.9
- opensuse-leap 16.0: corosync 3.1.9-160000.4.1 Β· BSD-3-Clause
- opensuse-leap 16.0: corosync 3.1.9-160000.4.1 Β· BSD-3-Clause
- opensuse-leap 16.0: corosync 3.1.9-160000.4.1 Β· BSD-3-Clause
- opensuse-leap 16.0: corosync 3.1.9-160000.4.1 Β· BSD-3-Clause
- ubuntu jammy: corosync 3.1.6-1ubuntu1 Β· BSD-3-Clause
- ubuntu jammy: corosync 3.1.6-1ubuntu1.2 Β· BSD-3-Clause
- ubuntu noble: corosync 3.1.7-1ubuntu3 Β· BSD-3-Clause
- ubuntu noble: corosync 3.1.7-1ubuntu3.2 Β· BSD-3-Clause
- ubuntu questing: corosync 3.1.9-2ubuntu1
- ubuntu questing: corosync 3.1.9-2ubuntu1.1
- ubuntu resolute: corosync 3.1.9-2ubuntu3 Β· BSD-3-Clause
- ubuntu stonking: corosync 3.1.10-3ubuntu1 Β· BSD-3-Clause
- Copyright (C) 2010,2014 Red Hat, Inc
- π girlified by deepseek-ai/DeepSeek-V4.1-Flash on : a language model's rewrite of the original, under its terms