2021-12-15 23:11:08 586 [ERROR] InnoDB: In pages [page id: space=488, page number=10] and [page id: space=488, page number=11] of index `arbitrary_table_arbitrary_key` of table `otrs`.`arbitrary_table` InnoDB: records in wrong order on adjacent pages InnoDB: record PHYSICAL RECORD: n_fields 2; compact format; info bits 0 0: len 28; hex 30303030303030303030303030303030303030303030303030303939; asc 0000000000000000000000000099;; 1: len 6; hex 000000000763; asc c;; InnoDB: record PHYSICAL RECORD: n_fields 2; compact format; info bits 0 0: len 27; hex 5b3030303030303030303030303030303030303030303030303030; asc [00000000000000000000000000;; 1: len 6; hex 000000000700; asc ;; 2021-12-15 23:11:08 586 [ERROR] InnoDB: Corruption of an index tree: table `otrs`.`arbitrary_table` index `arbitrary_table_arbitrary_key`, father ptr page no 11, child page no 10 PHYSICAL RECORD: n_fields 2; compact format; info bits 0 0: len 27; hex 303030303030303030303030303030303030303030303030303031; asc 000000000000000000000000001;; 1: len 6; hex 000000000701; asc ;; 2021-12-15 23:11:08 586 [Note] InnoDB: n_owned: 0; heap_no: 2; next rec: 165 PHYSICAL RECORD: n_fields 3; compact format; info bits 0 0: len 27; hex 5b3030303030303030303030303030303030303030303030303030; asc [00000000000000000000000000;; 1: len 6; hex 000000000700; asc ;; 2: len 4; hex 0000000b; asc ;; 2021-12-15 23:11:08 586 [Note] InnoDB: n_owned: 0; heap_no: 3; next rec: 112 2021-12-15 23:11:08 586 [ERROR] [FATAL] InnoDB: You should dump + drop + reimport the table to fix the corruption. If the crash happens at database startup. Please refer to https://mariadb.com/kb/en/library/innodb-recovery-modes/ for information about forcing recovery. Then dump + drop + reimport. 211215 23:11:08 [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.5.13-MariaDB-log key_buffer_size=16777216 read_buffer_size=262144 max_used_connections=1 max_threads=52 thread_count=1 It is possible that mysqld could use up to key_buffer_size + (read_buffer_size + sort_buffer_size)*max_threads = 57542 K bytes of memory Hope that's ok; if not, decrease some variables in the equation. Thread pointer: 0x7fb1f4000c58 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 = 0x7fb34c1edd58 thread_stack 0x49000 /usr/sbin/mysqld(my_print_stacktrace+0x2e)[0x55c2f220b7ee] /usr/sbin/mysqld(handle_fatal_signal+0x478)[0x55c2f1d42d98] /lib64/libpthread.so.0(+0x121d0)[0x7fb35d4181d0] /lib64/libc.so.6(gsignal+0x13e)[0x7fb35d27963e] /lib64/libc.so.6(abort+0x112)[0x7fb35d263536] /usr/sbin/mysqld(+0x60c03f)[0x55c2f1a3a03f] /usr/sbin/mysqld(+0x60ce16)[0x55c2f1a3ae16] /usr/sbin/mysqld(+0xcc7a6d)[0x55c2f20f5a6d] /usr/sbin/mysqld(+0xbc9e5c)[0x55c2f1ff7e5c] /usr/sbin/mysqld(_ZN7handler8ha_checkEP3THDP15st_ha_check_opt+0x62)[0x55c2f1d4b352] /usr/sbin/mysqld(+0x825a81)[0x55c2f1c53a81] /usr/sbin/mysqld(_ZN19Sql_cmd_check_table7executeEP3THD+0x86)[0x55c2f1c54886] /usr/sbin/mysqld(_Z21mysql_execute_commandP3THD+0xb56)[0x55c2f1b4f9a6] /usr/sbin/mysqld(_Z11mysql_parseP3THDPcjP12Parser_statebb+0x1c3)[0x55c2f1b52c03] /usr/sbin/mysqld(_Z16dispatch_command19enum_server_commandP3THDPcjbb+0xd14)[0x55c2f1b54144] /usr/sbin/mysqld(_Z10do_commandP3THD+0xe3)[0x55c2f1b55a93] /usr/sbin/mysqld(_Z24do_handle_one_connectionP7CONNECTb+0x2e2)[0x55c2f1c47232] /usr/sbin/mysqld(handle_one_connection+0x5d)[0x55c2f1c474cd] /usr/sbin/mysqld(+0xb4b222)[0x55c2f1f79222] /lib64/libpthread.so.0(+0x7d4e)[0x7fb35d40dd4e] /lib64/libc.so.6(clone+0x3f)[0x7fb35d33971f] Trying to get some variables. Some pointers may be invalid and cause the dump to abort. Query (0x7fb1f4012330): CHECK TABLE arbitrary_table Connection ID (thread ID): 586 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,not_null_range_scan=off 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 /var/lib/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 256963 256963 processes Max open files 160093 160093 files Max locked memory 65536 65536 bytes Max address space unlimited unlimited bytes Max file locks unlimited unlimited locks Max pending signals 256963 256963 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