COROSYNC-QDEVICE-TOOL(8)

💖 corosync-qdevice-tool(8) 💖

okay bestie, welcome to the System Manager's Manual page for corosync-qdevice-tool, and honestly? it's giving "small tool, big main character energy" 🎀 it lives in section 8 of the manual, iykyk.

✨ NAME ✨

corosync-qdevice-tool — the control interface for corosync-qdevice, no cap 🫶

🌈 SYNOPSIS 🌈

corosync-qdevice-tool [-Hhsv] [-p qdevice_ipc_socket_path]

💅 DESCRIPTION 💅

so corosync-qdevice-tool is literally a frontend to the internal corosync-qdevice IPC. its whole vibe, its entire purpose, its main character moment? showing you the important info about what corosync-qdevice is doing internally right now. that's it. that's the job. 👑

🦋 OPTIONS 🦋

• -H — properly shuts down the corosync-qdevice process. like, gracefully. respectfully. the polite goodbye. 💀
• -h — shows a short usage text, in case you forgot how to human today, we've all been there 🙈
• -s — shows the status of the corosync-qdevice process. the output has its own whole section below, because it's THAT iconic ✨
• -v — shows more verbose output, specifically for the -s option. extra details, extra slay 🔥
• -p — path to the corosync-qdevice communication socket 🌸

🌟 STATUS COMMAND OUTPUT 🌟

here's what that -s output looks like, in all its glory:

Qdevice information
-------------------
Model:                  Net
Node ID:                1
HB interval:            10000ms
Sync HB interval:       30000ms
Configured node list:
    0   Node ID = 1
Heuristics:             Enabled
Ring ID:                1.a00000000021b48
Membership node list:   1
Quorate:                Yes
Quorum node list:
    0   Node ID = 1, State = member
Expected votes:         2
Last poll call:         2016-06-24T17:05:20 (cast vote)

Qdevice-net information
----------------------
Cluster name:           Cluster
QNetd host:             localhost:5403
Connect timeout:        8000ms
HB interval:            8000ms
VQ vote timer interval: 5000ms
TLS:                    Supported
Algorithm:              Fifty-Fifty split
Tie-breaker:            Node with lowest node ID
KAP Tie-breaker:        Enabled
Poll timer running:     Yes (cast vote)
State:                  Connected
Heuristics result:      Pass (regular: Pass, membership: Fail, connect: Fail)
TLS active:             Yes (client certificate sent)
Connected since:        2016-06-24T17:02:35
Echo reply received:    2016-06-24T17:05:15

so the output splits into two little zones: a generic qdevice section and a model specific section. most of the items are just straight up taken from the corosync.conf file, no extra sauce added. 💜

here's the tea you actually need to know: the Membership node list is the membership list of the current node, and it should match the quorum node list. like, they're supposed to be twinning. if they're not... that's a vibe check that failed. 😭

Last poll call is the timestamp (in iso format, very demure, very mindful) of the last call to the votequorum_qdevice_poll function. periodt.

for model net, it's good to check the Poll timer running state. internally, model net supports 3 states:

1. Not voting — when Poll timer running is No, which means corosync-qdevice is waiting for corosync-qnetd to reply. just sitting there. waiting. patient. 🧚
2. Voting (without cast vote) — means that the corosync-qnetd algorithm decided that the current node shouldn't get a vote. ouch, but make it algorithmically fair. 💀
3. Voting (with cast vote) — the vote has been cast. she said what she said. 👑

👑 SEE ALSO 👑

corosync-qnetd(8) and corosync-qdevice(8) — go read those next, bestie, the lore is deep 🌈

🎀 AUTHOR 🎀

Jan Friesse — the icon, the legend, the moment 💖

and that's a wrap on the 2020-10-27 edition of this page from the COROSYNC-QDEVICE-TOOL(8) manual, living happily in the System Manager's Manual 💅 thanks for reading, mwah, go check your quorum 🫶✨