Description:
my mysql server alawys crash, so i see the log.like this :
InnoDB: ###### Diagnostic info printed to the standard error stream
2019-10-24T20:34:02.493026Z 0 [ERROR] [MY-012872] [InnoDB] [FATAL] Semaphore wait has lasted > 600 seconds. We intentionally crash the server because it appears to be hung.
2019-10-24T20:34:02.493066Z 0 [ERROR] [MY-013183] [InnoDB] Assertion failure: ut0ut.cc:532 thread 140640003274496
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.
20:34:02 UTC - mysqld got signal 6 ;
Most likely, you have hit a bug, but this error can also be caused by malfunctioning hardware.
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 0x46000
/usr/sbin/mysqld(my_print_stacktrace(unsigned char const*, unsigned long)+0x3d) [0x1f104dd]
/usr/sbin/mysqld(handle_fatal_signal+0x333) [0xf8b933]
/usr/lib64/libpthread.so.0(+0xf5e0) [0x7fe9add5d5e0]
/usr/lib64/libc.so.6(gsignal+0x37) [0x7fe9abe1d1f7]
/usr/lib64/libc.so.6(abort+0x148) [0x7fe9abe1e8e8]
/usr/sbin/mysqld() [0xcf7214]
/usr/sbin/mysqld(ib::fatal::~fatal()+0xa4) [0x21bc824]
/usr/sbin/mysqld(srv_error_monitor_thread()+0x882) [0x215ede2]
/usr/sbin/mysqld(std::thread::_State_impl<std::thread::_Invoker<std::tuple<Runnable, void (*)()> > >::_M_run()+0xb5) [0x2072995]
/usr/sbin/mysqld() [0x263cf3f]
/usr/lib64/libpthread.so.0(+0x7e25) [0x7fe9add55e25]
/usr/lib64/libc.so.6(clone+0x6d) [0x7fe9abee034d]
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.
2019-10-24T20:34:03.217866Z 0 [Warning] [MY-010139] [Server] Changed limits: max_open_files: 10000 (requested 10010)
2019-10-24T20:34:03.217877Z 0 [Warning] [MY-010142] [Server] Changed limits: table_open_cache: 3995 (requested 4000)
2019-10-24T20:34:03.480761Z 0 [Warning] [MY-011070] [Server] 'Disabling symbolic links using --skip-symbolic-links (or equivalent) is the default. Consider not using this option as it' is deprecated and will be removed in a future release.
2019-10-24T20:34:03.482389Z 0 [System] [MY-010116] [Server] /usr/sbin/mysqld (mysqld 8.0.18) starting as process 30995
2019-10-24T20:34:05.361786Z 0 [System] [MY-010229] [Server] Starting crash recovery...
2019-10-24T20:34:05.368817Z 0 [System] [MY-010232] [Server] Crash recovery finished.
2019-10-24T20:34:05.993814Z 0 [Warning] [MY-010068] [Server] CA certificate ca.pem is self signed.
please help me,thanks
How to repeat:
InnoDB: ###### Diagnostic info printed to the standard error stream
2019-10-24T20:34:02.493026Z 0 [ERROR] [MY-012872] [InnoDB] [FATAL] Semaphore wait has lasted > 600 seconds. We intentionally crash the server because it appears to be hung.
2019-10-24T20:34:02.493066Z 0 [ERROR] [MY-013183] [InnoDB] Assertion failure: ut0ut.cc:532 thread 140640003274496
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.
20:34:02 UTC - mysqld got signal 6 ;
Most likely, you have hit a bug, but this error can also be caused by malfunctioning hardware.
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 0x46000
/usr/sbin/mysqld(my_print_stacktrace(unsigned char const*, unsigned long)+0x3d) [0x1f104dd]
/usr/sbin/mysqld(handle_fatal_signal+0x333) [0xf8b933]
/usr/lib64/libpthread.so.0(+0xf5e0) [0x7fe9add5d5e0]
/usr/lib64/libc.so.6(gsignal+0x37) [0x7fe9abe1d1f7]
/usr/lib64/libc.so.6(abort+0x148) [0x7fe9abe1e8e8]
/usr/sbin/mysqld() [0xcf7214]
/usr/sbin/mysqld(ib::fatal::~fatal()+0xa4) [0x21bc824]
/usr/sbin/mysqld(srv_error_monitor_thread()+0x882) [0x215ede2]
/usr/sbin/mysqld(std::thread::_State_impl<std::thread::_Invoker<std::tuple<Runnable, void (*)()> > >::_M_run()+0xb5) [0x2072995]
/usr/sbin/mysqld() [0x263cf3f]
/usr/lib64/libpthread.so.0(+0x7e25) [0x7fe9add55e25]
/usr/lib64/libc.so.6(clone+0x6d) [0x7fe9abee034d]
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.
2019-10-24T20:34:03.217866Z 0 [Warning] [MY-010139] [Server] Changed limits: max_open_files: 10000 (requested 10010)
2019-10-24T20:34:03.217877Z 0 [Warning] [MY-010142] [Server] Changed limits: table_open_cache: 3995 (requested 4000)
2019-10-24T20:34:03.480761Z 0 [Warning] [MY-011070] [Server] 'Disabling symbolic links using --skip-symbolic-links (or equivalent) is the default. Consider not using this option as it' is deprecated and will be removed in a future release.
2019-10-24T20:34:03.482389Z 0 [System] [MY-010116] [Server] /usr/sbin/mysqld (mysqld 8.0.18) starting as process 30995
2019-10-24T20:34:05.361786Z 0 [System] [MY-010229] [Server] Starting crash recovery...
2019-10-24T20:34:05.368817Z 0 [System] [MY-010232] [Server] Crash recovery finished.
2019-10-24T20:34:05.993814Z 0 [Warning] [MY-010068] [Server] CA certificate ca.pem is self signed.