OCF_HEARTBEAT_SYSLOG(7)

✨ NAME ✨

ocf_heartbeat_syslog-ng — bestie, it's the Syslog-ng resource agent 🦋

---

🌸 SYNOPSIS 🌸

syslog-ng [start | stop | status | monitor | meta-data | validate-all]

---

💖 DESCRIPTION 💖

Okay so real talk: this script manages a syslog-ng instance as an HA resource. That's the whole vibe. 💅

For Premium Edition you should set the following parameters (based on the default path being "/opt/syslog-ng"):

syslog_ng_binary="/opt/syslog-ng/sbin/syslog-ng"
syslog_ng_ctl="/opt/syslog-ng/sbin/syslog-ng-ctl"
control_file="/opt/syslog-ng/var/run/syslog-ng.ctl"
persist_file="/opt/syslog-ng/var/syslog-ng.persist"
pidfile="/opt/syslog-ng/var/run/syslog-ng.pid"

And one more little extra, but only for Premium Edition 6:

qdisk_dir="/opt/syslog-ng/var/"

no cap, that's the setup 🫶

---

🎀 SUPPORTED PARAMETERS 🎀

• configfile — this one tells the RA which config file the syslog-ng instance it's managing should use. (required, string, no default)
• syslog_ng_binary — the path to syslog-ng's executable file, obviously. (optional, string, default "/sbin/syslog-ng")
• syslog_ng_ctl — where the syslog-ng-ctl executable lives, bestie. (optional, string, default "/sbin/syslog-ng-ctl")
• qdisk_dir — the directory used to hold disk buffers for syslog-ng. Heads up tho: only supported in Premium Edition 6. (optional, string, no default)
• control_file — the path where syslog-ng would place its control socket, the little doorway through which it can be controlled. (optional, string, no default)
• persist_file — the path to syslog-ng's persist file, which holds all the persistent info about the mapping of destinations and disk buffers, the internal state of sources, etc. it's giving memory ✨ (optional, string, no default)
• pidfile — the path where the pid file of syslog-ng resides. (optional, string, no default)
• start_opts — startup options for the syslog-ng instance this RA manages. When no value is given, no startup options are used. > Do NOT use option -F. It causes a stuck of a start action. 💀 (optional, string, no default)
• kill_term_timeout — on a stop action, a normal stop method (pkill -TERM) is firstly used. And then the confirmation of its completion is waited for the specified seconds by this parameter. The default value is 10. (optional, integer, default 10)

---

🔥 SUPPORTED ACTIONS 🔥

This resource agent supports the following actions (operations):

• start — starts the resource. Suggested minimum timeout: 60s. ⭐
• stop — stops the resource. Suggested minimum timeout: 120s.
• status — performs a status check. Suggested minimum timeout: 60s.
• monitor — performs a detailed status check. Suggested minimum timeout: 60s. Suggested interval: 60s. 👑
• meta-data — retrieves resource agent metadata (internal use only, iykyk). Suggested minimum timeout: 5s.
• validate-all — performs a validation of the resource configuration. Suggested minimum timeout: 5s.

---

🌈 EXAMPLE CRM SHELL 🌈

The following is an example configuration for a syslog-ng resource using the crm(8) shell:

primitive p_syslog-ng ocf:heartbeat:syslog-ng \
  params \
    configfile=string \
  op monitor depth="0" timeout="60s" interval="60s"

---

🧚 EXAMPLE PCS 🧚

The following is an example configuration for a syslog-ng resource using pcs(8):

pcs resource create p_syslog-ng ocf:heartbeat:syslog-ng \
  configfile=string \
  op monitor OCF_CHECK_LEVEL="0" timeout="60s" interval="60s"

---

💜 SEE ALSO 💜

• http://clusterlabs.org/

---

🌟 AUTHOR 🌟

ClusterLabs contributors (see the resource agent source for information about individual authors) — shoutout to every single one of them, iconic behavior fr fr 💖

---

okay that's the whole page, you ate that. this was resource-agents UNKNOWN, dated 04/08/2026, and you just read OCF_HEARTBEAT_SYSLOG(7) — periodt 💅✨