Website Down - 1016 - Can't open file: 'sessions.MYI'. (errno: 145)

[jmdesign]

Hi,

Just tried to do some work on one of my shops (http://www.foot-shop.co.uk/) and found the site is down:

"1016 - Can't open file: 'sessions.MYI'. (errno: 145)

select value from sessions where sesskey = '4e35589800a368e2d3cb6744dabe627e' and expiry > '1207988486'

[TEP STOP]"

I've done some searching on the forums and it sounds quite easy to fix (repairing table in database via PhpMyAdmin) but all the links I've found in previous threads don't seem to work? I want to make sure I do it properly and don't make the problem worse! Can someone please help ASAP?

Many thanks,

James

[michael_s]

To repair the table, go use phpmyadmin (most hosts provide this in your control panel) and select the database. Then click the checkbox next to the sessions table, and select Repair from the dropdown at the bottom of the page.

That should fix it.

[jmdesign]

Hi Michael,

As always your advice is spot on! Thanks a bunch for that.

Any idea what causes it? Is it likely to happen again?

James

[michael_s]

It is mostly a server level issue. Usually it is caused by an improper shutdown/restart of mysql (forced reboot, or not properly shutting down mysql during a service restart).

Yes it can happen again at any time, if the server you are on is overloaded, unstable or otherwise poorly managed. It can also happen if whomever is working on the mysql server does not properly restart the service when they are doing that.

Table corruption happens, especially on shared servers. It is a good idea to periodically repair and optimize all tables.

[jmdesign]

Hi Michael,

Okay thanks for the info, will keep an eye out for that from now on.

James

[met00]

Just a fast note. If you are on a shared server think about getting off and getting on one where you have control. All it takes is one badly formed sql statement to bring your server to it knees - and this is your business after all. At about $200USD/mo the cost of a root server where you have control over it (or a managed server) is well worth the cost.

If you are on your own server then you can do what I do on the servers I have, which is repair and optimize the tables on the 15th of each month. It's a simple cron job and it ensures that the server and mysql runs clean.