Subscribe
WebWordPress

Recover a broken WordPress

Rob Weaver2 Comments on Recover a broken WordPress
I was helping out http://www.pmi-sfbac.org whose web site was down.
 
The server was being unresponsive, and Larry Van Cantfort (the Director of Operations for PMI SFBAC) sent me this clue:
 
It appears that httpd has a lot of running processes and when I try to kill them I am unable to. THis is causing the server to sloooow way down. There are also error messages from mysqld with a corrupt table:
131103 12:18:30 [ERROR] /usr/libexec/mysqld: Table './wordpress_2/wp_comments' is marked as crashed and should be repaired
I couldn’t even get into the control panel to get things going, so the cleanest approach was to simply rebuild the server.
 
So I shut down the database and started to try and get it backed up so we’d at least save all the hard work of the volunteers.
 
So I tried to run the dump, with the following command that I got from the Parallels support site:
[root@u15893654 ~]# mysqldump -uadmin -p`cat /etc/psa/.psa.shadow` -A > dumpall.sql

But that gave me the same error:

mysqldump: Got error: 145: Table './wordpress_2/wp_comments' is marked as crashed and should be repaired when using LOCK TABLES

A quick Google search and I found the “fix” for this is to run a repair on the tables: http://www.daveperrett.com/articles/2009/06/18/mysql-table-is-marked-as-crashed/

That fixed the issue, and I was able to create the “dumpall.sql”.

Once I had ALL of the tables fixed, I simply rebuilt the server and migrated it into a new database as described in the Parallels KB article mentioned above (a lot more steps to make sure the backup was good, but once it was the newly imaged server was able to run without incident).

 
Hi, I’m Rob Weaver

Related Posts