After a token loss event fenced is not called to fence a node in a RHEL 5 High Availability cluster
Issue
- My cluster experienced a token loss event and a node was removed from the cluster. However the first cluster node who was supposed to issue the fence never did so.
- Several nodes reported a token loss, followed by "fencing deferred to
", but that node never fenced the missing node
Aug 27 15:27:08 node2 openais[26368]: [TOTEM] The token was lost in the OPERATIONAL state.
[...]
Aug 27 15:27:43 node2 openais[26368]: [CLM ] CLM CONFIGURATION CHANGE
Aug 27 15:27:43 node2 openais[26368]: [CLM ] New Configuration:
Aug 27 15:27:43 node2 openais[26368]: [CLM ] r(0) ip(192.168.10.1)
Aug 27 15:27:43 node2 openais[26368]: [CLM ] r(0) ip(192.168.10.2)
Aug 27 15:27:43 node2 openais[26368]: [CLM ] r(0) ip(192.168.10.3)
Aug 27 15:27:43 node2 openais[26368]: [CLM ] r(0) ip(192.168.10.4)
Aug 27 15:27:43 node2 openais[26368]: [CLM ] Members Left:
Aug 27 15:27:43 node2 openais[26368]: [CLM ] r(0) ip(192.168.10.5)
[...]
Aug 27 15:27:43 node2 fenced[26387]: fencing deferred to node1
Environment
- Red Hat Enterprise Linux (RHEL) 5 with the High Availability Add On
Subscriber exclusive content
A Red Hat subscription provides unlimited access to our knowledgebase of over 48,000 articles and solutions.
Close
Welcome! Check out the Getting Started with Red Hat page for quick tours and guides for common tasks.