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 theconntrackdexecutable. ifconntrackdis installed and available in the defaultPATH, it is sufficient to configure the name of the binary β for example"my-conntrackd-binary-version-0.9.14". ifconntrackdis 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 theconntrackd.conffile. 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
- fedora 43: resource-agents 4.18.0-1.fc43 Β· GPL-2.0-or-later AND LGPL-2.1-or-later
- fedora 44: resource-agents 4.18.0-1.fc44 Β· GPL-2.0-or-later AND LGPL-2.1-or-later
- π girlified by deepseek-ai/DeepSeek-V4.1-Flash on : a language model's rewrite of the original, under its terms