Hi Christine,
Thanks for your input!
> It worries me that corosync-quorumtool behaves differently on some nodes
> - some show names, some just IP addresses. That could be a cause of some
> inconsistency.
Haven't noticed this, we use static node names (not hostnames), so
this even more strange
A few things really stand out from this report, I think the inconsistent
ring_id is just a symptom.
It worries me that corosync-quorumtool behaves differently on some nodes
- some show names, some just IP addresses. That could be a cause of some
inconsistency.
Also the messages
"
Jan 26
BTW checked log, corosync reload failed:
-- Logs begin at Thu 2021-01-14 15:41:10 UTC, end at Tue 2021-01-26
01:42:48 UTC. --
Jan 22 14:33:09 destination-standby corosync[13180]: Starting Corosync
Cluster Engine (corosync): [ OK ]
Jan 22 14:33:09 destination-standby systemd[1]: Started Corosync
Hi All,
> pacemakerd -$
Pacemaker 1.1.15-11.el7
> corosync -v
Corosync Cluster Engine, version '2.4.0'
> rpm -qi libqb
Name: libqb
Version : 1.0.1
Please assist. Recently faced a strange bug (I suppose), when one of the
cluster nodes gets different from others "Ring ID" for example
