MySQL Forums
Forum List  »  General

MySQL crashed and process in zombie state
Posted by: Sophal Lee
Date: November 14, 2023 02:59PM

MySQL server crashed and was in a zombie state. Attempted to send kill -s SIGCHLD to the parent process but failed. Killing the parent was not an option since it was the init process and I was forced to restart the server.

Once the server started, MySQL started without issues and I have checked the database for corruption. No corruption detected using the mysqlcheck utility.

I checked the error logs and found the entries as below. Server is AlmaLinux 8.8 (4.18.0-477.21.1.el8_8.x86_64 x86_64 x86_64) and MySQL version is 8.0.32.

I see it received signal 6, the thread pointer is 0x0 and several functions. How do I go about debugging the back trace?


InnoDB: ###### Diagnostic info printed to the standard error stream
2023-11-11T03:24:14.418528Z 0 [ERROR] [MY-012872] [InnoDB] [FATAL] Semaphore wait has lasted > 600 seconds. We intentionally crash the server because it appears to be hung.
2023-11-11T03:24:14.424144Z 0 [ERROR] [MY-013183] [InnoDB] Assertion failure: srv0srv.cc:1871:ib::fatal triggered thread 140054773094144
InnoDB: We intentionally generate a memory trap.
InnoDB: Submit a detailed bug report to http://bugs.mysql.com.
InnoDB: If you get repeated assertion failures or crashes, even
InnoDB: immediately after the mysqld startup, there may be
InnoDB: corruption in the InnoDB tablespace. Please refer to
InnoDB: http://dev.mysql.com/doc/refman/8.0/en/forcing-innodb-recovery.html
InnoDB: about forcing recovery.
2023-11-11T03:24:14Z UTC - mysqld got signal 6 ;
Most likely, you have hit a bug, but this error can also be caused by malfunctioning hardware.
BuildID[sha1]=40c1f0e0d826a573f7f320e98f4b61484baf534a
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/libexec/mysqld(my_print_stacktrace(unsigned char const*, unsigned long)+0x41) [0x558268818c51]
/usr/libexec/mysqld(print_fatal_signal(int)+0x3c3) [0x55826785ef43]
/usr/libexec/mysqld(my_server_abort()+0x76) [0x55826785f066]
/usr/libexec/mysqld(my_abort()+0xe) [0x558268812c1e]
/usr/libexec/mysqld(ut_dbg_assertion_failed(char const*, char const*, unsigned long)+0x32a) [0x558268a7142a]
/usr/libexec/mysqld(ib::fatal::~fatal()+0xde) [0x558268a7406e]
/usr/libexec/mysqld(srv_error_monitor_thread()+0x86f) [0x558268a056bf]
/usr/libexec/mysqld(std::thread::_State_impl<std::thread::_Invoker<std::tuple<Detached_thread, void (*)()> > >::_M_run()+0xc4) [0x55826891f154]
/lib64/libstdc++.so.6(+0xc2b13) [0x7f613b028b13]
/lib64/libpthread.so.0(+0x81ca) [0x7f613f5cb1ca]
/lib64/libc.so.6(clone+0x43) [0x7f613a640e73]
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.

Options: ReplyQuote


Subject
Written By
Posted
MySQL crashed and process in zombie state
November 14, 2023 02:59PM


Sorry, you can't reply to this topic. It has been closed.

Content reproduced on this site is the property of the respective copyright holders. It is not reviewed in advance by Oracle and does not necessarily represent the opinion of Oracle or any other party.