syslog console log not logging SCSI problems
Nick Barnes
Nick.Barnes at pobox.com
Thu May 15 09:55:53 UTC 2008
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
More information about the freebsd-stable
mailing list