ipfail works with v1 only. For v2 you need to use pingd. On Wed, Aug 20, 2008 at 11:02 PM, Jai <[EMAIL PROTECTED]> wrote: > Hi, > > I'm interested to know if it is possible to run multiple respawn directives > in ha.cf? For example: > > # Heartbeat logging configuration > #logfacility daemon > use_logd on > > # Heartbeat cluster menbers > coredumps yes > crm no > auto_failback on > node hosta hostb > > # Heartbeat communication timing > keepalive 1 > warntime 10 > deadtime 30 > initdead 120 > > # Heartbeat communication paths > udpport 694 > bcast eth1 > # syntax: mcast dev mcast-group udp-port ttl 1 > mcast eth0 239.0.0.1 694 1 1 > > # Monitoring of network connection to default gateway > ping 10.10.11.254 > respawn hacluster /usr/lib/heartbeat/ipfail > apiauth ipfail gid=haclient uid=hacluster > > respawn hacluster /usr/lib/heartbeat/dopd > apiauth dopd gid=haclient uid=hacluster > > My reason for asking is that with this configuration there i see no errors > while running heartbeat, however during testing, if the gateway interface > (10.10.11.254) disappears from one server but the other can still see it, it > fails over as expected. But after about 5 minutes it fails back > (auto_failback on), even though the gateway is still not visible from that > server. > > # rpm -q heartbeat > heartbeat-2.1.4-1.1 > > _______________________________________________ > 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
