[ClusterLabs] Help to Handling Split brain on Pacemaker

2016-10-18 Thread K Aravind
Hi All I have two few questions regarding pacemaker's handling of pacemaker 1.Is there a way to notify the clusters upon detection of a split brain on the network ? I would like to take certain actions based on it such as blocking the DB,logging etc 2.Under Section 5.4 of Pacemaker Explained

Re: [ClusterLabs] Pacemaker remote - invalid message detected, endian mismatch

2016-10-18 Thread Radoslaw Garbacz
Hi, I am sorry for the long delay, just I moved on with my tool and had to narrow down the circumstances of this error. So apparently this error is related to many remote nodes querying CIB (I had an OCF monitor agent running on all nodes), once turned off it works with ~100 nodes. Parts of the

Re: [ClusterLabs] Antw: Re: Antw: Unexpected Resource movement after failover

2016-10-18 Thread Ken Gaillot
On 10/17/2016 11:29 PM, Nikhil Utane wrote: > Thanks Ken. > I will give it a shot. > > http://oss.clusterlabs.org/pipermail/pacemaker/2011-August/011271.html > On this thread, if I interpret it correctly, his problem was solved when > he swapped the anti-location constraint > > From (mapping to

[ClusterLabs] Antw: Re: Antw: Re: Can't do anything right; how do I start over?

2016-10-18 Thread Ulrich Windl
>>> Dmitri Maziuk schrieb am 17.10.2016 um 16:51 in Nachricht <0d370bc7-c74e-4250-5848-b9c7de941...@gmail.com>: > On 2016-10-17 02:12, Ulrich Windl wrote: > >> Have you tried a proper variant of "lsof" before? So maybe you know > which process might block the device. I

[ClusterLabs] Antw: Re: Antw: Re: Antw: Unexpected Resource movement after failover

2016-10-18 Thread Ulrich Windl
>>> Nikhil Utane schrieb am 17.10.2016 um 16:46 in Nachricht