Linux centos 7 mysql can’t start with error infomation Job for mysqld.service failed because the control process exited with error code

admin

I run the command “service mysqld status”, then console shows following:

Redirecting to /bin/systemctl status mysqld.service
● mysqld.service - MySQL Server
   Loaded: loaded (/usr/lib/systemd/system/mysqld.service; enabled; vendor preset: disabled)
   Active: failed (Result: start-limit) since Thu 2023-05-04 09:46:13 EDT; 8min ago
     Docs: man:mysqld(8)
           http://dev.mysql.com/doc/refman/en/using-systemd.html
  Process: 13621 ExecStart=/usr/sbin/mysqld $MYSQLD_OPTS (code=exited, status=2)
  Process: 13589 ExecStartPre=/usr/bin/mysqld_pre_systemd (code=exited, status=0/SUCCESS)
 Main PID: 13621 (code=exited, status=2)
   Status: "Server startup in progress"

and my “/var/log/mysqld.log” shows folloing:


2023-05-04T13:57:48.755032Z 0 [System] [MY-013951] [Server] 2023-05-04T13:57:48Z UTC - mysqld got signal 11 ;
2023-05-04T13:57:48.755033Z 0 [System] [MY-013951] [Server] Most likely, you have hit a bug, but this error can also be caused by malfunctioning hardware.
2023-05-04T13:57:48.755034Z 0 [System] [MY-013951] [Server] BuildID[sha1]=9ae612eb139943fd0ad78ded1a800776626be701
2023-05-04T13:57:48.755035Z 0 [System] [MY-013951] [Server] Thread pointer: 0x0
2023-05-04T13:57:48.755036Z 0 [System] [MY-013951] [Server] Attempting backtrace. You can use the following information to find out
2023-05-04T13:57:48.755037Z 0 [System] [MY-013951] [Server] where mysqld died. If you see no messages after this, something went
2023-05-04T13:57:48.755038Z 0 [System] [MY-013951] [Server] terribly wrong...
2023-05-04T13:57:48.755039Z 0 [System] [MY-013951] [Server] stack_bottom = 0 thread_stack 0x100000
2023-05-04T13:57:48.755040Z 0 [System] [MY-013951] [Server] /usr/sbin/mysqld(my_print_stacktrace(unsigned char const*, unsigned long)+0x44) [0x1e07324]
2023-05-04T13:57:48.755041Z 0 [System] [MY-013951] [Server] /usr/sbin/mysqld(print_fatal_signal(int)+0x33c) [0xf121fc]
2023-05-04T13:57:48.755042Z 0 [System] [MY-013951] [Server] /usr/sbin/mysqld(handle_fatal_signal+0x98) [0xf122d8]
2023-05-04T13:57:48.755043Z 0 [System] [MY-013951] [Server] [0x7f8369c7b0]
2023-05-04T13:57:48.755044Z 0 [System] [MY-013951] [Server] /usr/sbin/mysqld(memory::Aligned_atomic<long>::Aligned_atomic()+0x70) [0x1ac75b0]
2023-05-04T13:57:48.755045Z 0 [System] [MY-013951] [Server] /usr/sbin/mysqld(Delegate::Delegate(unsigned int)+0x5c) [0x1ac785c]
2023-05-04T13:57:48.755046Z 0 [System] [MY-013951] [Server] /usr/sbin/mysqld(delegates_init()+0x40) [0x1ac79c0]
2023-05-04T13:57:48.755047Z 0 [System] [MY-013951] [Server] /usr/sbin/mysqld() [0xce3b60]
2023-05-04T13:57:48.755048Z 0 [System] [MY-013951] [Server] /usr/sbin/mysqld(mysqld_main(int, char**)+0x1d8c) [0xcea76c]
2023-05-04T13:57:48.755049Z 0 [System] [MY-013951] [Server] /lib64/libc.so.6(__libc_start_main+0xf0) [0x7f82efa724]
2023-05-04T13:57:48.755050Z 0 [System] [MY-013951] [Server] /usr/sbin/mysqld() [0xccfc40]
2023-05-04T13:57:48.755051Z 0 [System] [MY-013951] [Server] The manual page at http://dev.mysql.com/doc/mysql/en/crashing.html contains
2023-05-04T13:57:48.755052Z 0 [System] [MY-013951] [Server] information that should help you find out what is causing the crash.
2023-05-04T13:57:48.926319Z 0 [System] [MY-010116] [Server] /usr/sbin/mysqld (mysqld 8.0.33) starting as process 14138
2023-05-04T13:57:48.928040Z 0 [System] [MY-013951] [Server] A backtrace was processed and added to the main error-log in the appropriate format.

I don’t understand the stack trace. and what the information I can learn from the log files? thanks a lot.

Read more here: Source link