Bug #99016 During shutdown: InnoDB: Assertion failure in thread 4146852864 in file ut0ut.cc
Submitted: 21 Mar 2020 11:20 Modified: 23 Mar 2020 6:10
Reporter: Michael Brunnbauer Email Updates:
Status: Duplicate Impact on me:
None 
Category:MySQL Server Severity:S2 (Serious)
Version:5.7.29 OS:Linux (glibc 2.30 kernel 4.9.210)
Assigned to: CPU Architecture:x86

[21 Mar 2020 11:20] Michael Brunnbauer
Description:
2020-03-21T11:07:28.629444Z 0 [Note] Shutting down plugin 'InnoDB'
2020-03-21T11:07:28.629594Z 0 [Note] InnoDB: FTS optimize thread exiting.
2020-03-21T11:07:28.629927Z 0 [Note] InnoDB: Starting shutdown...
2020-03-21T11:07:28.739360Z 0 [Note] InnoDB: Dumping buffer pool(s) to /var/databases/mysql/ib_buffer_pool
2020-03-21T11:07:28.740377Z 0 [Note] InnoDB: Buffer pool(s) dump completed at 200321 12:07:28
2020-03-21T11:07:29.396859Z 0 [ERROR] [FATAL] InnoDB: Page [page id: space=416161, page number=35] still fixed or dirty
2020-03-21 12:07:29 0xf72bf400  InnoDB: Assertion failure in thread 4146852864 in file ut0ut.cc line 918
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.7/en/forcing-innodb-recovery.html
InnoDB: about forcing recovery.
11:07:29 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.
Attempting to collect some information that could help diagnose the problem.
As this is a crash and something is definitely wrong, the information
collection process might fail.

key_buffer_size=1073741824
read_buffer_size=16777216
max_used_connections=50
max_threads=200
thread_count=0
connection_count=0
It is possible that mysqld could use up to
key_buffer_size + (read_buffer_size + sort_buffer_size)*max_threads = 657150 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 0x30000
/usr/bin/mysqld(my_print_stacktrace+0x28)[0x8adbb78]
/usr/bin/mysqld(handle_fatal_signal+0x42a)[0x83a3b3a]
/lib/libpthread.so.0(+0x14268)[0xf7788268]
/lib/ld-linux.so.2(+0xd22)[0xf77a0d22]
/lib/libc.so.6(gsignal+0xd6)[0xf72f0386]
/lib/libc.so.6(abort+0x17e)[0xf72f18be]
/usr/bin/mysqld[0x837a222]
/usr/bin/mysqld(_ZN2ib5fatalD1Ev+0x53)[0x8e63a13]
/usr/bin/mysqld(_Z13buf_all_freedv+0x38e)[0x8e9c12e]
/usr/bin/mysqld(_Z37logs_empty_and_mark_files_at_shutdownv+0x14f3)[0x8d31423]
/usr/bin/mysqld(_Z27innobase_shutdown_for_mysqlv+0x98f)[0x8e0575f]
/usr/bin/mysqld[0x8ccdd0d]
/usr/bin/mysqld(_Z22ha_finalize_handlertonP13st_plugin_int+0x33)[0x83f5133]
/usr/bin/mysqld[0x88abb36]
/usr/bin/mysqld(_Z15plugin_shutdownv+0x272)[0x88adf22]
/usr/bin/mysqld[0x83986c7]
/usr/bin/mysqld(_Z11mysqld_mainiPPc+0x1e6e)[0x839e6ae]
/usr/bin/mysqld(main+0x1b)[0x837b7db]
/lib/libc.so.6(__libc_start_main+0x105)[0xf72d9395]
/usr/bin/mysqld(_start+0x21)[0x8392f21]
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.
2020-03-21T11:07:29.612993Z mysqld_safe Number of processes running now: 0
2020-03-21T11:07:29.618776Z mysqld_safe mysqld restarted

How to repeat:
call mysqladmin shutdown
[23 Mar 2020 6:10] MySQL Verification Team
please follow https://bugs.mysql.com/bug.php?id=95285