We’ve seen some customers with this issue, where after a reboot on a current version of cPanel, the MySQL server won’t start fully and keeps crashing with logs like:
2024-07-08T00:03:13Z UTC – mysqld got signal 11 ;
Most likely, you have hit a bug, but this error can also be caused by malfunctioning hardware.
BuildID[sha1]=539914406f129270c6bd39a48640d0f1eeecc1af
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…
stack_bottom = 0 thread_stack 0x100000
/usr/sbin/mysqld(my_print_stacktrace(unsigned char const, unsigned long)+0x41) [0x213f031] /usr/sbin/mysqld(print_fatal_signal(int)+0x397) [0xffa557] /usr/sbin/mysqld(handle_fatal_signal+0xa5) [0xffa615] /lib64/libpthread.so.0(+0x12d20) [0x7fee37433d20] /usr/sbin/mysqld(Validate_files::check(__gnu_cxx::__normal_iterator > > const&, __gnu_cxx::__normal_iterator > > const&, unsigned long)+0x909) [0x218ddb9] /usr/sbin/mysqld(std::thread::_State_impl > > const&, __gnu_cxx::__normal_iterator > > const&, unsigned long)>, __gnu_cxx::__normal_iterator const, std::vector, /lib64/libstdc++.so.6(+0xc2b23) [0x7fee361b4b23]
/lib64/libpthread.so.0(+0x81ca) [0x7fee374291ca]
/lib64/libc.so.6(clone+0x43) [0x7fee357bb8d3]
The manual page at http://dev.mysql.com/doc/mysql/en/crashing.html contains
information that should help you find out what is causing the crash.
We’ve been in-touch with cPanel about this and here’s the solution/fix:
On a terminal session as root to your cPanel VPS, run:
yum downgrade mysql-community-*
Then your MySQL server should restart and run ok.
This is a known bug in this version of MySQL and cPanel recommend you lock your MySQL server version at this release for a while with commands like:
dnf install python3-dnf-plugin-versionlock
yum versionlock mysql-community-*
FYI,
Richard.