2024-02-01 20:14:58 0x7f0f641d0700 InnoDB: Assertion failure in file /build/reproducible-path/mariadb-10.3-10.3.39/storage/innobase/row/row0upd.cc line 1887 InnoDB: Failing assertion: dict_index_is_clust(index) || ind_field->prefix_len <= dfield_len 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. 240201 20:14:58 [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.3.39-MariaDB-0+deb10u2-log source revision: ca001cf2048f0152689e1895e2dc15486dd0b1af key_buffer_size=536870912 read_buffer_size=131072 max_used_connections=0 max_threads=252 thread_count=0 It is possible that mysqld could use up to key_buffer_size + (read_buffer_size + sort_buffer_size)*max_threads = 1078312 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 = 0x0 thread_stack 0x30000 /usr/sbin/mysqld(my_print_stacktrace+0x2e)[0x559828137ede] /usr/sbin/mysqld(handle_fatal_signal+0x55d)[0x559827c5eced] /lib/x86_64-linux-gnu/libpthread.so.0(+0x12730)[0x7f10f4702730] /lib/x86_64-linux-gnu/libc.so.6(gsignal+0x10b)[0x7f10f45678eb] /lib/x86_64-linux-gnu/libc.so.6(abort+0x121)[0x7f10f4552535] /usr/sbin/mysqld(+0x4e8c5b)[0x55982799cc5b] /usr/sbin/mysqld(+0x4dde25)[0x559827991e25] /usr/sbin/mysqld(+0xb27324)[0x559827fdb324] /usr/sbin/mysqld(+0x9f5310)[0x559827ea9310] /usr/sbin/mysqld(+0x9a8a88)[0x559827e5ca88] /usr/sbin/mysqld(+0xa28bb1)[0x559827edcbb1] /usr/sbin/mysqld(+0xa28df7)[0x559827edcdf7] /usr/sbin/mysqld(+0x4e6ed8)[0x55982799aed8] /lib/x86_64-linux-gnu/libpthread.so.0(+0x7fa3)[0x7f10f46f7fa3] /lib/x86_64-linux-gnu/libc.so.6(clone+0x3f)[0x7f10f462906f] 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 /srv/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 64053 64053 processes Max open files 65821 65821 files Max locked memory 67108864 67108864 bytes Max address space unlimited unlimited bytes Max file locks unlimited unlimited locks Max pending signals 64053 64053 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 Kernel version: Linux version 4.19.0-17-amd64 (debian-kernel@lists.debian.org) (gcc version 8.3.0 (Debian 8.3.0-6)) #1 SMP Debian 4.19.194-3 (2021-07-18) 2024-02-01 20:14:59 0 [Note] Starting MariaDB 10.3.39-MariaDB-0+deb10u2-log source revision ca001cf2048f0152689e1895e2dc15486dd0b1af as process 9665 2024-02-01 20:14:59 0 [Note] InnoDB: Using Linux native AIO 2024-02-01 20:14:59 0 [Note] InnoDB: Mutexes and rw_locks use GCC atomic builtins 2024-02-01 20:14:59 0 [Note] InnoDB: Uses event mutexes 2024-02-01 20:14:59 0 [Note] InnoDB: Compressed tables use zlib 1.2.11 2024-02-01 20:14:59 0 [Note] InnoDB: Number of pools: 1 2024-02-01 20:14:59 0 [Note] InnoDB: Using SSE2 crc32 instructions 2024-02-01 20:14:59 0 [Note] InnoDB: Initializing buffer pool, total size = 5G, instances = 8, chunk size = 128M 2024-02-01 20:14:59 0 [Note] InnoDB: Completed initialization of buffer pool 2024-02-01 20:14:59 0 [Note] InnoDB: If the mysqld execution user is authorized, page cleaner thread priority can be changed. See the man page of setpriority(). 2024-02-01 20:14:59 0 [Note] InnoDB: 2 transaction(s) which must be rolled back or cleaned up in total 2 row operations to undo 2024-02-01 20:14:59 0 [Note] InnoDB: Trx id counter is 11575718719 2024-02-01 20:14:59 0 [Note] InnoDB: 128 out of 128 rollback segments are active. 2024-02-01 20:14:59 0 [Note] InnoDB: Starting in background the rollback of recovered transactions