Re: AW: Status of FailSafe on RH7.2 with GLIBC 2.2.4
Nemeth Lorant <[email protected]>
| Newsgroups | gmane.linux.failsafe |
|---|---|
| Message-ID | <[email protected]> |
> > Could you tell me, what kind of patches are these, and where from can > > I get them? > > Sure. A great deal of the ongoing development for linux failsafe is done > by Suse GmbH / Lars Marowsky-Bree (Thanks for the great work!), so suse Thx, for the support :) I've got an WTI RPS-10 type power switch. First I set the sysctrl_type to stonith, and tried to run the following from the CLI: admin reset node labpc2 and admin reset standalone node labpc2 both commands returned with errors (Doesn't now anything about ....) I tried after with 'sysctrl_type to null'. The admin reset node labpc2 command said, that the reset was succesfull, however the powerswitch didn't switched off the other computer. Which is the correct setting, and how do failsafe now, what should he sent via the serial line (^B^X^X^B^X^X00^M or something like that for this powerswitch type). Should be some kind of additional prgram be installed, which communicates with the powerswitch? Lorant Nemeth (Loci) This was the node defiition for the primary node (the same with other IP-s and names for the other): define node labpc1 set hostname to labpc1.inf.mit.bme.hu set is_failsafe to true set nodeid to 1 set sysctrl_type to null set sysctrl_status to enabled set sysctrl_owner to labpc2.inf.mit.bme.hu set sysctrl_device to /dev/ttyS0 set sysctrl_owner_type to tty add nic 152.66.242.71 set heartbeat to true set ctrl_msgs to true set priority to 1 done add nic 192.168.0.1 set heartbeat to true set ctrl_msgs to true set priority to 0 done done I also created a cluster with the 2 nodes.