[ClusterLabs] pcsd 99% CPU

2017-02-03 Thread Scott Greenlese
Hi all.. Over the past few days, I noticed that pcsd and ruby process is pegged at 99% CPU, and commands such as pcs status pcsd take up to 5 minutes to complete. On all active cluster nodes, top shows: PID USER PR NI VIRT RES SHRS %CPU %MEM TIME+ COMMAND 27225

Re: [ClusterLabs] Failure to configure iface-bridge resource causes cluster node fence action.

2017-02-03 Thread Scott Greenlese
Ken, Thanks for the explanation. One other thing, relating to the iface-bridge resource creation. I specified --disabled flag: > [root@zs95kj VD]# date;pcs resource create br0_r1 > ocf:heartbeat:iface-bridge bridge_name=br0 bridge_slaves=vlan1292 op > monitor timeout="20s" interval="10s"

[ClusterLabs] odd cluster failure

2017-02-03 Thread Greg Woods
(Apologies if this is a duplicate. I accidentally posted to the old linux-ha.org address, and I couldn't tell from the auto-reply whether my message was actually posted to the list or not). For the second time in a few weeks, we have had one node of a particular cluster getting fenced. It isn't

Re: [ClusterLabs] gfs2-utils.git moving on Feb 3

2017-02-03 Thread Andrew Price
Hi, This is now complete and pushes to the old Fedora Hosted git repository should no longer work. Please update your gfs2-utils trees as below. Thanks, Andy On 31/01/17 15:15, Andrew Price wrote: Hi, This is a heads-up that from Friday February 3 the gfs2-utils git repository will be

Re: [ClusterLabs] [Question] About a change of crm_failcount.

2017-02-03 Thread Jehan-Guillaume de Rorthais
On Fri, 3 Feb 2017 09:45:18 -0600 Ken Gaillot wrote: > On 02/02/2017 12:33 PM, Ken Gaillot wrote: > > On 02/02/2017 12:23 PM, renayama19661...@ybb.ne.jp wrote: > >> Hi All, > >> > >> By the next correction, the user was not able to set a value except zero > >> in

Re: [ClusterLabs] [Question] About a change of crm_failcount.

2017-02-03 Thread Ken Gaillot
On 02/02/2017 12:33 PM, Ken Gaillot wrote: > On 02/02/2017 12:23 PM, renayama19661...@ybb.ne.jp wrote: >> Hi All, >> >> By the next correction, the user was not able to set a value except zero in >> crm_failcount. >> >> - [Fix: tools: implement crm_failcount command-line options correctly] >>

[ClusterLabs] Manage Docker service and containers with pacemaker

2017-02-03 Thread Stephane Gaucher
Hello I am completing a proof of concept. Here are the facts: An active / passive cluster.Done A drbd partition for exchanging files for different servicesDone A shared VIP between the two nodesDone The docker/containers are functional. I do not want to use docker swarm. This is not

Re: [ClusterLabs] Pacemaker kill does not cause node fault ???

2017-02-03 Thread RaSca
On 03/02/2017 11:06, Ferenc Wágner wrote: > Ken Gaillot writes: > >> On 01/10/2017 04:24 AM, Stefan Schloesser wrote: >> >>> I am currently testing a 2 node cluster under Ubuntu 16.04. The setup >>> seems to be working ok including the STONITH. >>> For test purposes I

Re: [ClusterLabs] Pacemaker kill does not cause node fault ???

2017-02-03 Thread Ferenc Wágner
Ken Gaillot writes: > On 01/10/2017 04:24 AM, Stefan Schloesser wrote: > >> I am currently testing a 2 node cluster under Ubuntu 16.04. The setup >> seems to be working ok including the STONITH. >> For test purposes I issued a "pkill -f pace" killing all pacemaker >>