Hello, I am a very new user of Linux-HA, as you will quickly realize as you read this. :) We are putting together a system that is not HA in the clustered sense, but does require good availability. We want the system to be able to reboot if it somehow gets extremely hosed/bogged down/whatever, and someone recommended to us that Linux-HA can do that by working with the software watchdog device. So, contrary to all of the examples on the site, we have only 1 "node".
So here's what my ha.cf looks like (mostly defaults): debugfile /var/log/ha-debug logfile /var/log/ha-log logfacility local0 keepalive 5 deadtime 30 warntime 10 initdead 120 udpport 694 bcast eth0 auto_failback off watchdog /dev/watchdog node mynode I have tried running both with an empty haresources file and with an haresources with the following definition: mynode <ip-addr-gotten-via-BOOTP> I have also tried something like: mynode <arbitrary-IP> I am able to get the heartbeat going via "heartbeat start" just fine, but when I issue the "heartbeat stop" command, it just hangs there indefinitely. The ha-log file has the following message: "Shutdown delayed until current resource activity finishes" This seemed especially odd to me when I had an empty haresources file, and therefore no resources. I really don't need heartbeat to be monitoring any of my resources, since I'm not using it to fail over any resources to a second node. I'm really just using it to use the watchdog device. Is heartbeat overkill for what we're trying to do, or should I be able to get a 1-node "cluster" set up and I'm just configuring something wrong? Is there some other tool that I should be using for this purpose? (Told you I was a newbie!) Thanks for any advice, Michael _______________________________________________ Linux-HA mailing list [email protected] http://lists.linux-ha.org/mailman/listinfo/linux-ha See also: http://linux-ha.org/ReportingProblems
