HELP! Forum Crashed!

[The Librarian]

It looks like I crashed my forum.

All was well when I logged in this morning. I went to the AdminCP to run my daily "db repair" script. Usually this works just fine. Today it crashed my system.

I've now tried several times to repair the system in cPanel. I've also tried through SSH. Everytime I run it I get OKs all down the line except two places where it says:

note : The storage engine for the table doesn't support repair

There are now 112 error messages in my inbox. They all basically say this:

MySQL Error : Table './library1_thehomeschoollibrary1/vb_post' is marked as crashed and last (automatic?) repair failed
Error Number : 144

Please help! I don't know what to try next.

Thanks!

[Zachery]

It looks like we are getting half errors not full errors, what two tables cannot be repaired? If it is session and cpsession this is normal.

Try running from ssh specificly running a repair on vb_post

[The Librarian]

The two that don't say OK are:

databasename.vb_cpsession
note : The storage engine for the table doesn't support repair

databasename.vb_session
note : The storage engine for the table doesn't support repair

So it's good to know this is normal. I'll try running that repair, but I don't know how to JUST repair one thing... could you give me that command, please? I just noticed that vb_post doesn't show up on the list...so maybe that's why it's not repairing it?

Thanks!

[The Librarian]

putting on thinking cap here... is it databasename/vb_post ? I'm going to try that.

[The Librarian]

putting on thinking cap here... is it databasename/vb_post ? I'm going to try that.

nope...that didn't work.

[The Librarian]

nope...that didn't work.

ok... DUH.... it's .vb_post not /vb_post.

Let me try that.

[The Librarian]

I'm pretty sure that databasename.vb_post *should* be correct, but it still says "error 1102 Incorrect Database Name" Is it gone or something?

[Zachery]

In the mysql console

SELECT DATABASE databasename;

REPAIR vb_post;

[The Librarian]

In the mysql console

SELECT DATABASE databasename;

REPAIR vb_post;

Ok... I didn't find something specifically called "mysql console" but phpMyAdmin had the mysql stuff so I guess that's what you meant....anyway, I found the correct bit and told it to repair and VOILA! I'm back in business!!!

Thank you so much Zachary! I'd give you a big hug, but I know that's unprofessional so I'll just say "You're a great guy!" and leave it at that.

Thanks for bearing with my ignorance, and for your quick replies. My forum members will thank you, too!

[The Librarian]

Oh, BTW... is this likely to happen again? Is there anyway to avoid it? Just before this occurred I was thinking of setting up the repairs as a scheduled task... is that advisable? I do a backup daily at 3am. I was thinking of running the repair at 3:30am. What do you think?

Thanks!

[Zachery]

Is it likely? Not an easy question to anwser. Crashes should not happen often.

[The Librarian]

Is it likely? Not an easy question to anwser. Crashes should not happen often.

So I guess there's nothing to do to avoid it?

Do you think running the normal vBulletin db repair script daily is a good idea?

The reason I'd started running it is because we'd had a few random errors here and there (nothing serious enough to crash the system though) and I thought if I ran it I could avoid them...and I had, until today.