Cron Failure

[abinidi]

Good Monday to you all...

 

I'm getting a message with the following cron failure message:

 

subject: Cron <username@server#> mysqldump -u database_name -ppassword table_name | gzip -c > /home/username/backups/backup-bkclub-Monday.sql.gz

 

Message body: mysqldump: Can't get CREATE TABLE for table `wp_bad_behavior_log` (Can't open file: 'wp_bad_behavior_log.MYI'. (errno: 145))

 

 

This cron job has been working for months, and just stopped working late last week. I've been getting daily cron failures with the same message since that date. (With the obvious slight difference of the backup day and file name.)

 

Any suggestions on what may be causing this cron failure or what I could do to make it work again?

[TCH-Bruce]

Have you checked your error logs?

[abinidi]

At the risk of sounding stupid: what for? Meaning: what am I looking for in the error logs. I feel like I'd have more success reading "War and Peace" in Russian than reading my error logs...

 

[And I don't even know the cyrilic alphabet!]

[abinidi]

In the error logs, there are only 3 errors: all of them are looking for a robots.txt file.

 

No error logs earlier than [Mon Mar 20 13:14:52 2006]

 

Wonder what happened to my error logs?

[TweezerMan]

The CPanel Error Log is only a web server error log, so your cron job would not record any errors there. (The cron job runs outside of the web server.)

 

It appears that the 'wp_bad_behavior_log' table has become damaged or corrupted, as indicated by the error number included with the error (errno: 145):

145 = Table was marked as crashed and should be repaired

I'd suggest attempting to repair the table in phpMyAdmin.

[MikeJ]

Yea, it sounds like your table got corrupted somehow.

 

Try going into phpmyadmin as David suggested, select your 'wp_bad_behavior_log' table, select operations, and you should have an option to repair table in there. That will most likely fix your problem. You can try a check table after that to see if it still reports any problems.

[cajunman4life]

As stated above, repair table should do the trick for you. And the cyrilic alphabet is not as hard as it looks .

[abinidi]

Thanks everybody for the help.

 

I've repaired the table. I tested a cron job, and I didn't get any messages, so I guess it is fixed. I'll verify when my daily cron job runs tomorrow morning. If I'm still having trouble, I'll get back to you!

[TCH-Bruce]

Hey Paul, glad you got it fixed. Sorry for leading you astray.

[abinidi]

Thanks Bruce.

 

No problem. You had a better guess at what to do than I did!