Date: Thu, 15 May 2008 10:55:50 +0100 From: Nick Barnes <Nick.Barnes@pobox.com> To: Jeremy Chadwick <koitsu@FreeBSD.org> Cc: freebsd-stable@FreeBSD.org Subject: Re: syslog console log not logging SCSI problems Message-ID: <60461.1210845350@thrush.ravenbrook.com> In-Reply-To: <20080515094632.GA2738@eos.sc1.parodius.com> from Jeremy Chadwick <koitsu@FreeBSD.org> of "Thu, 15 May 2008 02:46:32 -0700"
next in thread | previous in thread | raw e-mail | index | archive | help
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
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?60461.1210845350>