Re: [ClusterLabs] Three node cluster becomes completely fenced if one node leaves

We are only using one mount, and that mount has nothing on it currently. I have fixed the problem. Our OS is Ubuntu 16.04 LTS (Xenial). I added the 17.04 (Zesty) repo to get newer a newer version of Corosync. I upgraded Corosync, which upgraded a long list of other related packages (Pacemaker

Re: [ClusterLabs] Three node cluster becomes completely fenced if one node leaves

- Original Message - | I can confirm that doing an ifdown is not the source of my corosync issues. | My cluster is in another state, so I can't pull a cable, but I can down a | port on a switch. That had the exact same affects as doing an ifdown. Two | machines got fenced when it should

Re: [ClusterLabs] Three node cluster becomes completely fenced if one node leaves

I can confirm that doing an ifdown is not the source of my corosync issues. My cluster is in another state, so I can't pull a cable, but I can down a port on a switch. That had the exact same affects as doing an ifdown. Two machines got fenced when it should have only been one. --- Seth Reid

Re: [ClusterLabs] Three node cluster becomes completely fenced if one node leaves

Hi, On Fri, Mar 31, 2017 at 02:39:02AM -0400, Digimer wrote: > On 31/03/17 02:32 AM, Jan Friesse wrote: > >> The original message has the logs from nodes 1 and 3. Node 2, the one > >> that > >> got fenced in this test, doesn't really show much. Here are the logs from > >> it: > >> > >> Mar 24

Re: [ClusterLabs] Three node cluster becomes completely fenced if one node leaves

On 31/03/17 02:32 AM, Jan Friesse wrote: >> The original message has the logs from nodes 1 and 3. Node 2, the one >> that >> got fenced in this test, doesn't really show much. Here are the logs from >> it: >> >> Mar 24 16:35:10 b014 ntpd[2318]: Deleting interface #5 enp6s0f0, >>

Re: [ClusterLabs] Three node cluster becomes completely fenced if one node leaves

The original message has the logs from nodes 1 and 3. Node 2, the one that got fenced in this test, doesn't really show much. Here are the logs from it: Mar 24 16:35:10 b014 ntpd[2318]: Deleting interface #5 enp6s0f0, 192.168.100.14#123, interface stats: received=0, sent=0, dropped=0,

Re: [ClusterLabs] Three node cluster becomes completely fenced if one node leaves

The original message has the logs from nodes 1 and 3. Node 2, the one that got fenced in this test, doesn't really show much. Here are the logs from it: Mar 24 16:35:10 b014 ntpd[2318]: Deleting interface #5 enp6s0f0, 192.168.100.14#123, interface stats: received=0, sent=0, dropped=0,

Re: [ClusterLabs] Three node cluster becomes completely fenced if one node leaves

On 24/03/17 20:44, Seth Reid wrote: > I have a three node Pacemaker/GFS2 cluster on Ubuntu 16.04. Its not in > production yet because I'm having a problem during fencing. When I > disable the network interface of any one machine, If you mean by using ifdown or similar then ... don't do that. A

Re: [ClusterLabs] Three node cluster becomes completely fenced if one node leaves

- Original Message - | I will try to install updated packages from ubuntu 16.10 or newer. It can't | get worse than not working. | | Can you think of any logs that might help? I've enabled debug on corosync | log, but it really doesn't show anything else other than corosync exiting. | Any

Re: [ClusterLabs] Three node cluster becomes completely fenced if one node leaves

On Fri, Mar 24, 2017 at 01:44:44PM -0700, Seth Reid wrote: > I have a three node Pacemaker/GFS2 cluster on Ubuntu 16.04. Its not in > production yet because I'm having a problem during fencing. When I disable > the network interface of any one machine, the disabled machines is properly > fenced

Re: [ClusterLabs] Three node cluster becomes completely fenced if one node leaves

I will try to install updated packages from ubuntu 16.10 or newer. It can't get worse than not working. Can you think of any logs that might help? I've enabled debug on corosync log, but it really doesn't show anything else other than corosync exiting. Any diagnostic tools you can recommend?

Re: [ClusterLabs] Three node cluster becomes completely fenced if one node leaves

On 03/27/2017 03:54 PM, Seth Reid wrote: > > > > On Fri, Mar 24, 2017 at 2:10 PM, Ken Gaillot > wrote: > > On 03/24/2017 03:52 PM, Digimer wrote: > > On 24/03/17 04:44 PM, Seth Reid wrote: > >> I have a three node Pacemaker/GFS2

Re: [ClusterLabs] Three node cluster becomes completely fenced if one node leaves

On Fri, Mar 24, 2017 at 2:10 PM, Ken Gaillot wrote: > On 03/24/2017 03:52 PM, Digimer wrote: > > On 24/03/17 04:44 PM, Seth Reid wrote: > >> I have a three node Pacemaker/GFS2 cluster on Ubuntu 16.04. Its not in > >> production yet because I'm having a problem during

Re: [ClusterLabs] Three node cluster becomes completely fenced if one node leaves

> On 24/03/17 04:44 PM, Seth Reid wrote: > > I have a three node Pacemaker/GFS2 cluster on Ubuntu 16.04. Its not in > > production yet because I'm having a problem during fencing. When I > > disable the network interface of any one machine, the disabled machines > > is properly fenced leaving me,

Re: [ClusterLabs] Three node cluster becomes completely fenced if one node leaves

On 24/03/17 04:44 PM, Seth Reid wrote: > I have a three node Pacemaker/GFS2 cluster on Ubuntu 16.04. Its not in > production yet because I'm having a problem during fencing. When I > disable the network interface of any one machine, the disabled machines > is properly fenced leaving me, briefly,

[ClusterLabs] Three node cluster becomes completely fenced if one node leaves

I have a three node Pacemaker/GFS2 cluster on Ubuntu 16.04. Its not in production yet because I'm having a problem during fencing. When I disable the network interface of any one machine, the disabled machines is properly fenced leaving me, briefly, with a two node cluster. A second node is then