pcs shows several "Failed actions" for my fence_vmware_soap devices with "'unknown error' (1)" and status=Timed Out" in RHEL High Availability or Resilient Storage Cluster with Pacemaker
Issue
- What do the
Failed actions' mean in the output of
pcs status` for my stonith devices? - How to cleanup the "Failed actions:" seen in "pcs status" command for
fence_vmware_soap
devices? - With
fence_vmware_soap
, I see multiple failed start actions inpcs
output:
#pcs status
[..... ]
Full list of resources:
vmfence1 (stonith:fence_vmware_soap): Started node1.example.com
vmfence2 (stonith:fence_vmware_soap): Started node2.example.com
Failed actions:
vmfence1_start_0 on node1.example.com 'unknown error' (1): call=13, status=Timed Out, last-rc-change='Fri Jan 10 19:36:00 2014', queued=20189ms, exec=0ms
vmfence2_start_0 on node2.example.com 'unknown error' (1): call=15, status=Timed Out, last-rc-change='Fri Jan 10 19:36:00 2014', queued=20103ms, exec=0ms
vmfence1_start_0 on node1.example.com 'unknown error' (1): call=13, status=Timed Out, last-rc-change='Fri Jan 10 19:36:35 2014', queued=22046ms, exec=0ms
vmfence2_start_0 on node2.example.com 'unknown error' (1): call=15, status=Timed Out, last-rc-change='Fri Jan 10 19:36:36 2014', queued=21042ms, exec=0ms
Environment
- Red Hat Enterprise Linux (RHEL) 6 with the High Availability Add On
- Red Hat Enterprise Linux (RHEL) 7 with the High Availability Add On
pacemaker
- One or more stonith devices using
fence_vmware_soap
as the agent
Subscriber exclusive content
A Red Hat subscription provides unlimited access to our knowledgebase, tools, and much more.