[ClusterLabs] Corosync/Pacemaker bug methinks! (Was: pacemaker won't start because duplicate node but can't remove dupe node because pacemaker won't start)

Klaus Wenninger kwenning at redhat.com
Tue Jan 7 04:37:28 EST 2020

On 12/19/19 6:43 PM, JC wrote:
> OK! That did it! I ran `pcs cluster destroy --all` and edited the
> corosync.conf on all nodes adding `transport: udpu` in the totem
> block. I re-added the errant node into the nodelist and restarted the
> cluster. All nodes are present and accounted for. Sincerely appreciate
> your assistance.
Glad you got it solved!
Just for completeness - as I had the impression you were puzzled
initially where
the non-random ID came from and I haven't read about it in the thread later:
It is derived from the IP-address.

> - Jim
>> On Dec 19, 2019, at 08:02, Ken Gaillot <kgaillot at redhat.com
>> <mailto:kgaillot at redhat.com>> wrote:
>> udpu
> _______________________________________________
> Manage your subscription:
> https://lists.clusterlabs.org/mailman/listinfo/users
> ClusterLabs home: https://www.clusterlabs.org/

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://lists.clusterlabs.org/pipermail/users/attachments/20200107/0b8a9fe8/attachment.html>

More information about the Users mailing list