Re: [ClusterLabs] Create ressource to monitor each IPSEC VPN

2017-03-24 Thread Ken Gaillot
On 03/09/2017 01:44 AM, Damien Bras wrote: > Hi, > > > > We have a 2 nodes cluster with ipsec (libreswan). > > Actually we have a resource to monitor the service ipsec (via system). > > > > But now I would like to monitor each VPN. Is there a way to do that ? > Which agent could I use for

Re: [ClusterLabs] pending actions

2017-03-24 Thread Ken Gaillot
On 03/07/2017 04:13 PM, Jehan-Guillaume de Rorthais wrote: > Hi, > > Occasionally, I find my cluster with one pending action not being executed for > some minutes (I guess until the "PEngine Recheck Timer" elapse). > > Running "crm_simulate -SL" shows the pending actions. > > I'm still confused

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

2017-03-24 Thread Seth Reid
> 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

2017-03-24 Thread Digimer
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

2017-03-24 Thread Seth Reid
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

Re: [ClusterLabs] error: The cib process (17858) exited: Key has expired (127)

2017-03-24 Thread Ken Gaillot
On 03/24/2017 11:06 AM, Rens Houben wrote: > I activated debug=cib, and retried. > > New log file up at > http://proteus.systemec.nl/~shadur/pacemaker/pacemaker_2.log.txt > ; > unfortunately, while that *is* more information I'm

Re: [ClusterLabs] error: The cib process (17858) exited: Key has expired (127)

2017-03-24 Thread Rens Houben
I activated debug=cib, and retried. New log file up at http://proteus.systemec.nl/~shadur/pacemaker/pacemaker_2.log.txt ; unfortunately, while that *is* more information I'm not seeing anything that looks like it could be the cause, although it shouldn't be reading any config files yet

Re: [ClusterLabs] stonith in dual HMC environment

2017-03-24 Thread Ken Gaillot
On 03/22/2017 09:42 AM, Alexander Markov wrote: > >> Please share your config along with the logs from the nodes that were >> effected. > > I'm starting to think it's not about how to define stonith resources. If > the whole box is down with all the logical partitions defined, then HMC > cannot

Re: [ClusterLabs] error: The cib process (17858) exited: Key has expired (127)

2017-03-24 Thread Ken Gaillot
On 03/24/2017 08:06 AM, Rens Houben wrote: > I recently upgraded a two-node cluster (named 'castor' and 'pollux' > because I should not be allowed to think up computer names before I've > had my morning caffeine) from Debian wheezy to Jessie after the > backports for corosync and pacemaker finally

[ClusterLabs] error: The cib process (17858) exited: Key has expired (127)

2017-03-24 Thread Rens Houben
I recently upgraded a two-node cluster (named 'castor' and 'pollux' because I should not be allowed to think up computer names before I've had my morning caffeine) from Debian wheezy to Jessie after the backports for corosync and pacemaker finally made it in. However, one of the two servers