Greg Woods writes:
> For the second time in a few weeks, we have had one node of a particular
> cluster getting fenced. It isn't totally clear why this is happening. On
> the surviving node I see:
>
> Feb 2 16:48:52 vmc1 stonith-ng[4331]: notice: stonith-vm2 can fence
>
On Thu, Feb 9, 2017 at 2:28 AM, Ferenc Wágner wrote:
> Looks like your VM resource was destroyed (maybe due to the xen balloon
> errors above), and the monitor operation noticed this.
>
Thank you for helping me interpret that. I think what happened is that the
VM in question