Bug #111053 mysql server can not startup
Submitted: 17 May 2:46 Modified: 17 May 8:18
Reporter: shou lee Email Updates:
Status: Unsupported Impact on me:
Category:MySQL Server Severity:S1 (Critical)
Version:5.6.39 OS:CentOS (2.6.32-431.el6.x86_64)
Assigned to: CPU Architecture:x86

[17 May 2:46] shou lee
InnoDB: ###### Diagnostic info printed to the standard error stream
InnoDB: Error: semaphore wait has lasted > 600 seconds
InnoDB: We intentionally crash the server, because it appears to be hung.
2023-05-16 15:25:34 7ff615485700  InnoDB: Assertion failure in thread 140694895744768 in file srv0srv.cc line 1757
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/5.6/en/forcing-innodb-recovery.html
InnoDB: about forcing recovery.
07:25:34 UTC - mysqld got signal 6 ;
This could be because you hit a bug. It is also possible that this binary
or one of the libraries it was linked against is corrupt, improperly built,
or misconfigured. This error can also be caused by malfunctioning hardware.
We will try our best to scrape up some info that will hopefully help
diagnose the problem, but since we have already crashed, 
something is definitely wrong and this may fail.

It is possible that mysqld could use up to 
key_buffer_size + (read_buffer_size + sort_buffer_size)*max_threads = 603387 K  bytes of memory
Hope that's ok; if not, decrease some variables in the equation.

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 0x40000
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.

How to repeat:
when there are many transactions,and then delete data in a large table.
[17 May 8:18] MySQL Verification Team
Hello shou lee,

Thank you for the report and feedback.
However, please note that MySQL 5.6 is off the maintenance for a long time. 
Please upgrade to 8.0, report us back if you are still experiencing the reported issue along with the a test case to reproduce at our end. 

Quoting from official EOL announcement - 
"MySQL 5.6 is covered under Oracle Lifetime Sustaining Support.

Per Oracle's Lifetime Support policy, as of February 1, 2021, MySQL 5.6 is covered under Oracle Sustaining Support.

Users are encouraged to upgrade to MySQL 8.0.". https://www.mysql.com/support/eol-notice.html