250829 21:19:46 [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: 11.2.6-MariaDB-ubu2204-log source revision: 67c0fd2a41034eae1ea04b81cace6a154783aedd key_buffer_size=134217728 read_buffer_size=131072 max_used_connections=419 max_threads=802 thread_count=140 It is possible that mysqld could use up to key_buffer_size + (read_buffer_size + sort_buffer_size)*max_threads = 1897813 K bytes of memory Hope that's ok; if not, decrease some variables in the equation. Thread pointer: 0x7868a80f9038 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 = 0x786d7e875000 thread_stack 0x49000 2025-08-29 21:19:55 0 [Note] /usr/sbin/mariadbd (initiated by: unknown): Normal shutdown /usr/sbin/mariadbd(my_print_stacktrace+0x32)[0x5b3fd82bb5a2] /usr/sbin/mariadbd(handle_fatal_signal+0x478)[0x5b3fd7d753d8] /lib/x86_64-linux-gnu/libc.so.6(+0x42520)[0x78ce15042520] 2025-08-29 21:20:15 0 [Warning] /usr/sbin/mariadbd: Thread 36369 (user : 'xp1') did not exit /usr/sbin/mariadbd(_ZN19Table_triggers_list16mark_fields_usedE14trg_event_type+0x165)[0x5b3fd7bbb8d5] /usr/sbin/mariadbd(_ZN5TABLE30mark_columns_needed_for_insertEv+0x24)[0x5b3fd7bf0444] /usr/sbin/mariadbd(_ZN13select_insert7prepareER4ListI4ItemEP18st_select_lex_unit+0x376)[0x5b3fd7aaa766] /usr/sbin/mariadbd(_ZN4JOIN7prepareEP10TABLE_LISTP4ItemjP8st_orderbS5_S3_S5_P13st_select_lexP18st_select_lex_unit+0x1797)[0x5b3fd7b588b7] /usr/sbin/mariadbd(_Z12mysql_selectP3THDP10TABLE_LISTR4ListI4ItemEPS4_jP8st_orderS9_S7_S9_yP13select_resultP18st_select_lex_unitP13st_select_lex+0x615)[0x5b3fd7b6c0c5] /usr/sbin/mariadbd(_Z13handle_selectP3THDP3LEXP13select_resulty+0x154)[0x5b3fd7b6c3c4] /usr/sbin/mariadbd(_Z21mysql_execute_commandP3THDb+0x490a)[0x5b3fd7aece8a] /usr/sbin/mariadbd(_Z11mysql_parseP3THDPcjP12Parser_state+0x1e7)[0x5b3fd7aedaa7] /usr/sbin/mariadbd(_Z16dispatch_command19enum_server_commandP3THDPcjb+0xee5)[0x5b3fd7aefc85] /usr/sbin/mariadbd(_Z10do_commandP3THDb+0x143)[0x5b3fd7af21e3] /usr/sbin/mariadbd(_Z24do_handle_one_connectionP7CONNECTb+0x39d)[0x5b3fd7c2111d] /usr/sbin/mariadbd(handle_one_connection+0x5d)[0x5b3fd7c2146d] /usr/sbin/mariadbd(+0xd444a6)[0x5b3fd7fbc4a6] /lib/x86_64-linux-gnu/libc.so.6(+0x94ac3)[0x78ce15094ac3] nptl/pthread_create.c:442(start_thread)[0x78ce15126850] Trying to get some variables. Some pointers may be invalid and cause the dump to abort. Query (0x7868a8000910): insert into act_inregeldeclaratie (inrgl_basisid,stactrglcode_id,stactrglsta_id,taak_id,ovr_id) select inregel.inrgl_basisid,1,1,null,batch.ovr_id from inregel inner join inbestand on inregel.inbst_id=inbestand.inbst_id inner join batch on batch.batch_id=inbestand.inbatch_id where inbestand.inbatch_id=303711 on duplicate key update ovr_id=batch.ovr_id Connection ID (thread ID): 36369 Status: KILL_SERVER Optimizer switch: index_merge=on,index_merge_union=on,index_merge_sort_union=on,index_merge_intersection=off,index_merge_sort_intersection=off,engine_condition_pushdown=off,index_condition_pushdown=on,derived_merge=on,derived_with_keys=on,firstmatch=on,loo sescan=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,condi tion_pushdown_from_having=on,not_null_range_scan=off,hash_join_cardinality=on,cset_narrowing=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 /intel1/mydata/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 2062182 2062182 processes Max open files 100000 100000 files Max locked memory 524288 524288 bytes Max address space unlimited unlimited bytes Max file locks unlimited unlimited locks Max pending signals 2062182 2062182 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/share/apport/apport -p%p -s%s -c%c -d%d -P%P -u%u -g%g -F%F -- %E Kernel version: Linux version 6.8.0-65-generic (buildd@lcy02-amd64-003) (x86_64-linux-gnu-gcc-12 (Ubuntu 12.3.0-1ubuntu1~22.04) 12.3.0, GNU ld (GNU Binutils for Ubuntu) 2.38) #68~22.04.1-Ubuntu SMP PREEMPT_DYNAMIC Tue Jul 15 18:06:34 UTC 2 2025-08-29 21:25:52 0 [Note] Starting MariaDB 11.2.6-MariaDB-ubu2204-log source revision 67c0fd2a41034eae1ea04b81cace6a154783aedd server_uid h6cBr1lzKErgo1NqIP0o7tE8zvA= as process 1946371