Path: utzoo!utgpu!jarvis.csri.toronto.edu!cs.utexas.edu!yale!ox.com!oxtrap!oxtrap!tc From: tc@oxtrap.aa.ox.com (Tse Chih Chao) Newsgroups: comp.sys.isis Subject: Re: isis start up probs on SUN4 Message-ID: Date: 1 Mar 90 18:45:50 GMT References: <1200@swbatl.UUCP> <37894@cornell.UUCP> Sender: tc@oxtrap.aa.ox.com (Tse Chih Chao) Organization: Ocwen Trading Inc. - Ann Arbor, MI Lines: 40 In-Reply-To: ken@gvax.cs.cornell.edu's message of 28 Feb 90 15:18:29 GMT In article <37894@cornell.UUCP> ken@gvax.cs.cornell.edu (Ken Birman) writes: In article <1200@swbatl.UUCP> jmd@swbatl.UUCP (03) writes: > > I have been using isis for several months without problems >on a sun 3/260 platforms however as we near closer to implentation i have ported >to the sun 4/390 servers and am getting the following start up probs I can't >seem to figure out. Could any of you take a look and point me in the >right direction. Below is the log file. help! > >****************LOG FILE ********************** >Mon Feb 26 13:32:54 1990 >ISIS release V1.2, June 1989 >Site is now coming up, site-id 13, isis_dir <./13.logdir> >Detect site-failure after: 60 secs This one may not be vital. It often revives itself. >calvin (13/128): -- panic -- This is the critical one. A timestamp from isis would be very usefull. Another suggestion for the isis group is to add the timestamps for the proto's core dumps in the log file. Although the timestamp of the file will help, but not always, if there are several dumps in the file. >isis monitoring process at this site has crashed! >... etc (remainder is not relevant to problem) I have been working on crash problems for running isis on a DEC 3100 (Ultrix V2.2). After some research/experiments, it now points to Ultrix UDP related or name service problems (not an isis problem). Isis used to crash on "not enough cores", "not getting enough bytes", "panic". I rarely got core files, although I did get it once or twice. What happens was that I got stray messages and Ken told me how to detect them. I doubt that you have the same problem, becuase isis runs fine on our sun 3/50's. If you didn't have a core file, then my suggestion is to invoke isis from the debugger and you can tell where it crashed. If not, the old fashioned printf's and breakpoints should be able to help.