On 23/05/2013, at 9:47 PM, Brian J. Murrell wrote:
> On 13-05-22 07:05 PM, Andrew Beekhof wrote:
>>
>> Also, 1.1.8-7 was not tested with the plugin _at_all_ (and neither will
>> future RHEL builds).
>
> Was 1.1.7-* in EL 6.3 tested with the plugin?
No. Which is why I didn't notice logging w
On 13-05-22 07:05 PM, Andrew Beekhof wrote:
>
> Also, 1.1.8-7 was not tested with the plugin _at_all_ (and neither will
> future RHEL builds).
Was 1.1.7-* in EL 6.3 tested with the plugin? Is staying with most
recent EL 6.3 pacemaker-1.1.7 release really the more stable option for
people not a
On 22/05/2013, at 9:44 PM, Brian J. Murrell wrote:
> Using pacemaker 1.1.8-7 on EL6, I got the following series of events
> trying to shut down pacemaker and then corosync. The corosync shutdown
> (service corosync stop) ended up spinning/hanging indefinitely (~7hrs
> now). The events, includi
Using pacemaker 1.1.8-7 on EL6, I got the following series of events
trying to shut down pacemaker and then corosync. The corosync shutdown
(service corosync stop) ended up spinning/hanging indefinitely (~7hrs
now). The events, including a:
May 21 23:47:18 node1 crmd[17598]:error: do_exit: C
