Across our clusters, I see the fence agent stop working, with no apparent
reason. It looks like shown below. I've found that I can do a `pcs resource
cleanup vmware_fence` to cause it to start back up again in a few seconds, but
why is this happening and how can I prevent it?
vmware_fence (stonith:fence_vmware_rest): Stopped
Failed Actions:
* vmware_fence_start_0 on q-gp2-dbpg57-1 'unknown error' (1): call=77,
status=Error, exitreason='none',
last-rc-change='Mon Jul 30 21:46:30 2018', queued=1ms, exec=1862ms
* vmware_fence_start_0 on q-gp2-dbpg57-3 'unknown error' (1): call=42,
status=Error, exitreason='none',
last-rc-change='Mon Jul 30 21:46:27 2018', queued=0ms, exec=1510ms
* vmware_fence_monitor_60000 on q-gp2-dbpg57-2 'unknown error' (1): call=84,
status=Error, exitreason='none',
last-rc-change='Tue Jul 24 16:11:42 2018', queued=0ms, exec=12142ms
Thank you,
--
Casey
_______________________________________________
Users mailing list: [email protected]
https://lists.clusterlabs.org/mailman/listinfo/users
Project Home: http://www.clusterlabs.org
Getting started: http://www.clusterlabs.org/doc/Cluster_from_Scratch.pdf
Bugs: http://bugs.clusterlabs.org
