On 21 Feb 2014, at 9:35 pm, Kazunori INOUE wrote:
> 2014-02-20 18:59 GMT+09:00 Andrew Beekhof :
>>
>> On 20 Feb 2014, at 8:37 pm, Kazunori INOUE wrote:
>>
>>> Hi,
>>>
>>> Is this by design although log levels differ with a stonith resource
>>> and other resources in Pacemaker-1.1.11 ?
>>>
>
Hi All,
I made a patch.
Please confirm the contents of the patch.
If there is not a problem, please reflect it in github.
Best Regards,
Hideo Yamauchi.
--- On Thu, 2014/2/20, renayama19661...@ybb.ne.jp
wrote:
> Hi All,
>
> The timer which is not stopped at the time of the stop of the monitor
On 24 Feb 2014, at 12:59 pm, Andrew Beekhof wrote:
>
> On 21 Feb 2014, at 9:36 pm, Kazunori INOUE wrote:
>
>> Hi,
>>
>> WARNING of the following is outputted after pacemaker stopped in
>> Pacemaker-1.1.11.
>>
>> Feb 21 18:22:57 bl460g1n6 ping(prmPing)[9195]: WARNING: Could not
>> update def
On 21 Feb 2014, at 9:36 pm, Kazunori INOUE wrote:
> Hi,
>
> WARNING of the following is outputted after pacemaker stopped in
> Pacemaker-1.1.11.
>
> Feb 21 18:22:57 bl460g1n6 ping(prmPing)[9195]: WARNING: Could not
> update default_ping_set = 100: rc=141
>
>
> This is because pacemaker does
On 22 Feb 2014, at 1:26 am, Ivan wrote:
> Andrew Beekhof writes:
>
>>
>>
>> On 29/08/2013, at 7:41 PM, Moturi Upendra
>> wrote:
>>
>>> Please find the attachment
>>
>> The problem is that the migration-threshold has been set as a cluster
> option rather than a resource default.
>> In rhel
On 21 Feb 2014, at 2:19 pm, Andrew Beekhof wrote:
>
> On 18 Feb 2014, at 1:23 pm, Andrew Beekhof wrote:
>
>>
>> On 6 Feb 2014, at 7:45 pm, Keisuke MORI wrote:
>>
>>> Hi,
>>>
>>> I observed that pre_notify_demote is issued twice when a master
>>> resource is migrating.
>>> I'm wondering if
On 22 Feb 2014, at 7:07 pm, Andrey Groshev wrote:
>
>
> 21.02.2014, 04:00, "Andrew Beekhof" :
>> On 20 Feb 2014, at 10:04 pm, Andrey Groshev wrote:
>>
>>> 20.02.2014, 13:57, "Andrew Beekhof" :
On 20 Feb 2014, at 5:33 pm, Andrey Groshev wrote:
> 20.02.2014, 01:22, "Andrew Beekho
