Re: [ClusterLabs] weird corosync - [TOTEM ] FAILED TO RECEIVE

2018-12-03 Thread lejeczek
On 28/11/2018 08:34, Jan Friesse wrote: Anyway, problem is solved and if it appears again, please try to check that corosync.conf is equal on all nodes. I'd propose that (if devel wizzs read here) that some checks in pcs should be implemented to account for ruby (variants/versions

Re: [ClusterLabs] weird corosync - [TOTEM ] FAILED TO RECEIVE

2018-11-28 Thread Jan Friesse
lejeczek napsal(a): On 23/11/2018 16:36, Jan Friesse wrote: lejeczek, On 15/10/2018 07:24, Jan Friesse wrote: lejeczek, hi guys, I have a 3-node cluser(centos 7.5), 2 nodes seems fine but third(or probably something else in between) is not right. I see this:   $ pcs status --all Cluster

Re: [ClusterLabs] weird corosync - [TOTEM ] FAILED TO RECEIVE

2018-11-27 Thread lejeczek
On 23/11/2018 16:36, Jan Friesse wrote: lejeczek, On 15/10/2018 07:24, Jan Friesse wrote: lejeczek, hi guys, I have a 3-node cluser(centos 7.5), 2 nodes seems fine but third(or probably something else in between) is not right. I see this:   $ pcs status --all Cluster name: CC Stack:

Re: [ClusterLabs] weird corosync - [TOTEM ] FAILED TO RECEIVE

2018-11-23 Thread Jan Friesse
lejeczek, On 15/10/2018 07:24, Jan Friesse wrote: lejeczek, hi guys, I have a 3-node cluser(centos 7.5), 2 nodes seems fine but third(or probably something else in between) is not right. I see this:   $ pcs status --all Cluster name: CC Stack: corosync Current DC: whale.private (version

Re: [ClusterLabs] weird corosync - [TOTEM ] FAILED TO RECEIVE

2018-11-23 Thread lejeczek
On 15/10/2018 07:24, Jan Friesse wrote: lejeczek, hi guys, I have a 3-node cluser(centos 7.5), 2 nodes seems fine but third(or probably something else in between) is not right. I see this:   $ pcs status --all Cluster name: CC Stack: corosync Current DC: whale.private (version

Re: [ClusterLabs] weird corosync - [TOTEM ] FAILED TO RECEIVE

2018-10-15 Thread Jan Friesse
lejeczek, hi guys, I have a 3-node cluser(centos 7.5), 2 nodes seems fine but third(or probably something else in between) is not right. I see this:  $ pcs status --all Cluster name: CC Stack: corosync Current DC: whale.private (version 1.1.18-11.el7_5.3-2b07d5c5a9) - partition with quorum

Re: [ClusterLabs] weird corosync - [TOTEM ] FAILED TO RECEIVE

2018-10-12 Thread Ken Gaillot
On Fri, 2018-10-12 at 15:51 +0100, lejeczek wrote: > hi guys, > I have a 3-node cluser(centos 7.5), 2 nodes seems fine but  > third(or probably something else in between) is not right. > I see this: > >   $ pcs status --all > Cluster name: CC > Stack: corosync > Current DC: whale.private (version 

[ClusterLabs] weird corosync - [TOTEM ] FAILED TO RECEIVE

2018-10-12 Thread lejeczek
hi guys, I have a 3-node cluser(centos 7.5), 2 nodes seems fine but third(or probably something else in between) is not right. I see this:  $ pcs status --all Cluster name: CC Stack: corosync Current DC: whale.private (version 1.1.18-11.el7_5.3-2b07d5c5a9) - partition with quorum Last