2023-04-26 13:06:45 11 [ERROR] InnoDB: Record in index `CIADC4B51B67D37D5B` of table `demotelereleve1`.`iotdevicegroup` was not found on update: TUPLE (info_bits=0, 2 fields): {[8] j(0x00000000D4B0DA6A),[32]b3dbc1d687b96b4b0187bc3a1e2c0a93(0x6233646263316436383762393662346230313837626333613165326330613933)} at: COMPACT RECORD(info_bits=0, 2 fields): {[8] (0x00000000D3EC98F2),[32]b3dbc1d67a1f80cf017a1f89d35c361d(0x6233646263316436376131663830636630313761316638396433356333363164)} 2023-04-26 13:06:45 0x7f9223aa7700 InnoDB: Assertion failure in file /home/buildbot/buildbot/padding_for_CPACK_RPM_BUILD_SOURCE_DIRS_PREFIX/mariadb-10.4.28/storage/innobase/row/row0ins.cc line 219 InnoDB: Failing assertion: !cursor->index->is_committed() 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. 230426 13:06:45 [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.28-MariaDB-log source revision: c8f2e9a5c0ac5905f28b050b7df5a9ffd914b7e7 key_buffer_size=134217728 read_buffer_size=131072 max_used_connections=5 max_threads=3002 thread_count=13 It is possible that mysqld could use up to key_buffer_size + (read_buffer_size + sort_buffer_size)*max_threads = 6738003 K bytes of memory Hope that's ok; if not, decrease some variables in the equation. Thread pointer: 0x7f9059a20e48 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 = 0x7f9223aa4cd8 thread_stack 0x49000 /usr/sbin/mysqld(my_print_stacktrace+0x2e)[0x556c47bb137e] /usr/sbin/mysqld(handle_fatal_signal+0x55d)[0x556c4765ff3d] /lib64/libpthread.so.0(+0x12cf0)[0x7f922200fcf0] /lib64/libc.so.6(gsignal+0x10f)[0x7f922136aaff] /lib64/libc.so.6(abort+0x127)[0x7f922133dea5] /usr/sbin/mysqld(+0x5c7051)[0x556c47367051] /usr/sbin/mysqld(+0x5b581b)[0x556c4735581b] /usr/sbin/mysqld(+0xc28fde)[0x556c479c8fde] /usr/sbin/mysqld(+0xc61e99)[0x556c47a01e99] /usr/sbin/mysqld(+0xc628ef)[0x556c47a028ef] /usr/sbin/mysqld(+0xc3c2ac)[0x556c479dc2ac] /usr/sbin/mysqld(+0xb7e1c1)[0x556c4791e1c1] /usr/sbin/mysqld(_ZN7handler13ha_update_rowEPKhS1_+0x12b)[0x556c4766d13b] /usr/sbin/mysqld(_ZN21Update_rows_log_event11do_exec_rowEP14rpl_group_info+0x237)[0x556c4775b2d7] /usr/sbin/mysqld(_ZN14Rows_log_event14do_apply_eventEP14rpl_group_info+0x237)[0x556c4774e4a7] /usr/sbin/mysqld(+0x621ed2)[0x556c473c1ed2] /usr/sbin/mysqld(handle_slave_sql+0x16d2)[0x556c473c9422] /usr/sbin/mysqld(+0xb234fa)[0x556c478c34fa] /lib64/libpthread.so.0(+0x81cf)[0x7f92220051cf] 2023-04-26 13:06:46 69907 [Warning] Access denied for user 'myuser'@'localhost' (using password: YES) /lib64/libc.so.6(clone+0x43)[0x7f9221355e73] Trying to get some variables. Some pointers may be invalid and cause the dump to abort. Query (0x0): (null) Connection ID (thread ID): 11 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. We think the query pointer is invalid, but we will try to print it anyway. Query: Writing a core file... Working directory at /opt/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 61942 61942 processes Max open files 200000 200000 files Max locked memory 200000 200000 bytes Max address space unlimited unlimited bytes Max file locks unlimited unlimited locks Max pending signals 61942 61942 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: |/usr/lib/systemd/systemd-coredump %P %u %g %s %t %c %h %e Kernel version: Linux version 4.18.0-425.19.2.el8_7.x86_64 (mockbuild@dal1-prod-builder001.bld.equ.rockylinux.org) (gcc version 8.5.0 20210514 (Red Hat 8.5.0-16) (GCC)) #1 SMP Tue Apr 4 22:38:11 UTC 2023