Try adding "innodb_force_recovery = 4" to the mysqld section of your
config file before restarting the server.If you can dump your tables
using "4" then only some data on corrupt individual pages is lost. If
you have to use innodb_force_recovery = 6, that means your db pages
are left in an obsolete state and your B-trees structures may also be
2009/6/10 Isart Montane <isart.montane@stripped>:
> any message on the error log? Have you tried restarting the mysql server?
> On Tue, May 26, 2009 at 7:24 PM, PJ <af.gourmet@stripped> wrote:
>> Hydro Quebec just f***ed my server just as I was booting up three
>> machines; XP is ok, FreeBSD 7.1 is the one with mysql problem, FreeBSD
>> 4.10 - don't know, but boots ok. Result: can't access database. One
>> table seems to abort mysqld. PhpMyAdmin connects to all databases except
>> mysql> CHECK TABLE producer;
>> ERROR 2006 (HY000): Mysql server has gone away
>> No connection. Trying to reconnect...
>> Connection id: 1
>> Current database: theproblem-one
>> Error 2006 (HY000: Mysql server has gone away
>> ERROR 2002 (HY000): Can't connect to local lMySQL server through socket
>> '/tmp/mysql.sock' (61)
>> ERROR: Can't connect to the server
>> ps shows mysqls is running in safe mode
>> Can't find anything on googie
>> I've tried SELECT .... INTO OUTFILE - same errors...
>> WEBMIN shows all dbs except the fro producer and phpMyAdmin resets to
>> login page when trying to access producer table.
>> Any suggestions or bad experiences solved?
>> Hervé Kempf: "Pour sauver la plančte, sortez du capitalisme."
>> Phil Jourdan --- pj@stripped
>> MySQL General Mailing List
>> For list archives: http://lists.mysql.com/mysql
>> To unsubscribe:
A: It reverses the normal flow of conversation.
Q: What's wrong with top-posting?
Q: What's the biggest scourge on plain text email discussions?