COROSYNC-QNETD-TOOL(8)

💖 corosync-qnetd-tool(8) — the System Manager's Manual glow-up 💖

okay bestie, sit DOWN, because this is corosync-qnetd-tool, a System Manager's Manual page, and it's lowkey the little backstage pass to your whole corosync-qnetd situation. 🎀

---

✨ NAME ✨

corosync-qnetd-tool — the corosync-qnetd control interface, aka your direct line to the daemon. 💅

---

✨ SYNOPSIS ✨

corosync-qnetd-tool [-Hhlsv] [-c cluster_name] [-p qnetd_ipc_socket_path]

---

✨ DESCRIPTION ✨

So like, corosync-qnetd-tool is a frontend to the internal corosync-qnetd IPC. 🫶

Its main purpose — its whole main character moment, honestly — is to show you important information about the current internal state of corosync-qnetd. That's it. That's the job. And it ate. 🔥

---

✨ OPTIONS ✨

• -H — Properly shutdown the corosync-qnetd process. Like, a proper goodbye. No ghosting. 👋
• -h — Display a short usage text. The "help me help you" option. 🙈
• -l — List all clients connected to the corosync-qnetd process. The output is described in its own section below, so keep scrolling bestie. 👀
• -s — Display status of the corosync-qnetd process. The vibe check, basically. 💫
• -v — Display more verbose output for options -l and -s. Give me more, give me details, give me everything. 🗣️
• -c — Used only with the -l option. By default, information about all clients from all clusters is displayed, but with this option it's possible to filter information from a single cluster given the cluster_name. Not me narrowing it down to one cluster. 💅
• -p — Path to the corosync-qnetd communication socket.

---

🌈 LIST COMMAND OUTPUT 🌈

Cluster "Cluster":
    Algorithm:          Fifty-Fifty split (KAP Tie-breaker)
    Tie-breaker:        Node with lowest node ID
    Node ID 1:
        Client address:         ::ffff:127.0.0.1:52000
        HB interval:            8000ms
        Configured node list:   1, 2
        Ring ID:                1.a00000000021b40
        Membership node list:   1, 2
        TLS active:             Yes (client certificate verified)
        Vote:                   No change (ACK)
 ...

okay so here's the tea on what you're looking at, because this output is giving receipts: 🧾

The output contains a list of clusters. Each cluster has the cluster common options Algorithm (optionally with Keep Active Partition Tie Breaker information) and Tie-breaker, as configured in the corosync.conf file. 🎀

Information about nodes follows. Let's break it down, one by one:

• Client address is the IP address and port of the client.
• HB interval is the heartbeat interval between corosync-qnetd and the corosync-qdevice client. This interval depends on the timeout option that can be set in the corosync.conf file.
• Configured node list is the list of nodes configured in corosync.conf.
• Ring ID and Membership node list are self-explanatory. (They said "iykyk" and honestly, fair. 😌)
• TLS active describes if an encrypted transport is used between server and client.
• Vote is the last vote sent to the corosync-qdevice client. The last ACK/NACK vote (if it exists) is in parentheses.

no cap, every single one of those fields is doing important work. don't skip them. 🫶

---

👑 SEE ALSO 👑

• corosync-qnetd(8)
• corosync-qdevice(8)

---

🦋 AUTHOR 🦋

Jan Friesse — the icon, the legend, the moment. ⭐

---

and that's the whole page bestie!! this was the corosync-qnetd-tool(8) page from 2025-04-09, living under the COROSYNC-QNETD-TOOL(8) banner — go forth, run it, and slay your cluster diagnostics. periodt. 💜✨