OCF_HEARTBEAT_ZABBIX(7)

📦
version 4.18.0 · 14 versions
, in fedora 43, fedora 44

💖 ocf_heartbeat_zabbixserver 💖

okay bestie, welcome to the OCF_HEARTBEAT_ZABBIX page, from the OCF resource agents manual collection. sit down, grab a strawberry 🍓, and let's get into it.

✨ NAME ✨

ocf_heartbeat_zabbixserver — the Zabbix server resource agent. that's the whole vibe. she monitors your Zabbix server, and she does it well. 👑

🌈 SYNOPSIS 🌈

zabbixserver [start | stop | monitor | meta-data | validate-all]

look at her. five little actions. so simple. so iconic. 💅

🦋 DESCRIPTION 🦋

so this right here is a Zabbix server Resource Agent — made for the zabbix_server monitoring daemon. like, she's the cluster's bestie whose entire job is keeping an eye on that daemon so your cluster knows what's up.

want the full lore? go look: http://www.zabbix.com/ — no cap, it's all there. 🌐

🎀 SUPPORTED PARAMETERS 🎀

these are the lil knobs you can turn. every single one matters, so pay attention bestie, not me skipping any of them. 🙈

  • binary — where the zabbix_server binary actually lives on your system. tell the agent where to find her.
    • (optional, string, default "zabbix_server")
  • pid — the path to the zabbix_server pidfile. and listen, this one's important: because the daemon creates that file itself, this path must match whatever you put in the Zabbix config file as PidFile=. like, they have to be the same string. periodt. 🚨
    • (unique, optional, string, default "/var/run/zabbix-server/zabbix_server.pid")
  • config — the path to the zabbix_server configuration file. if you don't specify it, it just assumes the server default. very chill of her. 🧘
    • (unique, optional, string, no default)

💫 SUPPORTED ACTIONS 💫

this resource agent supports the following actions (aka operations). one bullet each, because we respect the list:

  • start — starts the resource. suggested minimum timeout: 20s. get her up and running, slay. ✨
  • stop — stops the resource. suggested minimum timeout: 20s. sometimes you gotta let her rest. 😴
  • monitor — does a detailed status check. suggested minimum timeout: 20s. suggested interval: 10s. she's nosy and we love that. 🔍
  • validate-all — validates the resource configuration. suggested minimum timeout: 20s. making sure everything's giving what it's supposed to give. ✅
  • meta-data — retrieves resource agent metadata (internal use only, bestie, don't touch). suggested minimum timeout: 5s. 🫣

🌸 EXAMPLE CRM SHELL 🌸

here's what a zabbixserver resource looks like configured with the crm(8) shell. copy it exactly, don't freestyle:

primitive p_zabbixserver ocf:heartbeat:zabbixserver \
  op monitor timeout="20s" interval="10s" depth="0"

see? clean. elegant. ate. 💅

🧚 EXAMPLE PCS 🧚

and here's the same energy but with pcs(8):

pcs resource create p_zabbixserver ocf:heartbeat:zabbixserver \
  op monitor timeout="20s" interval="10s" OCF_CHECK_LEVEL="0"

notice the OCF_CHECK_LEVEL="0" in there — that's the pcs way of doing it. don't mix them up, iykyk. 🫶

👑 SEE ALSO 👑

💜 AUTHOR 💜

ClusterLabs contributors — see the resource agent source for information about individual authors. (they're the ones who built this, show some respect fr fr 🙏)

and that's the whole page, bestie!! you understood it, you're basically a cluster admin now, main character energy only. 💖

this was resource-agents version UNKNOWN, dated 04/08/2026, and it's the OCF_HEARTBEAT_ZABBIX(7) page — love that for us. byeee 🦋✨

📦 where this page comes from