> On 22 Oct 2014, at 4:34 pm, Andrei Borzenkov wrote:
>
> On Wed, Oct 22, 2014 at 8:01 AM, Andrew Beekhof wrote:
>>
>>> On 21 Oct 2014, at 11:15 pm, Andrei Borzenkov wrote:
>>>
>>> Pacemaker 1.1.11. I see in engine logs that it is going to restart resource:
>>>
>>> Oct 21 12:34:50 n2 pengin
On Wed, Oct 22, 2014 at 8:01 AM, Andrew Beekhof wrote:
>
>> On 21 Oct 2014, at 11:15 pm, Andrei Borzenkov wrote:
>>
>> Pacemaker 1.1.11. I see in engine logs that it is going to restart resource:
>>
>> Oct 21 12:34:50 n2 pengine[19748]: notice: LogActions: Restart
>> rsc_SAPHana_HDB_HDB00:0 (Ma
> On 21 Oct 2014, at 11:15 pm, Andrei Borzenkov wrote:
>
> Pacemaker 1.1.11. I see in engine logs that it is going to restart resource:
>
> Oct 21 12:34:50 n2 pengine[19748]: notice: LogActions: Restart
> rsc_SAPHana_HDB_HDB00:0 (Master n2)
>
> But I never see actual stop/start action being
> On 18 Oct 2014, at 1:52 am, John Osborne wrote:
>
> I have a two node cluster which manages 4 resources in a resource group.
> Node 1 was active and was rebooted. Resources started on the second node. At
> the exact time the first node completed rebooting, crmd failed on the second
> node. Log
> On 18 Oct 2014, at 7:49 am, Andrew Widdersheim
> wrote:
>
> I noticed a few broken links and the bugzilla seems broken as well:
These all broke when I turned off CGI as a precaution against the shellshock
vulnerability.
I need to find a way to turn it on again but in a limited fashion.
>
Pacemaker 1.1.11. I see in engine logs that it is going to restart resource:
Oct 21 12:34:50 n2 pengine[19748]: notice: LogActions: Restart
rsc_SAPHana_HDB_HDB00:0 (Master n2)
But I never see actual stop/start action being executed and in summary I get
Oct 21 12:35:11 n2 crmd[19749]: notice:
