COROSYNC-NOTIFYD(8)

💖 COROSYNC-NOTIFYD 💖

okay bestie, so this is a System Manager's Manual page, and it's for corosync-notifyd, which is a little icon that just... listens. like a nosy bestie but for your cluster. ✨

✨ NAME ✨

corosync-notifyd — Listen for important corosync events and send dbus and/or snmp traps.

like literally its whole job is eavesdropping on your cluster and then telling everybody. no cap. 🦋

🎀 SYNOPSIS 🎀

corosync-notifyd [-f] [-l] [-o] [-s] [-m manager] [-d] [-h]

that's the whole vibe check right there. flags go in, gossip comes out. 💅

🌸 DESCRIPTION 🌸

corosync-notifyd uses the corosync API to listen for important cluster events, and it can do three (3!) glow-up things with them:

• log them 📝
• generate dbus signals 📡
• generate snmp traps 🪤

pick your fave, or stack them, honestly it's your main character moment.

✨ OPTIONS ✨

• -f — Start application in foreground. (not me being a background gremlin by default 🙈)
• -l — Log all events.
• -o — Print events to stdout (and heads up, this turns on -l too, so it's a two-for-one 💖).
• -s — Send SNMP traps on all events.
• -m — Set the SNMP Manager IP address (defaults to localhost).
• -n — No reverse DNS lookup on cmap member change events. (yes skip the lookup, we're busy 💅)
• -d — Send DBUS signals on all events.
• -h — Print this help.

🦋 EXAMPLES 🦋

first one, printing events to stdout with -o:

$ corosync-notifyd -o
corosync-notifyd[18505]: troll[23374016] corosync-notify:18505:12 is now
connected to corosync
corosync-notifyd[18505]: troll[23374016] corosync-notify:18505:13 is now
disconnected from corosync
corosync-notifyd[18505]: troll[23374016] is now quorate
corosync-notifyd[18505]: r2[1550100672] ip:192.168.100.92 joined
corosync-notifyd[18505]: r2[1550100672] ip:192.168.100.92 left

then the dbus one:

$ corosync-notifyd -d

📌 Note this output below is from "dbus-monitor --system"

signal sender=:1.216 -> dest=(null destination) serial=2
path=/com/redhat/cluster/corosync;
 interface=com.redhat.cluster.corosync; member=ConnectionStateChange
   string "troll"
   uint32 23374016
   string "corosync-notify:18900:12"
   string "connected"
signal sender=:1.216 -> dest=(null destination) serial=3
path=/com/redhat/cluster/corosync;
 interface=com.redhat.cluster.corosync; member=ConnectionStateChange
   string "troll"
   uint32 23374016
   string "corosync-notify:18900:13"
   string "disconnected"
signal sender=:1.216 -> dest=(null destination) serial=4
path=/com/redhat/cluster/corosync;
 interface=com.redhat.cluster.corosync; member=QorumStateChange
   string "troll"
   uint32 23374016
   string "quorate"
signal sender=:1.216 -> dest=(null destination) serial=5
path=/com/redhat/cluster/corosync;
 interface=com.redhat.cluster.corosync; member=NodeStateChange
   string "r2"
   uint32 1550100672
   string "192.168.100.92"
   string "joined"
signal sender=:1.216 -> dest=(null destination) serial=6
path=/com/redhat/cluster/corosync;
 interface=com.redhat.cluster.corosync; member=NodeStateChange
   string "r2"
   uint32 1550100672
   string "192.168.100.92"
   string "left"

that QorumStateChange spelling? yeah it's literally in the output, we don't fix it, we respect it. periodt. 😭

👑 SEE ALSO 👑

• corosync(8)
• corosync-cmapctl(8)
• dbus-monitor(1)

💜 AUTHOR 💜

Angus Salkeld — the actual legend behind this. 🫶

and that's the whole page bestie!! this version is from 2011-01-14 and it's page COROSYNC-NOTIFYD(8) of the System Manager's Manual. go forth and listen to your cluster, mwah 💅💖✨