Re: [ClusterLabs] Pacemaker with Zookeeper??

tl;dr - dont port pacemaker, use pacemaker-remote instead On Wed, May 18, 2016 at 5:20 PM, Jan Friesse wrote: > Ken Gaillot napsal(a): > >> On 05/17/2016 09:54 AM, Digimer wrote: >>> >>> On 16/05/16 04:35 AM, Bogdan Dobrelya wrote: On 05/16/2016 09:23 AM, Jan

Re: [ClusterLabs] Informing RAs about recovery: failed resource recovery, or any start-stop cycle?

On Mon, Jun 13, 2016 at 9:34 PM, Adam Spiers wrote: > Andrew Beekhof wrote: >> On Wed, Jun 8, 2016 at 6:23 PM, Adam Spiers wrote: >> > Andrew Beekhof wrote: >> >> On Wed, Jun 8, 2016 at 12:11 AM, Adam Spiers

Re: [ClusterLabs] Processing failed op monitor for WebSite on node1: not running (7)

Hi, Every action on httpd is very slow due to ModSecurity 2.9. The reload in postrotate may take awhile. Here is the output log for message this morning : Jun 14 03:43:05 mail-px-** crmd[2685]: notice: State transition S_IDLE -> S_POLICY_ENGINE [ input=I_PE_CALC cause=C_FSA_INTERNAL

Re: [ClusterLabs] Processing failed op monitor for WebSite on node1: not running (7)

On 06/14/2016 03:10 AM, Jeremy Voisin wrote: > Hi all, > > > > We actually have a 2 nodes cluster with corosync and pacemaker for > httpd. We have 2 VIP configured. > > > > Since we’ve added ModSecurity 2.9, httpd restart is very slow. So I > increased the start / stop timeout. But