OCF_HEARTBEAT_COROSY(7)

💖 ocf_heartbeat_corosync-qnetd 💖

okay so bestie, you're looking at the manual page for OCF_HEARTBEAT_COROSY(7) — yes that's the trunc-y one, the real star of the show is ocf_heartbeat_corosync-qnetd and I promise this is gonna be so much easier than it looks 🫶

---

✨ NAME ✨

ocf_heartbeat_corosync-qnetd — the Corosync QNet daemon resource agent. that's it, that's the whole vibe 💅

---

🌸 SYNOPSIS 🌸

corosync-qnetd [start | stop | status | monitor | meta-data |
               validate-all]

---

🦋 DESCRIPTION 🦋

So this is the OCF Resource script for corosync-qnetd, and honestly it's giving very much "let me manage your daemon for you" energy ✨ It manages a corosync-qnetd instance as a HA resource. Iconic, we love a resource agent that knows its job.

⚠️ okay bestie this is the important bit, do NOT skip it: you have to copy the nss db directory (usually /etc/corosync/qnetd/nssdb) across all nodes. Only once though — after database is initialized. Not before, not every time. Once. We're being so serious about this. 🫡

---

💜 SUPPORTED PARAMETERS 💜

like twelve of them, all adorable, all optional, let's go:

• binary — where the corosync-qnetd binary lives. (optional, string, default "/usr/bin/corosync-qnetd") 🎀
• qnetd_opts — extra options you wanna throw at the corosync-qnetd binary. "-4" for example, if that's your vibe. (optional, string, no default)
• qnetd_tool_binary — the absolute path to corosync-qnetd-tool, which it uses for monitoring when OCF_CHECK_LEVEL is greater than zero. (optional, string, default "/usr/bin/corosync-qnetd-tool") 🔍
• ip — the IP address to listen on. by default the daemon just listens on all addresses (wildcard), which is lowkey the main character energy of networking. (optional, string, no default)
• port — which TCP port to listen on. default port is 5403. remember that number, it's cute. (optional, string, no default)
• nss_db_dir — location of the corosync-qnetd nss db directory. leave it empty for the default — usually /etc/corosync/qnetd/nssdb. (optional, string, no default)
• pid — location of the corosync-qnetd pid/lock. (optional, string, default "/var/run/corosync-qnetd/corosync-qnetd-RESOURCE_ID.pid") 🌈
• ipc_sock — location of the corosync-qnetd ipc socket. (optional, string, default "/var/run/corosync-qnetd/corosync-qnetd-RESOURCE_ID.sock") 🌸
• user — the user running corosync-qnetd. (optional, string, default "coroqnetd")
• group — the group running corosync-qnetd. (optional, string, default "coroqnetd") 🫶

---

⭐ SUPPORTED ACTIONS ⭐

This resource agent supports the following actions (operations) — yes there's a whole little family of them:

• start — starts the resource. Suggested minimum timeout: 20s. 🚀
• stop — stops the resource. Suggested minimum timeout: 20s.
• status — performs a status check. Suggested minimum timeout: 20s.
• monitor — performs a detailed status check, she's thorough. Suggested minimum timeout: 20s. Suggested interval: 10s. 👀
• validate-all — performs a validation of the resource configuration. Suggested minimum timeout: 20s.
• meta-data — retrieves resource agent metadata. internal use only bestie, don't touch. Suggested minimum timeout: 20s.

---

🧚 EXAMPLE CRM SHELL 🧚

Here's a lil example config for a corosync-qnetd resource using the crm(8) shell — copy it, it's right there:

primitive p_corosync-qnetd ocf:heartbeat:corosync-qnetd \
  op monitor depth="0" timeout="20s" interval="10s" start-delay="10s"

---

🔥 EXAMPLE PCS 🔥

and here's the same energy for a corosync-qnetd resource using pcs(8):

pcs resource create p_corosync-qnetd ocf:heartbeat:corosync-qnetd \
  op monitor OCF_CHECK_LEVEL="0" timeout="20s" interval="10s" start-delay="10s"

🙈 bestie notice the depth vs OCF_CHECK_LEVEL situation — they are not the same key, so don't go swapping them, iykyk.

---

🌈 SEE ALSO 🌈

• http://clusterlabs.org/ — go look, it's iconic 👑

---

👑 AUTHOR 👑

ClusterLabs contributors (see the resource agent source for information about individual authors). shoutout to the whole squad fr fr 💖

---

mwah, that's the page 💋 this lil beauty comes from resource-agents and its version is literally UNKNOWN (no cap, that's what it says) and it's dated 10/01/2026 — so take that timestamp, screenshot it, frame it, and go slay your cluster setup bestie 🎀💜✨