Version: '10.3.32-MariaDB' socket: '/var/vnix/mysql/3307.sock' port: 3307 Source distribution 2022-01-11 20:18:55 0 [Note] InnoDB: Buffer pool(s) load completed at 220111 20:18:55 220111 20:19:02 [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.32-MariaDB key_buffer_size=134217728 read_buffer_size=131072 max_used_connections=1 max_threads=153 thread_count=6 It is possible that mysqld could use up to key_buffer_size + (read_buffer_size + sort_buffer_size)*max_threads = 467428 K bytes of memory Hope that's ok; if not, decrease some variables in the equation. Thread pointer: 0x7ff26b84a008 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 = 0x700001cc9f20 thread_stack 0x49000 0 mysqld 0x00000001053e2660 my_print_stacktrace + 60 0 mysqld 0x0000000104dda505 handle_fatal_signal + 719 0 libsystem_platform.dylib 0x00007ff81d10de2d _sigtramp + 29 0 ??? 0x0000000106656000 0x0 + 4402274304 0 libsystem_c.dylib 0x00007ff81d044d10 abort + 123 0 libsystem_malloc.dylib 0x00007ff81cf223e2 has_default_zone0 + 0 0 libsystem_malloc.dylib 0x00007ff81cf255ed malloc_report + 151 0 libcrypto.3.dylib 0x0000000106d71820 evp_md_ctx_clear_digest + 220 0 libcrypto.3.dylib 0x0000000106d7188d EVP_MD_CTX_reset + 55 0 mysqld 0x00000001053c858c _ZL8md5_initP13evp_md_ctx_st + 28 0 mysqld 0x00000001053c852c my_md5 + 50 0 mysqld 0x0000000105393efb _Z21find_or_create_digestP10PFS_threadPK18sql_digest_storagePKcj + 180 0 mysqld 0x0000000105391c22 _ZL16end_statement_v1P20PSI_statement_lockerPv + 186 0 mysqld 0x0000000104f79f56 _Z16dispatch_command19enum_server_commandP3THDPcjbb + 7065 0 mysqld 0x0000000104f7a9fb _Z10do_commandP3THD + 309 0 mysqld 0x00000001050570d9 _Z24do_handle_one_connectionP7CONNECT + 400 0 mysqld 0x0000000105056f3c handle_one_connection + 56 0 mysqld 0x000000010538e2c7 pfs_spawn_thread + 247 0 libsystem_pthread.dylib 0x00007ff81d0f84f4 _pthread_start + 125 0 libsystem_pthread.dylib 0x00007ff81d0f400f thread_start + 15 Trying to get some variables. Some pointers may be invalid and cause the dump to abort. Query (0x0): (null) Connection ID (thread ID): 8 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=off,table_elimination=on,extended_keys=on,exists_to_in=on,orderby_uses_equalities=on,condition_pushdown_for_derived=on,split_materialized=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: Core pattern: /cores/core.%P 220111 20:19:02 mysqld_safe mysqld restarted 2022-01-11 20:19:03 0 [Note] /opt/local/lib/mariadb-10.3/bin/mysqld: ready for connections. Version: '10.3.32-MariaDB' socket: '/var/vnix/mysql/3307.sock' port: 3307 Source distribution 2022-01-11 20:19:03 0 [Note] InnoDB: Buffer pool(s) load completed at 220111 20:19:03 220111 20:19:17 [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.32-MariaDB key_buffer_size=134217728 read_buffer_size=131072 max_used_connections=1 max_threads=153 thread_count=6 It is possible that mysqld could use up to key_buffer_size + (read_buffer_size + sort_buffer_size)*max_threads = 467428 K bytes of memory Hope that's ok; if not, decrease some variables in the equation. Thread pointer: 0x7f7d74103808 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 = 0x700006d2bf20 thread_stack 0x49000 0 mysqld 0x000000010e377660 my_print_stacktrace + 60 0 mysqld 0x000000010dd6f505 handle_fatal_signal + 719 0 libsystem_platform.dylib 0x00007ff81d10de2d _sigtramp + 29 0 ??? 0x000000010f5eb000 0x0 + 4552830976 0 libsystem_c.dylib 0x00007ff81d044d10 abort + 123 0 libsystem_malloc.dylib 0x00007ff81cf223e2 has_default_zone0 + 0 0 libsystem_malloc.dylib 0x00007ff81cf255ed malloc_report + 151 0 libcrypto.3.dylib 0x000000010fd06820 evp_md_ctx_clear_digest + 220 0 libcrypto.3.dylib 0x000000010fd0688d EVP_MD_CTX_reset + 55 0 mysqld 0x000000010e35d58c _ZL8md5_initP13evp_md_ctx_st + 28 0 mysqld 0x000000010e35d52c my_md5 + 50 0 mysqld 0x000000010e328efb _Z21find_or_create_digestP10PFS_threadPK18sql_digest_storagePKcj + 180 0 mysqld 0x000000010e326c22 _ZL16end_statement_v1P20PSI_statement_lockerPv + 186 0 mysqld 0x000000010df0ef56 _Z16dispatch_command19enum_server_commandP3THDPcjbb + 7065 0 mysqld 0x000000010df0f9fb _Z10do_commandP3THD + 309 0 mysqld 0x000000010dfec0d9 _Z24do_handle_one_connectionP7CONNECT + 400 0 mysqld 0x000000010dfebf3c handle_one_connection + 56 0 mysqld 0x000000010e3232c7 pfs_spawn_thread + 247 0 libsystem_pthread.dylib 0x00007ff81d0f84f4 _pthread_start + 125 0 libsystem_pthread.dylib 0x00007ff81d0f400f thread_start + 15 Trying to get some variables. Some pointers may be invalid and cause the dump to abort. Query (0x0): (null) Connection ID (thread ID): 8 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=off,table_elimination=on,extended_keys=on,exists_to_in=on,orderby_uses_equalities=on,condition_pushdown_for_derived=on,split_materialized=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: