fencing fails with errors 'notice: stonith_choose_peer: Couldn't find anyone to fence <node>' when a fence_apc stonith device is configured in a RHEL 6 or 7 High Availability cluster with pacemaker
Issue
- Fencing fails with
fence_apc - I've created a
stonithdevice for each node and put them in a level, but fencing never succeeds if a node is removed or withpcs stonith fence <node> - I see errors from
stonith-ngindicating there's no device to fence a node, but I have a stonith device for each node
Dec 04 01:27:58 node1.example.com stonith-ng[2547]: notice: initiate_remote_stonith_op: Initiating remote operation reboot for node2.example.com: aa813c19-751b-4d2e-a903-78935b9afa4b (0)
Dec 04 01:28:08 node1.example.com stonith-ng[2547]: notice: stonith_topology_next: All fencing options to fence node2.example.com for stonith_admin.12701@node1.example.com.aa813c19 failed
Dec 04 01:28:08 node1.example.com stonith-ng[2547]: notice: stonith_choose_peer: Couldn't find anyone to fence node2.example.com with myPDU
Dec 04 01:28:08 node1.example.com stonith-ng[2547]: error: remote_op_done: Operation reboot of node2.example.com by node1.example.com for stonith_admin.12701@node1.example.com.aa813c19: No such device
Environment
- Red Hat Enterprise Linux (RHEL) 6 or 7 with the High Availability Add On
pacemaker- One or more
stonithdevices usingfence_apcas the agent- Those devices do not have
pcmk_host_listspecified, and do not have a validpcmk_host_map - The outlet labels on the APC PDU do not match the node names exactly
- Those devices do not have
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.