Michael,
Michael Schwartzkopff napsal(a):
Hi,
we just upgraded to corosync-1.4.5-2.5 from the suse build server. On one
cluster we have the problem, that corosync-objctl does not reflect the status
So if I understand it correctly, you have multiple clusters and all of
them was upgraded and only on one of them this bug appears?
of nodes properly. Even when the other node stops corosync we still see:
runtime.totem.mrp.srp.members.<ID>.status=joined
Is this consistent between nodes? I mean, ALL nodes sees already stopped
node as joined or some of them sees that as left?
Regards,
Honza
But the log says:
[TOTEM] A processor joined or left the membership and a new membership was
formed.
Any ideas?
Mit freundlichen Grüßen,
Michael Schwartzkopff
_______________________________________________
Pacemaker mailing list: Pacemaker@oss.clusterlabs.org
http://oss.clusterlabs.org/mailman/listinfo/pacemaker
Project Home: http://www.clusterlabs.org
Getting started: http://www.clusterlabs.org/doc/Cluster_from_Scratch.pdf
Bugs: http://bugs.clusterlabs.org
_______________________________________________
Pacemaker mailing list: Pacemaker@oss.clusterlabs.org
http://oss.clusterlabs.org/mailman/listinfo/pacemaker
Project Home: http://www.clusterlabs.org
Getting started: http://www.clusterlabs.org/doc/Cluster_from_Scratch.pdf
Bugs: http://bugs.clusterlabs.org
