OCF_HEARTBEAT_RSYSLO(7)
β¨ ocf_heartbeat_rsyslog β¨
okay bestie, so this is the manual page for OCF_HEARTBEAT_RSYSLO(7) β the rsyslog resource agent π it lives in section 7 of the manual, and it's genuinely one of the cutest little RAs out there, no cap.
π NAME π
ocf_heartbeat_rsyslog β the rsyslog resource agent. that's it, that's the whole vibe π¦
πΈ SYNOPSIS πΈ
rsyslog [start | stop | status | monitor | meta-data | validate-all]
like. it takes one of those six actions and that's the whole interface. simple. iconic. periodt π
π« DESCRIPTION π«
This script manages a rsyslog instance as an HA resource.
fr fr, that's the whole thing β you hand it a rsyslog, it keeps that rsyslog alive and behaving inside your cluster. main character energy for a logging daemon π«Ά
β¨ SUPPORTED PARAMETERS β¨
okay so these are the knobs you can turn. read them carefully, they matter π
configfileβ this one specifies a configuration file for a rsyslog instance managed by this RA. it's unique, required, a string, and it has no default β so like, you genuinely have to give it one. no skipping, bestie πrsyslog_binaryβ this one specifies rsyslog's executable file. it's optional, a string, and it defaults to/sbin/rsyslogdπstart_optsβ this one specifies startup options for a rsyslog instance managed by this RA. when no value is given, no startup options is used. Don't use option-F. it causes a stuck of a start action. like literally do not. it will ruin your whole afternoon π
the way that -F is right there and you just have to not use it. iykyk π
π SUPPORTED ACTIONS π
this resource agent supports the following actions (operations):
startβ starts the resource. suggested minimum timeout:20sβstopβ stops the resource. suggested minimum timeout:60sπstatusβ performs a status check. suggested minimum timeout:20sπmonitorβ performs a detailed status check. suggested minimum timeout:20s, suggested interval:20sπ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:5sβ
π§ EXAMPLE CRM SHELL π§
the following is an example configuration for a rsyslog resource using the crm(8) shell:
primitive p_rsyslog ocf:heartbeat:rsyslog \
params \
configfile=string \
op monitor depth="0" timeout="20s" interval="20s"
look at her. depth="0". she's perfect π
π¦ EXAMPLE PCS π¦
the following is an example configuration for a rsyslog resource using pcs(8):
pcs resource create p_rsyslog ocf:heartbeat:rsyslog \
configfile=string \
op monitor OCF_CHECK_LEVEL="0" timeout="20s" interval="20s"
same energy, different CLI. note that pcs says OCF_CHECK_LEVEL where crm says depth β that's just how they talk, don't stress it π
π SEE ALSO π
go. click. absorb the lore π
π AUTHOR π
ClusterLabs contributors (see the resource agent source for information about individual authors)
the whole squad contributed, we don't name names in the manpage, the source has the receipts π«Ά
this page came from resource-agents, version UNKNOWN, dated 04/08/2026 β and yes i know the version literally says UNKNOWN, we don't talk about it π slay tho πβ¨
π¦ 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