Can't open file

[klindley]

Webpost was running like a top then this little nasty popped up out of the blue:

[DATABASE ERROR:]1016: Can't open file: 'ts2_user.MYI'. (errno: 145)

Anybody got any ideas?

[mister]

Hi if your good at mysql and use phpMYadmin just do a repair on the database.... it will fix the problem .. if not just delete the database and rebuild it...

[klindley]

Gee Thanks Mister! I was afraid it was gonna come to that. It took me forever to figure out how to run that script the first time. Maybe this time I'll write down what I do!

Really thanks for the reply. Is Mysql bad about corrupting files? What would cause the database to blow up like that? I'm wondering if anything can be done to prevent future occurances.

[klindley]

Thanks again Mister, objective complete.

For those that might be like me, which means you're a complete dolt on Mysql here's what I did to fix the problem:

On a Windows system:

Run>command>cd mysql\bin

mysql

use webpost2;

repair table ts2_*; where "*" is the actual table name, but actually this command alone may work... I'm not that good. If it does work it should repair all the tables in one sweep.

I used individual commands for each table, ie:

repair table ts2_user; then
repair table ts2_channel; you get the idea.

There is also a "quick" repair function, which I also threw in, but ultimately I used the command without it on each table. I think each table for Webpost is so short, there is no sense using the "quick" parameter, I suggest a full repair for each table... leaving the "quick" off the command line. But should you want to try the "quick" parameter the command is:

repair table ts2_* quick;

Once again I replaced the "*" with the actual table name, your mileage may vary.

Anyway, up and running again.

Thanks again Mister.

[palp]

FYI, the info stored in the db by webpost is not in any way permanant data, so even if you have to drop all the tables and recreate them there's no loss. I had this happen to me once before with webpost, and oddly enough I've been using mysql for years and never had a single problem with a table getting corrupted.. must be something webpost does to cause it to happen.

[klindley]

It's really sporadic, with no seeming rhyme or reason. I've had to repair the DB 3 or 4 times now, with no pattern to indicate what the problem is.

At the moment it's run for 5 days or so with no issues.

You know, it seems to me that modifying webpost a little by looking at error conditions, a guy could code an automatic fix for this. I'll have to look into it, but completely doable and it'd render this issue nonexistant.