From owner-freebsd-questions Mon Apr 13 20:43:26 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id UAA07248 for freebsd-questions-outgoing; Mon, 13 Apr 1998 20:43:26 -0700 (PDT) (envelope-from owner-freebsd-questions@FreeBSD.ORG) Received: from federation.addy.com (federation.addy.com [207.239.68.2]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id DAA07227 for ; Tue, 14 Apr 1998 03:43:15 GMT (envelope-from fbsdlist@federation.addy.com) Received: from localhost (fbsdlist@localhost) by federation.addy.com (8.8.5/8.6.12) with SMTP id XAA27001 for ; Mon, 13 Apr 1998 23:43:11 -0400 (EDT) Date: Mon, 13 Apr 1998 23:43:11 -0400 (EDT) From: Cliff Addy To: FreeBSD-questions@FreeBSD.ORG Subject: Mysterious lockup In-Reply-To: Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-questions@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG I have a 2.2.2 server that has been quite happy for many months. Suddenly, last week, I began getting intermittent lockups. It runs fine for anywhere from a few hours to a few days and then BLAM it's dead. There is *nothing* on the console or in the logs of any problems, it just suddenly stops responding to anything but a ping. How does one even *start* tracking down a problem like this? I've been administering fbsd systems for three years and have never seen anything like it. Our other 9 2.2.2 systems are not exhibiting any problems like this. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-questions" in the body of the message