Mysql gone down and not coming up
With my cpanel server having the version 110.0.36 mysql version has gone down all of a sudden, I could see the below information in logs. mysqld got signal 11 error was first reported on 06/30/24 just after an upgrade from mysql version 8.0.37 to 8.0.38. When i have first faced the issue, i found the below fix and it worked.
But again today, mysql is going down with the same reason in logs. What is the fix for the same ?
2024-07-02T16:46:21.035022Z 0 [System] [MY-010116] [Server] /usr/sbin/mysqld (mysqld 8.0.38) starting as process 5564
2024-07-02T16:46:21.057081Z 1 [System] [MY-013576] [InnoDB] InnoDB initialization has started.
2024-07-02T16:47:31.380401Z 1 [System] [MY-013577] [InnoDB] InnoDB initialization has ended.
2024-07-02T16:47:33Z UTC - mysqld got signal 11 ;
Most likely, you have hit a bug, but this error can also be caused by malfunctioning hardware.
BuildID[sha1]=fefb8e8533cfe697780041130483d73f33c83e8a
Thread pointer: 0x0
Attempting backtrace. You can use the following information to find out
where mysqld died. If you see no messages after this, something went
terribly wrong...
-
Did you do the part about version locking mysql-community-* ? If not, every night upcp will just try to re-apply the updated packages.
0 -
Version locking was missed. I just realized the same. Is it possible to fix it one more time?
0 -
Not an expert on this particular bug, but I'd think you could simply downgrade again and then version lock. cPanel support ticket when in doubt.
0 -
It looks like we have resolved the issue temporarily, but it reoccurs after cPanel updates. This is a common scenario by daily cron job.
0 -
nisamudeen97 Check out this post - it seems you are getting the same error I was getting:
mysqld got signal 11 ;
Most likely, you have hit a bug, but this error can also be caused by malfunctioning hardware.https://support.cpanel.net/hc/en-us/community/posts/24546812407575-Mysql-cannot-start
0
Please sign in to leave a comment.
Comments
5 comments