[MDEV-24495] InnoDB: Assertion failure in file ut0lst.h line 334 Created: 2020-12-28  Updated: 2022-01-06  Resolved: 2022-01-06

Status: Closed
Project: MariaDB Server
Component/s: Storage Engine - InnoDB
Affects Version/s: 10.4.17
Fix Version/s: N/A

Type: Bug Priority: Major
Reporter: Silver Asu Assignee: Marko Mäkelä
Resolution: Incomplete Votes: 0
Labels: None
Environment:

Linux


Attachments: Text File lvpmd203_error_log.log    
Issue Links:
Relates
relates to MDEV-22956 rpl.rpl_old_master failed in buildbot... Open
relates to MDEV-24489 Server crashes: double free or corrup... Closed

 Description   

We have weird crash, that seems to be simple SELECT query, but every time server fails to recover from crash, because Cannot rename './db/catalog_product_index_eav_replica.ibd' to './db/catalog_product_index_eav.ibd' etc errors. (these rename errors are not in same database)

2020-12-28 17:33:34 0x7fc2f18ee700  InnoDB: Assertion failure in file /build/amd64-usr/var/tmp/portage/dev-db/mariadb-10.4.17/work/mariadb-10.4.17/storage/innobase/include/ut0lst.h line 334
InnoDB: Failing assertion: list.count > 0
InnoDB: We intentionally generate a memory trap.
InnoDB: Submit a detailed bug report to https://jira.mariadb.org/
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: https://mariadb.com/kb/en/library/innodb-recovery-modes/
InnoDB: about forcing recovery.
201228 17:33:34 [ERROR] 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.
To report this bug, see https://mariadb.com/kb/en/reporting-bugs
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.
Server version: 10.4.17-MariaDB-log
key_buffer_size=4294967296
read_buffer_size=2097152
max_used_connections=260
max_threads=1502
thread_count=89
It is possible that mysqld could use up to
key_buffer_size + (read_buffer_size + sort_buffer_size)*max_threads = 19611898 K  bytes of memory
Hope that's ok; if not, decrease some variables in the equation.
Thread pointer: 0x7fc13c000c48
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 = 0x7fc2f18edd98 thread_stack 0x49000
/opt/zse/sbin/mysqld(my_print_stacktrace+0x29)[0x556134be9319]
/opt/zse/sbin/mysqld(handle_fatal_signal+0x53d)[0x55613472878d]
sigaction.c:0(__restore_rt)[0x7fc6454722b0]
/lib64/libc.so.6(gsignal+0x141)[0x7fc644adfe41]
/lib64/libc.so.6(abort+0x127)[0x7fc644ac955d]
/opt/zse/sbin/mysqld(+0x54e2cd)[0x55613442c2cd]
/opt/zse/sbin/mysqld(+0x532d87)[0x556134410d87]
/opt/zse/sbin/mysqld(+0xb7e387)[0x556134a5c387]
/opt/zse/sbin/mysqld(+0x552d2c)[0x556134430d2c]
/opt/zse/sbin/mysqld(+0xb54796)[0x556134a32796]
/opt/zse/sbin/mysqld(+0xb557b9)[0x556134a337b9]
/opt/zse/sbin/mysqld(+0xb55da1)[0x556134a33da1]
/opt/zse/sbin/mysqld(+0xb3931e)[0x556134a1731e]
/opt/zse/sbin/mysqld(+0xb2d808)[0x556134a0b808]
/opt/zse/sbin/mysqld(+0xb320f8)[0x556134a100f8]
/opt/zse/sbin/mysqld(+0xb26f88)[0x556134a04f88]
/opt/zse/sbin/mysqld(+0xabdef9)[0x55613499bef9]
/opt/zse/sbin/mysqld(+0xac0325)[0x55613499e325]
/opt/zse/sbin/mysqld(+0x9f3809)[0x5561348d1809]
/opt/zse/sbin/mysqld(_ZN7handler18ha_index_next_sameEPhPKhj+0x1c8)[0x55613472e688]
/opt/zse/sbin/mysqld(_ZN7handler21multi_range_read_nextEPPv+0x2b)[0x556134640adb]
/opt/zse/sbin/mysqld(_ZN23Mrr_simple_index_reader8get_nextEPPv+0x40)[0x556134640bd0]
/opt/zse/sbin/mysqld(_ZN10DsMrr_impl10dsmrr_nextEPPv+0x42)[0x556134642042]
/opt/zse/sbin/mysqld(_ZN18QUICK_RANGE_SELECT8get_nextEv+0x23)[0x55613483b4a3]
/opt/zse/sbin/mysqld(_Z8filesortP3THDP5TABLEP8FilesortP16Filesort_trackerP4JOINy+0xabf)[0x556134726f3f]
/opt/zse/sbin/mysqld(_Z17create_sort_indexP3THDP4JOINP13st_join_tableP8Filesort+0xd0)[0x556134574980]
/opt/zse/sbin/mysqld(_ZN13st_join_table10sort_tableEv+0x71)[0x556134574cd1]
/opt/zse/sbin/mysqld(_Z21join_init_read_recordP13st_join_table+0x39)[0x556134574d59]
/opt/zse/sbin/mysqld(_Z10sub_selectP4JOINP13st_join_tableb+0x173)[0x556134560283]
/opt/zse/sbin/mysqld(_ZN4JOIN10exec_innerEv+0xd43)[0x55613458b8c3]
/opt/zse/sbin/mysqld(_ZN4JOIN4execEv+0x2b)[0x55613458baeb]
/opt/zse/sbin/mysqld(_Z12mysql_selectP3THDP10TABLE_LISTjR4ListI4ItemEPS4_jP8st_orderS9_S7_S9_yP13select_resultP18st_select_lex_unitP13st_select_lex+0x133)[0x556134589c63]
/opt/zse/sbin/mysqld(_Z13handle_selectP3THDP3LEXP13select_resultm+0x152)[0x55613458a712]
/opt/zse/sbin/mysqld(+0x63d539)[0x55613451b539]
/opt/zse/sbin/mysqld(_Z21mysql_execute_commandP3THD+0x6802)[0x556134529be2]
/opt/zse/sbin/mysqld(_Z11mysql_parseP3THDPcjP12Parser_statebb+0x1c4)[0x55613452c474]
/opt/zse/sbin/mysqld(_Z16dispatch_command19enum_server_commandP3THDPcjbb+0x1cd0)[0x55613452f2f0]
/opt/zse/sbin/mysqld(_Z10do_commandP3THD+0x101)[0x556134530a41]
/opt/zse/sbin/mysqld(_Z24do_handle_one_connectionP7CONNECT+0x1c4)[0x556134615844]
/opt/zse/sbin/mysqld(handle_one_connection+0x32)[0x556134615982]
/opt/zse/sbin/mysqld(+0xccaa63)[0x556134ba8a63]
nptl/pthread_create.c:480(start_thread)[0x7fc645466f87]
/lib64/libc.so.6(clone+0x3f)[0x7fc644ba317f]
Trying to get some variables.
Some pointers may be invalid and cause the dump to abort.
Query (0x7fc13c010050): SELECT t.*, tt.* FROM re_terms AS t INNER JOIN re_term_taxonomy AS tt ON t.term_id = tt.term_id WHERE tt.taxonomy IN ('post_tag') AND tt.count > 0 ORDER BY tt.count DESC LIMIT 300
Connection ID (thread ID): 6797144



 Comments   
Comment by Yakov Kushnirsky [ 2021-11-15 ]

Also reported in 10.4.19

Comment by Marko Mäkelä [ 2021-11-29 ]

Can you please provide a resolved stack trace of the crash? The addresses in the Description and in the stack trace that occurs in lvpmd203_error_log.log only include numeric addresses, which are specific to the executable that was used.

Generated at Thu Feb 08 09:30:25 UTC 2024 using Jira 8.20.16#820016-sha1:9d11dbea5f4be3d4cc21f03a88dd11d8c8687422.