2022-07-25 05:00:02 0x7fc02c2e2700 InnoDB: Assertion failure in file /home/buildbot/buildbot/padding_for_CPACK_RPM_BUILD_SOURCE_DIRS_PREFIX/mariadb-10.4.21/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. 220725 5:00:02 [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.21-MariaDB-log key_buffer_size=4294967296 read_buffer_size=1048576 max_used_connections=53 max_threads=122 thread_count=24 It is possible that mysqld could use up to key_buffer_size + (read_buffer_size + sort_buffer_size)*max_threads = 4447159 K bytes of memory Hope that's ok; if not, decrease some variables in the equation. Thread pointer: 0x7fbee02429a8 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 = 0x7fc02c2e1cc0 thread_stack 0x49000 /usr/sbin/mysqld(my_print_stacktrace+0x2e)[0x55a23c9cd25e] /usr/sbin/mysqld(handle_fatal_signal+0x30f)[0x55a23c45599f] sigaction.c:0(__restore_rt)[0x7fc990205630] :0(__GI_raise)[0x7fc98f650387] :0(__GI_abort)[0x7fc98f651a78] /usr/sbin/mysqld(+0x5cb5ae)[0x55a23c1475ae] /usr/sbin/mysqld(+0xaf466d)[0x55a23c67066d] /usr/sbin/mysqld(+0xc67bef)[0x55a23c7e3bef] /usr/sbin/mysqld(+0xc06c04)[0x55a23c782c04] /usr/sbin/mysqld(+0xc362a0)[0x55a23c7b22a0] /usr/sbin/mysqld(+0xc37de0)[0x55a23c7b3de0] /usr/sbin/mysqld(+0xc386eb)[0x55a23c7b46eb] /usr/sbin/mysqld(+0xc13dd1)[0x55a23c78fdd1] /usr/sbin/mysqld(+0xc03d1e)[0x55a23c77fd1e] /usr/sbin/mysqld(+0xc084e9)[0x55a23c7844e9] /usr/sbin/mysqld(+0xbfa1a7)[0x55a23c7761a7] /usr/sbin/mysqld(+0xb75a5e)[0x55a23c6f1a5e] /usr/sbin/mysqld(+0xb78b80)[0x55a23c6f4b80] /usr/sbin/mysqld(+0xa8d377)[0x55a23c609377] /usr/sbin/mysqld(_ZN7handler18ha_index_next_sameEPhPKhj+0x86)[0x55a23c45ba16] /usr/sbin/mysqld(+0x70130d)[0x55a23c27d30d] /usr/sbin/mysqld(_Z10sub_selectP4JOINP13st_join_tableb+0x24f)[0x55a23c27418f] /usr/sbin/mysqld(_ZN4JOIN10exec_innerEv+0xc3f)[0x55a23c2a1fbf] /usr/sbin/mysqld(_ZN4JOIN4execEv+0x33)[0x55a23c2a22d3] /usr/sbin/mysqld(_Z12mysql_selectP3THDP10TABLE_LISTjR4ListI4ItemEPS4_jP8st_orderS9_S7_S9_yP13select_resultP18st_select_lex_unitP13st_select_lex+0x186)[0x55a23c2a0406] /usr/sbin/mysqld(_Z13handle_selectP3THDP3LEXP13select_resultm+0x1e7)[0x55a23c2a0fa7] /usr/sbin/mysqld(+0x5b5e4e)[0x55a23c131e4e] /usr/sbin/mysqld(_Z21mysql_execute_commandP3THD+0x398f)[0x55a23c2452cf] /usr/sbin/mysqld(_Z11mysql_parseP3THDPcjP12Parser_statebb+0x22b)[0x55a23c249dfb] /usr/sbin/mysqld(_Z16dispatch_command19enum_server_commandP3THDPcjbb+0x1e19)[0x55a23c24ccb9] /usr/sbin/mysqld(_Z10do_commandP3THD+0x11b)[0x55a23c24df1b] /usr/sbin/mysqld(_Z24do_handle_one_connectionP7CONNECT+0x202)[0x55a23c32f382] /usr/sbin/mysqld(handle_one_connection+0x3d)[0x55a23c32f46d] /usr/sbin/mysqld(+0xe02eed)[0x55a23c97eeed] /lib64/libpthread.so.0(+0x7ea5)[0x7fc9901fdea5] /lib64/libc.so.6(clone+0x6d)[0x7fc98f718b0d] Trying to get some variables. Some pointers may be invalid and cause the dump to abort. Query (0x7fbee0136d58): SELECT MAX(issue_dtg) AS issue_dtg FROM roads.pat_forecasts WHERE issued = 1 Connection ID (thread ID): 8555812 Status: NOT_KILLED Optimizer switch: index_merge=on,index_merge_union=on,index_merge_sort_union=on,index_merge_intersection=on,index_merge_sort_intersection=off,engine_condition_pushdown=off,index_condition_pushdown=on,derived_merge=on,derived_with_keys=on,firstmatch=on,loosescan=on,materialization=on,in_to_exists=on,semijoin=on,partial_match_rowid_merge=on,partial_match_table_scan=on,subquery_cache=on,mrr=off,mrr_cost_based=off,mrr_sort_keys=off,outer_join_with_cache=on,semijoin_with_cache=on,join_cache_incremental=on,join_cache_hashed=on,join_cache_bka=on,optimize_join_buffer_size=on,table_elimination=on,extended_keys=on,exists_to_in=on,orderby_uses_equalities=on,condition_pushdown_for_derived=on,split_materialized=on,condition_pushdown_for_subquery=on,rowid_filter=on,condition_pushdown_from_having=on The manual page at https://mariadb.com/kb/en/how-to-produce-a-full-stack-trace-for-mysqld/ contains information that should help you find out what is causing the crash. Writing a core file... Working directory at /data/mysql Resource Limits: Limit Soft Limit Hard Limit Units Max cpu time unlimited unlimited seconds Max file size unlimited unlimited bytes Max data size unlimited unlimited bytes Max stack size 8388608 unlimited bytes Max core file size 0 unlimited bytes Max resident set unlimited unlimited bytes Max processes 767291 767291 processes Max open files 32768 32768 files Max locked memory 65536 65536 bytes Max address space unlimited unlimited bytes Max file locks unlimited unlimited locks Max pending signals 767291 767291 signals Max msgqueue size 819200 819200 bytes Max nice priority 0 0 Max realtime priority 0 0 Max realtime timeout unlimited unlimited us Core pattern: core 2022-07-25 5:00:51 0 [Note] InnoDB: Using Linux native AIO 2022-07-25 5:00:51 0 [Note] InnoDB: Mutexes and rw_locks use GCC atomic builtins 2022-07-25 5:00:51 0 [Note] InnoDB: Uses event mutexes 2022-07-25 5:00:51 0 [Note] InnoDB: Compressed tables use zlib 1.2.7 2022-07-25 5:00:51 0 [Note] InnoDB: Number of pools: 1 2022-07-25 5:00:51 0 [Note] InnoDB: Using SSE2 crc32 instructions 2022-07-25 5:00:51 0 [Note] InnoDB: Initializing buffer pool, total size = 32G, instances = 32, chunk size = 128M 2022-07-25 5:00:52 0 [Note] InnoDB: Completed initialization of buffer pool 2022-07-25 5:00:52 0 [Note] InnoDB: If the mysqld execution user is authorized, page cleaner thread priority can be changed. See the man page of setpriority(). 2022-07-25 5:00:52 0 [Note] InnoDB: Starting crash recovery from checkpoint LSN=84290055906128 2022-07-25 5:00:53 0 [Note] InnoDB: 3 transaction(s) which must be rolled back or cleaned up in total 21984 row operations to undo 2022-07-25 5:00:53 0 [Note] InnoDB: Trx id counter is 462641896621 2022-07-25 5:00:53 0 [Note] InnoDB: Starting final batch to recover 1760 pages from redo log. 2022-07-25 5:00:54 0 [Note] InnoDB: Last binlog file './mddb-bin.000005', position 391166 2022-07-25 5:00:54 0 [Note] InnoDB: 128 out of 128 rollback segments are active. 2022-07-25 5:00:54 0 [Note] InnoDB: Starting in background the rollback of recovered transactions 2022-07-25 5:00:54 0 [Note] InnoDB: Removed temporary tablespace data file: "ibtmp1" 2022-07-25 5:00:54 0 [Note] InnoDB: Creating shared tablespace for temporary tables 2022-07-25 5:00:54 0 [Note] InnoDB: Setting file './ibtmp1' size to 12 MB. Physically writing the file full; Please wait ... 2022-07-25 5:00:54 0 [Note] InnoDB: File './ibtmp1' size is now 12 MB. 2022-07-25 5:00:54 0 [Note] InnoDB: Waiting for purge to start 2022-07-25 5:00:54 0 [Note] InnoDB: Rolled back recovered transaction 462641890483 2022-07-25 5:00:54 0 [Note] InnoDB: 10.4.21 started; log sequence number 84290061072745; transaction id 462641896623 2022-07-25 5:00:54 0 [Note] InnoDB: Loading buffer pool(s) from /data/mysql/ib_buffer_pool 2022-07-25 5:00:54 0 [Note] Plugin 'FEEDBACK' is disabled. 2022-07-25 5:00:54 0 [Note] Recovering after a crash using mddb-bin 2022-07-25 5:00:54 0 [Note] Starting crash recovery... 2022-07-25 5:00:54 0 [Note] Crash recovery finished.