From owner-freebsd-isp Thu Jun 5 15:44:28 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.5/8.8.5) id PAA11617 for isp-outgoing; Thu, 5 Jun 1997 15:44:28 -0700 (PDT) Received: from obiwan.TerraNova.net (root@obiwan.TerraNova.net [205.152.26.129]) by hub.freebsd.org (8.8.5/8.8.5) with ESMTP id PAA11604 for ; Thu, 5 Jun 1997 15:44:22 -0700 (PDT) Received: from P1mpBSD (coolholio@P1mpBSD.TerraNova.net [205.152.26.130]) by obiwan.TerraNova.net (8.8.5/TerraNovaNet) with SMTP id SAA12874; Thu, 5 Jun 1997 18:45:27 -0400 (EDT) Message-ID: <3397420D.6765@TerraNova.net> Date: Thu, 05 Jun 1997 18:47:41 -0400 From: Travis Mikalson Organization: TerraNovaNet X-Mailer: Mozilla 3.01 (WinNT; I) MIME-Version: 1.0 To: "Robert P. Ricci" CC: freebsd-isp@FreeBSD.ORG Subject: Re: Discovering the cause of crashes References: Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-isp@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk Robert P. Ricci wrote: > > 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). I dealt with a similar problem over six months ago. It turned out to be a bad motherboard/processor. Replaced it and well.. hasn't crashed since *knock knock* Went from a P150+ to a P166+ both were on Triton II boards. Those P150+'s are kind of wocked. P166+'s work wonderfully, though! Hardware is most suspect. You need to find out what will make it stop spontaneously combusting by starting to swap hardware out.. Travis -- -=--==--===---====----======------=======------- TerraNovaNet Internet Services - Key Largo, FL Voice: (305)453-4011 Fax: (305)451-5991 http://www.TerraNova.net -------=======------======----====---===--==--=- Always remember that you are unique. Just like everyone else.