Corosync continuously logs messages: "Marking seqid xx ringid x interface x.x.x.x FAULTY" on a pacemaker cluster
Issue
- Faulty ring issue is observed after recent change to
rrp_modein/etc/corosync/corosync.conf -
corosyncon one of the pacemaker nodes continuously logs theFAULTYmessages as seen below :Jun 1 14:50:16 node2 corosync[3413]: [TOTEM ] ring 1 active with no faults Jun 1 14:50:18 node2 corosync[3413]: [TOTEM ] Marking seqid 66 ringid 0 interface 192.x.x.2 FAULTY Jun 1 14:50:19 node2 corosync[3413]: [TOTEM ] Automatically recovered ring 0 Jun 1 14:50:20 node2 corosync[3413]: [TOTEM ] ring 0 active with no faults Jun 1 14:50:26 node2 corosync[3413]: [TOTEM ] ring 0 active with no faults Jun 1 14:50:29 node2 corosync[3413]: [TOTEM ] Marking seqid 162 ringid 1 interface 192.x.x.1 FAULTY Jun 1 14:50:30 node2 corosync[3413]: [TOTEM ] Automatically recovered ring 1
Environment
- Red Hat Enterprise Linux (RHEL) 6 or 7 with the High Availability Add On
- pacemaker cluster configured to use the Redundant Ring Protocol (RRP)
Subscriber exclusive content
A Red Hat subscription provides unlimited access to our knowledgebase, tools, and much more.
