MySQL8.4 upgraded to MySQL9.7 during nightly updates.
This one stinks. I have 3 servers to replace today.
Even after follow instructions in link, the data is already mysql 9.7 and will not allow mysql to start.
Might as well start replacing servers early.
Crap!
-
Update - April 23 - The details in the support article are correct, and it also appears that MySQL has resolved the upstream issue with their repositories. That doesn't help you if the damage has already happened to your server, but at this point we have a few options:
-we've released an autofixer to help prevent users from receiving the update, which went out last night
-the support article has copy/pastable steps to resolve the issue if your server experienced the upgrade
-if you have *any* doubts at all, feel free to submit a ticket.0 -
the copy paste steps did not work on my servers.
MySLQ won't stay running long enough to implement any steps that needs MySQL running to complete. I can get it to start then it dies.
To add to my problems, the 3 servers affected use OVH licensing. Of source OVH does NOT provide cPanel support and cPanel will not provide support be OVH sold the license.
So have one server of 3 addressed in the last 10 hours.
Next two more broken servers migrate. Yay!
0 -
This occurred on some of my servers - The instructions did not work either (I only tried them on one server). I followed the successful update path - but about 3/4 of the way through the commands stopped working. SO I have submitted a ticket.
This was my ns1 name server!
(thanks to cPanel Support, I was able to remove mysql competly from DNS only boxes). Good luck to everyone else!
0 -
slim - I'm glad we could help!
0 -
Spoke to soon.. While removing mysql was a fix, it now stops updates - and right now those are kind of important as per: https://support.cpanel.net/hc/en-us/articles/40073787579671-Security-CVE-2026-41940-cPanel-WHM-WP2-Security-Update-04-28-2026
The update script for DNS Only needs to cater for missing mysql!
0 -
Can you share the specific error you receive when updating the system?
0 -
For my host106 server, the only way I could get it fixed was to move the mysql data to a new folder, remove mysql, and clean install mysql 8.4.
After that none of the cpanel users had mysql users in mysql. You can manually add them back or in my case I did a backup restore from about an hour before the incident.
I'm in the process now of life cycling out host106 to a new server and moving everyone off so they are on a clean new server.
This was a mess for sure. I'm lucky it only impacted 3 servers for me.
0 -
The issue was caused by mysql being removed (which I did after cPanel recommended it after some sort of mysql update overnight went crazy).
The cPanel update would no longer apply itself due to the missing mysql. cPanel support reinstalled mysql via command line for me, and I have now been able to update the DNS only servers.
I suggest if mysql isnt needed, you remove it, and update the update scripts so it works if its not installed.
0
Please sign in to leave a comment.
Comments
8 comments