Hi Piotr,
Sorry for the delay. I'm not a pacemaker expert, so I don't really know
how pacemaker behaves in various corner cases. Even if I were, it would
be difficult to advise you, since you haven't even posted what version
of pacemaker / corosync / pcs you are using.
In any case, the first
Hi Tomas,
Thank you very much for the idea. I have played with stonith_admin
--unfence and --confirm. Whenever I try, pcs status show my actions
under Failed Fencing Actions. I see this in the log file:
error: Unfencing of n2 by failed: No such device
No surprise here, since I have not got
Hi Piotr,
Based on 'pcs cluster node add n2' and 'pcs config' outputs, pcs added
the node to your cluster successfully, that is corosync config has been
modified, distributed and loaded.
It looks like the problem is with pacemaker. This is a wild guess, but
maybe pacemaker wants to fence n2,
Hi,
I used to have a working cluster with 3 nodes (and stonith disabled).
After an unexpected restart of one node, the cluster split. The node #2
started to see the others as unclean. Nodes 1 and 2 were cooperating
with each other, showing #2 as offline. There were no network connection
probl
