cpanel 124 false positive database corruption
After upgrading to cpanel 124, and upgrading databases to mariadb 11.4, i am getting the error messages:
"check_mysql has determined that there are corrupted database tables"
contained in the error is:
| Database | Error |
|---|---|
| mysql | /usr/bin/mysqlcheck: Deprecated program name. It will be removed in a future release, use '/usr/bin/mariadb-check' instead |
I believe this is a false positive because the error is program name deprecation, not a specific database, and when i run '/usr/bin/mariadb-check -A' from the terminal, all tables check out OK.
-
Hey there! I do agree this seems like a false positive, although the real issue is why the mysqlcheck script was left in place on your system after the update. Could you submit a ticket so this can be investigated? I don't believe I'll be able to create a test system where I can reliably reproduce this exact issue, and I'm not finding any other cases open about it at this time.
0 -
Hey cPRex,
There's actually another forum post from about two hours ago directly above mine in the database section that is referencing the same false positive, but i can open a ticket if it helps.
0 -
And i also had it happen on two separate servers...so, i'd say it isn't that one server did something funny.
0 -
Sorry for a third reply - I guess i cannot submit a support request since my cpanel license was purchased from a third party.
I'll be happy to help you troubleshoot by proxy though - let me know.
0 -
I just saw that other post - I'm looking into it now and I'll let you know what I find!
0 -
I've created case CPANEL-46060 with our developers and I'll be creating a public article soon with more details that you can follow along with.
1 -
Here you go - you can follow along with this article for updates - https://support.cpanel.net/hc/en-us/articles/27543937363863-MariaDB-11-4-4-gives-false-positive-update-about-corrupted-tables-during-upcp
1 -
Thanks, will follow.
0 -
Hey cPRex,
I was just perusing the cpanel changelog as i do from time to time, and noticed
124.0.14
Fixed ZC-12322: Fix check_mysql false positives on MariaDB 11.4.I wanted to let you know that I'm still getting the error message, and my server is on 124.0.17. I just ran /scripts/upcp once again to make sure and it is indeed still happening.
Thanks!
0 -
Same here, on 124.0.17 and still getting false positives.
0 -
cPRex Also, yesterday I attempted to re-run the mariadb 11.4 install tool from within whm, which completed successfully, but when upcp ran later that night i still received the false positive. I know this bug probably isn't super high-priority as there are no negative consequences, but it is quite irritating.
0 -
sierrablue and danfbach - I setup a 124.0.17 server and I couldn't make this happen on my end. Could one of you (or both, why not!) submit a ticket from one of the systems where this is happening so this can be examined?
0 -
sierrablue can you? i have a 3rd party license so i cannot open a ticket.
Otherwise, cPRex are you able to open a ticket for me and request server access?
0 -
I'm *supposed* to say something along the lines of "you should open a ticket with your provider and then they'll escalate to us as necessary" but for a reported issue like this I'm willing to make some magic happen.
Give me a few minutes to finish up something and I'll reach out :D
0 -
I'll acknowledge that this is a special case and won't expect this treatment in the future - thanks!
0 -
Alright - I've worked on this with the team and confirmed that the changelogs are indeed incorrect and the official fix isn't until version .18. SO...this will be released in the next update soon!
1 -
Thank you cPRex
0 -
You're very welcome - always happy to help!
0
Please sign in to leave a comment.
Comments
18 comments