Description:
Mysqld will get crashed unexpectedly.
The info in mysql.err as follows:
2023-08-17T15:00:11.123272Z 0 [ERROR] InnoDB: ibuf cursor restoration fails!. ibuf record inserted to page 1956:28
2023-08-17T15:00:11.134535Z 0 [ERROR] InnoDB: Submit a detailed bug report to http://bugs.mysql.com
PHYSICAL RECORD: n_fields 1; 1-byte offsets; info bits 0
0: len 8; hex 696e66696d756d00; asc infimum ;;
PHYSICAL RECORD: n_fields 6; 1-byte offsets; info bits 32
0: len 4; hex 000007a4; asc ;;
1: len 1; hex 00; asc ;;
2: len 4; hex 0000001c; asc ;;
3: len 16; hex 001700010c0f012c0021080000068000; asc , ! ;;
4: len 30; hex e98391e5b79ee5b882e7b4abe88d86e5b1b1e585ace59bade5b08fe58d96; asc ; (total 33 bytes);
5: len 6; hex 0003dbfd0a84; asc ;;
DATA TUPLE: 3 fields;
0: len 4; hex 000007a4; asc ;;
1: len 1; hex 00; asc ;;
2: len 4; hex 0000001c; asc ;;
PHYSICAL RECORD: n_fields 6; 1-byte offsets; info bits 32
0: len 4; hex 000007a4; asc ;;
1: len 1; hex 00; asc ;;
2: len 4; hex 0000001c; asc ;;
3: len 16; hex 001700010c0f012c0021080000068000; asc , ! ;;
4: len 30; hex e98391e5b79ee5b882e7b4abe88d86e5b1b1e585ace59bade5b08fe58d96; asc ; (total 33 bytes);
5: len 6; hex 0003dbfd0a84; asc ;;
2023-08-17T15:00:11.184896Z 0 [ERROR] [FATAL] InnoDB: Failed to restore ibuf position.
2023-08-17 23:00:11 0x7fa05b16b700 InnoDB: Assertion failure in thread 140326699710208 in file ut0ut.cc line 916
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.
15:00:11 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=8388608
read_buffer_size=131072
max_used_connections=72
max_threads=151
thread_count=48
connection_count=47
It is possible that mysqld could use up to
key_buffer_size + (read_buffer_size + sort_buffer_size)*max_threads = 68190 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
/usr/mysql/bin/mysqld(my_print_stacktrace+0x35)[0xf1dff5]
/usr/mysql/bin/mysqld(handle_fatal_signal+0x4a4)[0x79d3b4]
/lib64/libpthread.so.0(+0xf100)[0x7fa07165c100]
/lib64/libc.so.6(gsignal+0x37)[0x7fa07025b5f7]
/lib64/libc.so.6(abort+0x148)[0x7fa07025cce8]
/usr/mysql/bin/mysqld[0x1159d65]
/usr/mysql/bin/mysqld(_ZN2ib5fatalD1Ev+0xb3)[0x115e8b3]
/usr/mysql/bin/mysqld[0x102b4d1]
/usr/mysql/bin/mysqld[0x102f531]
/usr/mysql/bin/mysqld(_Z29ibuf_merge_or_delete_for_pageP11buf_block_tRK9page_id_tPK11page_size_tm+0xb09)[0x1033b29]
/usr/mysql/bin/mysqld(_Z20buf_page_io_completeP10buf_page_tb+0x4e1)[0x11a59a1]
/usr/mysql/bin/mysqld(_Z12fil_aio_waitm+0x15b)[0x1200afb]
/usr/mysql/bin/mysqld(io_handler_thread+0xc8)[0x110db48]
/lib64/libpthread.so.0(+0x7dc5)[0x7fa071654dc5]
/lib64/libc.so.6(clone+0x6d)[0x7fa07031c1cd]
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.
2023-08-17T15:00:11.409568Z mysqld_safe Number of processes running now: 0
mysqld_safe mysqld restarted but failed:
2023-08-17T15:00:16.308291Z 0 [Note] Found 1 prepared transaction(s) in InnoDB
2023-08-17 23:00:16 0x7fba95e39740 InnoDB: Assertion failure in thread 140439355365184 in file ut0lst.h line 293
InnoDB: Failing assertion: list.count > 0
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.
15:00:16 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=8388608
read_buffer_size=131072
max_used_connections=0
max_threads=151
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 = 68190 K bytes of memory
Hope that's ok; if not, decrease some variables in the equation.
How to repeat:
I can't repaet this problem.
Suggested fix:
I find a similar bug:
Bug #91033 InnoDB: ibuf cursor restoration fails!
but I'm not sure if it's the same as mine.
