From owner-freebsd-isp Thu Jun 5 14:58:11 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.5/8.8.5) id OAA09547 for isp-outgoing; Thu, 5 Jun 1997 14:58:11 -0700 (PDT) Received: from ns1.theonlynet.com (olympus.intermountain.com [206.29.203.1]) by hub.freebsd.org (8.8.5/8.8.5) with ESMTP id OAA09532 for ; Thu, 5 Jun 1997 14:58:04 -0700 (PDT) Received: (from rricci@localhost) by ns1.theonlynet.com (8.8.5/8.7.3) id PAA00979; Thu, 5 Jun 1997 15:57:40 -0600 (MDT) Date: Thu, 5 Jun 1997 15:57:39 -0600 (MDT) From: "Robert P. Ricci" To: freebsd-isp@FreeBSD.ORG Subject: Discovering the cause of crashes Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-isp@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk Thank you all for your help regarding NIS and radius. Now, I have another, more urgent problem. Our server is crashing (and rebooting itself) frequently - some times as often as 3x in one day. We're running 2.2-970215-GAMMA (We've had no luck installing later versions, and this is the most stable kernel we've been able to build) on a Cyrix P150 with 32 megs of ram. There are never any errors recorded in /var/log/messages, just the reboot. No core dump is left behind, either. Are any logs kept that I can use to figure out what processes were running and which users were logged in at the time of the crash? Is it worth it to take the machine down for a few hours and build a new kernel? Any suggestions will be greatly appreciated. PS - One more thing: Once, a message appeared on the console at crash time about an invalid page fault while in kernel mode. The current process was #4 (update). Frustrated, Robert Ricci rricci@theonlynet.com