[Linux-HA] After restart of primary node secondary ist shutdown

Peter Weiss Peter.Weiss at ConSol.de
Tue Mar 22 09:13:07 MST 2005


Peter Weiss <Peter.Weiss at consol.de> writes:

> Hi,
>
> I've no idea why the first node shuts down the second in this configuration
> (auto_failback is off) after restarting heartbeat facilities:
>
> keepalive 2
> deadtime 45
> warntime 10
> initdead 120
>
> stonith_host itaibi09 external foo /etc/ha.d/stonith.ibmrsa -h rsa-itaibi12 -c "power off"
> stonith_host itaibi12 external foo /etc/ha.d/stonith.ibmrsa -h rsa-itaibi09 -c "power off"
>
> # What interfaces to broadcast heartbeats over?
> ucast eth0 10.250.22.118
> ucast eth1 192.168.22.2
> udpport 694
> auto_failback off
>
> # Tell what machines are in the cluster
> node itaibi09
> node itaibi12
>
> # external ping address to test network
> # (10.250.22.104 is the ip address of one of the nodes of the hp cluster)
> ping 10.250.22.1
> respawn hacluster /usr/lib64/heartbeat/ipfail
>
> Failover itaibi09 -> itaibi12 works:
> [...]
> Mar 21 14:54:37 itaibi09 heartbeat[10906]: info: Core process 10913 exited. 2 remaining
> Mar 21 14:54:37 itaibi09 heartbeat[10906]: info: Core process 10914 exited. 1 remaining
> Mar 21 14:54:37 itaibi09 heartbeat[10906]: info: Heartbeat shutdown complete.
> [...]
>
> And on the second node: Why these messages Link itaibi09/eth0 now has status
> dead ??
>
> [...]

Or in other words, to be more precise:

Is there a ha.cf tunable that prevents the primary node to stonith the
secondary if it comes up and the services are on the second node?

(With allways auto_failback set to off)

TIA -- Peter

-- 
BMW Group
Peter Weiss
FZ-33  IT Lösungen - Hardware- und  Netzwerkkomponenten
Telefon: +49-89-382-11538
mailto: Peter.WA.Weiss at Partner.bmw.de




More information about the Linux-HA mailing list