Re: Identifying cause of crash
On Apr 17, 2007, at 11:45 AM, Jeffrey Goldberg wrote: Is there some setting I should set so that in future crashes will be dumped there [/var/crash]? Never mind, I've just found what I needed in man rc.conf, I've now set dumpdev and dumpdir in rc.conf and am rebuilding the kernel with debugging. It's been a long time since I've looked at a core dump, and I don't think I've ever looked at a kernel dump. And now I'm not sure whether I want the system to crash again (so that I can try to figure out what the problem is) or not. Cheers, -j -- Jeffrey Goldberghttp://www.goldmark.org/jeff/ ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: Identifying cause of crash
On Apr 17, 2007, at 11:22 AM, Robert Huff wrote: Jeffrey Goldberg writes: I had a complete system crash this morning sometime shortly after 17/Apr/2007:08:51:22 -0500. (from my most active apache log). I can't seem to find any information whatsoever about the crash. Is there anything in /var/crash? Thanks! I didn't know about that place to look. Unfortunately there is nothing useful there either. There is only a file called minfree dated from January. minfree is a text file containing 2048 Is there some setting I should set so that in future crashes will be dumped there? Let me also add that the system is on an APC UPS and another machine that is on the same UPS logs no UPS events since the thunderstorms that hit the area on Friday. -j -- Jeffrey Goldberghttp://www.goldmark.org/jeff/ ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: Identifying cause of crash
On Tue, Apr 17, 2007 at 11:16:17AM -0500, Jeffrey Goldberg wrote: > I had a complete system crash this morning sometime shortly after 17/ > Apr/2007:08:51:22 -0500. (from my most active apache log). > > I can't seem to find any information whatsoever about the crash. > It's just that a few hours later I noticed that the system was down, > and had to power cycle the box. There was nothing on the console > except some much older stuff. > > I'm running 6.2-RELEASE-p3 on VIA C3 Nehemiah (999.52-MHz 686-class CPU) > > Looking in messages or auth.log I see nothing from around the time of > the crash. Is there some place else I should look? I've also > checked logs that are sysloged remotely > > $ grep '@10' /etc/syslog.conf > *.err;kern.warning;auth.notice;mail.crit@10.1.10.131 > security.* @10.1.10.131 > auth.info;authpriv.info @10.1.10.131 > *.emerg @10.1.10.131 > > And there is nothing from near the time of the crash there either. > > So the system appeared to crash before anything could be logged. > > The system has been running fine since I've had it (a few months > ago), and my most recent kernel rebuild was on April 13 (and then > only to add msdosfs which I needed for USB memory devices). > > Where should I look next? Unless you have enabled crashdumps nothing will be logged. If you did, or to learn how, see the chapter on kernel debugging in the developers' handbook. Kris pgpU3GsSLa3DC.pgp Description: PGP signature
