[Pacemaker] catch-22: can't fence node A because node A has the fencing resource

Nikita Staroverov nsforth at gmail.com
Wed Dec 4 04:21:49 UTC 2013


> It explains the differences, but unfortunately I'm still not sure why it
> wouldn't get run somewhere else, eventually, rather than continually
> being attempted on the node to be killed (which as I mentioned, was shut
> down at the time the log was made).
>
> Cheers,
> b.
>
May be fence devices were started on other nodes but failed to do so.
Afaik, failed fence device doesn't start on node before failure-timeout 
expired,
so pacemaker tries to do fencing on "last known good" node, despite of 
node state.
We need more logs :)




More information about the Pacemaker mailing list