Issue
MySQL was updated to v8.0.38 and it fails to start.
Environment
- MySQL v8.0.38
Solution
The situation is known as a bug from the upstream, and some details can be obtained via the following articles (check the Useful Links section for more).
For now, the main recommendation is to Not Upgrade to Any Version of MySQL After 8.0.37.
CloudLinux released MySQL Governor's support for 8.0.38
The MySQL Governor's support for 8.0.38 was released through the rollout repo: https://changelog.cloudlinux.com/cl-MySQL80
However, our developers are investigating the situation within an internal task CLOS-2787 and the rollout has already been paused so that the package containing the bug is not available for download.
Workaround
- A workaround which can be applied to the server with MySQL upgraded to 8.0.38 is to downgrade the MySQL version back to 8.0.37. We've experienced several similar cases where this method worked:
- if the server uses Governor:
yum downgrade cl-MySQL*
-
- for MySQL-community:
yum downgrade mysql-community-*
-
- and you may simply undo a yum transaction during which the upgrade occurred:
yum history undo ID
NB! Please be careful whenever manipulating with Governor/MYSQL packages! Always prepare a full DB backup so it can be restored in case of any issues. |
- Another option is to version lock MYSQL packages to prevent the update but we advise removing the lock once issue is resolved.
Comments
0 comments
Please sign in to leave a comment.