240618 8:07:17 [ERROR] mysqld got signal 11 ; Sorry, we probably made a mistake, and this is a bug. Your assistance in bug reporting will enable us to fix this for the next release. 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.6.17-12-MariaDB-enterprise-log source revision: 249b7e2a0440ae1eb3ba14c607bdb61393bd464e key_buffer_size=33554432 read_buffer_size=131072 max_used_connections=493 max_threads=514 thread_count=424 It is possible that mysqld could use up to key_buffer_size + (read_buffer_size + sort_buffer_size)*max_threads = 1164794 K bytes of memory Hope that's ok; if not, decrease some variables in the equation. Thread pointer: 0x7f23f8278528 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 = 0x7f24c67adb98 thread_stack 0x49000 Can't start addr2line /usr/sbin/mariadbd(my_print_stacktrace+0x2e)[0x55ed7e007d3e] /usr/sbin/mariadbd(handle_fatal_signal+0x475)[0x55ed7dac1755] /lib64/libpthread.so.0(+0x12cf0)[0x7f3a89c1ccf0] /usr/sbin/mariadbd(_ZN13st_join_table17save_explain_dataEP20Explain_table_accessybPS_+0x376)[0x55ed7d8cd396] /usr/sbin/mariadbd(_ZN4JOIN24save_explain_data_internEP13Explain_querybbbPKc+0xc50)[0x55ed7d8cf100] /usr/sbin/mariadbd(_ZN4JOIN17save_explain_dataEP13Explain_querybbbb+0x1f8)[0x55ed7d8cf3b8] /usr/sbin/mariadbd(_ZN4JOIN13build_explainEv+0x80)[0x55ed7d8cf480] /usr/sbin/mariadbd(_ZN4JOIN8optimizeEv+0x8a)[0x55ed7d8db20a] /usr/sbin/mariadbd(_Z12mysql_selectP3THDP10TABLE_LISTR4ListI4ItemEPS4_jP8st_orderS9_S7_S9_yP13select_resultP18st_select_lex_unitP13st_select_lex+0xb3)[0x55ed7d8db2f3] /usr/sbin/mariadbd(_Z13handle_selectP3THDP3LEXP13select_resultm+0x16c)[0x55ed7d8dbb3c] /usr/sbin/mariadbd(+0x7ec041)[0x55ed7d851041] /usr/sbin/mariadbd(_Z21mysql_execute_commandP3THDb+0x4aeb)[0x55ed7d86067b] /usr/sbin/mariadbd(_Z11mysql_parseP3THDPcjP12Parser_state+0x211)[0x55ed7d861d21] /usr/sbin/mariadbd(_Z16dispatch_command19enum_server_commandP3THDPcjb+0x1b85)[0x55ed7d864f35] /usr/sbin/mariadbd(_Z10do_commandP3THDb+0x132)[0x55ed7d866d92] /usr/sbin/mariadbd(_Z24do_handle_one_connectionP7CONNECTb+0x3b7)[0x55ed7d989fc7] /usr/sbin/mariadbd(handle_one_connection+0x5d)[0x55ed7d98a30d] /usr/sbin/mariadbd(+0xca7732)[0x55ed7dd0c732] /lib64/libpthread.so.0(+0x81ca)[0x7f3a89c121ca] /lib64/libc.so.6(clone+0x43)[0x7f3a88f63e73] Trying to get some variables. Some pointers may be invalid and cause the dump to abort. Query (0x7f23f827f6f0): SET STATEMENT max_statement_time=14395 FOR SELECT sys_attachment0.`sys_id`, sys_attachment0.`table_sys_id` FROM sys_attachment sys_attachment0 WHERE sys_attachment0.`table_name` = 'ZZ_YYsys_user' AND sys_attachment0.`file_name` = 'photo' AND sys_attachment0.`table_sys_id` = '200d9a8697fe0d94e35f3aafe153afa1' /* a4_16002, gs:9DE172EA6CFA02D0F90A73A39B28E581, tx:285583aa6c3642d0f90a73a39b28e54a, hash:1476480957 */ Connection ID (thread ID): 10307906 Status: KILL_QUERY 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,hash_join_cardinality=off,cset_narrowing=off,sargable_casefold=off The manual page at https://mariadb.com/kb/en/how-to-produce-a-full-stack-trace-for-mariadbd/ contains information that should help you find out what is causing the crash. Writing a core file... Working directory at /mariadb/data 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 515328 515328 processes Max open files 1048576 1048576 files Max locked memory unlimited unlimited bytes Max address space unlimited unlimited bytes Max file locks unlimited unlimited locks Max pending signals 515328 515328 signals Max msgqueue size 819200 819200 bytes 240618 8:07:17 [ERROR] mysqld got signal 11 ; Sorry, we probably made a mistake, and this is a bug. Your assistance in bug reporting will enable us to fix this for the next release. 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.6.17-12-MariaDB-enterprise-log source revision: 249b7e2a0440ae1eb3ba14c607bdb61393bd464e key_buffer_size=33554432 read_buffer_size=131072 max_used_connections=493 max_threads=514 thread_count=424 It is possible that mysqld could use up to key_buffer_size + (read_buffer_size + sort_buffer_size)*max_threads = 1164794 K bytes of memory Hope that's ok; if not, decrease some variables in the equation. Thread pointer: 0x7f23f8278528 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 = 0x7f24c67adb98 thread_stack 0x49000 Can't start addr2line /usr/sbin/mariadbd(my_print_stacktrace+0x2e)[0x55ed7e007d3e] /usr/sbin/mariadbd(handle_fatal_signal+0x475)[0x55ed7dac1755] /lib64/libpthread.so.0(+0x12cf0)[0x7f3a89c1ccf0] /usr/sbin/mariadbd(_ZN13st_join_table17save_explain_dataEP20Explain_table_accessybPS_+0x376)[0x55ed7d8cd396] /usr/sbin/mariadbd(_ZN4JOIN24save_explain_data_internEP13Explain_querybbbPKc+0xc50)[0x55ed7d8cf100] /usr/sbin/mariadbd(_ZN4JOIN17save_explain_dataEP13Explain_querybbbb+0x1f8)[0x55ed7d8cf3b8] /usr/sbin/mariadbd(_ZN4JOIN13build_explainEv+0x80)[0x55ed7d8cf480] /usr/sbin/mariadbd(_ZN4JOIN8optimizeEv+0x8a)[0x55ed7d8db20a] /usr/sbin/mariadbd(_Z12mysql_selectP3THDP10TABLE_LISTR4ListI4ItemEPS4_jP8st_orderS9_S7_S9_yP13select_resultP18st_select_lex_unitP13st_select_lex+0xb3)[0x55ed7d8db2f3] /usr/sbin/mariadbd(_Z13handle_selectP3THDP3LEXP13select_resultm+0x16c)[0x55ed7d8dbb3c] /usr/sbin/mariadbd(+0x7ec041)[0x55ed7d851041]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-513.18.1.el8_9.x86_64 (mockbuild@x86-vm-08.build.eng.bos.redhat.com) (gcc version 8.5.0 20210514 (Red Hat 8.5.0-20) (GCC)) #1 SMP Thu Feb 1 03:51:05 EST 2024 2024-06-18 8:07:41 0 [Note] Starting MariaDB 10.6.17-12-MariaDB-enterprise-log source revision 249b7e2a0440ae1eb3ba14c607bdb61393bd464e as process 2831850 2024-06-18 8:07:41 0 [Note] InnoDB: Compressed tables use zlib 1.2.11 2024-06-18 8:07:41 0 [Note] InnoDB: Number of pools: 1 2024-06-18 8:07:41 0 [Note] InnoDB: Using crc32 + pclmulqdq instructions 2024-06-18 8:07:41 0 [Note] InnoDB: Using Linux native AIO 2024-06-18 8:07:41 0 [Note] InnoDB: Initializing buffer pool, total size = 85899345920, chunk size = 134217728 2024-06-18 8:07:41 0 [Note] InnoDB: Completed initialization of buffer pool 2024-06-18 8:07:42 0 [Note] InnoDB: Starting crash recovery from checkpoint LSN=79310994720320,79311016850840 2024-06-18 8:07:42 0 [Note] InnoDB: 16 transaction(s) which must be rolled back or cleaned up in total 18 row operations to undo 2024-06-18 8:07:42 0 [Note] InnoDB: Trx id counter is 70429452732 2024-06-18 8:07:42 0 [Note] InnoDB: To recover: 5812 pages 2024-06-18 8:07:43 0 [Note] InnoDB: Last binlog file '/mariadb/logs/binary/mariadb_binlog.046236', position 321531599 2024-06-18 8:07:43 0 [Note] InnoDB: 128 rollback segments are active. 2024-06-18 8:07:43 0 [Note] InnoDB: Starting in background the rollback of recovered transactions 2024-06-18 8:07:43 0 [Note] InnoDB: Removed temporary tablespace data file: "/mariadb/data/ibtmp1" 2024-06-18 8:07:43 0 [Note] InnoDB: Creating shared tablespace for temporary tables 2024-06-18 8:07:43 0 [Note] InnoDB: Setting file '/mariadb/data/ibtmp1' size to 12 MB. Physically writing the file full; Please wait ... 2024-06-18 8:07:43 0 [Note] InnoDB: File '/mariadb/data/ibtmp1' size is now 12 MB. 2024-06-18 8:07:43 0 [Note] InnoDB: 10.6.17 started; log sequence number 79311016860521; transaction id 70429452733 2024-06-18 8:07:43 0 [Note] Plugin 'FEEDBACK' is disabled. 2024-06-18 8:07:43 0 [Note] InnoDB: Loading buffer pool(s) from /mariadb/data/ib_buffer_pool 2024-06-18 8:07:43 0 [Note] Recovering after a crash using /mariadb/logs/binary/mariadb_binlog 2024-06-18 8:07:43 0 [Note] Starting table crash recovery... 2024-06-18 8:07:43 0 [Note] Crash table recovery finished. 2024-06-18 8:07:43 0 [Note] InnoDB: Rolled back recovered transaction 70429452666 2024-06-18 8:07:43 0 [Note] InnoDB: Rolled back recovered transaction 70429452654 2024-06-18 8:07:43 0 [Note] InnoDB: Rolled back recovered transaction 70429452724 2024-06-18 8:07:43 0 [Note] InnoDB: Rolled back recovered transaction 70429452648 2024-06-18 8:07:43 0 [Note] InnoDB: Rolled back recovered transaction 70429452700 2024-06-18 8:07:43 0 [Note] InnoDB: Rolled back recovered transaction 70429452718 2024-06-18 8:07:43 0 [Note] InnoDB: Rolled back recovered transaction 70429452710 2024-06-18 8:07:43 0 [Note] InnoDB: Rolled back recovered transaction 70429452707 2024-06-18 8:07:43 0 [Note] InnoDB: Rolled back recovered transaction 70429452711 2024-06-18 8:07:43 0 [Note] InnoDB: Rolled back recovered transaction 70429452691 2024-06-18 8:07:43 0 [Note] InnoDB: Rolled back recovered transaction 70429452709 2024-06-18 8:07:43 0 [Note] InnoDB: Rolled back recovered transaction 70429452725 2024-06-18 8:07:43 0 [Note] InnoDB: Rolled back recovered transaction 70429452713 2024-06-18 8:07:43 0 [Note] InnoDB: Rolled back recovered transaction 70429452705 2024-06-18 8:07:43 0 [Note] InnoDB: Rolled back recovered transaction 70429452701 2024-06-18 8:07:43 0 [Note] InnoDB: Rolled back recovered transaction 70429452721 2024-06-18 8:07:43 0 [Note] InnoDB: Rollback of non-prepared transactions completed 2024-06-18 8:07:43 0 [Note] Server socket created on IP: '0.0.0.0'. 2024-06-18 8:07:43 0 [Warning] Recovery from master pos 124058027 and file mariadb_binlog.004645. 2024-06-18 8:07:43 0 [Note] /usr/sbin/mariadbd: ready for connections. Version: '10.6.17-12-MariaDB-enterprise-log' socket: '/mariadb/logs/mariadb.sock' port: 3306 MariaDB Enterprise Server