[Pacemaker] Solved: removing a node from corosync

[Michael Schwartzkopff]

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:
> 
> root at node2:~# corosync-cfgtool -a node1
> 192.168.1.2
> root at 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
-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 198 bytes
Desc: This is a digitally signed message part.
URL: <https://lists.clusterlabs.org/pipermail/pacemaker/attachments/20101026/620ff4d4/attachment-0004.sig>