Systemd failed to start the service “mysqld”

Tryfonas Tryfonopoulos

• June 30, 2024 21:30

Hi, i have a problem with mysql after cpanel attempted an update

Mysql server will not start at all!

I found this in the log

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) [0x7f06e889cd20]
/usr/sbin/mysqld(Validate_files::check(__gnu_cxx::__normal_iterator<dd::Tablespace const* const*, std::vector<dd::Tablespace const*, std::allocator<dd::Tablespace const*> > > const&, __gnu_cxx::__normal_iterator<dd::Tablespace const* const*, std::vector<dd::Tablespace const*, std::allocator<dd::Tablespace const*> > > const&, unsigned long)+0x909) [0x218ddb9]
/usr/sbin/mysqld(std::thread::_State_impl<std::thread::_Invoker<std::tuple<Detached_thread, std::function<void (__gnu_cxx::__normal_iterator<dd::Tablespace const* const*, std::vector<dd::Tablespace const*, std::allocator<dd::Tablespace const*> > > const&, __gnu_cxx::__normal_iterator<dd::Tablespace const* const*, std::vector<dd::Tablespace const*, std::allocator<dd::Tablespace const*> > > const&, unsigned long)>,__gnu_cxx::__normal_iterator<dd::Tablespace const* const*, std::vector<dd::Tablespace const*, /lib64/libstdc++.so.6(+0xc2b23) [0x7f06e761db23]
/lib64/libpthread.so.0(+0x81ca) [0x7f06e88921ca]
/lib64/libc.so.6(clone+0x43) [0x7f06e6c248d3]
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.

Any ideas about how i might solve this?

• 

  Jim Groom

  • June 30, 2024 21:48

  If you're on CentOS/AlmaLinux/Rocky/some other yum based distro, you can try a yum undo or a yum downgrade as mentioned here.

  https://support.cpanel.net/hc/en-us/community/posts/24546812407575-Mysql-cannot-start
  
  But if you're on Ubuntu, I'm not sure. Still working through a way to downgrade myself. In the meantime, I've run the following on all of my our servers so this update (hopefully) doesn't impact them.

  apt-mark hold mysql-community-client && apt-mark hold mysql-community-client-core && apt-mark hold libmysqlclient-dev && apt-mark hold libmysqlclient21 && apt-mark hold mysql-community-client-plugins && apt-mark hold mysql-community-server-core && apt-mark hold mysql-community-server && apt-mark hold mysql-client && apt-mark hold mysql-common && apt-mark hold mysql-shell

  1
• 

  Tryfonas Tryfonopoulos

  • June 30, 2024 21:51

  I am on cloudlinux and i downgraded like this

  yum downgrade mysql-community-*

  This was from a cpanel update, almost wiped my entire database in order to try and fix it because there was no info at the time. I thought it was only me that i had the problem

  1
• 

  amin alnasra

  • June 30, 2024 22:51

  I faced the same issue 

  to prevent this issue I locked the mysql version by this command on almalinux 

  dnf install python3-dnf-plugin-versionlock

  yum versionlock mysql-community-*

  0
• 

  yayhosting

  • July 01, 2024 01:41

  https://support.cpanel.net/hc/en-us/articles/24546938662039-Upstream-issue-MySQL-8-0-38-does-not-start-Segmentation-Fault
  Ubuntu fixes here - which works fine.

  0
• 

  LvH

  • July 01, 2024 02:03

  Tryfonas Tryfonopoulos
  You and me both brother. I also removed the entire datadir, which magically fixed the issue but is going to cause *a lot* of work to restore all databases. Like you, I couldn't find info about this particular error anywhere and seeing how removing all data lead to a solution I just assumed something in the datadir got corrupted upgrading from 5.7 to 8.0 (which I was doing just as this bug apparently got introduced. :| Adding insult to injury.) and started terminating/restoring accounts on a blank mySQL server. 

  0
• 

  BlueSteam

  • July 01, 2024 05:37

  Im sitting with the exact same issue this morning!  On Almalinux....What am I to do??

  0
• 

  BlueSteam

  • July 01, 2024 06:04

  The solution can be found here:

  https://support.cpanel.net/hc/en-us/community/posts/24546812407575-Mysql-cannot-start?page=1#community_comment_24552615268375

  0
• 

  danitheman

  • July 01, 2024 06:20

  Fixed for me as well. So many work hours wasted early morning trying to debug this...

  0
• 

  Cloudlinux/Cpanel User

  • July 02, 2024 20:25

  Why is there no fix for this  - why do WE have to do a manual fix ?????

  0
• 

  sumi21kav

  • July 02, 2024 20:45

  Hi,
  
  i`m trying to downgrade but is not working.
  We did downgrade yesterday but did not put lock and today we face the same issue but we cant downgrade.
  Any HELP PLEASE!
  
  
  [root@warp ~]# yum downgrade mysql-community-*
  This system is receiving updates from CloudLinux Network server.
  Last metadata expiration check: 1:07:57 ago on Tue 02 Jul 2024 09:35:47 PM CEST.
  No package mysql-community-* available.
  Error: No packages marked for downgrade.

  0
• 

  Cloudlinux/Cpanel User

  • July 02, 2024 21:09

  Hi, what is the output for:

  mysql - V

   

   

  0

Please sign in to leave a comment.