Re: [ClusterLabs] CIB: op-status=4 ?

2017-05-23 Thread Radoslaw Garbacz
Thanks, your explanation is very helpful considering that it happens rarely and only on the first boot after VMs are created. On Mon, May 22, 2017 at 9:34 PM, Ken Gaillot wrote: > On 05/19/2017 02:03 PM, Radoslaw Garbacz wrote: > > Hi, > > > > I have some more information

Re: [ClusterLabs] failcount is not getiing reset after failure_timeout if monitoring is disabled

2017-05-23 Thread Ken Gaillot
On 05/23/2017 08:00 AM, ashutosh tiwari wrote: > Hi, > > We are running a two node cluster(Active(X)/passive(Y)) having muliple > resources of type IpAddr2. > Running monitor operations for multiple IPAddr2 resource is actually > hoging the cpu, > as we have configured very low value for monitor

Re: [ClusterLabs] both nodes OFFLINE

2017-05-23 Thread 石井 俊直
Hi. Thanks for reply. And sorry for my report that problem has solved. As mentioned, corosync versions were not same. “Syncing” versions solved the problem. This was just an installation problem. Although we used Ansible to update the rpm file, there was a failure and we missed it happend. >

[ClusterLabs] Pacemaker 1.1.17 Release Candidate 2

2017-05-23 Thread Ken Gaillot
The second release candidate for Pacemaker version 1.1.17 is now available at: https://github.com/ClusterLabs/pacemaker/releases/tag/Pacemaker-1.1.17-rc2 This release contains multiple fixes related to the new bundle feature, plus: * A regression introduced in Pacemaker 1.1.15 has been

[ClusterLabs] failcount is not getiing reset after failure_timeout if monitoring is disabled

2017-05-23 Thread ashutosh tiwari
Hi, We are running a two node cluster(Active(X)/passive(Y)) having muliple resources of type IpAddr2. Running monitor operations for multiple IPAddr2 resource is actually hoging the cpu, as we have configured very low value for monitor interval (200 msec). To avoid this problem ,we are trying to

Re: [ClusterLabs] "Connecting" Pacemaker with another cluster manager

2017-05-23 Thread Timo
On 05/23/2017 09:44 AM, Kristoffer Grönlund wrote: > Timo writes: > >> Hi, >> >> I have a proprietary cluster manager running on a bunch (four) of nodes. >> It decides to run the daemon for which HA is required on its own set of >> (undisclosed) requirements and

Re: [ClusterLabs] "Connecting" Pacemaker with another cluster manager

2017-05-23 Thread Kristoffer Grönlund
Timo writes: > Hi, > > I have a proprietary cluster manager running on a bunch (four) of nodes. > It decides to run the daemon for which HA is required on its own set of > (undisclosed) requirements and decisions. This is, unfortunately, > unavoidable due to business

[ClusterLabs] "Connecting" Pacemaker with another cluster manager

2017-05-23 Thread Timo
Hi, I have a proprietary cluster manager running on a bunch (four) of nodes. It decides to run the daemon for which HA is required on its own set of (undisclosed) requirements and decisions. This is, unfortunately, unavoidable due to business requirements. However, I have to put also Pacemaker

[ClusterLabs] two node cluster. each node shows other node offline.

2017-05-23 Thread Jimmy Prescott
Hello all, I have two nginx nodes running nginx version: nginx/1.11.10 (nginx-plus-r12-p2), Corosync Cluster Engine, version '2.3.5', and Pacemaker 1.1.14 on Ubuntu 16.04.1 LTS. This cluster is intended to replace our old nginx cluster running on 14.04 and older versions of corosync/pacemaker.