On Mon, Apr 23, 2007 at 04:08:46PM +0200, Max Hofer wrote:
> I think i want the same functioanlity as Christopher wants:
> 
> * when a resource on a node goes into FAILED state, reboot the machine
> (currently we have no STONITH device - i know, it is insecure but i have to 
> use
> what i have)
> 
> Heartbeat version 2.0.8
> 
> Situation:
> * 2 node cluster
> * dummy-resource provided by heartbeat runs on management2
> * DC management1
> 
> Actions:
> * touch /tmp/Dummy.monitor /tmp/Dummy.stop --> in this way monitor and stop 
> opeartion fails
> 
> Afterwards:
> * dummy-resource does not run anywhere
> * stonithd seems to core dump

Seems? If this is on Linux, please do

# ulimit -c unlimited (from the same terminal, before starting the heartbeat)
# echo 1 > /proc/sys/kernel/core_uses_pid

Then you'll have the core dumps. That'd be nice (that's not to say
that core dumps are nice to have, but, well, you get my point :)

> * reboot of management2 failed (?? may this be because the stonithd core 
> dumps?)
> * "etc/init.d/heartbeat stop" on management2 hangs forever
> 
> Here the attached CIB, pe-warn* from management1 and ha-log of both machine.

Don't see the CIB, though I can see them in the pe-input*.
cibadmin -Q would be good too. ha.cf perhaps too.

Have you read this one: http://linux-ha.org/ReportingProblems ?

> Do i something wrong with the stonith device?

This is what I see:

lrmd[1319]: 2007/04/23_15:43:46 info: Try to start STONITH resource 
<rsc_id=child-do-reboot:1> : Device=suicide
stonithd[1274]: 2007/04/23_15:43:46 ERROR: Could not list nodes for stonith RA 
suicide.

Never used the suicide agent, so can't comment further now, but
there's definitely sth wrong here. Perhaps the agent's broken?

Alan, looks like we need stonith idioms too :)

Thanks.

> On Tuesday 17 April 2007 15:07, Dave Blaschke wrote:
> > Christophe Zwecker wrote:
> > > Dave Blaschke wrote:
> > >> Christophe Zwecker wrote:
> > >>> Dave Blaschke wrote:
> > >>>> Christophe Zwecker wrote:
> > >>>>> Hi Dave,
> > >>>>>
> > >>>>> its this:
> > >>>>>
> > >>>>> grep mw-test /etc/ha.d/ha.cf
> > >>>>> node    mw-test-n1.i-dis.net
> > >>>>> node    mw-test-n2.i-dis.net
> > >>>>>
> > >>>>> [EMAIL PROTECTED] ~]# uname -n
> > >>>>> mw-test-n2.i-dis.net
> > >>>>>
> > >>>> And your cib.xml?
> > >>>>>
> > >>>
> > >>>  grep mw-test /var/lib/heartbeat/crm/cib.xml
> > >>>        <node uname="mw-test-n1.i-dis.net" type="normal" 
> > >>> id="5b1a3c52-a893-44c5-a9c7-035fc632ff8d">
> > >>>        <node uname="mw-test-n2.i-dis.net" type="normal" 
> > >>> id="cc1c8955-58d2-4ee3-8e98-b07599335e0c">
> > >>>            <expression attribute="#uname" 
> > >>> id="prefered_location_group_1_expr" operation="eq" 
> > >>> value="mw-test-n1.i-dis.net"/>
> > >>>
> > >> I'd actually like to see the whole thing please...
> > >
> > >
> > > here ya go, sorry for the delay i was on vacation!
> > Ahh, vacation.  Okay, envying over... :-)
> > 
> > I don't proclaim to be a R2 config expert, but I'm pretty sure you'll 
> > need something similar to the following in your CIB to tell heartbeat 
> > how to STONITH:
> > 
> > <primitive id="child_DoFencing" class="stonith" type="suicide" 
> > provider="heartbeat">
> > 
> > You won't need any attributes for suicide, you'll need a hostlist if you 
> > choose to use ssh.  See 
> > http://www.linux-ha.org/ConfiguringStonithPlugins for the full XML sample.
> > >
> > > thx alot for your input and time
> > >
> > > Christophe
> > 
> > _______________________________________________
> > Linux-HA mailing list
> > [email protected]
> > http://lists.linux-ha.org/mailman/listinfo/linux-ha
> > See also: http://linux-ha.org/ReportingProblems
> > 
> 










> _______________________________________________
> Linux-HA mailing list
> [email protected]
> http://lists.linux-ha.org/mailman/listinfo/linux-ha
> See also: http://linux-ha.org/ReportingProblems

-- 
Dejan
_______________________________________________
Linux-HA mailing list
[email protected]
http://lists.linux-ha.org/mailman/listinfo/linux-ha
See also: http://linux-ha.org/ReportingProblems

Reply via email to