[Linux-ha-dev] Heartbeat 0.45 experiences
Alan Robertson
alanr@bell-labs.com
Wed, 20 Oct 1999 23:29:13 -0600
Hi Thomas,
Thomas Hepper wrote:
>
> Hi,
> On Mon, Oct 18, 1999 at 06:16:23PM -0600, Alan Robertson wrote:
> >
> > The two things I thought of for debugging this are:
> >
> > 1) do the "resource-script status" for the resources you think
> > it should give up before restarting the master. You can
> > do this at any time. Any time it doesn't show the
> > "running" on the right resources, things are broken.
> > Maybe I should do this after taking over any resources.
>
> Not tested yet, will do it
>
> > 2) Turn on debug to level 5 (5 SIGUSR1's) on the slave
> > just before restarting the master. After the master
> > has restarted (a minute or two elapsed), you can run
> > the debug level back down again on the slave.
> >
> OK did it. I have attached my debug files from different tests.
>
> One strange thing is that on startup, heartbeat is started by init,
> it does not work. Either it hangs, or it thinks himself is dead (see the logs).
I'm going to ignore this for now. We'll come back to it later... I suspect
SIGSTOP.
> If i stop it in the normal root shell, and start it again it will take
> the resources, and the slave will release it .....
Your debug files were a little strange...
In particular, I noticed that every time /etc/ha.d/rc.d/ip-request-resp was
invoked, it gave a usage message. It shouldn't ever do that. Maybe it didn't
get installed correctly on Debian?
Could you add
set -x
echo "$0: $# arguments: " $* >&2
env >&2
to the top of this script and send me the output when you run it again?
Thanks!
-- Alan Robertson
alanr@bell-labs.com