TCP/IP dies and won't resurrect

Conor P. Cahill cpcahil at virtech.uucp
Sat Sep 29 21:41:48 AEST 1990


In article <533 at denwa.uucp> jimmy at denwa.info.com (Jim Gottlieb) writes:
>The problem is that at random we find that all network services on a
>particular machine have died.  I bring the machine down to init level
>2, then back up to 3.  At this point I get flooded with error messages,
>starting with:

In 386/ix 2.0.2 this is a known bug (as far as I am concerned).  The correct
way to recover from it is to bring the system down (not just to run level 2)
and power cycle the machine (although the power cycle may not be necessary,
but you do have to go all the way down).

>The only solution I've found is to reload Streams, TCP/IP, and NFS in
>that order.  Any better solutions would be welcomed.  Thanks.

You definately shouldn't have to reload.  We had this kind of problem at
least once a week when we were running 2.0.2. 

The real answer is to upgrade to 2.2 where the problem appears to have 
gone away.

-- 
Conor P. Cahill            (703)430-9247        Virtual Technologies, Inc.,
uunet!virtech!cpcahil                           46030 Manekin Plaza, Suite 160
                                                Sterling, VA 22170 



More information about the Comp.unix.sysv386 mailing list