[Pacemaker] node1 fencing itself after node2 being fenced

[Andrew Beekhof]

On 19 Feb 2014, at 7:16 am, Vladislav Bogdanov <bubble at hoster-ok.com> wrote:

> 18.02.2014 23:01, David Vossel wrote:
>> 
>> 
>> 
>> 
>> ----- Original Message -----
>>> From: "Vladislav Bogdanov" <bubble at hoster-ok.com> To:
>>> pacemaker at oss.clusterlabs.org Sent: Tuesday, February 18, 2014
>>> 1:02:09 PM Subject: Re: [Pacemaker] node1 fencing itself after
>>> node2 being fenced
>>> 
>>> 18.02.2014 19:49, Asgaroth wrote:
>>>>> i sometimes have the same situation. sleep ~30 seconds between
>>>>> startup cman and clvmd helps a lot.
>>>>> 
>>>> 
>>>> Thanks for the tip, I just tried this (added sleep 30 in the
>>>> start section of case statement in cman script, but this did not
>>>> resolve the issue for me), for some reason clvmd just refuses to
>>>> start, I don’t see much debugging errors shooting up, so I cannot
>>>> say for sure what clvmd is trying to do :(
>> 
>> I actually just made a patch related to this. If you are managing the
>> dlm with pacemaker, you'll want to use this patch. It disables
>> startup fencing in the dlm and has pacemaker perform the fencing
>> instead. The agent checks the startup fencing condition, so you'll
>> need that bit as well instead of just disabling startup fencing in
>> the dlm.
> 
> Asgaroth said earlier that dlm and clvmd starts from init scripts now in
> that install, so RA magic would not help, but it is great to know about
> this feature.

The agent David is talking about applies to corosync2/rhel7.

> I'd try to disable startup fencing in cman/dlm and look if it helps.
> Something weird is happening there. I cannot simulate similar symptoms
> in my setups, but I run on corosync2, manage everything with pacemaker,
> and have startup fencing disabled in dlm.
> 
>> 
>> -- Vossel
>> 
>>> Just a guess. Do you have startup fencing enabled in dlm-controld
>>> (I actually do not remember if it is applicable to cman's version,
>>> but it exists in dlm-4) or cman? If yes, then that may play its
>>> evil game, because imho it is not intended to use with pacemaker
>>> which has its own startup fencing policy (if you redirect fencing
>>> to pacemaker).
>>> 
>>> _______________________________________________ Pacemaker mailing
>>> list: Pacemaker at oss.clusterlabs.org 
>>> http://oss.clusterlabs.org/mailman/listinfo/pacemaker
>>> 
>>> Project Home: http://www.clusterlabs.org Getting started:
>>> http://www.clusterlabs.org/doc/Cluster_from_Scratch.pdf Bugs:
>>> http://bugs.clusterlabs.org
>>> 
>> 
>> _______________________________________________ Pacemaker mailing
>> list: Pacemaker at oss.clusterlabs.org 
>> http://oss.clusterlabs.org/mailman/listinfo/pacemaker
>> 
>> Project Home: http://www.clusterlabs.org Getting started:
>> http://www.clusterlabs.org/doc/Cluster_from_Scratch.pdf Bugs:
>> http://bugs.clusterlabs.org
>> 
> 
> 
> _______________________________________________
> Pacemaker mailing list: Pacemaker at oss.clusterlabs.org
> http://oss.clusterlabs.org/mailman/listinfo/pacemaker
> 
> Project Home: http://www.clusterlabs.org
> Getting started: http://www.clusterlabs.org/doc/Cluster_from_Scratch.pdf
> Bugs: http://bugs.clusterlabs.org

-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 841 bytes
Desc: Message signed with OpenPGP using GPGMail
URL: <https://lists.clusterlabs.org/pipermail/pacemaker/attachments/20140219/cfcd559c/attachment-0003.sig>