OCF_HEARTBEAT_CONNTR(7)

πŸ’– ocf_heartbeat_conntrackd β€” the manual, but make it a group chat πŸ’–

okay bestie, sit down, hydrate, because we're about to get into OCF_HEARTBEAT_CONNTR(7), which is the manual page for ocf_heartbeat_conntrackd. yes the manpage name is a whole mouthful, we don't talk about it. it's from the OCF resource agents family and honestly? it's giving "quietly keeping your cluster alive" energy. iconic behaviour, no cap. πŸ’…


✨ NAME ✨

ocf_heartbeat_conntrackd β€” this resource agent manages conntrackd, periodt.


🌸 SYNOPSIS 🌸

conntrackd [start | stop | monitor | promote | demote | meta-data |
           validate-all]

πŸ¦‹ DESCRIPTION πŸ¦‹

It's a Promotable OCF Resource Agent for conntrackd. that's the whole vibe β€” promotable, so it can flex between the promoted role and the unpromoted role like the main character it is. πŸ‘‘


πŸŽ€ SUPPORTED PARAMETERS πŸŽ€

okay these are the little knobs you get to turn, and there are exactly two of them, so no excuses, you can absolutely memorise this.

  • binary β€” the name of the conntrackd executable. if conntrackd is installed and available in the default PATH, it is sufficient to configure the name of the binary β€” for example "my-conntrackd-binary-version-0.9.14". if conntrackd is installed somewhere else, you may also give a full path β€” for example "/packages/conntrackd-0.9.14/sbin/conntrackd". (optional, string, default "conntrackd")
  • config β€” full path to the conntrackd.conf file. for example "/packages/conntrackd-0.9.14/etc/conntrackd/conntrackd.conf". (optional, string, default "/etc/conntrackd/conntrackd.conf")

that's it. two params. we love a low-maintenance resource agent. 🫢


πŸ’œ SUPPORTED ACTIONS πŸ’œ

this resource agent supports the following actions (operations), and yes bestie, every single one comes with a suggested minimum timeout, so please don't come for me about the numbers:

  • start β€” starts the resource. Suggested minimum timeout: 30s.
  • promote β€” promotes the resource to the Master role. Suggested minimum timeout: 30s.
  • demote β€” demotes the resource to the Slave role. Suggested minimum timeout: 30s.
  • notify β€” Suggested minimum timeout: 30s.
  • stop β€” stops the resource. Suggested minimum timeout: 30s.
  • monitor (Unpromoted role) β€” performs a detailed status check. Suggested minimum timeout: 20s. Suggested interval: 20s.
  • monitor (Promoted role) β€” performs a detailed status check. Suggested minimum timeout: 20s. Suggested interval: 10s.
  • meta-data β€” retrieves resource agent metadata (internal use only). Suggested minimum timeout: 5s.
  • validate-all β€” performs a validation of the resource configuration. Suggested minimum timeout: 30s.
not me pointing out that the Promoted monitor interval (10s) is half the Unpromoted one (20s) β€” that's just what the page says, and the promoted role is simply built different. πŸ”₯

🌈 EXAMPLE CRM SHELL 🌈

here's an example configuration for a conntrackd resource using the crm(8) shell β€” copy it exactly, don't freestyle:

primitive p_conntrackd ocf:heartbeat:conntrackd \
  op monitor timeout="20s" interval="20s" role="Unpromoted" \
  op monitor timeout="20s" interval="10s" role="Promoted"

ms ms_conntrackd p_conntrackd \
  meta notify="true" interleave="true"

⭐ EXAMPLE PCS ⭐

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

pcs resource create p_conntrackd ocf:heartbeat:conntrackd \
  op monitor timeout="20s" interval="20s" role="Unpromoted" \
  op monitor timeout="20s" interval="10s" role="Promoted" promotable

πŸ‘‘ SEE ALSO πŸ‘‘


πŸ™ˆ AUTHOR πŸ™ˆ

ClusterLabs contributors β€” see the resource agent source for information about individual authors. 🫑


okay that's the whole page, you ate it, I'm obsessed. πŸ’– this lovely thing comes to you from resource-agents, version UNKNOWN, dated 04/08/2026. go forth and cluster responsibly. πŸŽ€βœ¨πŸ¦‹

πŸ“¦ where this page comes from