On 10/04/2010 02:04 AM, Stephan-Frank Henry wrote:
Hello all,
still working on my nodes and although the last problem is not officially
solved (I hard coded certain versions of the packages and that seems to be ok
now) I have a different interesting feature I need to handle.
I am setting up my nodes by default as single node setups. But today when I set
up another node, *without* doing any special config to make them know each
other, the corosyncs on each nodes found each other and distributed the cib.xml
between each other.
They both also show up together in crm_mon.
Not quite what I wanted. :)
I presume I have a config that is too generic and thus the nodes are finding
each other and thinking they should link up.
What configs do I have to look into to avoid this?
thanks
A unique cluster is defined by mcastaddr and mcastport in the file
/etc/corosync/corosync.conf
If you simply installed them, you may have the same corosync.conf file
for each unique cluster which would result in the problem you describe.
Regards
-steve
_______________________________________________
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
