ip_monitor jobs dying??

Phil Boardman (phil@gi.net)
Mon, 3 Mar 1997 11:17:26 -0600 (CST)

I seem to have run into a problem with an ip_monitor job persistently dying.
I know the job is invoked because one of the nodes in the job shows up as
unreachable. I noticed that normally, when something causes a job to die,
the xterm I started tkined in is flooded with error messages. However,
I do not receive any indicators for this particular problem.

The only relevant information I have been able to obtain is that it is the same
job everytime (job0), and the job is started (I get a message that the node is
unreachable). Is there a way to invoke some kind of debugging durring the
procedure?

It should be noted that the ip_monitor script that I am using is a modified
brunel_ip_monitor.tcl. However, I do not believe that my modifications could
be causing the problem, for during multiple instances of running tkined, I had
various nodes that were unreachable, and only 1 job, the same job, was deleted
everytime. And, although I made some modifications, every important variable
was followed by an '[if info exists $var]' routine, so that should not be
causing the job to die.

I guess what I am looking for is any info on how to further debug this problem,
or any helpful suggestions. If you would like a copy of my modified monitor
script, let me know and I will make it available.

Thanks much.

-phil

--
!! This message is brought to you via the `tkined & scotty' mailing list.
!! Please do not reply to this message to unsubscribe. To subscribe or
!! unsubscribe, send a mail message to <tkined-request@ibr.cs.tu-bs.de>.
!! See http://wwwsnmp.cs.utwente.nl/~schoenw/scotty/ for more information.