[Case 185925] check_mysql sends a notification that databases are broken when they cannot be locked

[AdamDresch]

Hi all,

I just started getting a daily email with the following content:

cPanel & WHM has determined that the following database tables are corrupt:

Database

Error

mysql

mysql.general_log
Error : You can't use locks with log tables.
mysql.slow_log
Error : You can't use locks with log tables.
We recommend that you repair these tables with WHM’s “Repair a MySQL Database” interface (WHM Home » SQL Services » Repair a MySQL Database). If the repair fails, contact cPanel Support for further assistance.

Is anyone else getting these emails? and does anyone have any info on how to stop them?
There's obviously no corrupt tables, given that the two issues it mentions are log files

 

[LostNerd]

Please see this part of the email...

We recommend that you repair these tables with WHM’s “Repair a MySQL Database” interface (WHM Home » SQL Services » Repair a MySQL Database). If the repair fails, contact cPanel Support for further assistance.

You can also try

mysqlcheck -r DATABASE_NAME

Contact cPanel support so that they can look in to it.

 

[AdamDresch]

Please see this part of the email...



You can also try

mysqlcheck -r DATABASE_NAME

Contact cPanel support so that they can look in to it.

Hiya
Yea I already ran a repair on that database, but the error isn't about corruption, for some reason it sees this message "Error : You can't use locks with log tables." as corruption of tables, when it shouldn't.

 

[cPanelMichael]

Hello,

Internal case number 185925 is open to address an issue where /script/check_mysql sends out false errors for tables that complain about locks when mysqlcheck is run on their database. You can monitor our change log for the inclusion of this case number at:

cPanel - 11.50 Change Log

Thank you.

 

[AdamDresch]

Thanks Michael
We did upgrade whm/cpanel on this server, but it still emails us every morning with the same message
Restarting mysql also sends the email too.


cPanel & WHM has determined that the following database tables are corrupt:

Database

Error

mysql

mysql.general_log
Error : You can't use locks with log tables.
mysql.slow_log
Error : You can't use locks with log tables.

 

[cPanelMichael]

We did upgrade whm/cpanel on this server, but it still emails us every morning with the same message
Restarting mysql also sends the email too.

Please post the output from:

cat /usr/local/cpanel/version

Thank you.

 

[grizewald]

I just received one of these e-mails today.

Our cPanel version is 11.50.0.10

I thought this was fixed in 11.50.0.4?

 

[Apoc]

I just received one of these e-mails today.

Our cPanel version is 11.50.0.10

I thought this was fixed in 11.50.0.4?

Exactly the same here.

 

[briansol]

I also got it for the first time last night. I must've been upgraded by cron task as i haven't been in to whm in a few weeks.

With your current Update Settings, you will be upgrading to the latest release build.

# cat /usr/local/cpanel/version
11.50.0.10

I don't care if it's a BS email... but I also didn't get my backup complete email. It looks like the tar/gz files are there, but it's a bit disconcerting that the script didn't finish completely to send the email when done.


I'm looking to upgrade to maria 10, but with this lingering, i'm not sure

 

[bremboy79]

same here. got the message this morning
11.50.0 build 10

 

[grizewald]

Oddly, I didn't get one today but nothing has been upgraded or changed.

Ghosts in the machine...

 

[hdctest]

I have a server that had the same email today.
11.50.0 build 10

 

[LostNerd]

Oddly, I didn't get one today but nothing has been upgraded or changed.

Ghosts in the machine...

cPanel updates nightly unless you have otherwise specified. It's possible that the update has fixed your issue.

I have a server that had the same email today.
11.50.0 build 10

/scripts/upcp --force

Give that a shot, hdctest.

 

[cPanelNick]

I also got it for the first time last night. I must've been upgraded by cron task as i haven't been in to whm in a few weeks.

With your current Update Settings, you will be upgrading to the latest release build.

# cat /usr/local/cpanel/version
11.50.0.10

I don't care if it's a BS email... but I also didn't get my backup complete email. It looks like the tar/gz files are there, but it's a bit disconcerting that the script didn't finish completely to send the email when done.


I'm looking to upgrade to maria 10, but with this lingering, i'm not sure

Hi briansol,

The spurious mysql check notice is solved in 11.50.0.12 (now available in CURRENT)

As for the backup completion email, you probably just need to adjust "Backup Successful" or "Successful Backup" (wording is different in some versions) in the Contact Manager in WHM to make the notification priority higher.

Please see the release notes:
http://documentation.cpanel.net/dis...tprioritiesforalertsinContactManagerinterface
In cPanel & WHM version 11.50, we improved error reports and created separate notifications for critical issues. As a result, we lowered the default priority level for several non-critical alerts in order to reduce the volume of notifications that require no action.

We strongly recommend that you review your alert preferences in WHM's Contact Manager interface (Home >> Server Contacts >> Contact Manager) and make any necessary adjustments.

 

[Jay RIgby]

I have this email - cPanel & WHM has determined that the following database tables are corrupt:

Database Error
mysql
mysql.help_category
error : Table upgrade required. Please do "REPAIR TABLE `help_category`" or dump/reload to fix it!
mysql.help_keyword
error : Table upgrade required. Please do "REPAIR TABLE `help_keyword`" or dump/reload to fix it!
mysql.help_topic
error : Table upgrade required. Please do "REPAIR TABLE `help_topic`" or dump/reload to fix it!
mysql.proc
error : Table upgrade required. Please do "REPAIR TABLE `proc`" or dump/reload to fix it!
mysql.procs_priv
error : Table upgrade required. Please do "REPAIR TABLE `procs_priv`" or dump/reload to fix it!
mysql.time_zone_name
error : Table upgrade required. Please do "REPAIR TABLE `time_zone_name`" or dump/reload to fix it!

But I cannot see how to under SQL Services » Repair a MySQL Database

Greatly appreciate a pointer!

 

[kcrnc]

This happened on a client site recently...the initial issue where general_log and slow_log report an error via automated emails, but upon repair it is really just a warning.

In my case, Cpanel/WHM was set to auto-upgrade and updated itself to the latest version. However, the mysql server was really old. Going to the SQL Services -> Repair Table section prompted a warning about the old version.

After backing everything up, I upgraded to a more recent version of mysql and the check table no longer reports the error. I believe the issues(along with a warning about Horde and no Innodb support) have been fixed.

 

[Mostafaewig]

after upgrade cpanel/whm i have this notification error
where can i find this key? and what should i do?

cPanel & WHM has determined that the following database tables are corrupt:

Database Error
eximstats
error : Found 12892 keys of 12891
error : Corrupt

We recommend that you repair these tables with WHM’s “Repair a MySQL Database” interface (WHM Home » SQL Services » Repair a MySQL Database). If the repair fails, contact cPanel Support for further assistance.

i did repair database but still i get notification

 

[Infopro]

Fro the error:

"If the repair fails, contact cPanel Support for further assistance."

Please feel free to open a ticket to cPanel Technical Support.

 

[Apoc]

We've been getting a bunch more of these across different servers (which all have the latest build running) - looks like this is still ongoing.

 

[cPanelMichael]

We've been getting a bunch more of these across different servers (which all have the latest build running) - looks like this is still ongoing.

Hello

Could you elaborate on the specific notification that you received? For instance, are you sure it's for the issue discussed on this thread and not because the database referenced is actually corrupted?

Thank you.