[Pacemaker] node offline after fencing (pacemakerd hangs)

[Andrew Beekhof]

On Fri, Jul 20, 2012 at 1:51 AM, Raoul Bhatia [IPAX] <r.bhatia at ipax.at> wrote:
> On 2012-07-19 16:05, Jake Smith wrote:
>> Another solution is something like (will vary a little in RHEL I believe):
>>
>> Disable corosync autostart
>> $sudo update-rc.d -f corosync disable S
>>
>> add 'post-up /etc/init.d/corosync start' to bonding (or in your case bridged) interface in
>> /etc/network/interfaces.
>
> Just for the records:
> If you're using pacemakerd with a seperate init file,
> you will have to consider this one too.

Personally I've never been a fan of starting the cluster at boot.
Getting fenced is a reasonably severe condition and having a human
check over the node before adding it back to the cluster seems like a
sane pre-condition.