Date: Mon, 7 Jul 1997 15:54:23 -0700 (PDT) From: David Lowe <dlowe@sirius.com> To: freebsd-questions@freebsd.org Subject: Logging kernel panics Message-ID: <Pine.NXT.3.95q.970707152905.13964A-100000@ds9>
next in thread | raw e-mail | index | archive | help
People - I'm trying to find a nice way of discovering the causes of kernel panics, post-mortem. Details: A news server, which is running beautifully except that twice now it has rebooted without any hints in the logfiles. We'd really like to figure out what is going on - but we don't want to have to go down to the remote site where the server lives, to look at the console in order to figure out the cause of the crashes (while the server remains out of service...) Is there some fairly reliable way of storing panic messages, short of logging all console output via a serial port? We already have a serial console, but the darned thing doesn't have any logging at all. A quick glance through the -questions archives shows me that setting savecore_enable="YES" in rc.conf might do the trick. Anything I should know about this option? If I set this to yes, how might I find out the cause of a panic from the dump? Any other/better ideas? I assume this will not work if the root filesystem is fubared... but it would be better than nothing. Muchas gracias, David Lowe
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?Pine.NXT.3.95q.970707152905.13964A-100000>