From owner-freebsd-questions@FreeBSD.ORG Fri Apr 2 18:27:05 2004 Return-Path: Delivered-To: freebsd-questions@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id BB57E16A4CE for ; Fri, 2 Apr 2004 18:27:05 -0800 (PST) Received: from www.mcmanis.com (www.mcmanis.com [66.125.189.29]) by mx1.FreeBSD.org (Postfix) with SMTP id 8BDB943D3F for ; Fri, 2 Apr 2004 18:27:05 -0800 (PST) (envelope-from cmcmanis@mcmanis.com) Received: (qmail 28007 invoked from network); 3 Apr 2004 02:37:48 -0000 Received: from home.mcmanis.com (HELO manowar.mcmanis.com) (66.125.189.30) by www.mcmanis.com with SMTP; 3 Apr 2004 02:37:48 -0000 Message-Id: <6.0.0.22.2.20040402183012.022828b8@66.125.189.29> X-Mailer: QUALCOMM Windows Eudora Version 6.0.0.22 Date: Fri, 02 Apr 2004 18:33:03 -0800 To: "meimi" , From: Chuck McManis In-Reply-To: References: Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii"; format=flowed Subject: Re: Server down regularly X-BeenThere: freebsd-questions@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: User questions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sat, 03 Apr 2004 02:27:05 -0000 At 11:12 AM 4/2/2004, meimi wrote: >Actually, what I want to know is the general steps for finding the problems. Step #1 - Look in the message log (/var/log/messages), and ideally a copy of the console output, to see why you server stopped running. (or if your server stopped running) The latter is important because your server can seem to be "down" when the problem is actually you cannot connect to it (the network is down). If you can log into your server and get a shell prompt, then I would try the command uptime(1) first, to see how long the server thinks its been running, and then start looking at /var/log/messages for reboot messages, and /var/crash for kernel coredumps (if you panic, and have savecore set, it will create a core file there) --Chuck