[Pacemaker] will online node shoots the standby node when no cluster services?

[Andrew Beekhof]

On Tue, Nov 13, 2012 at 7:28 AM, Arnold Krille <arnold at arnoldarts.de> wrote:
> On Friday 19 October 2012 10:25:32 Andrew Beekhof wrote:
>> On Fri, Oct 19, 2012 at 3:29 AM, Arnold Krille <arnold at arnoldarts.de> wrote:
>> > On Thursday 18 October 2012 11:24:25 Andrew Beekhof wrote:
>> >> On Thu, Oct 18, 2012 at 9:58 AM, Arnold Krille <arnold at arnoldarts.de>
> wrote:
>> >> > On Wed, 17 Oct 2012 14:21:24 -0400 Digimer <lists at alteeve.ca> wrote:
>> >> >> On 10/17/2012 02:10 PM, Jean-Francois Malouin wrote:
>> >> >> > Hi,
>> >> >> >
>> >> >> > A simple question for a simple 2-nodes cluster running
>> >> >> > pacemaker-1.0.9, corosync-1.2.1 (Debian/Squeeze):
>> >> >> >
>> >> >> > will the online node stonith the other standby node if I stop the
>> >> >> > cluster services on it? (I need to open the chassis)
>> >> >> >
>> >> >> > thanks!
>> >> >> > jf
>> >> >>
>> >> >> No.
>> >> >>
>> >> >> The idea behind fencing is to restore a node to a known state. If you
>> >> >> gracefully shutdown the cluster stack, then it is able to inform the
>> >> >> peer node that it is leaving and will not be offering any clustered
>> >> >> services. Thus, it is in a known state and all is fine.
>> >> >
>> >> > If my understanding is correct, the same applies when you "only" put
>> >> > the node in standby?
>> >> > At least I couldn't manually fence the node long after I did put it to
>> >> > standby...
>> >>
>> >> That doesn't sound right.  How did you try and fence it?
>> >
>> > "crm node fence nebel2", where nebel2 is the host concerned and currently
>> > the only one with a working ipmi-implementation on the mobo.
>>
>> Hmmm, I'm not familiar with that command. Do you know how it is
>> supposed to work?
>> Depending on your version you might have more luck with: stonith_admin
>> --fence nebel2
>> This bypasses the CIB+PE+CRMD and goes straight to the fencing subsystem.
>
> I finally got around to testing this (got yet another major network reordering
> here and now ipmi seems to work correctly). Unfortunately executing the above
> command on nebel2 kills nebel1 (should have killed nebel2)...
>
> Any more ideas?


Your stonith configuration (in pacemaker or the switch itself) must be wrong.