Return to BSD News archive
Xref: sserve comp.os.386bsd.bugs:2972 comp.os.386bsd.questions:16448 Path: sserve!newshost.anu.edu.au!harbinger.cc.monash.edu.au!msunews!uwm.edu!cs.utexas.edu!swrinde!pipex!peernews.demon.co.uk!demon!awfulhak.demon.co.uk!awfulhak.demon.co.uk!not-for-mail From: brian@awfulhak.demon.co.uk (Brian Somers) Newsgroups: comp.os.386bsd.bugs,comp.os.386bsd.questions Subject: Re: Odd Problem with news server.. Followup-To: comp.os.386bsd.bugs,comp.os.386bsd.questions Date: 6 Feb 1995 02:53:56 -0000 Organization: None Lines: 19 Message-ID: <3h4304$5p@awfulhak.demon.co.uk> References: <3gt436$cd@news.ip.net> NNTP-Posting-Host: awfulhak.demon.co.uk X-Newsreader: TIN [version 1.2 PL2] Mark Imbriaco (mark@taliesin) wrote: : Hi, I'm currently trying to use a FreeBSD-2.0 box as a news server with innd : 1.4sec on our network. I keep having a strange problem where the box will : 'crash' in such a way that it is inaccessable from both the network and the : console. Physically examining the machine while it is in this state reveals : that the hard drive access light is solid on. Previous to the 'crash', the : machine will run fine for a seemingly random amount of time. Anywhere from : 2 hours to 2 days, then /boom!/ Any clues or suggestions would be apprec- : iated! I run a similar setup with no problems. The only answer to this sort of thing that I've seen is dodgy SCSI cabling / termination. Hope it helps -- Brian <brian@awfulhak.demon.co.uk> Don't _EVER_ lose your sense of humour....