[ClusterLabs] Corosync cluster issue

[Jan Friesse]

Hi Pascu,

> 
> Hi,
> 
> We are using Corosync 2.4.0; we are having 3-node cluster (let's say, they are 1, 2, 3); we 

Probably not a solution but update to latest 2.4.4 may be helpful.

encountered a situation where node 3 was unable to join the cluster.
> 
> 
> Node 1 logs:
> 
> Nov12 22:50:02 corosync[3301]: [TOTEM ] A new membership (169.254.64.30:1852376) was formed. Members joined: 3
> 
> Node 2 logs:
> Nov12 22:50:02 corosync[3421]: [TOTEM ] A new membership (169.254.64.30:1852376) was formed. Members joined: 3
> Nov 12 22:50:02 corosync[3421]: [TOTEM ] A new membership (169.254.64.30:1852380) was formed. Members left: 3
> Nov 12 22:50:02 corosync[3421]: [TOTEM ] Failed to receive the leave message. failed: 3
> Nov 12 22:50:02 corosync[3421]: [QUORUM] Members[2]: 1 2
> Nov 12 22:50:02 corosync[3421]: [MAIN  ] Completed service synchronization, ready to provide service.
> 
> 
> Node 3 logs:
> 
> Nov12 22:50:02 corosync[2548]: [TOTEM ] A new membership (169.254.64.30:1852376) was formed. Members joined: 1 2
> Nov 12 22:50:02 corosync[2548]: [TOTEM ] FAILED TO RECEIVE
> 
> Can you give a hint on what could be the problem?

It's probably one of:
- Configs are not in sync (node 1,2 are missing node 3, node 1,2 are set 
to udpu transport and node 3 set to udp, ...)

- Badly configured firewall - try to delete all rules and set 
input/output to accept policy

- MTU problem - try set totem.netmtu in config file to some smaller 
value (like 1000)

If none of hints above helps, please attach your config file (with 
removed sensitive information).

Regards,
   Honza

> 
> 
> 
> Thanks,
> 
> Ciprian.
> 
> 
> 
> _______________________________________________
> Users mailing list: Users at clusterlabs.org
> https://lists.clusterlabs.org/mailman/listinfo/users
> 
> Project Home: http://www.clusterlabs.org
> Getting started: http://www.clusterlabs.org/doc/Cluster_from_Scratch.pdf
> Bugs: http://bugs.clusterlabs.org
>