Date: Sun, 4 Aug 1996 15:10:24 -0400 (EDT) From: "Marc G. Fournier" <scrappy@ki.net> To: Michael Smith <msmith@atrad.adelaide.edu.au> Cc: dg@root.com, current@freebsd.org Subject: Re: problem with -current system grinding to a halt... Message-ID: <Pine.NEB.3.95.960804150700.6237C-100000@quagmire.ki.net> In-Reply-To: <199608040859.SAA07448@genesis.atrad.adelaide.edu.au>
next in thread | previous in thread | raw e-mail | index | archive | help
On Sun, 4 Aug 1996, Michael Smith wrote: > David Greenman stands accused of saying: > > > > This can happen if your nameserver isn't reachable. Have you tried "w -n" ? > > This disables the nameserver lookups and is useful for this specific problem. > > Nameserver lookup failures cause the whole system to grind to a halt, > forcing a hard reset? Sorry, I know what nameserver timeouts look like, > and that's not the problem. I wish it was. > > I should have been clearer I guess; the 'w' freeze was coincidental - > the system dies _consistently_ after about 18 hours of uptime, with no > console messages. Regardless of whether I'm logged in or not, and > apparently unrelated to any specific system activity. I say 'apparently' > because it's not easy to see exactly what the system is doing. > This sounds like the SCSI bus hangs I used to get with one of my systems...where everything seemed to be running until you tried to deal with somethin gthat had to go to the drive (ie. login, w, df, etc) When this happens, check your drive...does the hard drive light come on and stay on? Marc G. Fournier scrappy@ki.net Systems Administrator @ ki.net scrappy@freebsd.org
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?Pine.NEB.3.95.960804150700.6237C-100000>