From owner-freebsd-stable@FreeBSD.ORG Thu May 15 09:55:53 2008 Return-Path: Delivered-To: freebsd-stable@FreeBSD.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 45312106564A for ; Thu, 15 May 2008 09:55:53 +0000 (UTC) (envelope-from nb@ravenbrook.com) Received: from raven.ravenbrook.com (raven.ravenbrook.com [193.164.110.8]) by mx1.freebsd.org (Postfix) with ESMTP id CBA958FC12 for ; Thu, 15 May 2008 09:55:52 +0000 (UTC) (envelope-from nb@ravenbrook.com) Received: from thrush.ravenbrook.com (thrush.ravenbrook.com [193.164.110.145]) by raven.ravenbrook.com (8.13.8/8.13.8) with ESMTP id m4F9toJh081211; Thu, 15 May 2008 10:55:50 +0100 (BST) (envelope-from nb@ravenbrook.com) Received: from thrush.ravenbrook.com (localhost [127.0.0.1]) by thrush.ravenbrook.com (8.13.4/8.13.4) with ESMTP id m4F9toOe060462; Thu, 15 May 2008 10:55:50 +0100 (BST) (envelope-from nb@thrush.ravenbrook.com) From: Nick Barnes To: Jeremy Chadwick In-Reply-To: <20080515094632.GA2738@eos.sc1.parodius.com> from Jeremy Chadwick of "Thu, 15 May 2008 02:46:32 -0700" Date: Thu, 15 May 2008 10:55:50 +0100 Message-ID: <60461.1210845350@thrush.ravenbrook.com> Sender: nb@ravenbrook.com X-Virus-Scanned: ClamAV 0.92.1/6882/Tue Apr 22 18:33:01 2008 on raven.ravenbrook.com X-Virus-Status: Clean X-Spam-Checker-Version: SpamAssassin 3.2.3 (2007-08-08) on raven.ravenbrook.com X-Spam-Level: X-Spam-Status: No, score=-3.7 required=5.0 tests=ALL_TRUSTED,AWL,BAYES_00 autolearn=ham version=3.2.3 Cc: freebsd-stable@FreeBSD.org Subject: Re: syslog console log not logging SCSI problems X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 15 May 2008 09:55:53 -0000 At 2008-05-15 09:46:32+0000, Jeremy Chadwick writes: > On Thu, May 15, 2008 at 10:14:01AM +0100, Nick Barnes wrote: > > One of our FreeBSD boxes has a SCSI controller and disk, which showed > > problems earlier this week. There was a lot of of chatter from the > > SCSI driver in /var/log/messages and to the console. However, the > > console is unattended and we only discovered the problem subsequently > > because /var/log/console.log didn't show any of the chatter. > > > > console.log is otherwise working, and very helpful (e.g. it shows > > /etc/rc output at boot which lets us spot daemon failures). > > > > We've rebuilt the machine now (fan failure leading to boot disk > > failure), so I can't report the SCSI chatter in question, but here is > > the dmesg and syslog.conf. Any suggestions? > > /boot/loader.conf, /boot.config, and /etc/make.conf would also be > useful. All empty, except setting kern.maxdsiz in /boot/loader.conf. Running GENERIC. If this happens again, I will retain a copy of /var/log/messages so I can report the SCSI messages in question, but they aren't as interesting to me as the fact that they didn't appear in console.log. Nick B