MySQL Crashed After Upgrade to 8.0.38
We have identified that MySQL crashed on some servers following the recent upgrade to version 8.0.38. Errors seen in logs:
To mitigate this issue, please follow the steps below:
Rollback the Upgrade:
You can downgrade MySQL using the command
Version Lock MySQL 8.0.37:
Lock MySQL to version 8.0.37 until further updates in this regard from MySQL or cPanel.
Here is the procedure to version lock:
Install version lock:
Lock the MySQL version:
For detailed instructions, please refer to the official guide: How to version lock RPM packages.
cPanel has now published an official update on this issue:
https://support.cpanel.net/hc/en-us/articles/24546938662039-Upstream-issue-MySQL-8-0-38-does-not-start-Segmentation-Fault
Additional Notes:
To check mysql version on the server:
In case sites have an issue even after the downgrade, you may need to rebuild Apache.
mysqld.service: Main process exited, code=killed, status=11/SEGV
Most likely, you have hit a bug, but this error can also be caused by malfunctioning hardware.
To mitigate this issue, please follow the steps below:
Rollback the Upgrade:
You can downgrade MySQL using the command
yum downgrade mysql-community*
Version Lock MySQL 8.0.37:
Lock MySQL to version 8.0.37 until further updates in this regard from MySQL or cPanel.
Here is the procedure to version lock:
Install version lock:
dnf install python3-dnf-plugin-versionlock
Lock the MySQL version:
yum versionlock mysql-community-*
For detailed instructions, please refer to the official guide: How to version lock RPM packages.
cPanel has now published an official update on this issue:
https://support.cpanel.net/hc/en-us/articles/24546938662039-Upstream-issue-MySQL-8-0-38-does-not-start-Segmentation-Fault
Additional Notes:
To check mysql version on the server:
mysql -V
In case sites have an issue even after the downgrade, you may need to rebuild Apache.
/scripts/rebuildhttpdconf ;/scripts/restartsrv_httpd
Updated on: 05/07/2024
Thank you!