Date: Wed, 23 May 2007 17:58:18 -0400 From: Kris Kennaway <kris@obsecurity.org> To: Volker <volker@vwsoft.com> Cc: rmiranda@digitalrelay.ca, freebsd-stable@FreeBSD.ORG Subject: Re: ghosthunting: machine freeze 6.2R Message-ID: <20070523215818.GB64723@xor.obsecurity.org> In-Reply-To: <4654C0C4.2030405@vwsoft.com> References: <200705230717.l4N7HuPW010071@lurza.secnetix.de> <465408F9.6080302@vwsoft.com> <4654C0C4.2030405@vwsoft.com>
next in thread | previous in thread | raw e-mail | index | archive | help
On Wed, May 23, 2007 at 11:31:32PM +0100, Volker wrote: > talking to myself... ;) > > On 2007-05-23 10:27, Volker wrote: > > Currently I'm watching this machine over the distance and waiting for the freeze... > > ...and the machine freeze came this afternoon. I've had a good dump > of the network traffic and haven't seen any strange network traffic. > Unfortunately three hours later, the machine died completely. It has > been a hardware failure which came quietly. > > Sorry for the noise I've put on this list but when experiencing > things like that, one has to think in all possible directions (I > first thought about a DoS attack). Even though it turned out to be a hardware failure, it was helpful to publicize this fact. It is often difficult to convince users to accept the possibility that hardware failure may be the cause of weird system behaviour, because "it has always been fine". It is worth remembering that if your hardware is going to fail, then there is going to be a first time. Kris
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20070523215818.GB64723>