Post
by Theo »
There was a problem with the database today. For some reason the mysql database decided that it would continously crash because of a bad innodb page. If this sounds greek, then you're part of the 99.99% of the world who doesn't need to know this. To fix the problem I had to stop the web services, stop mysql, add a special line to the mysql config file to allow innodb recovery, do a full export of the entire database (which wasn't that bad), renamed the mysql data folder, created a new mysql data folder, ran the mysql_install_db script, updated the permissions on the folder (and it's contents), removed the line that I added to the mysql config, started mysql, performed a full import of the data (which was slow as it's a large database), and then finally started the web services.
Why is this important. It's not, but if someone runs into the same problem, google would have indexed this page and they might just find the answer they were looking for.
So, the keywords of the day are: mysql innodb corrupt table recovery shot who in the foot and didn't know it tacobell and things you can buy theo for xmas