From owner-freebsd-questions@FreeBSD.ORG Tue Apr 7 19:44:22 2009 Return-Path: Delivered-To: freebsd-questions@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 722141065743 for ; Tue, 7 Apr 2009 19:44:22 +0000 (UTC) (envelope-from jalmberg@identry.com) Received: from mx1.identry.com (on.identry.com [66.111.0.194]) by mx1.freebsd.org (Postfix) with ESMTP id 0B22A8FC12 for ; Tue, 7 Apr 2009 19:44:21 +0000 (UTC) (envelope-from jalmberg@identry.com) Received: (qmail 96794 invoked by uid 89); 7 Apr 2009 19:44:59 -0000 Received: from unknown (HELO ?192.168.1.110?) (jalmberg@75.127.142.66) by mx1.identry.com with ESMTPA; 7 Apr 2009 19:44:59 -0000 In-Reply-To: References: <13D52068-D184-42D9-AE6C-F095C1283975@identry.com> Mime-Version: 1.0 (Apple Message framework v753.1) Content-Type: text/plain; charset=US-ASCII; delsp=yes; format=flowed Message-Id: <3A934D4A-1864-401C-8CD8-86B37EB2B183@identry.com> Content-Transfer-Encoding: 7bit From: John Almberg Date: Tue, 7 Apr 2009 15:44:20 -0400 To: Chuck Swiger X-Mailer: Apple Mail (2.753.1) Cc: freebsd-questions@freebsd.org Subject: Re: low-level format before install? X-BeenThere: freebsd-questions@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: User questions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 07 Apr 2009 19:44:22 -0000 On Apr 7, 2009, at 3:37 PM, Chuck Swiger wrote: > On Apr 7, 2009, at 12:15 PM, John Almberg wrote: >> Well, I've got real problems with that database server that lost >> power over the weekend. We reloaded FreeBSD from scratch and then >> reinstalled mysql, and pf. I loaded up my database and switched >> over all my customer's websites. The database server ran fine for >> about 2 minutes, and then died. At the moment, I can't even ssh >> into the machine, although they can get into it using a keyboard/ >> monitor at the data center. In other words, sshd is not working. > > That sounds like either a hardware problem (ie CPU overheating or > marginal PSU failing under production load), or less likely, some > kind of software misconfiguration. System logs would be useful to > see whether any signs of trouble are being mentioned. Apparently, power was fluctuating drastically before they decided to cut power, so a hardware problem is a definite possibility. A PSU failure would not surprise me in the circumstances. Assuming I can ever ssh in again, what log would hardware failures be reported to? -- John