From owner-freebsd-questions@FreeBSD.ORG Sun Apr 5 18:10:18 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 DFE011065686 for ; Sun, 5 Apr 2009 18:10:18 +0000 (UTC) (envelope-from freebsd-questions@m.gmane.org) Received: from ciao.gmane.org (main.gmane.org [80.91.229.2]) by mx1.freebsd.org (Postfix) with ESMTP id 601548FC18 for ; Sun, 5 Apr 2009 18:10:18 +0000 (UTC) (envelope-from freebsd-questions@m.gmane.org) Received: from list by ciao.gmane.org with local (Exim 4.43) id 1LqWnQ-0000oy-Oc for freebsd-questions@freebsd.org; Sun, 05 Apr 2009 18:10:16 +0000 Received: from pool-70-21-17-13.res.east.verizon.net ([70.21.17.13]) by main.gmane.org with esmtp (Gmexim 0.1 (Debian)) id 1AlnuQ-0007hv-00 for ; Sun, 05 Apr 2009 18:10:16 +0000 Received: from nightrecon by pool-70-21-17-13.res.east.verizon.net with local (Gmexim 0.1 (Debian)) id 1AlnuQ-0007hv-00 for ; Sun, 05 Apr 2009 18:10:16 +0000 X-Injected-Via-Gmane: http://gmane.org/ To: freebsd-questions@freebsd.org From: Michael Powell Followup-To: gmane.os.freebsd.questions Date: Sun, 05 Apr 2009 14:10:56 -0400 Lines: 39 Message-ID: References: <4ad871310904050141k11eda14vd8db9224f4384757@mail.gmail.com> <1ED100F1-51AE-478D-873C-40FF43EA17FB@identry.com> Mime-Version: 1.0 Content-Type: text/plain; charset="US-ASCII" Content-Transfer-Encoding: 7Bit X-Complaints-To: usenet@ger.gmane.org X-Gmane-NNTP-Posting-Host: pool-70-21-17-13.res.east.verizon.net User-Agent: KNode/0.99.01 Sender: news Subject: Re: how to recover after power outage X-BeenThere: freebsd-questions@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list Reply-To: nightrecon@verizon.net List-Id: User questions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 05 Apr 2009 18:10:19 -0000 John Almberg wrote: [snip] > > Okay, so the machine is back online and I can log in again. > > The hardware is only 18 months old or so... good quality stuff, so > hopefully nothing is physically damaged. We'll see... > > Unfortunately, mysql isn't working at the moment... will make a > backup of data (I have the previous night's backup, of course, but > would like the latest, if possible.) Then will try to figure out > what's working and what's not. > Check the machine-hostname.err file when you manually try and start MySQL. Provided that you have mysql_enable="YES" in /etc/rc.conf you should be able to manually attempt to start with /usr/local/etc/rc.d/mysql-server start (it seems to work reliably when you type out the entire command path-wise). Note that if somehow permissions on the my.cnf file got changed MySQL won't start if my.cnf is world writable. Check for stale PID and sockets. Normally these shouldn't be a problem as a startup will just overwrite them. Check these to eliminate any wonkiness, e.g. some permission change isn't allowing for MySQL to wipe the old ones. The whateverthehostname.err log and possibly /var/log/messages might give some clue for what's going on. If the database files are corrupt just clean them out and replace with a backup done with dump. Ensure the /var/db/mysql tree is chowned mysql:mysql. If you had to install/reinstall from ports the install should have created the appropriate uid/gid accounts. Check and see if these are missing. At any rate I wish you the best of luck. Now that you can SSH in you can probably fix it up. -Mike