Re: [ClusterLabs] corosync cannot acquire quorum

On 11/03/17 02:50, cys wrote: > We have a cluster containing 3 nodes(nodeA, nodeB, nodeC). > After nodeA is taken offline(by ifdown, this may be not right?), ifdown isn't right, no. you need to do a physical cable pull or use iptables to simulate loss of traffic, ifdown does odd things to

Re: [ClusterLabs] corosync cannot acquire quorum

I usually use `corosync-cfgtool -R` instead On 03/13/2017 11:08 AM, cys wrote: At first there were 2 nodes, nodeA and nodeC. nodeB was added later. It seems corosync reload failed. It's strange that `crm corosync reload` did not print any error message. 在2017年03月13 09时35分,

Re: [ClusterLabs] corosync cannot acquire quorum

At first there were 2 nodes, nodeA and nodeC. nodeB was added later. It seems corosync reload failed. It's strange that `crm corosync reload` did not print any error message. 在2017年03月13 09时35分, "bliu"写道: Hi, There is waitforall on nodeC, while not on

Re: [ClusterLabs] corosync cannot acquire quorum

在2017年03月13 09时35分, "bliu"写道: Hi, There is waitforall on nodeC, while not on nodeB, could you disable waitforall no nodeC And then have a re-try. On 03/11/2017 10:50 AM, cys wrote: We have a cluster containing 3 nodes(nodeA, nodeB,

Re: [ClusterLabs] corosync cannot acquire quorum

Hi, There is waitforall on nodeC, while not on nodeB, could you disable waitforall no nodeC And then have a re-try. On 03/11/2017 10:50 AM, cys wrote: We have a cluster containing 3 nodes(nodeA, nodeB, nodeC). After nodeA is taken offline(by ifdown, this may be not right?), nodeC cannot

[ClusterLabs] corosync cannot acquire quorum

We have a cluster containing 3 nodes(nodeA, nodeB, nodeC). After nodeA is taken offline(by ifdown, this may be not right?), nodeC cannot acquire quorum while nodeB can. NodeC: corosync-quorumtool -s Quorum information -- Date: Sat Mar 11 10:42:22 2017 Quorum provider: