[Pacemaker] process not getting started after a failure

Hi All, I have a 3 node cluster (node1,node2,node3). The oc_pluginhandler resource is running in clone mode on 2 nodes as: primitive oc_pluginhandler lsb:pluginhandler \ meta

Re: [Pacemaker] Why order o inf: VIP A B starts VIP, A and B simultaneously ?

Thank you Andrew, perfect ! The more I use Pacemaker, the more tricky it gets when working with third-party tools (although crmsh is great). Completing PCMK configuration obviously involves some manual XML file tuning. It's often more crmsh issues than PCMK actually... 2014-06-27 7:43

Re: [Pacemaker] Announcing 1.1.12 - Final

- Original Message - I am pleased to report that 1.1.12 is finally done. This is a really great release and includes three key improvements: - ACLs are now on by default - pacemaker-remote now works for bare-metal nodes - Thanks to a new algorithm, the CIB is now two orders of

Re: [Pacemaker] process not getting started after a failure

On 22 Jul 2014, at 7:01 pm, ESWAR RAO eswar7...@gmail.com wrote: Hi All, I have a 3 node cluster (node1,node2,node3). The oc_pluginhandler resource is running in clone mode on 2 nodes as:

Re: [Pacemaker] Signal hangup handling for pacemaker and corosync

On 21 Jul 2014, at 3:45 pm, Vladislav Bogdanov bub...@hoster-ok.com wrote: 21.07.2014 08:36, Andrew Beekhof wrote: On 21 Jul 2014, at 2:50 pm, Vladislav Bogdanov bub...@hoster-ok.com wrote: 21.07.2014 06:28, Andrew Beekhof wrote: On 15 Jul 2014, at 8:45 pm, Arjun Pandey

Re: [Pacemaker] Signal hangup handling for pacemaker and corosync

Hi Andrew Yes this change would be useful. Regards Arjun On Wed, Jul 23, 2014 at 8:26 AM, Andrew Beekhof and...@beekhof.net wrote: On 21 Jul 2014, at 3:45 pm, Vladislav Bogdanov bub...@hoster-ok.com wrote: 21.07.2014 08:36, Andrew Beekhof wrote: On 21 Jul 2014, at 2:50 pm, Vladislav

[Pacemaker] Understanding virtual IP migration

Hi all I am using virtual IP resource on a 2 node (Active-Passive) cluster. I was testing the migration of IP address. Moving the link down moves the IP over to the other node. However if i bring interface up on the node the VIP is still associated with this interface. Shouldn't we have removed

Re: [Pacemaker] Signal hangup handling for pacemaker and corosync

23.07.2014 05:56, Andrew Beekhof wrote: On 21 Jul 2014, at 3:45 pm, Vladislav Bogdanov bub...@hoster-ok.com wrote: 21.07.2014 08:36, Andrew Beekhof wrote: On 21 Jul 2014, at 2:50 pm, Vladislav Bogdanov bub...@hoster-ok.com wrote: 21.07.2014 06:28, Andrew Beekhof wrote: On 15 Jul 2014,