[corosync] Two node cluster not connected to each other

Digimer linux at alteeve.com
Wed Nov 30 16:44:11 GMT 2011


On 11/30/2011 11:39 AM, David Golovan wrote:
> Hi,
> 
> Thanks for the help.
> 
> I have removed the multicast address(now the cluster choose the address)
> and tried to change the default port for multicast (from 5404 to 5400),
> but no luck, still same problem...
> 
> While changing this settings I have noticed something:
> 
> I have removed to multicast address from the cluster(using luci) and
> reboot only one node. When the node started it couldn't connect to the
> cluster(as they had different multicast addresses), so it created
> cluster of his own with same ring id as the second node's cluster. And
> this time it didn't entered the loop of creating cluster generation number
> 
> David Golovan

If you can avoid changing the port or the IP and just let the cluster
use the default multicast, it would be best. Also make sure that, if you
have a managed switch, that it is handling multicast properly.

-- 
Digimer
E-Mail:              digimer at alteeve.com
Freenode handle:     digimer
Papers and Projects: http://alteeve.com
Node Assassin:       http://nodeassassin.org
"omg my singularity battery is dead again.
stupid hawking radiation." - epitron


More information about the discuss mailing list