Today I woke up to the news that a friend’s e-commerce site was down, spewing up ‘errno 145′ and generally not doing much by way of commerce.
Now, errno 145 is a MySQL error, not actually a problem with the MySQL software itself, rather it is a corruption of the data held in the database. Such corruptions tend to happen when data is being written to a table and the server becomes overstressed and goes down (even momentarily).
This overloading seems quite likely knowing the hosting company which handles the website runs the virtual host packages without any margin to spare. To add insult to injury, I didn’t have SSH access to the server. I could probably have gained SSH access but only after a long telephone call to the host’s support, holding/verifying my ID etc.
Instead, I found that I was able to use phpMyAdmin which was provided by the hosts. I logged in, selected the corrupt database from the list on the left, scrolled to the bottom, selected ‘check all’ (to select all tables) and then selected ‘Repair Table’ from the drop down list. Behold! the database was unborked.
Please note, I’m a risk-taker but you should take a backup of the database (even if broken) before attempting this as it *could* make matters even worse.
Entries (RSS)