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 Friesse wrote:
>>
>
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 wrote:
>> >> > Ken Gaillot wrote:
>> >> >> On 06/06/2016 05:45 PM, Adam Spiers wrote:
On 06/13/2016 10:13 PM, Kevin THIERRY wrote:
> Hello,
>
> I've been trying to setup pacemaker to get a HA system for a web
> application but I am having a hard time with DRBD.
This worked for me:
First, make sure your drbd resource is consistent/up to date and
finished syncing. IME initial setu
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
origin=abor
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 sometime
On 06/13/2016 10:13 PM, Kevin THIERRY wrote:
> Hello,
>
> I've been trying to setup pacemaker to get a HA system for a web
> application but I am having a hard time with DRBD. I have two nodes and
> drbd is configured in single primary mode. The issue I am facing is that
> I always end up with the
Hi All,
I confirm new alert function.
The trap of the current alert function is carried out in async.
Therefore, the transmission of the trap when Pacemaker stops may fail.
As a result, the trap of the stop of the resource may not transmit.
The ratio to fail in the transmission of the trap is
Hi all,
We actually have a 2 nodes cluster with corosync and pacemaker for httpd. We
have 2 VIP configured.
Since weve added ModSecurity 2.9, httpd restart is very slow. So I
increased the start / stop timeout. But sometimes, after logrotate the
following error occurs :
Failed Actions
