On Tuesday 26 October 2010 20:51:29 Michael Schwartzkopff wrote: > Hi, > > somehow I managed to mess my cluster. corosync on one node would not start > properly and on he other node I see: > > r...@node2:~# corosync-cfgtool -a node1 > 192.168.1.2 > r...@node2:~# corosync-cfgtool -a node2 > 192.168.1.2 > > Who could both nodes have the same I address? How can solve the problem? > > Greetings,
Hi, Cause: on node1 a LOT of corosync processes were running in the background. Killing manually solved the problem. corosync-cfgtool -a <node> always shows the local IP address. -- Dr. Michael Schwartzkopff Guardinistr. 63 81375 München Tel: (0163) 172 50 98
signature.asc
Description: This is a digitally signed message part.
_______________________________________________ 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://developerbugs.linux-foundation.org/enter_bug.cgi?product=Pacemaker
