From owner-freebsd-hardware@FreeBSD.ORG Sun Mar 5 19:23:44 2006 Return-Path: X-Original-To: freebsd-hardware@freebsd.org Delivered-To: freebsd-hardware@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 6857316A420 for ; Sun, 5 Mar 2006 19:23:44 +0000 (GMT) (envelope-from jhs@flat.berklix.net) Received: from thin.berklix.org (thin.berklix.org [194.246.123.68]) by mx1.FreeBSD.org (Postfix) with ESMTP id C391943D46 for ; Sun, 5 Mar 2006 19:23:43 +0000 (GMT) (envelope-from jhs@flat.berklix.net) Received: from js.berklix.net (p549A56BD.dip.t-dialin.net [84.154.86.189]) (authenticated bits=128) by thin.berklix.org (8.12.11/8.12.11) with ESMTP id k25JNaaK011598; Sun, 5 Mar 2006 20:23:41 +0100 (CET) (envelope-from jhs@flat.berklix.net) Received: from fire.jhs.private (fire.jhs.private [192.168.91.41]) by js.berklix.net (8.12.11/8.12.11) with ESMTP id k25JNViR031432; Sun, 5 Mar 2006 20:23:31 +0100 (CET) (envelope-from jhs@flat.berklix.net) Received: from fire.jhs.private (localhost.jhs.private [127.0.0.1]) by fire.jhs.private (8.13.1/8.13.1) with ESMTP id k25JR0sl043971; Sun, 5 Mar 2006 20:27:00 +0100 (CET) (envelope-from jhs@fire.jhs.private) Message-Id: <200603051927.k25JR0sl043971@fire.jhs.private> To: "FreeBSD" In-Reply-To: Message from "FreeBSD" of "Sat, 04 Mar 2006 19:14:24 EST." <1141517664.1407@swaggi.com> Date: Sun, 05 Mar 2006 20:26:59 +0100 From: "Julian H. Stacey" Cc: freebsd-hardware@freebsd.org Subject: Re: FreeBSD shutting down unexpectedly X-BeenThere: freebsd-hardware@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: General discussion of FreeBSD hardware List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 05 Mar 2006 19:23:44 -0000 > I'm having a problem with my FreeBSD server shutting down for no reason. This started happening recently (within the last month) so I'm not sure if the hardware is dying or if there's another underlying problem. The server is a rackmountable 1U chassis at a remote location connected to an APC UPS. When I lose connectivity and go to physically inspect the server, it's powered off completely as if there was a power outage. However, each time I can confirm that the UPS did not lose power and there were no voltage spikes (the APC can be managed via telnet and SNMP so there are logs I can look at). So far the only way I've been able to reproduce the problem is by running "portsdb -Uu" to update the ports DB after a cvsup of the ports tree. I suppose this is a CPU/disk intensive task so maybe I have a dying hard drive? Running this command used to take about 10 minutes for me, now when I run it about 5 minutes later the box powers off mysteriously. There's nothing in /var/log/messa Please prune your line length ! APC can also be controlled & logged by NUT /usr/ports/sysutils/nut > ges and after I bring it back up, dmesg does not show anything unusual. I setup a console server to monitor this server's console but there was absolutely nothing on the console during the last such "crash". > I'm looking for some suggestions on how to troubleshoot this problem, perhaps I can enable crash dump files or some sort of debugging? Here's some output: Maybe your CPU or chassis fan is sticky/ slow/ dead. You can check your running temps withn other things in /usr/ports/sysutils/ > Any suggestions would be welcome. Good luck. -- Julian Stacey. Consultant Unix Net & Sys. Eng., Munich. http://berklix.com Mail in Ascii, HTML=spam. Ihr Rauch = meine allergischen Kopfschmerzen.