260205 5:12:24 [ERROR] /usr/sbin/mariadbd 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 about how to report a bug on https://jira.mariadb.org/. Please include the information from the server start above, to the end of the information below. Server version: 10.11.11-MariaDB-log source revision: e69f8cae1a15e15b9e4f5e0f8497e1f17bdc81a4 The information page at https://mariadb.com/kb/en/how-to-produce-a-full-stack-trace-for-mariadbd/ contains instructions to obtain a better version of the backtrace below. Following these instructions will help MariaDB developers provide a fix quicker. Attempting backtrace. Include this in the bug report. (note: Retrieving this information may fail) Thread pointer: 0x7f0ad009b088 stack_bottom = 0x7f0cb574a000 thread_stack 0x49000 2026-02-05 5:12:27 0 [Note] /usr/sbin/mariadbd (initiated by: unknown): Normal shutdown 2026-02-05 5:12:27 5 [Note] Master 's-db3': Error reading relay log event: slave SQL thread was killed 2026-02-05 5:12:27 5 [Note] Master 's-db3': Slave SQL thread exiting, replication stopped in log 'FIRST' at position 0, master: :3306 2026-02-05 5:12:27 9272533 [Note] Error reading relay log event: slave SQL thread was killed 2026-02-05 5:12:27 9272533 [Note] Slave SQL thread exiting, replication stopped in log 'db1-binary.578165' at position 79130447, master: 10.76.24.71:3306 2026-02-05 5:12:27 9272532 [Note] Slave I/O thread exiting, read up to log 'db1-binary.578165', position 79130447, master 10.76.24.71:3306 2026-02-05 5:12:27 19 [Note] Master 's-db4': Error reading relay log event: slave SQL thread was killed 2026-02-05 5:12:27 19 [Note] Master 's-db4': Slave SQL thread exiting, replication stopped in log 'FIRST' at position 0, master: :3306 2026-02-05 5:12:27 21 [Note] Master 's-db1': Error reading relay log event: slave SQL thread was killed 2026-02-05 5:12:27 21 [Note] Master 's-db1': Slave SQL thread exiting, replication stopped in log 'FIRST' at position 0, master: :3306 2026-02-05 5:12:27 23 [Note] Master 's-db5': Error reading relay log event: slave SQL thread was killed 2026-02-05 5:12:27 23 [Note] Master 's-db5': Slave SQL thread exiting, replication stopped in log 'FIRST' at position 0, master: :3306 mysys/stacktrace.c:216(my_print_stacktrace)[0x5652f7bee43e] sql/signal_handler.cc:230(handle_fatal_signal)[0x5652f76d478d] /lib64/libpthread.so.0(+0x12cf0)[0x7f3421c0fcf0] sql/sql_yacc.yy:9116(MYSQLparse(THD*))[0x5652f7664ac3] sql/sql_parse.cc:10583(parse_sql(THD*, Parser_state*, Object_creation_ctx*, bool))[0x5652f746c820] sql/sql_parse.cc:8142(mysql_parse(THD*, char*, unsigned int, Parser_state*))[0x5652f746784d] sql/sql_parse.cc:1876(dispatch_command(enum_server_command, THD*, char*, unsigned int, bool))[0x5652f7474543] sql/sql_parse.cc:1418(do_command(THD*, bool))[0x5652f747651f] sql/sql_connect.cc:1386(do_handle_one_connection(CONNECT*, bool))[0x5652f75a3b25] sql/sql_connect.cc:1298(handle_one_connection)[0x5652f75a3e7d] perfschema/pfs.cc:2204(pfs_spawn_thread)[0x5652f78f3bc5] /lib64/libpthread.so.0(+0x81ca)[0x7f3421c051ca] 2026-02-05 5:12:49 0 [Warning] /usr/sbin/mariadbd: Thread 9237414 (user : 'alepoaaa') did not exit /lib64/libc.so.6(clone+0x43)[0x7f3420d3de73] Connection ID (thread ID): 9237414 Status: KILL_SERVER Query (0x7f0ad00a9fd0): Select NASIP, NASPort, AcctSessionId, NASIndex, UserIndex, UserID, GroupIndex, MainGroupIndex, Service, UserIP, StartDateTime, CallerId, CalledStationId, AlepoSessionId, SessionExpiryTime, ParentSessionId, InterimSessionTime, InterimBytes, LastUpdateTime, PreCleanupAction, ExternalChargingIdentifier, InterimInputOctets, InterimOutputOctets, FramedInterfaceId, FramedIPv6Prefix, NasportType, UserSpeed, FramedIPv6Address,AcctMultiSessionId, NetworkServiceName, DelegateIPv6Prefix From ActiveSessions Where AlepoSessionId = 'HWI-LHR012161231400000a3f412AAAAVj3010576' 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 Writing a core file... Working directory at /var/lib/mysql Resource Limits (excludes unlimited resources): Limit Soft Limit Hard Limit Units Max stack size 8388608 unlimited bytes Max processes 2061710 2061710 processes Max open files 32768 32768 files Max locked memory 65536 65536 bytes Max pending signals 2061710 2061710 signals Max msgqueue size 819200 819200 bytes Max nice priority 0 0 Max realtime priority 0 0 Core pattern: /var/coredumps/core.%e.%p Kernel version: Linux version 4.18.0-477.13.1.el8_8.x86_64 (mockbuild@x86-vm-08.build.eng.bos.redhat.com) (gcc version 8.5.0 20210514 (Red Hat 8.5.0-18) (GCC)) #1 SMP Thu May 18 10:27:05 EDT 2023 2026-02-05 5:13:28 0 [Note] Starting MariaDB 10.11.11-MariaDB-log source revision e69f8cae1a15e15b9e4f5e0f8497e1f17bdc81a4 server_uid wYn99w5VDhETcyMGJQuIkkpBnas= as process 1029711 2026-02-05 5:13:28 0 [Warning] option 'innodb-log-buffer-size': unsigned value 5368709120 adjusted to 2147479552 2026-02-05 5:13:28 0 [Note] InnoDB: Compressed tables use zlib 1.2.11 2026-02-05 5:13:28 0 [Note] InnoDB: Number of transaction pools: 1 2026-02-05 5:13:28 0 [Note] InnoDB: Using crc32 + pclmulqdq instructions 2026-02-05 5:13:28 0 [Note] InnoDB: Using Linux native AIO 2026-02-05 5:13:28 0 [Note] InnoDB: Initializing buffer pool, total size = 150.000GiB, chunk size = 2.344GiB 2026-02-05 5:13:29 0 [Note] InnoDB: Completed initialization of buffer pool 2026-02-05 5:13:30 0 [Note] InnoDB: File system buffers for log disabled (block size=512 bytes) 2026-02-05 5:13:32 0 [Note] InnoDB: Starting crash recovery from checkpoint LSN=84901761724863 2026-02-05 5:13:44 0 [Note] InnoDB: Parsed redo log up to LSN=84902723899169; to recover: 163678 pages 2026-02-05 5:13:59 0 [Note] InnoDB: Parsed redo log up to LSN=84903974299243; to recover: 243712 pages 2026-02-05 5:14:14 0 [Note] InnoDB: Parsed redo log up to LSN=84904901891180; to recover: 765753 pages 2026-02-05 5:14:14 0 [Note] InnoDB: End of log at LSN=84904929579137 2026-02-05 5:14:18 0 [Note] InnoDB: To recover: 783800 pages 2026-02-05 5:14:33 0 [Note] InnoDB: To recover: 783800 pages 2026-02-05 5:14:48 0 [Note] InnoDB: To recover: 783800 pages 2026-02-05 5:15:03 0 [Note] InnoDB: To recover: 783800 pages 2026-02-05 5:15:12 0 [Note] InnoDB: Last binlog file './db2-binary.577895', position 67253177 2026-02-05 5:15:12 0 [Note] InnoDB: 128 rollback segments are active. 2026-02-05 5:15:13 0 [Note] InnoDB: Removed temporary tablespace data file: "./ibtmp1" 2026-02-05 5:15:13 0 [Note] InnoDB: Setting file './ibtmp1' size to 12.000MiB. Physically writing the file full; Please wait ... 2026-02-05 5:15:13 0 [Note] InnoDB: File './ibtmp1' size is now 12.000MiB. 2026-02-05 5:15:13 0 [Note] InnoDB: log sequence number 84904929579137; transaction id 224400345643 2026-02-05 5:15:13 0 [Note] InnoDB: Loading buffer pool(s) from /var/lib/mysql/ib_buffer_pool 2026-02-05 5:15:13 0 [Note] Plugin 'FEEDBACK' is disabled. 2026-02-05 5:15:13 0 [Warning] 'thread-concurrency' was removed. It does nothing now and exists only for compatibility with old my.cnf files. 2026-02-05 5:15:13 0 [Warning] 'innodb-thread-concurrency' was removed. It does nothing now and exists only for compatibility with old my.cnf files. 2026-02-05 5:15:13 0 [Warning] 'innodb-log-files-in-group' was removed. It does nothing now and exists only for compatibility with old my.cnf files. 2026-02-05 5:15:13 0 [Note] Recovering after a crash using db2-binary 2026-02-05 5:15:13 0 [Note] Starting table crash recovery... 2026-02-05 5:15:13 0 [Note] Crash table recovery finished. 2026-02-05 5:15:13 0 [Note] Server socket created on IP: '0.0.0.0'. 2026-02-05 5:15:13 0 [Note] Server socket created on IP: '::'. 2026-02-05 5:15:13 0 [Warning] 'user' entry '@alepo-db2-ilb' ignored in --skip-name-resolve mode. 2026-02-05 5:15:13 0 [Warning] 'user' entry 'root@localhost.localdomain' ignored in --skip-name-resolve mode. 2026-02-05 5:15:13 0 [Warning] 'proxies_priv' entry '@% root@alepo-db2-ilb' ignored in --skip-name-resolve mode. 2026-02-05 5:15:13 3 [Note] Reading Master_info: 'master-s@002ddb3.info' Relay_info:'relay-log-s@002ddb3.info' 2026-02-05 5:15:13 3 [Note] Initialized Master_info from 'master-s@002ddb3.info' 2026-02-05 5:15:13 4 [Note] Master 's-db3': Slave I/O thread: Start asynchronous replication to master '@:3306' in log '' at position 4 2026-02-05 5:15:13 4 [ERROR] Master 's-db3': Slave I/O: Fatal error: Invalid (empty) username when attempting to connect to the master server. Connection attempt terminated. Internal MariaDB error code: 1593 2026-02-05 5:15:13 4 [Note] Master 's-db3': Slave I/O thread killed while connecting to master 2026-02-05 5:15:13 4 [Note] Master 's-db3': Slave I/O thread exiting, read up to log 'FIRST', position 4, master :3306 2026-02-05 5:15:13 3 [Note] Started replication for 's-db3' @@@ 2026-02-05 5:15:13 5 [Note] Master 's-db3': Slave SQL thread initialized, starting replication in log 'FIRST' at position 0, relay log './db2-relay-s@002ddb3.000051' position: 4 2026-02-05 5:15:13 3 [Note] Reading Master_info: 'master-s@002ddb4.info' Relay_info:'relay-log-s@002ddb4.info' 2026-02-05 5:15:13 3 [Note] Initialized Master_info from 'master-s@002ddb4.info' 2026-02-05 5:15:13 18 [Note] Master 's-db4': Slave I/O thread: Start asynchronous replication to master '@:3306' in log '' at position 4 2026-02-05 5:15:13 18 [ERROR] Master 's-db4': Slave I/O: Fatal error: Invalid (empty) username when attempting to connect to the master server. Connection attempt terminated. Internal MariaDB error code: 1593 2026-02-05 5:15:13 18 [Note] Master 's-db4': Slave I/O thread killed while connecting to master 2026-02-05 5:15:13 18 [Note] Master 's-db4': Slave I/O thread exiting, read up to log 'FIRST', position 4, master :3306 2026-02-05 5:15:13 3 [Note] Started replication for 's-db4' 2026-02-05 5:15:13 3 [Note] Reading Master_info: 'master-s@002ddb1.info' Relay_info:'relay-log-s@002ddb1.info' 2026-02-05 5:15:13 19 [Note] Master 's-db4': Slave SQL thread initialized, starting replication in log 'FIRST' at position 0, relay log './db2-relay-s@002ddb4.000043' position: 4 2026-02-05 5:15:13 3 [Note] Initialized Master_info from 'master-s@002ddb1.info' 2026-02-05 5:15:13 20 [Note] Master 's-db1': Slave I/O thread: Start asynchronous replication to master '@:3306' in log '' at position 4 2026-02-05 5:15:13 20 [ERROR] Master 's-db1': Slave I/O: Fatal error: Invalid (empty) username when attempting to connect to the master server. Connection attempt terminated. Internal MariaDB error code: 1593 2026-02-05 5:15:13 20 [Note] Master 's-db1': Slave I/O thread killed while connecting to master 2026-02-05 5:15:13 20 [Note] Master 's-db1': Slave I/O thread exiting, read up to log 'FIRST', position 4, master :3306 2026-02-05 5:15:13 3 [Note] Started replication for 's-db1' 2026-02-05 5:15:13 21 [Note] Master 's-db1': Slave SQL thread initialized, starting replication in log 'FIRST' at position 0, relay log './db2-relay-s@002ddb1.000050' position: 4 2026-02-05 5:15:13 3 [Note] Reading Master_info: 'master-s@002ddb5.info' Relay_info:'relay-log-s@002ddb5.info' 2026-02-05 5:15:13 3 [Note] Initialized Master_info from 'master-s@002ddb5.info' 2026-02-05 5:15:13 22 [Note] Master 's-db5': Slave I/O thread: Start asynchronous replication to master '@:3306' in log '' at position 4 2026-02-05 5:15:13 22 [ERROR] Master 's-db5': Slave I/O: Fatal error: Invalid (empty) username when attempting to connect to the master server. Connection attempt terminated. Internal MariaDB error code: 1593 2026-02-05 5:15:13 22 [Note] Master 's-db5': Slave I/O thread killed while connecting to master 2026-02-05 5:15:13 22 [Note] Master 's-db5': Slave I/O thread exiting, read up to log 'FIRST', position 4, master :3306 2026-02-05 5:15:13 3 [Note] Started replication for 's-db5' 2026-02-05 5:15:13 23 [Note] Master 's-db5': Slave SQL thread initialized, starting replication in log 'FIRST' at position 0, relay log './db2-relay-s@002ddb5.000043' position: 4 2026-02-05 5:15:13 25 [Note] Slave I/O thread: Start asynchronous replication to master 'gtid@10.76.24.71:3306' in log 'db1-binary.578165' at position 79130447 2026-02-05 5:15:13 0 [Note] /usr/sbin/mariadbd: ready for connections. Version: '10.11.11-MariaDB-log' socket: '/var/lib/mysql/mysql.sock' port: 3306 MariaDB Server 2026-02-05 5:15:13 26 [Note] Slave SQL thread initialized, starting replication in log 'db1-binary.578165' at position 79130447, relay log './db2-relay.122176' position: 783 2026-02-05 5:15:13 25 [Note] Slave I/O thread: connected to master 'gtid@10.76.24.71:3306',replication started in log 'db1-binary.578165' at position 79130447 2026-02-05 5:16:11 449 [Note] Start binlog_dump to slave_server(1), pos(db2-binary.577895, 67253177), using_gtid(0), gtid('') 2026-02-05 5:18:04 0 [Note] InnoDB: Buffer pool(s) load completed at 260205 5:18:04