ken@cs.cornell.edu (Ken Birman) (06/25/91)
Received: from eola.cs.ucf.edu by cloyd.cs.cornell.edu (5.65/I-1.98N)
id AA12414; Mon, 24 Jun 91 13:30:54 -0400
Received: by eola.cs.ucf.edu (5.61/1.34)
id AA28275; Mon, 24 Jun 91 17:28:23 GMT
Date: Mon, 24 Jun 91 17:28:23 GMT
From: amit@eola.cs.ucf.edu (Amit Jain)
Message-Id: <9106241728.AA28275@eola.cs.ucf.edu>
To: isis@cs.cornell.edu
Hi
We have isis running on DECstation 3100 and SPARCstations. On the
3100 isis seems to get stuck after running for somw time. When
I execute "cmd" I get the message "connect failed isis is not
currently running" even though all the isis processes are running.
Also when I do cmd from the Sparcstation it shows the 3100
in the list of sites up. Is there a fix for this problem?
Amit
------- End of Forwarded Message
& m amit@eola.cs.ucf.edu
Subject: Re: isis gets sytuck sometimes
Two possible explanations:
1) Someone might be deleting the file /tmp/Isxxxx (xxx = port number)
which is how programs connect to ISIS. Without this file, ISIS is up
but cannot be accessed.
If this is the case, either change the name to /tmp/isis/Isxxxx (and
create the directory /tmp/isis), or change ISIS to not use UNIX_DOM
(delete #define from pr.h and isis.h)
2) Or, perhaps this is the famous "24 day timer". After ISIS is up
for 24 days on one machine, it enters an infinite loop. Fixed in V3.0.
Work-around: reboot the isis system now and then.
--
Kenneth P. Birman E-mail: ken@cs.cornell.edu
4105 Upson Hall, Dept. of Computer Science TEL: 607 255-9199 (office)
Cornell University Ithaca, NY 14853 (USA) FAX: 607 255-4428