> It will reboot the other node if you have a STONITH device configured. > Do you have one?
No, I don't. Yes I know, I need a stonith device but I don't have a real one yet. Anyway even without should the node which is not able to stop its resources not reboot voluntary?? I mean instead of ignoring this fault?! Is there a way to do this? Cheers, Holger > > On Thu, Feb 28, 2008 at 12:16 PM, <[EMAIL PROTECTED]> wrote: >> Hi, >> >> I read at http://www.linux-ha.org/HeartbeatResourceAgent that >> "After repeated stop failures, we will do a status on the resource. If >> the >> status reports that the resource is still running, then we will reboot >> the >> machine to make sure things are really stopped." >> >> I have a 2 node cluster and the nodes are connected per >> Ata-over-Ethernet >> to some Filesystems. Each resource depends on pingd and will be stopped >> if >> there is no connectivity. >> >> So when I disconnect node mrbrown from the network I'll get a >> split-brain >> condition. Because of the pingd constraint mrbrown tries to stop the >> Filesystem-resource. This will timeout or produce errors because the >> Filesystem is not reachable. >> But mrbrown doesn't reboot as it should. It case of ignores that >> error?!? >> Did I made a mistake? >> >> Btw. there is no real stonith device at the moment, just ssh and this >> will >> not work without network. You can find some output of mrbrown in close. >> >> Any help is really appreciated.. >> Cheers, >> Holger >> >> _______________________________________________ >> Linux-HA mailing list >> [email protected] >> http://lists.linux-ha.org/mailman/listinfo/linux-ha >> See also: http://linux-ha.org/ReportingProblems >> > > > > -- > Serge Dubrouski. > _______________________________________________ > 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
