From owner-freebsd-questions@FreeBSD.ORG Tue Jun 5 13:34:00 2007 Return-Path: X-Original-To: freebsd-questions@FreeBSD.ORG Delivered-To: freebsd-questions@FreeBSD.ORG Received: from mx1.freebsd.org (mx1.freebsd.org [69.147.83.52]) by hub.freebsd.org (Postfix) with ESMTP id E96B916A46D for ; Tue, 5 Jun 2007 13:34:00 +0000 (UTC) (envelope-from freebsd-questions-local@be-well.ilk.org) Received: from mail7.sea5.speakeasy.net (mail7.sea5.speakeasy.net [69.17.117.9]) by mx1.freebsd.org (Postfix) with ESMTP id BF76D13C469 for ; Tue, 5 Jun 2007 13:34:00 +0000 (UTC) (envelope-from freebsd-questions-local@be-well.ilk.org) Received: (qmail 23880 invoked from network); 5 Jun 2007 13:34:00 -0000 Received: from dsl092-078-145.bos1.dsl.speakeasy.net (HELO be-well.ilk.org) ([66.92.78.145]) (envelope-sender ) by mail7.sea5.speakeasy.net (qmail-ldap-1.03) with SMTP for ; 5 Jun 2007 13:34:00 -0000 Received: from Lowell-Desk.lan (Lowell-Desk.lan [172.30.250.6]) by be-well.ilk.org (Postfix) with ESMTP id F3F702843A; Tue, 5 Jun 2007 09:33:56 -0400 (EDT) Received: by Lowell-Desk.lan (Postfix, from userid 1147) id 47ADC1CCA9; Tue, 5 Jun 2007 09:33:56 -0400 (EDT) To: Paul Hoffman References: From: Lowell Gilbert Date: Tue, 05 Jun 2007 09:33:56 -0400 In-Reply-To: (Paul Hoffman's message of "Mon\, 4 Jun 2007 08\:18\:07 -0700") Message-ID: <44y7iyr0e3.fsf@Lowell-Desk.lan> User-Agent: Gnus/5.11 (Gnus v5.11) Emacs/22.0.99 (berkeley-unix) MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Cc: freebsd-questions@FreeBSD.ORG Subject: Re: Short HOWTO on reading a core to determine why my server is rebooting? X-BeenThere: freebsd-questions@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list Reply-To: freebsd-questions@FreeBSD.ORG List-Id: User questions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 05 Jun 2007 13:34:01 -0000 Paul Hoffman writes: > Hi again. I have a server running 6.0 that has been spontaneously > rebooting every few weeks. Is there a short HOWTO that tells me how to > read the files in /var/crash to at least find out what the kernel > thinks the issue is? There is nothing in /var/log/messages of interest > before the crash, nothing in 'dmesg -a' in coming up that says > anything interesting, and there's plenty of room on the drives. There is some information in developers' handbook. The FAQ entry about looking at kernel panics might help also.