2024-04-21 17:32:53 0 [Note] Starting MariaDB 10.11.5-MariaDB-log source revision 7875294b6b74b53dd3aaa723e6cc103d2bb47b2c as process 1759574 2024-04-21 17:32:53 0 [Note] mariadbd: Aria engine: starting recovery tables to flush: 3 2 1 0 (0.0 seconds); 2024-04-21 17:32:53 0 [Note] mariadbd: Aria engine: recovery done 2024-04-21 17:32:53 0 [Note] InnoDB: Compressed tables use zlib 1.2.11 2024-04-21 17:32:53 0 [Note] InnoDB: Number of transaction pools: 1 2024-04-21 17:32:53 0 [Note] InnoDB: Using crc32 + pclmulqdq instructions 2024-04-21 17:32:53 0 [Note] InnoDB: Using Linux native AIO 2024-04-21 17:32:53 0 [Note] InnoDB: Initializing buffer pool, total size = 300.000GiB, chunk size = 4.688GiB 2024-04-21 17:32:54 0 [Note] InnoDB: Completed initialization of buffer pool 2024-04-21 17:32:54 0 [Note] InnoDB: File system buffers for log disabled (block size=512 bytes) 2024-04-21 17:32:56 0 [Warning] InnoDB: 3692117504 bytes should have been read at 602849792 from (unknown file), but got only 2147479552. Retrying. 2024-04-21 17:33:00 0 [Warning] InnoDB: 2360309248 bytes should have been read at 1934658048 from (unknown file), but got only 2147479552. Retrying. 2024-04-21 17:33:00 0 [Note] InnoDB: Starting crash recovery from checkpoint LSN=28048221917653 2024-04-21 17:33:09 0 [Note] InnoDB: Parsed redo log up to LSN=28049073583563; to recover: 155295 pages 2024-04-21 17:33:24 0 [Note] InnoDB: Parsed redo log up to LSN=28050375064155; to recover: 173459 pages 2024-04-21 17:33:28 0 [Warning] InnoDB: 4294955008 bytes should have been read at 12288 from (unknown file), but got only 2147479552. Retrying. 2024-04-21 17:33:37 0 [Note] InnoDB: End of log at LSN=28051185131461 2024-04-21 17:33:38 0 [Note] InnoDB: Transaction 87331866965 was in the XA prepared state. 2024-04-21 17:33:38 0 [Note] InnoDB: Transaction 87331867212 was in the XA prepared state. 2024-04-21 17:33:38 0 [Note] InnoDB: Transaction 87331867258 was in the XA prepared state. 2024-04-21 17:33:38 0 [Note] InnoDB: Transaction 87331867261 was in the XA prepared state. 2024-04-21 17:33:38 0 [Note] InnoDB: Transaction 87331867265 was in the XA prepared state. 2024-04-21 17:33:38 0 [Note] InnoDB: Transaction 87331867271 was in the XA prepared state. 2024-04-21 17:33:38 0 [Note] InnoDB: Transaction 87331867272 was in the XA prepared state. 2024-04-21 17:33:38 0 [Note] InnoDB: Transaction 87331867273 was in the XA prepared state. 2024-04-21 17:33:38 0 [Note] InnoDB: Transaction 87331867274 was in the XA prepared state. 2024-04-21 17:33:38 0 [Note] InnoDB: Transaction 87331867275 was in the XA prepared state. 2024-04-21 17:33:38 0 [Note] InnoDB: Transaction 87331867276 was in the XA prepared state. 2024-04-21 17:33:38 0 [Note] InnoDB: Transaction 87331867277 was in the XA prepared state. 2024-04-21 17:33:38 0 [Note] InnoDB: Transaction 87331867278 was in the XA prepared state. 2024-04-21 17:33:38 0 [Note] InnoDB: Transaction 87331867280 was in the XA prepared state. 2024-04-21 17:33:38 0 [Note] InnoDB: Transaction 87331866610 was in the XA prepared state. 2024-04-21 17:33:38 0 [Note] InnoDB: Transaction 87331867284 was in the XA prepared state. 2024-04-21 17:33:38 0 [Note] InnoDB: Transaction 87331867285 was in the XA prepared state. 2024-04-21 17:33:38 0 [Note] InnoDB: Transaction 87331867286 was in the XA prepared state. 2024-04-21 17:33:38 0 [Note] InnoDB: Transaction 87331867289 was in the XA prepared state. 2024-04-21 17:33:38 0 [Note] InnoDB: Transaction 87331867291 was in the XA prepared state. 2024-04-21 17:33:38 0 [Note] InnoDB: Transaction 87331867292 was in the XA prepared state. 2024-04-21 17:33:38 0 [Note] InnoDB: Transaction 87331867295 was in the XA prepared state. 2024-04-21 17:33:38 0 [Note] InnoDB: Transaction 87331867297 was in the XA prepared state. 2024-04-21 17:33:38 0 [Note] InnoDB: Transaction 87331867301 was in the XA prepared state. 2024-04-21 17:33:38 0 [Note] InnoDB: Transaction 87331867303 was in the XA prepared state. 2024-04-21 17:33:38 0 [Note] InnoDB: Transaction 87331867308 was in the XA prepared state. 2024-04-21 17:33:38 0 [Note] InnoDB: Transaction 87331867084 was in the XA prepared state. 2024-04-21 17:33:38 0 [Note] InnoDB: Transaction 87331867309 was in the XA prepared state. 2024-04-21 17:33:38 0 [Note] InnoDB: Transaction 87331867314 was in the XA prepared state. 2024-04-21 17:33:38 0 [Note] InnoDB: 74 transaction(s) which must be rolled back or cleaned up in total 45 row operations to undo 2024-04-21 17:33:38 0 [Note] InnoDB: Trx id counter is 87331867343 2024-04-21 17:33:39 0 [Note] InnoDB: To recover: 193978 pages 2024-04-21 17:33:54 0 [Note] InnoDB: To recover: 193978 pages 2024-04-21 17:34:09 0 [Note] InnoDB: Last binlog file './db1-binary.115031', position 196863845 2024-04-21 17:34:09 0 [Note] InnoDB: 128 rollback segments are active. 2024-04-21 17:34:09 0 [Note] InnoDB: Starting in background the rollback of recovered transactions 2024-04-21 17:34:09 0 [Note] InnoDB: To roll back: 45 transactions, 45 rows 2024-04-21 17:34:09 0 [Note] InnoDB: Rolled back recovered transaction 87331867320 2024-04-21 17:34:09 0 [Note] InnoDB: Removed temporary tablespace data file: "./ibtmp1" 2024-04-21 17:34:09 0 [Note] InnoDB: Setting file './ibtmp1' size to 12.000MiB. Physically writing the file full; Please wait ... 2024-04-21 17:34:09 0 [Note] InnoDB: Rolled back recovered transaction 87331867208 2024-04-21 17:34:09 0 [Note] InnoDB: File './ibtmp1' size is now 12.000MiB. 2024-04-21 17:34:09 0 [Note] InnoDB: log sequence number 28051185131461; transaction id 87331867346 2024-04-21 17:34:09 0 [Note] InnoDB: Loading buffer pool(s) from /var/lib/mysql/ib_buffer_pool 2024-04-21 17:34:09 0 [Note] Plugin 'FEEDBACK' is disabled. 2024-04-21 17:34:09 0 [Note] InnoDB: Rolled back recovered transaction 87331866856 2024-04-21 17:34:09 0 [Note] InnoDB: Rolled back recovered transaction 87331867336 2024-04-21 17:34:09 0 [Note] InnoDB: Rolled back recovered transaction 87331866924 2024-04-21 17:34:09 0 [Note] InnoDB: Rolled back recovered transaction 87331866926 2024-04-21 17:34:09 0 [Note] InnoDB: Rolled back recovered transaction 87331867312 2024-04-21 17:34:09 0 [Note] InnoDB: Rolled back recovered transaction 87331867300 2024-04-21 17:34:09 0 [Warning] 'thread-concurrency' was removed. It does nothing now and exists only for compatibility with old my.cnf files. 2024-04-21 17:34:09 0 [Warning] 'innodb-thread-concurrency' was removed. It does nothing now and exists only for compatibility with old my.cnf files. 2024-04-21 17:34:09 0 [Warning] 'innodb-log-files-in-group' was removed. It does nothing now and exists only for compatibility with old my.cnf files. 2024-04-21 17:34:09 0 [Note] InnoDB: Rolled back recovered transaction 87331866607 2024-04-21 17:34:09 0 [Note] InnoDB: Rolled back recovered transaction 87331867316 2024-04-21 17:34:09 0 [Note] InnoDB: Rolled back recovered transaction 87331867252 2024-04-21 17:34:09 0 [Note] InnoDB: Rolled back recovered transaction 87331867262 2024-04-21 17:34:09 0 [Note] Recovering after a crash using db1-binary 2024-04-21 17:34:09 0 [Note] Starting table crash recovery... 2024-04-21 17:34:09 0 [Note] InnoDB: Starting recovery for XA transactions... 2024-04-21 17:34:09 0 [Note] InnoDB: Transaction 87331867291 in prepared state after recovery 2024-04-21 17:34:09 0 [Note] InnoDB: Transaction contains changes to 1 rows 2024-04-21 17:34:09 0 [Note] InnoDB: Transaction 87331867275 in prepared state after recovery 2024-04-21 17:34:09 0 [Note] InnoDB: Transaction contains changes to 1 rows 2024-04-21 17:34:09 0 [Note] InnoDB: Transaction 87331867271 in prepared state after recovery 2024-04-21 17:34:09 0 [Note] InnoDB: Transaction contains changes to 1 rows 2024-04-21 17:34:09 0 [Note] InnoDB: Transaction 87331867303 in prepared state after recovery 2024-04-21 17:34:09 0 [Note] InnoDB: Transaction contains changes to 1 rows 2024-04-21 17:34:09 0 [Note] InnoDB: Transaction 87331867295 in prepared state after recovery 2024-04-21 17:34:09 0 [Note] InnoDB: Transaction contains changes to 1 rows 2024-04-21 17:34:09 0 [Note] InnoDB: Transaction 87331867285 in prepared state after recovery 2024-04-21 17:34:09 0 [Note] InnoDB: Transaction contains changes to 1 rows 2024-04-21 17:34:09 0 [Note] InnoDB: Transaction 87331867297 in prepared state after recovery 2024-04-21 17:34:09 0 [Note] InnoDB: Transaction contains changes to 1 rows 2024-04-21 17:34:09 0 [Note] InnoDB: Transaction 87331867265 in prepared state after recovery 2024-04-21 17:34:09 0 [Note] InnoDB: Transaction contains changes to 1 rows 2024-04-21 17:34:09 0 [Note] InnoDB: Transaction 87331867301 in prepared state after recovery 2024-04-21 17:34:09 0 [Note] InnoDB: Transaction contains changes to 1 rows 2024-04-21 17:34:09 0 [Note] InnoDB: Transaction 87331867273 in prepared state after recovery 2024-04-21 17:34:09 0 [Note] InnoDB: Transaction contains changes to 1 rows 2024-04-21 17:34:09 0 [Note] InnoDB: Transaction 87331867289 in prepared state after recovery 2024-04-21 17:34:09 0 [Note] InnoDB: Transaction contains changes to 1 rows 2024-04-21 17:34:09 0 [Note] InnoDB: Transaction 87331867277 in prepared state after recovery 2024-04-21 17:34:09 0 [Note] InnoDB: Transaction contains changes to 1 rows 2024-04-21 17:34:09 0 [Note] InnoDB: Transaction 87331867309 in prepared state after recovery 2024-04-21 17:34:09 0 [Note] InnoDB: Transaction contains changes to 1 rows 2024-04-21 17:34:09 0 [Note] InnoDB: Transaction 87331867261 in prepared state after recovery 2024-04-21 17:34:09 0 [Note] InnoDB: Transaction contains changes to 1 rows 2024-04-21 17:34:09 0 [Note] InnoDB: Transaction 87331866965 in prepared state after recovery 2024-04-21 17:34:09 0 [Note] InnoDB: Transaction contains changes to 1 rows 2024-04-21 17:34:09 0 [Note] InnoDB: Transaction 87331867314 in prepared state after recovery 2024-04-21 17:34:09 0 [Note] InnoDB: Transaction contains changes to 1 rows 2024-04-21 17:34:09 0 [Note] InnoDB: Transaction 87331867258 in prepared state after recovery 2024-04-21 17:34:09 0 [Note] InnoDB: Transaction contains changes to 1 rows 2024-04-21 17:34:09 0 [Note] InnoDB: Transaction 87331867274 in prepared state after recovery 2024-04-21 17:34:09 0 [Note] InnoDB: Transaction contains changes to 1 rows 2024-04-21 17:34:09 0 [Note] InnoDB: Transaction 87331867286 in prepared state after recovery 2024-04-21 17:34:09 0 [Note] InnoDB: Transaction contains changes to 1 rows 2024-04-21 17:34:09 0 [Note] InnoDB: Transaction 87331867278 in prepared state after recovery 2024-04-21 17:34:09 0 [Note] InnoDB: Transaction contains changes to 1 rows 2024-04-21 17:34:09 0 [Note] InnoDB: Transaction 87331867276 in prepared state after recovery 2024-04-21 17:34:09 0 [Note] InnoDB: Transaction contains changes to 1 rows 2024-04-21 17:34:09 0 [Note] InnoDB: Transaction 87331867308 in prepared state after recovery 2024-04-21 17:34:09 0 [Note] InnoDB: Transaction contains changes to 1 rows 2024-04-21 17:34:09 0 [Note] InnoDB: Transaction 87331867212 in prepared state after recovery 2024-04-21 17:34:09 0 [Note] InnoDB: Transaction contains changes to 1 rows 2024-04-21 17:34:09 0 [Note] InnoDB: Transaction 87331867284 in prepared state after recovery 2024-04-21 17:34:09 0 [Note] InnoDB: Transaction contains changes to 1 rows 2024-04-21 17:34:09 0 [Note] InnoDB: Transaction 87331866610 in prepared state after recovery 2024-04-21 17:34:09 0 [Note] InnoDB: Transaction contains changes to 1 rows 2024-04-21 17:34:09 0 [Note] InnoDB: Transaction 87331867292 in prepared state after recovery 2024-04-21 17:34:09 0 [Note] InnoDB: Transaction contains changes to 1 rows 2024-04-21 17:34:09 0 [Note] InnoDB: Transaction 87331867280 in prepared state after recovery 2024-04-21 17:34:09 0 [Note] InnoDB: Transaction contains changes to 1 rows 2024-04-21 17:34:09 0 [Note] InnoDB: Transaction 87331867272 in prepared state after recovery 2024-04-21 17:34:09 0 [Note] InnoDB: Transaction contains changes to 1 rows 2024-04-21 17:34:09 0 [Note] InnoDB: Transaction 87331867084 in prepared state after recovery 2024-04-21 17:34:09 0 [Note] InnoDB: Transaction contains changes to 1 rows 2024-04-21 17:34:09 0 [Note] InnoDB: 29 transactions in prepared state after recovery 2024-04-21 17:34:09 0 [Note] Found 29 prepared transaction(s) in InnoDB 2024-04-21 17:34:09 0 [Note] Crash table recovery finished. 2024-04-21 17:34:09 0 [Note] InnoDB: Rolled back recovered transaction 87331867294 2024-04-21 17:34:09 0 [Note] InnoDB: Rolled back recovered transaction 87331867310 2024-04-21 17:34:09 0 [Note] InnoDB: Rolled back recovered transaction 87331867326 2024-04-21 17:34:09 0 [Note] InnoDB: Rolled back recovered transaction 87331867334 2024-04-21 17:34:09 0 [Note] InnoDB: Rolled back recovered transaction 87331867015 2024-04-21 17:34:09 0 [Note] InnoDB: Rolled back recovered transaction 87331866939 2024-04-21 17:34:09 0 [Note] InnoDB: Rolled back recovered transaction 87331866858 2024-04-21 17:34:09 0 [Note] InnoDB: Rolled back recovered transaction 87331867302 2024-04-21 17:34:09 0 [Note] InnoDB: Rolled back recovered transaction 87331867254 2024-04-21 17:34:09 0 [Note] InnoDB: Rolled back recovered transaction 87331866905 2024-04-21 17:34:09 0 [Note] InnoDB: Rolled back recovered transaction 87331867322 2024-04-21 17:34:09 0 [Note] InnoDB: Rolled back recovered transaction 87331867290 2024-04-21 17:34:09 0 [Note] InnoDB: Rolled back recovered transaction 87331867298 2024-04-21 17:34:09 0 [Note] InnoDB: Rolled back recovered transaction 87331867330 2024-04-21 17:34:09 0 [Note] InnoDB: Rolled back recovered transaction 87331866925 2024-04-21 17:34:09 0 [Note] InnoDB: Rolled back recovered transaction 87331867085 2024-04-21 17:34:09 0 [Note] InnoDB: Rolled back recovered transaction 87331867282 2024-04-21 17:34:09 0 [Note] InnoDB: Rolled back recovered transaction 87331866851 2024-04-21 17:34:09 0 [Note] InnoDB: Rolled back recovered transaction 87331867145 2024-04-21 17:34:09 0 [Note] InnoDB: Rolled back recovered transaction 87331867305 2024-04-21 17:34:09 0 [Note] InnoDB: Rolled back recovered transaction 87331867257 2024-04-21 17:34:09 0 [Note] InnoDB: Rolled back recovered transaction 87331867333 2024-04-21 17:34:09 0 [Note] InnoDB: Rolled back recovered transaction 87331867313 2024-04-21 17:34:09 0 [Note] InnoDB: Rolled back recovered transaction 87331867317 2024-04-21 17:34:09 0 [Note] InnoDB: Rolled back recovered transaction 87331867311 2024-04-21 17:34:09 0 [Note] InnoDB: Rolled back recovered transaction 87331866853 2024-04-21 17:34:09 0 [Note] InnoDB: Rolled back recovered transaction 87331867335 2024-04-21 17:34:09 0 [Note] InnoDB: Rolled back recovered transaction 87331867255 2024-04-21 17:34:09 0 [Note] InnoDB: Rolled back recovered transaction 87331867331 2024-04-21 17:34:09 0 [Note] InnoDB: Rolled back recovered transaction 87331867299 2024-04-21 17:34:09 0 [Note] InnoDB: Rolled back recovered transaction 87331866697 2024-04-21 17:34:09 0 [Note] InnoDB: Rolled back recovered transaction 87331867259 2024-04-21 17:34:09 0 [Note] InnoDB: Rolled back recovered transaction 87331867315 2024-04-21 17:34:09 0 [Note] InnoDB: Rollback of non-prepared transactions completed 2024-04-21 17:34:10 0 [Note] Server socket created on IP: '0.0.0.0'. 2024-04-21 17:34:10 0 [Note] Server socket created on IP: '::'. 2024-04-21 17:34:10 0 [Warning] 'user' entry '@alepo-db2-ilb' ignored in --skip-name-resolve mode. 2024-04-21 17:34:10 0 [Warning] 'user' entry 'root@localhost.localdomain' ignored in --skip-name-resolve mode. 2024-04-21 17:34:10 0 [Warning] 'proxies_priv' entry '@% root@alepo-db2-ilb' ignored in --skip-name-resolve mode. 2024-04-21 17:34:10 3 [Note] Reading Master_info: 'master-s@002ddb3.info' Relay_info:'relay-log-s@002ddb3.info' 2024-04-21 17:34:10 3 [Note] Initialized Master_info from 'master-s@002ddb3.info' 2024-04-21 17:34:10 4 [Note] Master 's-db3': Slave I/O thread: Start asynchronous replication to master '@:3306' in log '' at position 4 2024-04-21 17:34:10 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 2024-04-21 17:34:10 4 [Note] Master 's-db3': Slave I/O thread killed while connecting to master 2024-04-21 17:34:10 4 [Note] Master 's-db3': Slave I/O thread exiting, read up to log 'FIRST', position 4, master :3306 2024-04-21 17:34:10 3 [Note] Started replication for 's-db3' 2024-04-21 17:34:10 5 [Note] Master 's-db3': Slave SQL thread initialized, starting replication in log 'FIRST' at position 0, relay log './db1-relay-s@002ddb3.000019' position: 4 2024-04-21 17:34:10 3 [Note] Reading Master_info: 'master-s@002ddb4.info' Relay_info:'relay-log-s@002ddb4.info' 2024-04-21 17:34:10 3 [Note] Initialized Master_info from 'master-s@002ddb4.info' 2024-04-21 17:34:10 18 [Note] Master 's-db4': Slave I/O thread: Start asynchronous replication to master 'gtid@10.76.25.11:3306' in log 'db4-binary.090586' at position 192763340 2024-04-21 17:34:10 3 [Note] Started replication for 's-db4' 2024-04-21 17:34:10 19 [Note] Master 's-db4': Slave SQL thread initialized, starting replication in log 'db4-binary.090586' at position 192763340, relay log './db1-relay-s@002ddb4.023031' position: 783 2024-04-21 17:34:10 3 [Note] Reading Master_info: 'master-s@002ddb2.info' Relay_info:'relay-log-s@002ddb2.info' 2024-04-21 17:34:10 3 [Note] Initialized Master_info from 'master-s@002ddb2.info' 2024-04-21 17:34:10 20 [Note] Master 's-db2': Slave I/O thread: Start asynchronous replication to master '@:3306' in log '' at position 4 2024-04-21 17:34:10 20 [ERROR] Master 's-db2': Slave I/O: Fatal error: Invalid (empty) username when attempting to connect to the master server. Connection attempt terminated. Internal MariaDB error code: 1593 2024-04-21 17:34:10 20 [Note] Master 's-db2': Slave I/O thread killed while connecting to master 2024-04-21 17:34:10 20 [Note] Master 's-db2': Slave I/O thread exiting, read up to log 'FIRST', position 4, master :3306 2024-04-21 17:34:10 3 [Note] Started replication for 's-db2' 2024-04-21 17:34:10 21 [Note] Master 's-db2': Slave SQL thread initialized, starting replication in log 'FIRST' at position 0, relay log './db1-relay-s@002ddb2.000018' position: 4 2024-04-21 17:34:10 3 [Note] Reading Master_info: 'master-s@002ddb5.info' Relay_info:'relay-log-s@002ddb5.info' 2024-04-21 17:34:10 18 [Note] Master 's-db4': Slave I/O thread: connected to master 'gtid@10.76.25.11:3306',replication started in log 'db4-binary.090586' at position 192763340 2024-04-21 17:34:10 3 [Note] Initialized Master_info from 'master-s@002ddb5.info' 2024-04-21 17:34:10 22 [Note] Master 's-db5': Slave I/O thread: Start asynchronous replication to master '@:3306' in log '' at position 4 2024-04-21 17:34:10 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 2024-04-21 17:34:10 22 [Note] Master 's-db5': Slave I/O thread killed while connecting to master 2024-04-21 17:34:10 22 [Note] Master 's-db5': Slave I/O thread exiting, read up to log 'FIRST', position 4, master :3306 2024-04-21 17:34:10 3 [Note] Started replication for 's-db5' 2024-04-21 17:34:10 23 [Note] Master 's-db5': Slave SQL thread initialized, starting replication in log 'FIRST' at position 0, relay log './db1-relay-s@002ddb5.000010' position: 4 2024-04-21 17:34:10 25 [Note] Slave I/O thread: Start asynchronous replication to master 'gtid@10.76.24.77:3306' in log 'db2-binary.115728' at position 114886046 2024-04-21 17:34:10 0 [Note] /usr/sbin/mariadbd: ready for connections. Version: '10.11.5-MariaDB-log' socket: '/var/lib/mysql/mysql.sock' port: 3306 MariaDB Server 2024-04-21 17:34:10 26 [Note] Slave SQL thread initialized, starting replication in log 'db2-binary.115728' at position 114886046, relay log './db1-relay.025305' position: 767 2024-04-21 17:34:10 25 [Note] Slave I/O thread: connected to master 'gtid@10.76.24.77:3306',replication started in log 'db2-binary.115728' at position 114886046 2024-04-21 17:34:11 0 [Note] InnoDB: Buffer pool(s) load completed at 240421 17:34:11 2024-04-21 17:34:32 2734 [Note] Start binlog_dump to slave_server(2), pos(db1-binary.115031, 196892648), using_gtid(0), gtid('') 2024-04-21 17:34:32 2737 [Note] Start binlog_dump to slave_server(3), pos(db1-binary.115031, 196363042), using_gtid(0), gtid('') 2024-04-21 17:34:32 2744 [Note] Start binlog_dump to slave_server(4), pos(db1-binary.115031, 196768680), using_gtid(0), gtid('') 2024-04-25 14:20:03 25 [ERROR] Error reading packet from server: Lost connection to server during query (server_errno=2013) 2024-04-25 14:20:03 25 [Note] Slave I/O thread: Failed reading log event, reconnecting to retry, log 'db2-binary.118419' at position 16937422 2024-04-25 14:20:04 25 [ERROR] Slave I/O: error reconnecting to master 'gtid@10.76.24.77:3306' - retry-time: 60 maximum-retries: 100000 message: Lost connection to server at 'reading initial communication packet', system error: 104 "Connection reset by peer", Internal MariaDB error code: 2013 2024-04-25 14:20:12 2734 [Warning] Aborted connection 2734 to db: 'unconnected' user: 'gtid' host: '10.76.24.77' (Got an error writing communication packets) 2024-04-25 14:20:47 11311764 [Note] Start binlog_dump to slave_server(2), pos(db1-binary.117723, 99332905), using_gtid(0), gtid('') 2024-04-25 14:21:04 25 [Note] Slave: connected to master 'gtid@10.76.24.77:3306',replication resumed in log 'db2-binary.118419' at position 16937422 2024-05-01 2:00:01 26 [Note] Slave SQL thread exiting, replication stopped in log 'db2-binary.122443' at position 97336607, master: 10.76.24.77:3306 2024-05-01 2:00:01 25 [Note] Slave I/O thread exiting, read up to log 'db2-binary.122443', position 97338973, master 10.76.24.77:3306 2024-05-01 2:00:01 25589168 [Note] Slave I/O thread: Start asynchronous replication to master 'gtid@10.76.24.77:3306' in log 'db2-binary.122443' at position 97338973 2024-05-01 2:00:01 25589169 [Note] Slave SQL thread initialized, starting replication in log 'db2-binary.122443' at position 97336607, relay log './db1-relay.046808' position: 767 2024-05-01 2:00:01 25589168 [Note] Slave I/O thread: connected to master 'gtid@10.76.24.77:3306',replication started in log 'db2-binary.122443' at position 97338973 2024-05-03 17:13:48 31931980 [Warning] Aborted connection 31931980 to db: 'unconnected' user: 'unauthenticated' host: '10.254.174.46' (This connection closed normally without authentication) 2024-05-03 17:13:48 31932273 [Warning] Aborted connection 31932273 to db: 'unconnected' user: 'unauthenticated' host: '10.254.174.46' (This connection closed normally without authentication) 2024-05-03 17:13:48 31932275 [Warning] Access denied for user ''@'10.254.174.46' (using password: NO) 2024-05-03 17:18:26 31940324 [Warning] Aborted connection 31940324 to db: 'unconnected' user: 'unauthenticated' host: '10.254.174.46' (This connection closed normally without authentication) 2024-05-05 11:52:09 11311590 [Warning] Aborted connection 11311590 to db: 'aaadb' user: 'alepoaaa' host: '10.76.24.87' (Got an error reading communication packets) 2024-05-05 11:52:09 11311589 [Warning] Aborted connection 11311589 to db: 'aaadb' user: 'alepoaaa' host: '10.76.24.87' (Got an error reading communication packets) 2024-05-05 11:52:09 11311588 [Warning] Aborted connection 11311588 to db: 'aaadb' user: 'alepoaaa' host: '10.76.24.87' (Got an error reading communication packets) 2024-05-05 11:52:09 11311587 [Warning] Aborted connection 11311587 to db: 'aaadb' user: 'alepoaaa' host: '10.76.24.87' (Got an error reading communication packets) 2024-05-05 11:52:09 11311585 [Warning] Aborted connection 11311585 to db: 'aaadb' user: 'alepoaaa' host: '10.76.24.87' (Got an error reading communication packets) 2024-05-05 11:52:09 11311586 [Warning] Aborted connection 11311586 to db: 'aaadb' user: 'alepoaaa' host: '10.76.24.87' (Got an error reading communication packets) 2024-05-05 11:52:09 11311584 [Warning] Aborted connection 11311584 to db: 'aaadb' user: 'alepoaaa' host: '10.76.24.87' (Got an error reading communication packets) 2024-05-05 11:52:09 11311583 [Warning] Aborted connection 11311583 to db: 'aaadb' user: 'alepoaaa' host: '10.76.24.87' (Got an error reading communication packets) 2024-05-05 11:52:09 11311581 [Warning] Aborted connection 11311581 to db: 'aaadb' user: 'alepoaaa' host: '10.76.24.87' (Got an error reading communication packets) 2024-05-05 11:52:09 11311582 [Warning] Aborted connection 11311582 to db: 'aaadb' user: 'alepoaaa' host: '10.76.24.87' (Got an error reading communication packets) 2024-05-05 11:52:09 11311580 [Warning] Aborted connection 11311580 to db: 'aaadb' user: 'alepoaaa' host: '10.76.24.87' (Got an error reading communication packets) 2024-05-05 11:52:09 11311576 [Warning] Aborted connection 11311576 to db: 'aaadb' user: 'alepoaaa' host: '10.76.24.87' (Got an error reading communication packets) 2024-05-05 11:52:09 11311579 [Warning] Aborted connection 11311579 to db: 'aaadb' user: 'alepoaaa' host: '10.76.24.87' (Got an error reading communication packets) 2024-05-05 11:52:09 11311575 [Warning] Aborted connection 11311575 to db: 'aaadb' user: 'alepoaaa' host: '10.76.24.87' (Got an error reading communication packets) 2024-05-05 11:52:09 11311564 [Warning] Aborted connection 11311564 to db: 'aaadb' user: 'alepoaaa' host: '10.76.24.87' (Got an error reading communication packets) 2024-05-05 11:52:09 11311552 [Warning] Aborted connection 11311552 to db: 'aaadb' user: 'alepoaaa' host: '10.76.24.87' (Got an error reading communication packets) 2024-05-05 11:52:09 11311559 [Warning] Aborted connection 11311559 to db: 'aaadb' user: 'alepoaaa' host: '10.76.24.87' (Got an error reading communication packets) 2024-05-05 11:52:09 11311573 [Warning] Aborted connection 11311573 to db: 'aaadb' user: 'alepoaaa' host: '10.76.24.87' (Got an error reading communication packets) 2024-05-05 11:52:09 11311549 [Warning] Aborted connection 11311549 to db: 'aaadb' user: 'alepoaaa' host: '10.76.24.87' (Got an error reading communication packets) 2024-05-05 11:52:09 11311555 [Warning] Aborted connection 11311555 to db: 'aaadb' user: 'alepoaaa' host: '10.76.24.87' (Got an error reading communication packets) 2024-05-05 11:52:09 11311569 [Warning] Aborted connection 11311569 to db: 'aaadb' user: 'alepoaaa' host: '10.76.24.87' (Got an error reading communication packets) 2024-05-05 11:52:09 11311548 [Warning] Aborted connection 11311548 to db: 'aaadb' user: 'alepoaaa' host: '10.76.24.87' (Got an error reading communication packets) 2024-05-05 11:52:09 11311547 [Warning] Aborted connection 11311547 to db: 'aaadb' user: 'alepoaaa' host: '10.76.24.87' (Got an error reading communication packets) 2024-05-05 11:52:09 11311546 [Warning] Aborted connection 11311546 to db: 'aaadb' user: 'alepoaaa' host: '10.76.24.87' (Got an error reading communication packets) 2024-05-05 11:52:09 11311545 [Warning] Aborted connection 11311545 to db: 'aaadb' user: 'alepoaaa' host: '10.76.24.87' (Got an error reading communication packets) 2024-05-05 11:52:09 11311554 [Warning] Aborted connection 11311554 to db: 'aaadb' user: 'alepoaaa' host: '10.76.24.87' (Got an error reading communication packets) 2024-05-05 11:52:09 11311544 [Warning] Aborted connection 11311544 to db: 'aaadb' user: 'alepoaaa' host: '10.76.24.87' (Got an error reading communication packets) 2024-05-05 11:52:09 11311543 [Warning] Aborted connection 11311543 to db: 'aaadb' user: 'alepoaaa' host: '10.76.24.87' (Got an error reading communication packets) 2024-05-05 11:52:09 11311542 [Warning] Aborted connection 11311542 to db: 'aaadb' user: 'alepoaaa' host: '10.76.24.87' (Got an error reading communication packets) 2024-05-05 11:52:09 11311541 [Warning] Aborted connection 11311541 to db: 'aaadb' user: 'alepoaaa' host: '10.76.24.87' (Got an error reading communication packets) 2024-05-05 11:52:09 11311540 [Warning] Aborted connection 11311540 to db: 'aaadb' user: 'alepoaaa' host: '10.76.24.87' (Got an error reading communication packets) 2024-05-05 11:52:09 11311539 [Warning] Aborted connection 11311539 to db: 'aaadb' user: 'alepoaaa' host: '10.76.24.87' (Got an error reading communication packets) 2024-05-05 11:52:09 11311538 [Warning] Aborted connection 11311538 to db: 'aaadb' user: 'alepoaaa' host: '10.76.24.87' (Got an error reading communication packets) 2024-05-05 11:52:09 11311537 [Warning] Aborted connection 11311537 to db: 'aaadb' user: 'alepoaaa' host: '10.76.24.87' (Got an error reading communication packets) 2024-05-05 11:52:09 11311574 [Warning] Aborted connection 11311574 to db: 'aaadb' user: 'alepoaaa' host: '10.76.24.87' (Got an error reading communication packets) 2024-05-05 11:52:09 11311536 [Warning] Aborted connection 11311536 to db: 'aaadb' user: 'alepoaaa' host: '10.76.24.87' (Got an error reading communication packets) 2024-05-05 11:52:09 11311557 [Warning] Aborted connection 11311557 to db: 'aaadb' user: 'alepoaaa' host: '10.76.24.87' (Got an error reading communication packets) 2024-05-05 11:52:09 11311561 [Warning] Aborted connection 11311561 to db: 'aaadb' user: 'alepoaaa' host: '10.76.24.87' (Got an error reading communication packets) 2024-05-05 11:52:09 11311535 [Warning] Aborted connection 11311535 to db: 'aaadb' user: 'alepoaaa' host: '10.76.24.87' (Got an error reading communication packets) 2024-05-05 11:52:09 11311534 [Warning] Aborted connection 11311534 to db: 'aaadb' user: 'alepoaaa' host: '10.76.24.87' (Got an error reading communication packets) 2024-05-05 11:52:09 11311533 [Warning] Aborted connection 11311533 to db: 'aaadb' user: 'alepoaaa' host: '10.76.24.87' (Got an error reading communication packets) 2024-05-05 11:52:09 11311568 [Warning] Aborted connection 11311568 to db: 'aaadb' user: 'alepoaaa' host: '10.76.24.87' (Got an error reading communication packets) 2024-05-05 11:52:09 11311563 [Warning] Aborted connection 11311563 to db: 'aaadb' user: 'alepoaaa' host: '10.76.24.87' (Got an error reading communication packets) 2024-05-05 11:52:09 11311531 [Warning] Aborted connection 11311531 to db: 'aaadb' user: 'alepoaaa' host: '10.76.24.87' (Got an error reading communication packets) 2024-05-05 11:52:09 11311532 [Warning] Aborted connection 11311532 to db: 'aaadb' user: 'alepoaaa' host: '10.76.24.87' (Got an error reading communication packets) 2024-05-05 11:52:09 11311572 [Warning] Aborted connection 11311572 to db: 'aaadb' user: 'alepoaaa' host: '10.76.24.87' (Got an error reading communication packets) 2024-05-05 11:52:09 11311558 [Warning] Aborted connection 11311558 to db: 'aaadb' user: 'alepoaaa' host: '10.76.24.87' (Got an error reading communication packets) 2024-05-05 11:52:09 11311530 [Warning] Aborted connection 11311530 to db: 'aaadb' user: 'alepoaaa' host: '10.76.24.87' (Got an error reading communication packets) 2024-05-05 11:52:09 11311553 [Warning] Aborted connection 11311553 to db: 'aaadb' user: 'alepoaaa' host: '10.76.24.87' (Got an error reading communication packets) 2024-05-05 11:52:09 11311578 [Warning] Aborted connection 11311578 to db: 'aaadb' user: 'alepoaaa' host: '10.76.24.87' (Got an error reading communication packets) 2024-05-05 11:52:09 11311571 [Warning] Aborted connection 11311571 to db: 'aaadb' user: 'alepoaaa' host: '10.76.24.87' (Got an error reading communication packets) 2024-05-05 11:52:09 11311551 [Warning] Aborted connection 11311551 to db: 'aaadb' user: 'alepoaaa' host: '10.76.24.87' (Got an error reading communication packets) 2024-05-05 11:52:09 11311556 [Warning] Aborted connection 11311556 to db: 'aaadb' user: 'alepoaaa' host: '10.76.24.87' (Got an error reading communication packets) 2024-05-05 11:52:09 11311562 [Warning] Aborted connection 11311562 to db: 'aaadb' user: 'alepoaaa' host: '10.76.24.87' (Got an error reading communication packets) 2024-05-05 11:52:09 11311529 [Warning] Aborted connection 11311529 to db: 'aaadb' user: 'alepoaaa' host: '10.76.24.87' (Got an error reading communication packets) 2024-05-05 11:52:09 11311577 [Warning] Aborted connection 11311577 to db: 'aaadb' user: 'alepoaaa' host: '10.76.24.87' (Got an error reading communication packets) 2024-05-05 11:52:09 11311528 [Warning] Aborted connection 11311528 to db: 'aaadb' user: 'alepoaaa' host: '10.76.24.87' (Got an error reading communication packets) 2024-05-05 11:52:09 11311527 [Warning] Aborted connection 11311527 to db: 'aaadb' user: 'alepoaaa' host: '10.76.24.87' (Got an error reading communication packets) 2024-05-05 11:52:09 11311526 [Warning] Aborted connection 11311526 to db: 'aaadb' user: 'alepoaaa' host: '10.76.24.87' (Got an error reading communication packets) 2024-05-05 11:52:09 11311570 [Warning] Aborted connection 11311570 to db: 'aaadb' user: 'alepoaaa' host: '10.76.24.87' (Got an error reading communication packets) 2024-05-05 11:52:09 11311525 [Warning] Aborted connection 11311525 to db: 'aaadb' user: 'alepoaaa' host: '10.76.24.87' (Got an error reading communication packets) 2024-05-05 11:52:09 11311550 [Warning] Aborted connection 11311550 to db: 'aaadb' user: 'alepoaaa' host: '10.76.24.87' (Got an error reading communication packets) 2024-05-05 11:52:09 11311524 [Warning] Aborted connection 11311524 to db: 'aaadb' user: 'alepoaaa' host: '10.76.24.87' (Got an error reading communication packets) 2024-05-05 11:52:09 11311560 [Warning] Aborted connection 11311560 to db: 'aaadb' user: 'alepoaaa' host: '10.76.24.87' (Got an error reading communication packets) 2024-05-05 11:52:09 11311567 [Warning] Aborted connection 11311567 to db: 'aaadb' user: 'alepoaaa' host: '10.76.24.87' (Got an error reading communication packets) 2024-05-05 11:52:09 11311523 [Warning] Aborted connection 11311523 to db: 'aaadb' user: 'alepoaaa' host: '10.76.24.87' (Got an error reading communication packets) 2024-05-05 11:52:09 11311522 [Warning] Aborted connection 11311522 to db: 'aaadb' user: 'alepoaaa' host: '10.76.24.87' (Got an error reading communication packets) 2024-05-05 11:52:09 11311521 [Warning] Aborted connection 11311521 to db: 'aaadb' user: 'alepoaaa' host: '10.76.24.87' (Got an error reading communication packets) 2024-05-05 11:52:09 11311519 [Warning] Aborted connection 11311519 to db: 'aaadb' user: 'alepoaaa' host: '10.76.24.87' (Got an error reading communication packets) 2024-05-05 11:52:09 11311520 [Warning] Aborted connection 11311520 to db: 'aaadb' user: 'alepoaaa' host: '10.76.24.87' (Got an error reading communication packets) 2024-05-05 11:52:09 11311518 [Warning] Aborted connection 11311518 to db: 'aaadb' user: 'alepoaaa' host: '10.76.24.87' (Got an error reading communication packets) 2024-05-10 3:55:11 47473886 [Warning] Aborted connection 47473886 to db: 'aaadb' user: 'alepoaaaems' host: '10.76.24.67' (Got timeout reading communication packets) 2024-05-10 3:55:34 47471999 [Warning] Aborted connection 47471999 to db: 'aaadb' user: 'alepoaaaems' host: '10.76.24.67' (Got timeout reading communication packets) 2024-05-10 3:55:36 47443070 [Warning] Aborted connection 47443070 to db: 'aaadb' user: 'alepoaaaems' host: '10.76.24.67' (Got timeout reading communication packets) 2024-05-10 3:57:37 47482592 [Warning] Aborted connection 47482592 to db: 'aaadb' user: 'alepoaaaems' host: '10.76.24.67' (Got timeout reading communication packets) 240510 12:33:32 [ERROR] mysqld got signal 11 ; 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.11.5-MariaDB-log source revision: 7875294b6b74b53dd3aaa723e6cc103d2bb47b2c key_buffer_size=67108864 read_buffer_size=131072 max_used_connections=496 max_threads=802 thread_count=476 It is possible that mysqld could use up to key_buffer_size + (read_buffer_size + sort_buffer_size)*max_threads = 1831964 K bytes of memory Hope that's ok; if not, decrease some variables in the equation. Thread pointer: 0x7f0ac4026908 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 = 0x7f0aa956eb98 thread_stack 0x49000 /usr/sbin/mariadbd(my_print_stacktrace+0x2e)[0x556726da712e] mysys/stacktrace.c:216(my_print_stacktrace)[0x5567268a05b5] /lib64/libpthread.so.0(+0x12cf0)[0x7f59cfc3dcf0] sql/sql_yacc.yy:9072(MYSQLparse(THD*))[0x556726826117] sql/sql_parse.cc:10394(parse_sql(THD*, Parser_state*, Object_creation_ctx*, bool))[0x55672665681a] sql/sql_parse.cc:7988(mysql_parse(THD*, char*, unsigned int, Parser_state*))[0x556726652a1a] sql/sql_parse.cc:1896(dispatch_command(enum_server_command, THD*, char*, unsigned int, bool))[0x55672665c6e6] sql/sql_parse.cc:1407(do_command(THD*, bool))[0x55672665ddab] sql/sql_connect.cc:1416(do_handle_one_connection(CONNECT*, bool))[0x556726771977] sql/sql_connect.cc:1318(handle_one_connection)[0x556726771cbd] perfschema/pfs.cc:2204(MyCTX_nopad::finish(unsigned char*, unsigned int*))[0x556726aa7c9d] /lib64/libpthread.so.0(+0x81ca)[0x7f59cfc331ca] /lib64/libc.so.6(clone+0x43)[0x7f59cef83e73] Trying to get some variables. Some pointers may be invalid and cause the dump to abort. Query (0x7f0ac40313b0): Select Users.UserIndex, UserID, Users.Password, GroupName, PasswordSource, UserService, UserIP, FilterName, UserActive, Users.StartDate, UserExpiryDate, CallBackNumber, CallerID, Lockout, Users.PasswordEncryptionMethod, MaxUserSessions, SkipPasswordCheck, HotlineStatus, BarringStatus, BarringReason, MaxVolumeCap, AllowedAccessTypes, CopyRadiusRequests, SubnetIP, SubnetMask, CIDR, CustomField1, CustomField2, CustomField3, CustomField4, CustomField5, CustomNumField1, CustomNumField2, CustomNumField3, CustomNumField4, CustomNumField5, SessionLimit, UserTokens, FirstLogon, FramedInterfaceId, FramedIPv6Prefix, PeriodicTimeUsage, PeriodicVolumeUsage, TimeUsageTriggerThresholds, VolumeUsageTriggerThresholds, CustomReplylist, CustomChecklist, BillingSystemCorrelationId, ChargingSystemCorrelationId, ChargingMode, LockOutTime, LockOutCount, Users.PseudoIdentity, CustomDate1, CustomDate2, CustomDate3, CustomDate4, CustomDate5, CustomField6, CustomField7, CustomField8, CustomField9, CustomField10, RestrictedLocations, MaxTimeCap, PortId, CustomNumField6, CustomNumField7, CustomNumField8, CustomNumField9, CustomNumField10,SpeedMapName,UserIPv6,NetworkService, CustomField11,CustomField12,CustomField13,CustomField14,CustomField15 , PasswordDate From Users Where UserID = '03023096513' Connection ID (thread ID): 11311609 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,hash_join_cardinality=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 unlimited unlimited bytes Max resident set unlimited unlimited bytes Max processes 2061710 2061710 processes Max open files 32768 32768 files Max locked memory 65536 65536 bytes Max address space unlimited unlimited bytes Max file locks unlimited unlimited locks Max pending signals 2061710 2061710 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: /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 2024-05-10 12:34:11 0 [Note] Starting MariaDB 10.11.5-MariaDB-log source revision 7875294b6b74b53dd3aaa723e6cc103d2bb47b2c as process 3680911 2024-05-10 12:34:11 0 [Note] InnoDB: Compressed tables use zlib 1.2.11 2024-05-10 12:34:11 0 [Note] InnoDB: Number of transaction pools: 1 2024-05-10 12:34:11 0 [Note] InnoDB: Using crc32 + pclmulqdq instructions 2024-05-10 12:34:11 0 [Note] InnoDB: Using Linux native AIO 2024-05-10 12:34:11 0 [Note] InnoDB: Initializing buffer pool, total size = 300.000GiB, chunk size = 4.688GiB 2024-05-10 12:34:12 0 [Note] InnoDB: Completed initialization of buffer pool 2024-05-10 12:34:12 0 [Note] InnoDB: File system buffers for log disabled (block size=512 bytes) 2024-05-10 12:34:15 0 [Warning] InnoDB: 2906818560 bytes should have been read at 1388148736 from (unknown file), but got only 2147479552. Retrying. 2024-05-10 12:34:17 0 [Note] InnoDB: Starting crash recovery from checkpoint LSN=30424134031520 2024-05-10 12:34:27 0 [Note] InnoDB: Parsed redo log up to LSN=30425158295107; to recover: 155725 pages 2024-05-10 12:34:34 0 [Warning] InnoDB: 4294955008 bytes should have been read at 12288 from (unknown file), but got only 2147479552. Retrying. 2024-05-10 12:34:42 0 [Note] InnoDB: Parsed redo log up to LSN=30426200033244; to recover: 168825 pages 2024-05-10 12:34:51 0 [Note] InnoDB: End of log at LSN=30427080918232 2024-05-10 12:34:53 0 [Note] InnoDB: To recover: 191317 pages 2024-05-10 12:35:08 0 [Note] InnoDB: To recover: 191317 pages 2024-05-10 12:35:20 0 [Note] InnoDB: Last binlog file './db1-binary.128269', position 98938609 2024-05-10 12:35:20 0 [Note] InnoDB: 128 rollback segments are active. 2024-05-10 12:35:21 0 [Note] InnoDB: Removed temporary tablespace data file: "./ibtmp1" 2024-05-10 12:35:21 0 [Note] InnoDB: Setting file './ibtmp1' size to 12.000MiB. Physically writing the file full; Please wait ... 2024-05-10 12:35:21 0 [Note] InnoDB: File './ibtmp1' size is now 12.000MiB. 2024-05-10 12:35:21 0 [Note] InnoDB: log sequence number 30427080918232; transaction id 96222712458 2024-05-10 12:35:21 0 [Note] InnoDB: Loading buffer pool(s) from /var/lib/mysql/ib_buffer_pool 2024-05-10 12:35:21 0 [Note] Plugin 'FEEDBACK' is disabled. 2024-05-10 12:35:21 0 [Warning] 'thread-concurrency' was removed. It does nothing now and exists only for compatibility with old my.cnf files. 2024-05-10 12:35:21 0 [Warning] 'innodb-thread-concurrency' was removed. It does nothing now and exists only for compatibility with old my.cnf files. 2024-05-10 12:35:21 0 [Warning] 'innodb-log-files-in-group' was removed. It does nothing now and exists only for compatibility with old my.cnf files. 2024-05-10 12:35:21 0 [Note] Recovering after a crash using db1-binary 2024-05-10 12:35:21 0 [Note] Starting table crash recovery... 2024-05-10 12:35:21 0 [Note] Crash table recovery finished. 2024-05-10 12:35:21 0 [Note] Server socket created on IP: '0.0.0.0'. 2024-05-10 12:35:21 0 [Note] Server socket created on IP: '::'. 2024-05-10 12:35:21 0 [Warning] 'user' entry '@alepo-db2-ilb' ignored in --skip-name-resolve mode. 2024-05-10 12:35:21 0 [Warning] 'user' entry 'root@localhost.localdomain' ignored in --skip-name-resolve mode. 2024-05-10 12:35:21 0 [Warning] 'proxies_priv' entry '@% root@alepo-db2-ilb' ignored in --skip-name-resolve mode. 2024-05-10 12:35:21 3 [Note] Reading Master_info: 'master-s@002ddb3.info' Relay_info:'relay-log-s@002ddb3.info' 2024-05-10 12:35:21 3 [Note] Initialized Master_info from 'master-s@002ddb3.info' 2024-05-10 12:35:21 4 [Note] Master 's-db3': Slave I/O thread: Start asynchronous replication to master '@:3306' in log '' at position 4 2024-05-10 12:35:21 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 2024-05-10 12:35:21 4 [Note] Master 's-db3': Slave I/O thread killed while connecting to master 2024-05-10 12:35:21 4 [Note] Master 's-db3': Slave I/O thread exiting, read up to log 'FIRST', position 4, master :3306 2024-05-10 12:35:21 3 [Note] Started replication for 's-db3' 2024-05-10 12:35:21 5 [Note] Master 's-db3': Slave SQL thread initialized, starting replication in log 'FIRST' at position 0, relay log './db1-relay-s@002ddb3.000019' position: 4 2024-05-10 12:35:21 3 [Note] Reading Master_info: 'master-s@002ddb4.info' Relay_info:'relay-log-s@002ddb4.info' 2024-05-10 12:35:21 3 [Note] Initialized Master_info from 'master-s@002ddb4.info' 2024-05-10 12:35:21 18 [Note] Master 's-db4': Slave I/O thread: Start asynchronous replication to master 'gtid@10.76.25.11:3306' in log 'db4-binary.104833' at position 102025635 2024-05-10 12:35:21 3 [Note] Started replication for 's-db4' 2024-05-10 12:35:21 3 [Note] Reading Master_info: 'master-s@002ddb2.info' Relay_info:'relay-log-s@002ddb2.info' 2024-05-10 12:35:21 19 [Note] Master 's-db4': Slave SQL thread initialized, starting replication in log 'db4-binary.104833' at position 102025635, relay log './db1-relay-s@002ddb4.051527' position: 783 2024-05-10 12:35:21 18 [Note] Master 's-db4': Slave I/O thread: connected to master 'gtid@10.76.25.11:3306',replication started in log 'db4-binary.104833' at position 102025635 2024-05-10 12:35:21 3 [Note] Initialized Master_info from 'master-s@002ddb2.info' 2024-05-10 12:35:21 20 [Note] Master 's-db2': Slave I/O thread: Start asynchronous replication to master '@:3306' in log '' at position 4 2024-05-10 12:35:21 20 [ERROR] Master 's-db2': Slave I/O: Fatal error: Invalid (empty) username when attempting to connect to the master server. Connection attempt terminated. Internal MariaDB error code: 1593 2024-05-10 12:35:21 20 [Note] Master 's-db2': Slave I/O thread killed while connecting to master 2024-05-10 12:35:21 20 [Note] Master 's-db2': Slave I/O thread exiting, read up to log 'FIRST', position 4, master :3306 2024-05-10 12:35:21 3 [Note] Started replication for 's-db2' 2024-05-10 12:35:21 21 [Note] Master 's-db2': Slave SQL thread initialized, starting replication in log 'FIRST' at position 0, relay log './db1-relay-s@002ddb2.000018' position: 4 2024-05-10 12:35:21 3 [Note] Reading Master_info: 'master-s@002ddb5.info' Relay_info:'relay-log-s@002ddb5.info' 2024-05-10 12:35:21 3 [Note] Initialized Master_info from 'master-s@002ddb5.info' 2024-05-10 12:35:21 22 [Note] Master 's-db5': Slave I/O thread: Start asynchronous replication to master '@:3306' in log '' at position 4 2024-05-10 12:35:21 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 2024-05-10 12:35:21 22 [Note] Master 's-db5': Slave I/O thread killed while connecting to master 2024-05-10 12:35:21 22 [Note] Master 's-db5': Slave I/O thread exiting, read up to log 'FIRST', position 4, master :3306 2024-05-10 12:35:21 3 [Note] Started replication for 's-db5' 2024-05-10 12:35:21 23 [Note] Master 's-db5': Slave SQL thread initialized, starting replication in log 'FIRST' at position 0, relay log './db1-relay-s@002ddb5.000010' position: 4 2024-05-10 12:35:21 25 [Note] Slave I/O thread: Start asynchronous replication to master 'gtid@10.76.24.77:3306' in log 'db2-binary.128969' at position 176894185 2024-05-10 12:35:21 0 [Note] /usr/sbin/mariadbd: ready for connections. Version: '10.11.5-MariaDB-log' socket: '/var/lib/mysql/mysql.sock' port: 3306 MariaDB Server 2024-05-10 12:35:21 26 [Note] Slave SQL thread initialized, starting replication in log 'db2-binary.128969' at position 176894185, relay log './db1-relay.059861' position: 767 2024-05-10 12:35:21 25 [Note] Slave I/O thread: connected to master 'gtid@10.76.24.77:3306',replication started in log 'db2-binary.128969' at position 176894185 2024-05-10 12:35:22 0 [Note] InnoDB: Buffer pool(s) load completed at 240510 12:35:22 2024-05-10 12:35:57 2311 [Note] Start binlog_dump to slave_server(3), pos(db1-binary.128269, 99030825), using_gtid(0), gtid('') 2024-05-10 12:35:57 2312 [Note] Start binlog_dump to slave_server(2), pos(db1-binary.128269, 99030825), using_gtid(0), gtid('') 2024-05-10 12:35:57 2315 [Note] Start binlog_dump to slave_server(4), pos(db1-binary.128269, 99030825), using_gtid(0), gtid('') 2024-05-17 1:26:14 2311 [Warning] Aborted connection 2311 to db: 'unconnected' user: 'gtid' host: '10.76.24.83' (Got an error writing communication packets) 2024-05-17 1:26:14 18952591 [Note] Start binlog_dump to slave_server(3), pos(db1-binary.132821, 149731022), using_gtid(0), gtid('') 2024-05-17 1:26:31 18952591 [Warning] Aborted connection 18952591 to db: 'unconnected' user: 'gtid' host: '10.76.24.83' (Got an error writing communication packets) 2024-05-17 1:26:31 18952855 [Note] Start binlog_dump to slave_server(3), pos(db1-binary.132821, 175375297), using_gtid(0), gtid('') 2024-05-17 1:26:38 18952855 [Warning] Aborted connection 18952855 to db: 'unconnected' user: 'gtid' host: '10.76.24.83' (Got an error writing communication packets) 2024-05-17 1:26:38 18952968 [Note] Start binlog_dump to slave_server(3), pos(db1-binary.132821, 186177133), using_gtid(0), gtid('') 2024-05-17 1:26:45 18952968 [Warning] Aborted connection 18952968 to db: 'unconnected' user: 'gtid' host: '10.76.24.83' (Got an error writing communication packets) 2024-05-17 1:26:45 18953071 [Note] Start binlog_dump to slave_server(3), pos(db1-binary.132821, 196443556), using_gtid(0), gtid('') 2024-05-17 1:26:51 18953071 [Warning] Aborted connection 18953071 to db: 'unconnected' user: 'gtid' host: '10.76.24.83' (Got an error writing communication packets) 2024-05-17 1:26:51 18953167 [Note] Start binlog_dump to slave_server(3), pos(db1-binary.132821, 205687497), using_gtid(0), gtid('') 2024-05-17 1:26:53 18953167 [Warning] Aborted connection 18953167 to db: 'unconnected' user: 'gtid' host: '10.76.24.83' (Got an error writing communication packets) 2024-05-17 1:26:53 18953202 [Note] Start binlog_dump to slave_server(3), pos(db1-binary.132821, 208942224), using_gtid(0), gtid('') 2024-05-17 1:32:08 18953202 [Warning] Aborted connection 18953202 to db: 'unconnected' user: 'gtid' host: '10.76.24.83' (Got an error writing communication packets) 2024-05-17 1:32:08 18958109 [Note] Start binlog_dump to slave_server(3), pos(db1-binary.132824, 60877245), using_gtid(0), gtid('') 2024-05-17 1:32:15 18958109 [Warning] Aborted connection 18958109 to db: 'unconnected' user: 'gtid' host: '10.76.24.83' (Got an error writing communication packets) 2024-05-17 1:32:15 18958234 [Note] Start binlog_dump to slave_server(3), pos(db1-binary.132824, 73091028), using_gtid(0), gtid('') 2024-05-17 1:33:14 18958234 [Warning] Aborted connection 18958234 to db: 'unconnected' user: 'gtid' host: '10.76.24.83' (Got an error writing communication packets) 2024-05-17 1:33:15 18959209 [Note] Start binlog_dump to slave_server(3), pos(db1-binary.132824, 169059896), using_gtid(0), gtid('') 2024-05-17 1:49:33 18959209 [Warning] Aborted connection 18959209 to db: 'unconnected' user: 'gtid' host: '10.76.24.83' (Got an error writing communication packets) 2024-05-17 1:49:33 18974697 [Note] Start binlog_dump to slave_server(3), pos(db1-binary.132832, 14427106), using_gtid(0), gtid('') 2024-05-17 1:49:48 18974697 [Warning] Aborted connection 18974697 to db: 'unconnected' user: 'gtid' host: '10.76.24.83' (Got an error writing communication packets) 2024-05-17 1:49:48 18974949 [Note] Start binlog_dump to slave_server(3), pos(db1-binary.132832, 38872019), using_gtid(0), gtid('') 2024-05-17 1:49:56 18974949 [Warning] Aborted connection 18974949 to db: 'unconnected' user: 'gtid' host: '10.76.24.83' (Got an error writing communication packets) 2024-05-17 1:49:56 18975067 [Note] Start binlog_dump to slave_server(3), pos(db1-binary.132832, 50530241), using_gtid(0), gtid('') 2024-05-17 1:50:01 18975067 [Warning] Aborted connection 18975067 to db: 'unconnected' user: 'gtid' host: '10.76.24.83' (Got an error writing communication packets) 2024-05-17 1:50:01 18975150 [Note] Start binlog_dump to slave_server(3), pos(db1-binary.132832, 58497920), using_gtid(0), gtid('') 2024-05-17 1:50:06 18975150 [Warning] Aborted connection 18975150 to db: 'unconnected' user: 'gtid' host: '10.76.24.83' (Got an error writing communication packets) 2024-05-17 1:50:06 18975227 [Note] Start binlog_dump to slave_server(3), pos(db1-binary.132832, 65848598), using_gtid(0), gtid('') 2024-05-17 1:50:13 18975227 [Warning] Aborted connection 18975227 to db: 'unconnected' user: 'gtid' host: '10.76.24.83' (Got an error writing communication packets) 2024-05-17 1:50:13 18975335 [Note] Start binlog_dump to slave_server(3), pos(db1-binary.132832, 76445463), using_gtid(0), gtid('') 2024-05-17 1:50:22 18975335 [Warning] Aborted connection 18975335 to db: 'unconnected' user: 'gtid' host: '10.76.24.83' (Got an error writing communication packets) 2024-05-17 1:50:22 18975479 [Note] Start binlog_dump to slave_server(3), pos(db1-binary.132832, 90450473), using_gtid(0), gtid('') 2024-05-17 1:50:24 18975479 [Warning] Aborted connection 18975479 to db: 'unconnected' user: 'gtid' host: '10.76.24.83' (Got an error writing communication packets) 2024-05-17 1:50:24 18975509 [Note] Start binlog_dump to slave_server(3), pos(db1-binary.132832, 93144490), using_gtid(0), gtid('') 2024-05-17 1:50:26 18975509 [Warning] Aborted connection 18975509 to db: 'unconnected' user: 'gtid' host: '10.76.24.83' (Got an error writing communication packets) 2024-05-17 1:50:26 18975537 [Note] Start binlog_dump to slave_server(3), pos(db1-binary.132832, 95805653), using_gtid(0), gtid('') 2024-05-17 1:50:34 18975537 [Warning] Aborted connection 18975537 to db: 'unconnected' user: 'gtid' host: '10.76.24.83' (Got an error writing communication packets) 2024-05-17 1:50:34 18975663 [Note] Start binlog_dump to slave_server(3), pos(db1-binary.132832, 108012713), using_gtid(0), gtid('') 2024-05-17 1:50:37 18975663 [Warning] Aborted connection 18975663 to db: 'unconnected' user: 'gtid' host: '10.76.24.83' (Got an error writing communication packets) 2024-05-17 1:50:37 18975712 [Note] Start binlog_dump to slave_server(3), pos(db1-binary.132832, 112694751), using_gtid(0), gtid('') 2024-05-17 1:57:37 18975712 [Warning] Aborted connection 18975712 to db: 'unconnected' user: 'gtid' host: '10.76.24.83' (Got an error writing communication packets) 2024-05-17 1:58:08 18982648 [Warning] Access denied for user 'replication'@'10.76.24.83' (using password: YES) 2024-05-17 1:59:08 18983573 [Warning] Access denied for user 'replication'@'10.76.24.83' (using password: YES) 2024-05-17 2:00:08 18984571 [Warning] Access denied for user 'replication'@'10.76.24.83' (using password: YES) 2024-05-17 2:01:08 18985523 [Warning] Access denied for user 'replication'@'10.76.24.83' (using password: YES) 2024-05-17 2:02:08 18986577 [Warning] Access denied for user 'replication'@'10.76.24.83' (using password: YES) 2024-05-17 2:03:02 18987516 [Note] Start binlog_dump to slave_server(3), pos(db1-binary.132831, 54590798), using_gtid(0), gtid('') 2024-05-17 2:03:59 18987516 [Warning] Aborted connection 18987516 to db: 'unconnected' user: 'replication' host: '10.76.24.83' (Got an error writing communication packets) 2024-05-17 2:04:09 18988631 [Note] Start binlog_dump to slave_server(3), pos(db1-binary.132831, 54704890), using_gtid(0), gtid('') 2024-05-17 2:05:09 18988631 [Warning] Aborted connection 18988631 to db: 'unconnected' user: 'replication' host: '10.76.24.83' (Got an error writing communication packets) 2024-05-17 2:05:15 18989719 [Warning] Access denied for user 'gtid'@'10.76.24.83' (using password: YES) 2024-05-17 2:06:15 18990679 [Warning] Access denied for user 'gtid'@'10.76.24.83' (using password: YES) 2024-05-17 2:06:45 18991126 [Note] Start binlog_dump to slave_server(3), pos(db1-binary.132831, 54704890), using_gtid(0), gtid('') 2024-05-17 2:11:03 18991126 [Warning] Aborted connection 18991126 to db: 'unconnected' user: 'replication' host: '10.76.24.83' (Got an error writing communication packets) 2024-05-17 2:13:13 18997065 [Note] Start binlog_dump to slave_server(3), pos(db1-binary.132843, 16733654), using_gtid(0), gtid('') 2024-05-17 2:13:32 18997364 [Note] Start binlog_dump to slave_server(3), pos(db1-binary.132844, 2583412), using_gtid(0), gtid('') 2024-05-17 2:13:32 18997065 [Warning] Aborted connection 18997065 to db: 'unconnected' user: 'replication' host: '10.76.24.83' (A slave with the same server_uuid/server_id as this slave has co) 2024-05-17 2:13:37 18997442 [Note] Start binlog_dump to slave_server(3), pos(db1-binary.132844, 10004721), using_gtid(0), gtid('') 2024-05-17 2:13:37 18997364 [Warning] Aborted connection 18997364 to db: 'unconnected' user: 'replication' host: '10.76.24.83' (A slave with the same server_uuid/server_id as this slave has co) 2024-05-17 2:13:40 18997442 [Warning] Aborted connection 18997442 to db: 'unconnected' user: 'replication' host: '10.76.24.83' (Got an error writing communication packets) 2024-05-17 2:13:40 18997499 [Note] Start binlog_dump to slave_server(3), pos(db1-binary.132844, 15538427), using_gtid(0), gtid('') 2024-05-17 2:13:44 18997499 [Warning] Aborted connection 18997499 to db: 'unconnected' user: 'replication' host: '10.76.24.83' (Got an error writing communication packets) 2024-05-17 2:13:44 18997560 [Note] Start binlog_dump to slave_server(3), pos(db1-binary.132844, 21619245), using_gtid(0), gtid('') 2024-05-17 2:13:49 18997560 [Warning] Aborted connection 18997560 to db: 'unconnected' user: 'replication' host: '10.76.24.83' (Got an error writing communication packets) 2024-05-17 2:13:49 18997628 [Note] Start binlog_dump to slave_server(3), pos(db1-binary.132844, 28163840), using_gtid(0), gtid('') 2024-05-17 2:13:52 18997628 [Warning] Aborted connection 18997628 to db: 'unconnected' user: 'replication' host: '10.76.24.83' (Got an error writing communication packets) 2024-05-17 2:13:52 18997683 [Note] Start binlog_dump to slave_server(3), pos(db1-binary.132844, 33434186), using_gtid(0), gtid('') 2024-05-17 2:13:56 18997683 [Warning] Aborted connection 18997683 to db: 'unconnected' user: 'replication' host: '10.76.24.83' (Got an error writing communication packets) 2024-05-17 2:13:56 18997754 [Note] Start binlog_dump to slave_server(3), pos(db1-binary.132844, 40358421), using_gtid(0), gtid('') 2024-05-17 3:21:37 18997754 [Warning] Aborted connection 18997754 to db: 'unconnected' user: 'replication' host: '10.76.24.83' (Got an error writing communication packets) 2024-05-17 3:21:37 19060918 [Note] Start binlog_dump to slave_server(3), pos(db1-binary.132873, 170049136), using_gtid(0), gtid('') 2024-05-17 3:21:42 19060918 [Warning] Aborted connection 19060918 to db: 'unconnected' user: 'replication' host: '10.76.24.83' (Got an error writing communication packets) 2024-05-17 3:21:42 19060994 [Note] Start binlog_dump to slave_server(3), pos(db1-binary.132873, 177487064), using_gtid(0), gtid('') 2024-05-17 3:21:48 19060994 [Warning] Aborted connection 19060994 to db: 'unconnected' user: 'replication' host: '10.76.24.83' (Got an error writing communication packets) 2024-05-17 3:21:48 19061084 [Note] Start binlog_dump to slave_server(3), pos(db1-binary.132873, 186203764), using_gtid(0), gtid('') 2024-05-17 3:52:57 19061084 [Warning] Aborted connection 19061084 to db: 'unconnected' user: 'replication' host: '10.76.24.83' (Got an error writing communication packets) 2024-05-17 3:52:57 19089801 [Note] Start binlog_dump to slave_server(3), pos(db1-binary.132887, 76954285), using_gtid(0), gtid('') 2024-05-17 9:56:30 25 [ERROR] Error reading packet from server: Lost connection to server during query (server_errno=2013) 2024-05-17 9:56:30 25 [Note] Slave I/O thread: Failed reading log event, reconnecting to retry, log 'db2-binary.133751' at position 83821920 2024-05-17 9:56:30 25 [ERROR] Slave I/O: error reconnecting to master 'gtid@10.76.24.77:3306' - retry-time: 60 maximum-retries: 100000 message: Can't connect to server on '10.76.24.77' (111 "Connection refused"), Internal MariaDB error code: 2003 2024-05-17 9:56:42 2312 [Warning] Aborted connection 2312 to db: 'unconnected' user: 'gtid' host: '10.76.24.77' (Got an error writing communication packets) 2024-05-17 9:56:53 19451067 [Note] Start binlog_dump to slave_server(2), pos(db1-binary.133054, 145348386), using_gtid(0), gtid('') 2024-05-17 9:57:30 25 [Note] Slave: connected to master 'gtid@10.76.24.77:3306',replication resumed in log 'db2-binary.133751' at position 83821920 2024-05-17 10:47:43 19089801 [Warning] Aborted connection 19089801 to db: 'unconnected' user: 'replication' host: '10.76.24.83' (Got an error writing communication packets) 2024-05-17 10:47:43 19490972 [Note] Start binlog_dump to slave_server(3), pos(db1-binary.133080, 102347549), using_gtid(0), gtid('') 2024-05-17 10:47:53 19490972 [Warning] Aborted connection 19490972 to db: 'unconnected' user: 'replication' host: '10.76.24.83' (Got an error writing communication packets) 2024-05-17 10:47:53 19491116 [Note] Start binlog_dump to slave_server(3), pos(db1-binary.133080, 123722095), using_gtid(0), gtid('') 2024-05-17 10:48:04 19491116 [Warning] Aborted connection 19491116 to db: 'unconnected' user: 'replication' host: '10.76.24.83' (Got an error writing communication packets) 2024-05-17 10:48:04 19491264 [Note] Start binlog_dump to slave_server(3), pos(db1-binary.133080, 144467206), using_gtid(0), gtid('') 2024-05-17 10:48:15 19491264 [Warning] Aborted connection 19491264 to db: 'unconnected' user: 'replication' host: '10.76.24.83' (Got an error writing communication packets) 2024-05-17 10:48:15 19491417 [Note] Start binlog_dump to slave_server(3), pos(db1-binary.133080, 166456177), using_gtid(0), gtid('') 2024-05-17 10:48:24 19491417 [Warning] Aborted connection 19491417 to db: 'unconnected' user: 'replication' host: '10.76.24.83' (Got an error writing communication packets) 2024-05-17 10:48:24 19491533 [Note] Start binlog_dump to slave_server(3), pos(db1-binary.133080, 182759146), using_gtid(0), gtid('') 2024-05-17 10:48:27 19491533 [Warning] Aborted connection 19491533 to db: 'unconnected' user: 'replication' host: '10.76.24.83' (Got an error writing communication packets) 2024-05-17 10:48:27 19491578 [Note] Start binlog_dump to slave_server(3), pos(db1-binary.133080, 188695438), using_gtid(0), gtid('') 2024-05-17 10:48:29 19491578 [Warning] Aborted connection 19491578 to db: 'unconnected' user: 'replication' host: '10.76.24.83' (Got an error writing communication packets) 2024-05-17 10:48:29 19491605 [Note] Start binlog_dump to slave_server(3), pos(db1-binary.133080, 192526789), using_gtid(0), gtid('') 2024-05-17 10:48:30 19491605 [Warning] Aborted connection 19491605 to db: 'unconnected' user: 'replication' host: '10.76.24.83' (Got an error writing communication packets) 2024-05-17 10:48:31 19491626 [Note] Start binlog_dump to slave_server(3), pos(db1-binary.133080, 195375842), using_gtid(0), gtid('') 2024-05-17 10:48:32 19491626 [Warning] Aborted connection 19491626 to db: 'unconnected' user: 'replication' host: '10.76.24.83' (Got an error writing communication packets) 2024-05-17 10:48:32 19491648 [Note] Start binlog_dump to slave_server(3), pos(db1-binary.133080, 198285624), using_gtid(0), gtid('') 2024-05-17 10:48:33 19491648 [Warning] Aborted connection 19491648 to db: 'unconnected' user: 'replication' host: '10.76.24.83' (Got an error writing communication packets) 2024-05-17 10:48:33 19491665 [Note] Start binlog_dump to slave_server(3), pos(db1-binary.133080, 200662866), using_gtid(0), gtid('') 2024-05-17 10:48:34 19491665 [Warning] Aborted connection 19491665 to db: 'unconnected' user: 'replication' host: '10.76.24.83' (Got an error writing communication packets) 2024-05-17 10:48:35 19491686 [Note] Start binlog_dump to slave_server(3), pos(db1-binary.133080, 202977455), using_gtid(0), gtid('') 2024-05-17 10:48:36 19491686 [Warning] Aborted connection 19491686 to db: 'unconnected' user: 'replication' host: '10.76.24.83' (Got an error writing communication packets) 2024-05-17 10:48:36 19491702 [Note] Start binlog_dump to slave_server(3), pos(db1-binary.133080, 205450165), using_gtid(0), gtid('') 2024-05-17 10:48:37 19491702 [Warning] Aborted connection 19491702 to db: 'unconnected' user: 'replication' host: '10.76.24.83' (Got an error writing communication packets) 2024-05-17 10:48:37 19491720 [Note] Start binlog_dump to slave_server(3), pos(db1-binary.133080, 207645027), using_gtid(0), gtid('') 2024-05-17 10:48:38 19491720 [Warning] Aborted connection 19491720 to db: 'unconnected' user: 'replication' host: '10.76.24.83' (Got an error writing communication packets) 2024-05-17 10:48:38 19491736 [Note] Start binlog_dump to slave_server(3), pos(db1-binary.133081, 415063), using_gtid(0), gtid('') 2024-05-17 10:48:39 19491753 [Note] Start binlog_dump to slave_server(3), pos(db1-binary.133081, 2562556), using_gtid(0), gtid('') 2024-05-17 10:48:41 19491753 [Warning] Aborted connection 19491753 to db: 'unconnected' user: 'replication' host: '10.76.24.83' (Got an error writing communication packets) 2024-05-17 10:48:41 19491769 [Note] Start binlog_dump to slave_server(3), pos(db1-binary.133081, 4783907), using_gtid(0), gtid('') 2024-05-17 10:48:42 19491769 [Warning] Aborted connection 19491769 to db: 'unconnected' user: 'replication' host: '10.76.24.83' (Got an error writing communication packets) 2024-05-17 10:48:42 19491787 [Note] Start binlog_dump to slave_server(3), pos(db1-binary.133081, 7111458), using_gtid(0), gtid('') 2024-05-17 10:48:43 19491787 [Warning] Aborted connection 19491787 to db: 'unconnected' user: 'replication' host: '10.76.24.83' (Got an error writing communication packets) 2024-05-17 10:48:43 19491802 [Note] Start binlog_dump to slave_server(3), pos(db1-binary.133081, 9489026), using_gtid(0), gtid('') 2024-05-17 10:48:52 19491802 [Warning] Aborted connection 19491802 to db: 'unconnected' user: 'replication' host: '10.76.24.83' (Got an error writing communication packets) 2024-05-17 10:48:52 19491917 [Note] Start binlog_dump to slave_server(3), pos(db1-binary.133081, 25973705), using_gtid(0), gtid('') 2024-05-17 10:48:54 19491917 [Warning] Aborted connection 19491917 to db: 'unconnected' user: 'replication' host: '10.76.24.83' (Got an error writing communication packets) 2024-05-17 10:48:54 19491942 [Note] Start binlog_dump to slave_server(3), pos(db1-binary.133081, 29764096), using_gtid(0), gtid('') 2024-05-17 10:48:55 19491942 [Warning] Aborted connection 19491942 to db: 'unconnected' user: 'replication' host: '10.76.24.83' (Got an error writing communication packets) 2024-05-17 10:48:55 19491966 [Note] Start binlog_dump to slave_server(3), pos(db1-binary.133081, 32628113), using_gtid(0), gtid('') 2024-05-17 10:48:57 19491966 [Warning] Aborted connection 19491966 to db: 'unconnected' user: 'replication' host: '10.76.24.83' (Got an error writing communication packets) 2024-05-17 10:48:57 19491984 [Note] Start binlog_dump to slave_server(3), pos(db1-binary.133081, 35134560), using_gtid(0), gtid('') 2024-05-17 10:48:58 19491984 [Warning] Aborted connection 19491984 to db: 'unconnected' user: 'replication' host: '10.76.24.83' (Got an error writing communication packets) 2024-05-17 10:48:58 19492000 [Note] Start binlog_dump to slave_server(3), pos(db1-binary.133081, 37382349), using_gtid(0), gtid('') 2024-05-17 10:48:59 19492000 [Warning] Aborted connection 19492000 to db: 'unconnected' user: 'replication' host: '10.76.24.83' (Got an error writing communication packets) 2024-05-17 10:48:59 19492017 [Note] Start binlog_dump to slave_server(3), pos(db1-binary.133081, 39730823), using_gtid(0), gtid('') 2024-05-17 10:49:01 19492017 [Warning] Aborted connection 19492017 to db: 'unconnected' user: 'replication' host: '10.76.24.83' (Got an error writing communication packets) 2024-05-17 10:49:01 19492035 [Note] Start binlog_dump to slave_server(3), pos(db1-binary.133081, 42201438), using_gtid(0), gtid('') 2024-05-17 10:49:02 19492035 [Warning] Aborted connection 19492035 to db: 'unconnected' user: 'replication' host: '10.76.24.83' (Got an error writing communication packets) 2024-05-17 10:49:02 19492053 [Note] Start binlog_dump to slave_server(3), pos(db1-binary.133081, 44555680), using_gtid(0), gtid('') 2024-05-17 10:49:04 19492053 [Warning] Aborted connection 19492053 to db: 'unconnected' user: 'replication' host: '10.76.24.83' (Got an error writing communication packets) 2024-05-17 10:49:04 19492076 [Note] Start binlog_dump to slave_server(3), pos(db1-binary.133081, 47756799), using_gtid(0), gtid('') 2024-05-17 10:49:05 19492076 [Warning] Aborted connection 19492076 to db: 'unconnected' user: 'replication' host: '10.76.24.83' (Got an error writing communication packets) 2024-05-17 10:49:05 19492093 [Note] Start binlog_dump to slave_server(3), pos(db1-binary.133081, 49904494), using_gtid(0), gtid('') 2024-05-17 10:49:06 19492093 [Warning] Aborted connection 19492093 to db: 'unconnected' user: 'replication' host: '10.76.24.83' (Got an error writing communication packets) 2024-05-17 10:49:06 19492107 [Note] Start binlog_dump to slave_server(3), pos(db1-binary.133081, 51904097), using_gtid(0), gtid('') 2024-05-17 10:49:07 19492107 [Warning] Aborted connection 19492107 to db: 'unconnected' user: 'replication' host: '10.76.24.83' (Got an error writing communication packets) 2024-05-17 10:49:07 19492122 [Note] Start binlog_dump to slave_server(3), pos(db1-binary.133081, 53763855), using_gtid(0), gtid('') 2024-05-17 10:49:08 19492122 [Warning] Aborted connection 19492122 to db: 'unconnected' user: 'replication' host: '10.76.24.83' (Got an error writing communication packets) 2024-05-17 10:49:08 19492136 [Note] Start binlog_dump to slave_server(3), pos(db1-binary.133081, 55564131), using_gtid(0), gtid('') 2024-05-17 10:49:09 19492136 [Warning] Aborted connection 19492136 to db: 'unconnected' user: 'replication' host: '10.76.24.83' (Got an error writing communication packets) 2024-05-17 10:49:09 19492152 [Note] Start binlog_dump to slave_server(3), pos(db1-binary.133081, 57879528), using_gtid(0), gtid('') 2024-05-17 10:49:10 19492152 [Warning] Aborted connection 19492152 to db: 'unconnected' user: 'replication' host: '10.76.24.83' (Got an error writing communication packets) 2024-05-17 10:49:10 19492170 [Note] Start binlog_dump to slave_server(3), pos(db1-binary.133081, 60086950), using_gtid(0), gtid('') 2024-05-17 10:49:11 19492170 [Warning] Aborted connection 19492170 to db: 'unconnected' user: 'replication' host: '10.76.24.83' (Got an error writing communication packets) 2024-05-17 10:49:11 19492185 [Note] Start binlog_dump to slave_server(3), pos(db1-binary.133081, 62004957), using_gtid(0), gtid('') 2024-05-17 10:49:12 19492185 [Warning] Aborted connection 19492185 to db: 'unconnected' user: 'replication' host: '10.76.24.83' (Got an error writing communication packets) 2024-05-17 10:49:12 19492199 [Note] Start binlog_dump to slave_server(3), pos(db1-binary.133081, 64082929), using_gtid(0), gtid('') 2024-05-17 10:49:13 19492199 [Warning] Aborted connection 19492199 to db: 'unconnected' user: 'replication' host: '10.76.24.83' (Got an error writing communication packets) 2024-05-17 10:49:13 19492213 [Note] Start binlog_dump to slave_server(3), pos(db1-binary.133081, 65933913), using_gtid(0), gtid('') 2024-05-17 10:49:14 19492213 [Warning] Aborted connection 19492213 to db: 'unconnected' user: 'replication' host: '10.76.24.83' (Got an error writing communication packets) 2024-05-17 10:49:14 19492231 [Note] Start binlog_dump to slave_server(3), pos(db1-binary.133081, 68021558), using_gtid(0), gtid('') 2024-05-17 10:49:16 19492231 [Warning] Aborted connection 19492231 to db: 'unconnected' user: 'replication' host: '10.76.24.83' (Got an error writing communication packets) 2024-05-17 10:49:16 19492247 [Note] Start binlog_dump to slave_server(3), pos(db1-binary.133081, 70256625), using_gtid(0), gtid('') 2024-05-17 10:49:17 19492247 [Warning] Aborted connection 19492247 to db: 'unconnected' user: 'replication' host: '10.76.24.83' (Got an error writing communication packets) 2024-05-17 10:49:17 19492262 [Note] Start binlog_dump to slave_server(3), pos(db1-binary.133081, 72165862), using_gtid(0), gtid('') 2024-05-17 10:49:18 19492262 [Warning] Aborted connection 19492262 to db: 'unconnected' user: 'replication' host: '10.76.24.83' (Got an error writing communication packets) 2024-05-17 10:49:18 19492277 [Note] Start binlog_dump to slave_server(3), pos(db1-binary.133081, 73978084), using_gtid(0), gtid('') 2024-05-17 10:49:19 19492277 [Warning] Aborted connection 19492277 to db: 'unconnected' user: 'replication' host: '10.76.24.83' (Got an error writing communication packets) 2024-05-17 10:49:19 19492292 [Note] Start binlog_dump to slave_server(3), pos(db1-binary.133081, 75815194), using_gtid(0), gtid('') 2024-05-17 10:49:20 19492292 [Warning] Aborted connection 19492292 to db: 'unconnected' user: 'replication' host: '10.76.24.83' (Got an error writing communication packets) 2024-05-17 10:49:20 19492307 [Note] Start binlog_dump to slave_server(3), pos(db1-binary.133081, 77550140), using_gtid(0), gtid('') 2024-05-17 10:49:21 19492307 [Warning] Aborted connection 19492307 to db: 'unconnected' user: 'replication' host: '10.76.24.83' (Got an error writing communication packets) 2024-05-17 10:49:21 19492320 [Note] Start binlog_dump to slave_server(3), pos(db1-binary.133081, 79306135), using_gtid(0), gtid('') 2024-05-17 10:49:22 19492320 [Warning] Aborted connection 19492320 to db: 'unconnected' user: 'replication' host: '10.76.24.83' (Got an error writing communication packets) 2024-05-17 10:49:22 19492334 [Note] Start binlog_dump to slave_server(3), pos(db1-binary.133081, 80993267), using_gtid(0), gtid('') 2024-05-17 10:49:23 19492334 [Warning] Aborted connection 19492334 to db: 'unconnected' user: 'replication' host: '10.76.24.83' (Got an error writing communication packets) 2024-05-17 10:49:23 19492348 [Note] Start binlog_dump to slave_server(3), pos(db1-binary.133081, 82815122), using_gtid(0), gtid('') 2024-05-17 10:49:24 19492348 [Warning] Aborted connection 19492348 to db: 'unconnected' user: 'replication' host: '10.76.24.83' (Got an error writing communication packets) 2024-05-17 10:49:24 19492363 [Note] Start binlog_dump to slave_server(3), pos(db1-binary.133081, 84737042), using_gtid(0), gtid('') 2024-05-17 10:49:25 19492363 [Warning] Aborted connection 19492363 to db: 'unconnected' user: 'replication' host: '10.76.24.83' (Got an error writing communication packets) 2024-05-17 10:49:25 19492379 [Note] Start binlog_dump to slave_server(3), pos(db1-binary.133081, 86530845), using_gtid(0), gtid('') 2024-05-17 10:49:26 19492379 [Warning] Aborted connection 19492379 to db: 'unconnected' user: 'replication' host: '10.76.24.83' (Got an error writing communication packets) 2024-05-17 10:49:26 19492394 [Note] Start binlog_dump to slave_server(3), pos(db1-binary.133081, 88251708), using_gtid(0), gtid('') 2024-05-17 10:49:28 19492394 [Warning] Aborted connection 19492394 to db: 'unconnected' user: 'replication' host: '10.76.24.83' (Got an error writing communication packets) 2024-05-17 10:49:28 19492425 [Note] Start binlog_dump to slave_server(3), pos(db1-binary.133081, 92472081), using_gtid(0), gtid('') 2024-05-17 10:49:29 19492425 [Warning] Aborted connection 19492425 to db: 'unconnected' user: 'replication' host: '10.76.24.83' (Got an error writing communication packets) 2024-05-17 10:49:29 19492440 [Note] Start binlog_dump to slave_server(3), pos(db1-binary.133081, 94481998), using_gtid(0), gtid('') 2024-05-17 10:49:30 19492440 [Warning] Aborted connection 19492440 to db: 'unconnected' user: 'replication' host: '10.76.24.83' (Got an error writing communication packets) 2024-05-17 10:49:30 19492455 [Note] Start binlog_dump to slave_server(3), pos(db1-binary.133081, 96409145), using_gtid(0), gtid('') 2024-05-17 10:49:31 19492455 [Warning] Aborted connection 19492455 to db: 'unconnected' user: 'replication' host: '10.76.24.83' (Got an error writing communication packets) 2024-05-17 10:49:31 19492469 [Note] Start binlog_dump to slave_server(3), pos(db1-binary.133081, 98109646), using_gtid(0), gtid('') 2024-05-17 10:49:32 19492469 [Warning] Aborted connection 19492469 to db: 'unconnected' user: 'replication' host: '10.76.24.83' (Got an error writing communication packets) 2024-05-17 10:49:32 19492484 [Note] Start binlog_dump to slave_server(3), pos(db1-binary.133081, 99997493), using_gtid(0), gtid('') 2024-05-17 10:49:33 19492484 [Warning] Aborted connection 19492484 to db: 'unconnected' user: 'replication' host: '10.76.24.83' (Got an error writing communication packets) 2024-05-17 10:49:33 19492502 [Note] Start binlog_dump to slave_server(3), pos(db1-binary.133081, 102388263), using_gtid(0), gtid('') 2024-05-17 10:49:35 19492502 [Warning] Aborted connection 19492502 to db: 'unconnected' user: 'replication' host: '10.76.24.83' (Got an error writing communication packets) 2024-05-17 10:49:35 19492521 [Note] Start binlog_dump to slave_server(3), pos(db1-binary.133081, 104548938), using_gtid(0), gtid('') 2024-05-17 10:50:04 19492521 [Warning] Aborted connection 19492521 to db: 'unconnected' user: 'replication' host: '10.76.24.83' (Got an error writing communication packets) 2024-05-17 10:50:04 19492907 [Note] Start binlog_dump to slave_server(3), pos(db1-binary.133081, 156077036), using_gtid(0), gtid('') 2024-05-17 10:50:16 19492907 [Warning] Aborted connection 19492907 to db: 'unconnected' user: 'replication' host: '10.76.24.83' (Got an error writing communication packets) 2024-05-17 10:50:16 19493074 [Note] Start binlog_dump to slave_server(3), pos(db1-binary.133081, 177578288), using_gtid(0), gtid('') 2024-05-17 10:50:25 19493074 [Warning] Aborted connection 19493074 to db: 'unconnected' user: 'replication' host: '10.76.24.83' (Got an error writing communication packets) 2024-05-17 10:50:25 19493190 [Note] Start binlog_dump to slave_server(3), pos(db1-binary.133081, 192530205), using_gtid(0), gtid('') 2024-05-17 10:50:27 19493190 [Warning] Aborted connection 19493190 to db: 'unconnected' user: 'replication' host: '10.76.24.83' (Got an error writing communication packets) 2024-05-17 10:50:27 19493212 [Note] Start binlog_dump to slave_server(3), pos(db1-binary.133081, 195742783), using_gtid(0), gtid('') 2024-05-17 10:50:28 19493212 [Warning] Aborted connection 19493212 to db: 'unconnected' user: 'replication' host: '10.76.24.83' (Got an error writing communication packets) 2024-05-17 10:50:28 19493229 [Note] Start binlog_dump to slave_server(3), pos(db1-binary.133081, 197760500), using_gtid(0), gtid('') 2024-05-17 10:50:29 19493229 [Warning] Aborted connection 19493229 to db: 'unconnected' user: 'replication' host: '10.76.24.83' (Got an error writing communication packets) 2024-05-17 10:50:29 19493244 [Note] Start binlog_dump to slave_server(3), pos(db1-binary.133081, 199631585), using_gtid(0), gtid('') 2024-05-17 10:50:30 19493244 [Warning] Aborted connection 19493244 to db: 'unconnected' user: 'replication' host: '10.76.24.83' (Got an error writing communication packets) 2024-05-17 10:50:30 19493260 [Note] Start binlog_dump to slave_server(3), pos(db1-binary.133081, 201502863), using_gtid(0), gtid('') 2024-05-17 10:50:31 19493260 [Warning] Aborted connection 19493260 to db: 'unconnected' user: 'replication' host: '10.76.24.83' (Got an error writing communication packets) 2024-05-17 10:50:31 19493276 [Note] Start binlog_dump to slave_server(3), pos(db1-binary.133081, 203569093), using_gtid(0), gtid('') 2024-05-17 10:50:32 19493276 [Warning] Aborted connection 19493276 to db: 'unconnected' user: 'replication' host: '10.76.24.83' (Got an error writing communication packets) 2024-05-17 10:50:32 19493291 [Note] Start binlog_dump to slave_server(3), pos(db1-binary.133081, 205409588), using_gtid(0), gtid('') 2024-05-17 10:50:34 19493291 [Warning] Aborted connection 19493291 to db: 'unconnected' user: 'replication' host: '10.76.24.83' (Got an error writing communication packets) 2024-05-17 10:50:34 19493307 [Note] Start binlog_dump to slave_server(3), pos(db1-binary.133081, 207592727), using_gtid(0), gtid('') 2024-05-17 10:50:35 19493307 [Warning] Aborted connection 19493307 to db: 'unconnected' user: 'replication' host: '10.76.24.83' (Got an error writing communication packets) 2024-05-17 10:50:35 19493328 [Note] Start binlog_dump to slave_server(3), pos(db1-binary.133082, 58591), using_gtid(0), gtid('') 2024-05-17 10:50:36 19493328 [Warning] Aborted connection 19493328 to db: 'unconnected' user: 'replication' host: '10.76.24.83' (Got an error writing communication packets) 2024-05-17 10:50:36 19493343 [Note] Start binlog_dump to slave_server(3), pos(db1-binary.133082, 2186644), using_gtid(0), gtid('') 2024-05-17 10:50:38 19493343 [Warning] Aborted connection 19493343 to db: 'unconnected' user: 'replication' host: '10.76.24.83' (Got an error writing communication packets) 2024-05-17 10:50:38 19493369 [Note] Start binlog_dump to slave_server(3), pos(db1-binary.133082, 5552971), using_gtid(0), gtid('') 2024-05-17 10:50:40 19493369 [Warning] Aborted connection 19493369 to db: 'unconnected' user: 'replication' host: '10.76.24.83' (Got an error writing communication packets) 2024-05-17 10:50:40 19493395 [Note] Start binlog_dump to slave_server(3), pos(db1-binary.133082, 8972649), using_gtid(0), gtid('') 2024-05-17 10:50:41 19493395 [Warning] Aborted connection 19493395 to db: 'unconnected' user: 'replication' host: '10.76.24.83' (Got an error writing communication packets) 2024-05-17 10:50:41 19493413 [Note] Start binlog_dump to slave_server(3), pos(db1-binary.133082, 11465411), using_gtid(0), gtid('') 2024-05-17 10:50:43 19493413 [Warning] Aborted connection 19493413 to db: 'unconnected' user: 'replication' host: '10.76.24.83' (Got an error writing communication packets) 2024-05-17 10:50:43 19493432 [Note] Start binlog_dump to slave_server(3), pos(db1-binary.133082, 13878890), using_gtid(0), gtid('') 2024-05-17 10:50:50 19493432 [Warning] Aborted connection 19493432 to db: 'unconnected' user: 'replication' host: '10.76.24.83' (Got an error writing communication packets) 2024-05-17 10:50:50 19493526 [Note] Start binlog_dump to slave_server(3), pos(db1-binary.133082, 25780704), using_gtid(0), gtid('') 2024-05-17 10:50:51 19493526 [Warning] Aborted connection 19493526 to db: 'unconnected' user: 'replication' host: '10.76.24.83' (Got an error writing communication packets) 2024-05-17 10:50:51 19493546 [Note] Start binlog_dump to slave_server(3), pos(db1-binary.133082, 28502639), using_gtid(0), gtid('') 2024-05-17 10:50:53 19493546 [Warning] Aborted connection 19493546 to db: 'unconnected' user: 'replication' host: '10.76.24.83' (Got an error writing communication packets) 2024-05-17 10:50:53 19493573 [Note] Start binlog_dump to slave_server(3), pos(db1-binary.133082, 31800953), using_gtid(0), gtid('') 2024-05-17 10:50:55 19493573 [Warning] Aborted connection 19493573 to db: 'unconnected' user: 'replication' host: '10.76.24.83' (Got an error writing communication packets) 2024-05-17 10:50:55 19493598 [Note] Start binlog_dump to slave_server(3), pos(db1-binary.133082, 34857168), using_gtid(0), gtid('') 2024-05-17 10:50:56 19493598 [Warning] Aborted connection 19493598 to db: 'unconnected' user: 'replication' host: '10.76.24.83' (Got an error writing communication packets) 2024-05-17 10:50:56 19493618 [Note] Start binlog_dump to slave_server(3), pos(db1-binary.133082, 37257118), using_gtid(0), gtid('') 2024-05-17 10:51:02 19493618 [Warning] Aborted connection 19493618 to db: 'unconnected' user: 'replication' host: '10.76.24.83' (Got an error writing communication packets) 2024-05-17 10:51:02 19493691 [Note] Start binlog_dump to slave_server(3), pos(db1-binary.133082, 46660928), using_gtid(0), gtid('') 2024-05-17 10:51:04 19493691 [Warning] Aborted connection 19493691 to db: 'unconnected' user: 'replication' host: '10.76.24.83' (Got an error writing communication packets) 2024-05-17 10:51:04 19493727 [Note] Start binlog_dump to slave_server(3), pos(db1-binary.133082, 51371980), using_gtid(0), gtid('') 2024-05-17 10:51:06 19493727 [Warning] Aborted connection 19493727 to db: 'unconnected' user: 'replication' host: '10.76.24.83' (Got an error writing communication packets) 2024-05-17 10:51:07 19493758 [Note] Start binlog_dump to slave_server(3), pos(db1-binary.133082, 55300047), using_gtid(0), gtid('') 2024-05-17 10:54:55 19493758 [Warning] Aborted connection 19493758 to db: 'unconnected' user: 'replication' host: '10.76.24.83' (Got an error writing communication packets) 2024-05-17 10:54:55 19496689 [Note] Start binlog_dump to slave_server(3), pos(db1-binary.133084, 27180265), using_gtid(0), gtid('') 2024-05-17 10:58:06 19496689 [Warning] Aborted connection 19496689 to db: 'unconnected' user: 'replication' host: '10.76.24.83' (Got an error writing communication packets) 2024-05-17 10:58:06 19499131 [Note] Start binlog_dump to slave_server(3), pos(db1-binary.133085, 143493904), using_gtid(0), gtid('') 2024-05-17 10:58:13 19499131 [Warning] Aborted connection 19499131 to db: 'unconnected' user: 'replication' host: '10.76.24.83' (Got an error writing communication packets) 2024-05-17 10:58:13 19499216 [Note] Start binlog_dump to slave_server(3), pos(db1-binary.133085, 154728081), using_gtid(0), gtid('') 2024-05-17 12:50:12 19499216 [Warning] Aborted connection 19499216 to db: 'unconnected' user: 'replication' host: '10.76.24.83' (Got an error writing communication packets) 2024-05-17 12:51:01 19589785 [Note] Start binlog_dump to slave_server(3), pos(db1-binary.132844, 4), using_gtid(0), gtid('') 2024-05-17 12:51:31 19589785 [Warning] Aborted connection 19589785 to db: 'unconnected' user: 'replication' host: '10.76.24.83' (Got an error writing communication packets) 2024-05-17 12:51:31 19590148 [Note] Start binlog_dump to slave_server(3), pos(db1-binary.132860, 174469842), using_gtid(0), gtid('') 2024-05-17 12:51:40 19590148 [Warning] Aborted connection 19590148 to db: 'unconnected' user: 'replication' host: '10.76.24.83' (Got an error writing communication packets) 2024-05-17 12:51:40 19590263 [Note] Start binlog_dump to slave_server(3), pos(db1-binary.132866, 25884693), using_gtid(0), gtid('') 2024-05-17 12:51:44 19590263 [Warning] Aborted connection 19590263 to db: 'unconnected' user: 'replication' host: '10.76.24.83' (Got an error writing communication packets) 2024-05-17 12:51:44 19590313 [Note] Start binlog_dump to slave_server(3), pos(db1-binary.132868, 90836514), using_gtid(0), gtid('') 2024-05-17 12:51:45 19590313 [Warning] Aborted connection 19590313 to db: 'unconnected' user: 'replication' host: '10.76.24.83' (Got an error writing communication packets) 2024-05-17 12:51:45 19590331 [Note] Start binlog_dump to slave_server(3), pos(db1-binary.132869, 14034187), using_gtid(0), gtid('') 2024-05-17 12:51:46 19590331 [Warning] Aborted connection 19590331 to db: 'unconnected' user: 'replication' host: '10.76.24.83' (Got an error writing communication packets) 2024-05-17 12:51:46 19590346 [Note] Start binlog_dump to slave_server(3), pos(db1-binary.132869, 158265583), using_gtid(0), gtid('') 2024-05-17 13:41:21 2315 [Warning] Aborted connection 2315 to db: 'unconnected' user: 'gtid' host: '10.76.25.11' (Got an error writing communication packets) 2024-05-17 13:41:28 19628830 [Note] Start binlog_dump to slave_server(4), pos(db1-binary.133169, 159491702), using_gtid(0), gtid('') 2024-05-17 13:58:51 19628830 [Warning] Aborted connection 19628830 to db: 'unconnected' user: 'gtid' host: '10.76.25.11' (Got an error writing communication packets) 2024-05-17 13:59:33 19643161 [Note] Start binlog_dump to slave_server(4), pos(db1-binary.132813, 47378079), using_gtid(0), gtid('') 2024-05-17 14:08:32 19590346 [Warning] Aborted connection 19590346 to db: 'unconnected' user: 'replication' host: '10.76.24.83' (Got an error writing communication packets) 2024-05-17 14:08:43 19669801 [Note] Start binlog_dump to slave_server(3), pos(db1-binary.132813, 47378079), using_gtid(0), gtid('') 2024-05-17 15:01:29 19643161 [Warning] Aborted connection 19643161 to db: 'unconnected' user: 'gtid' host: '10.76.25.11' (Got an error writing communication packets) 2024-05-17 15:01:53 19845231 [Note] Start binlog_dump to slave_server(4), pos(db1-binary.133210, 174203207), using_gtid(0), gtid('') 2024-05-25 0:39:55 35965720 [Warning] Aborted connection 35965720 to db: 'aaadb' user: 'alepoaaaems' host: '10.76.24.67' (Got an error reading communication packets) 2024-05-25 0:39:55 35964712 [Warning] Aborted connection 35964712 to db: 'aaadb' user: 'alepoaaaems' host: '10.76.24.67' (Got an error reading communication packets) 2024-05-25 0:39:55 35940993 [Warning] Aborted connection 35940993 to db: 'aaadb' user: 'alepoaaaems' host: '10.76.24.67' (Got an error reading communication packets) 2024-05-25 0:39:55 35977679 [Warning] Aborted connection 35977679 to db: 'aaadb' user: 'alepoaaaems' host: '10.76.24.67' (Got an error reading communication packets) 2024-05-25 0:43:36 35980287 [Warning] Aborted connection 35980287 to db: 'aaadb' user: 'alepoaaaems' host: '10.76.24.74' (Got an error reading communication packets) 2024-05-25 0:43:36 35981512 [Warning] Aborted connection 35981512 to db: 'aaadb' user: 'alepoaaaems' host: '10.76.24.74' (Got an error reading communication packets) 2024-05-25 0:43:36 35963376 [Warning] Aborted connection 35963376 to db: 'aaadb' user: 'alepoaaaems' host: '10.76.24.74' (Got an error reading communication packets) 2024-05-25 0:43:36 35981508 [Warning] Aborted connection 35981508 to db: 'aaadb' user: 'alepoaaaems' host: '10.76.24.74' (Got an error reading communication packets) 2024-05-25 0:43:36 35979421 [Warning] Aborted connection 35979421 to db: 'aaadb' user: 'alepoaaaems' host: '10.76.24.74' (Got an error reading communication packets) 2024-05-25 1:10:48 35980027 [Warning] Aborted connection 35980027 to db: 'aaadb' user: 'alepoaaaems' host: '10.76.24.67' (Got timeout reading communication packets) 2024-05-25 1:14:25 35984853 [Warning] Aborted connection 35984853 to db: 'aaadb' user: 'alepoaaaems' host: '10.76.24.74' (Got timeout reading communication packets) 240527 10:35:05 [ERROR] mysqld got signal 11 ; 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.11.5-MariaDB-log source revision: 7875294b6b74b53dd3aaa723e6cc103d2bb47b2c key_buffer_size=67108864 read_buffer_size=131072 max_used_connections=459 max_threads=802 thread_count=475 It is possible that mysqld could use up to key_buffer_size + (read_buffer_size + sort_buffer_size)*max_threads = 1831964 K bytes of memory Hope that's ok; if not, decrease some variables in the equation. Thread pointer: 0x7f7388018fb8 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 = 0x7f75b6bc7b98 thread_stack 0x49000 /usr/sbin/mariadbd(my_print_stacktrace+0x2e)[0x5626c568e12e] mysys/stacktrace.c:216(my_print_stacktrace)[0x5626c51875b5] /lib64/libpthread.so.0(+0x12cf0)[0x7fc4bc46bcf0] sql/sql_yacc.yy:9072(MYSQLparse(THD*))[0x5626c510d117] sql/sql_parse.cc:10394(parse_sql(THD*, Parser_state*, Object_creation_ctx*, bool))[0x5626c4f3d81a] sql/sql_parse.cc:7988(mysql_parse(THD*, char*, unsigned int, Parser_state*))[0x5626c4f39a1a] sql/sql_parse.cc:1896(dispatch_command(enum_server_command, THD*, char*, unsigned int, bool))[0x5626c4f436e6] sql/sql_parse.cc:1407(do_command(THD*, bool))[0x5626c4f44dab] sql/sql_connect.cc:1416(do_handle_one_connection(CONNECT*, bool))[0x5626c5058977] sql/sql_connect.cc:1318(handle_one_connection)[0x5626c5058cbd] perfschema/pfs.cc:2204(MyCTX_nopad::finish(unsigned char*, unsigned int*))[0x5626c538ec9d] /lib64/libpthread.so.0(+0x81ca)[0x7fc4bc4611ca] /lib64/libc.so.6(clone+0x43)[0x7fc4bb7b1e73] Trying to get some variables. Some pointers may be invalid and cause the dump to abort. Query (0x7f7388028e30): Select Users.UserIndex, UserID, Users.Password, GroupName, PasswordSource, UserService, UserIP, FilterName, UserActive, Users.StartDate, UserExpiryDate, CallBackNumber, CallerID, Lockout, Users.PasswordEncryptionMethod, MaxUserSessions, SkipPasswordCheck, HotlineStatus, BarringStatus, BarringReason, MaxVolumeCap, AllowedAccessTypes, CopyRadiusRequests, SubnetIP, SubnetMask, CIDR, CustomField1, CustomField2, CustomField3, CustomField4, CustomField5, CustomNumField1, CustomNumField2, CustomNumField3, CustomNumField4, CustomNumField5, SessionLimit, UserTokens, FirstLogon, FramedInterfaceId, FramedIPv6Prefix, PeriodicTimeUsage, PeriodicVolumeUsage, TimeUsageTriggerThresholds, VolumeUsageTriggerThresholds, CustomReplylist, CustomChecklist, BillingSystemCorrelationId, ChargingSystemCorrelationId, ChargingMode, LockOutTime, LockOutCount, Users.PseudoIdentity, CustomDate1, CustomDate2, CustomDate3, CustomDate4, CustomDate5, CustomField6, CustomField7, CustomField8, CustomField9, CustomField10, RestrictedLocations, MaxTimeCap, PortId, CustomNumField6, CustomNumField7, CustomNumField8, CustomNumField9, CustomNumField10,SpeedMapName,UserIPv6,NetworkService, CustomField11,CustomField12,CustomField13,CustomField14,CustomField15 , PasswordDate From Users Where UserID = '3465951024' Connection ID (thread ID): 35961824 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,hash_join_cardinality=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 unlimited unlimited bytes Max resident set unlimited unlimited bytes Max processes 2061710 2061710 processes Max open files 32768 32768 files Max locked memory 65536 65536 bytes Max address space unlimited unlimited bytes Max file locks unlimited unlimited locks Max pending signals 2061710 2061710 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: /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 2024-05-27 10:35:58 0 [Note] Starting MariaDB 10.11.5-MariaDB-log source revision 7875294b6b74b53dd3aaa723e6cc103d2bb47b2c as process 493517 2024-05-27 10:35:58 0 [Note] InnoDB: Compressed tables use zlib 1.2.11 2024-05-27 10:35:58 0 [Note] InnoDB: Number of transaction pools: 1 2024-05-27 10:35:58 0 [Note] InnoDB: Using crc32 + pclmulqdq instructions 2024-05-27 10:35:58 0 [Note] InnoDB: Using Linux native AIO 2024-05-27 10:35:58 0 [Note] InnoDB: Initializing buffer pool, total size = 300.000GiB, chunk size = 4.688GiB 2024-05-27 10:35:58 0 [Note] InnoDB: Completed initialization of buffer pool 2024-05-27 10:35:59 0 [Note] InnoDB: File system buffers for log disabled (block size=512 bytes) 2024-05-27 10:36:00 0 [Note] InnoDB: Starting crash recovery from checkpoint LSN=32490856668794 2024-05-27 10:36:02 0 [Note] InnoDB: End of log at LSN=32491099054573 2024-05-27 10:36:02 0 [Note] InnoDB: Transaction 103339873294 was in the XA prepared state. 2024-05-27 10:36:02 0 [Note] InnoDB: 1 transaction(s) which must be rolled back or cleaned up in total 0 row operations to undo 2024-05-27 10:36:02 0 [Note] InnoDB: Trx id counter is 103339873302 2024-05-27 10:36:02 0 [Note] InnoDB: To recover: 159700 pages 2024-05-27 10:36:07 0 [Note] InnoDB: Last binlog file './db1-binary.140171', position 201024989 2024-05-27 10:36:07 0 [Note] InnoDB: 128 rollback segments are active. 2024-05-27 10:36:08 0 [Note] InnoDB: Starting in background the rollback of recovered transactions 2024-05-27 10:36:08 0 [Note] InnoDB: Rollback of non-prepared transactions completed 2024-05-27 10:36:08 0 [Note] InnoDB: Removed temporary tablespace data file: "./ibtmp1" 2024-05-27 10:36:08 0 [Note] InnoDB: Setting file './ibtmp1' size to 12.000MiB. Physically writing the file full; Please wait ... 2024-05-27 10:36:08 0 [Note] InnoDB: File './ibtmp1' size is now 12.000MiB. 2024-05-27 10:36:08 0 [Note] InnoDB: log sequence number 32491099054573; transaction id 103339873303 2024-05-27 10:36:08 0 [Note] InnoDB: Loading buffer pool(s) from /var/lib/mysql/ib_buffer_pool 2024-05-27 10:36:08 0 [Note] Plugin 'FEEDBACK' is disabled. 2024-05-27 10:36:08 0 [Warning] 'thread-concurrency' was removed. It does nothing now and exists only for compatibility with old my.cnf files. 2024-05-27 10:36:08 0 [Warning] 'innodb-thread-concurrency' was removed. It does nothing now and exists only for compatibility with old my.cnf files. 2024-05-27 10:36:08 0 [Warning] 'innodb-log-files-in-group' was removed. It does nothing now and exists only for compatibility with old my.cnf files. 2024-05-27 10:36:08 0 [Note] Recovering after a crash using db1-binary 2024-05-27 10:36:08 0 [Note] Starting table crash recovery... 2024-05-27 10:36:08 0 [Note] InnoDB: Starting recovery for XA transactions... 2024-05-27 10:36:08 0 [Note] InnoDB: Transaction 103339873294 in prepared state after recovery 2024-05-27 10:36:08 0 [Note] InnoDB: Transaction contains changes to 1 rows 2024-05-27 10:36:08 0 [Note] InnoDB: 1 transactions in prepared state after recovery 2024-05-27 10:36:08 0 [Note] Found 1 prepared transaction(s) in InnoDB 2024-05-27 10:36:08 0 [Note] Crash table recovery finished. 2024-05-27 10:36:08 0 [Note] Server socket created on IP: '0.0.0.0'. 2024-05-27 10:36:08 0 [Note] Server socket created on IP: '::'. 2024-05-27 10:36:08 0 [Warning] 'user' entry '@alepo-db2-ilb' ignored in --skip-name-resolve mode. 2024-05-27 10:36:08 0 [Warning] 'user' entry 'root@localhost.localdomain' ignored in --skip-name-resolve mode. 2024-05-27 10:36:08 0 [Warning] 'proxies_priv' entry '@% root@alepo-db2-ilb' ignored in --skip-name-resolve mode. 2024-05-27 10:36:08 3 [Note] Reading Master_info: 'master-s@002ddb3.info' Relay_info:'relay-log-s@002ddb3.info' 2024-05-27 10:36:08 3 [Note] Initialized Master_info from 'master-s@002ddb3.info' 2024-05-27 10:36:08 4 [Note] Master 's-db3': Slave I/O thread: Start asynchronous replication to master '@:3306' in log '' at position 4 2024-05-27 10:36:08 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 2024-05-27 10:36:08 4 [Note] Master 's-db3': Slave I/O thread killed while connecting to master 2024-05-27 10:36:08 4 [Note] Master 's-db3': Slave I/O thread exiting, read up to log 'FIRST', position 4, master :3306 2024-05-27 10:36:08 3 [Note] Started replication for 's-db3' 2024-05-27 10:36:08 5 [Note] Master 's-db3': Slave SQL thread initialized, starting replication in log 'FIRST' at position 0, relay log './db1-relay-s@002ddb3.000019' position: 4 2024-05-27 10:36:08 3 [Note] Reading Master_info: 'master-s@002ddb4.info' Relay_info:'relay-log-s@002ddb4.info' 2024-05-27 10:36:08 3 [Note] Initialized Master_info from 'master-s@002ddb4.info' 2024-05-27 10:36:08 18 [Note] Master 's-db4': Slave I/O thread: Start asynchronous replication to master 'gtid@10.76.25.11:3306' in log 'db4-binary.116734' at position 126843791 2024-05-27 10:36:08 3 [Note] Started replication for 's-db4' 2024-05-27 10:36:08 3 [Note] Reading Master_info: 'master-s@002ddb2.info' Relay_info:'relay-log-s@002ddb2.info' 2024-05-27 10:36:08 19 [Note] Master 's-db4': Slave SQL thread initialized, starting replication in log 'db4-binary.116734' at position 126843791, relay log './db1-relay-s@002ddb4.075333' position: 783 2024-05-27 10:36:08 3 [Note] Initialized Master_info from 'master-s@002ddb2.info' 2024-05-27 10:36:08 20 [Note] Master 's-db2': Slave I/O thread: Start asynchronous replication to master '@:3306' in log '' at position 4 2024-05-27 10:36:08 20 [ERROR] Master 's-db2': Slave I/O: Fatal error: Invalid (empty) username when attempting to connect to the master server. Connection attempt terminated. Internal MariaDB error code: 1593 2024-05-27 10:36:08 20 [Note] Master 's-db2': Slave I/O thread killed while connecting to master 2024-05-27 10:36:08 20 [Note] Master 's-db2': Slave I/O thread exiting, read up to log 'FIRST', position 4, master :3306 2024-05-27 10:36:08 3 [Note] Started replication for 's-db2' 2024-05-27 10:36:08 3 [Note] Reading Master_info: 'master-s@002ddb5.info' Relay_info:'relay-log-s@002ddb5.info' 2024-05-27 10:36:08 21 [Note] Master 's-db2': Slave SQL thread initialized, starting replication in log 'FIRST' at position 0, relay log './db1-relay-s@002ddb2.000018' position: 4 2024-05-27 10:36:08 18 [Note] Master 's-db4': Slave I/O thread: connected to master 'gtid@10.76.25.11:3306',replication started in log 'db4-binary.116734' at position 126843791 2024-05-27 10:36:08 3 [Note] Initialized Master_info from 'master-s@002ddb5.info' 2024-05-27 10:36:08 22 [Note] Master 's-db5': Slave I/O thread: Start asynchronous replication to master '@:3306' in log '' at position 4 2024-05-27 10:36:08 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 2024-05-27 10:36:08 22 [Note] Master 's-db5': Slave I/O thread killed while connecting to master 2024-05-27 10:36:08 22 [Note] Master 's-db5': Slave I/O thread exiting, read up to log 'FIRST', position 4, master :3306 2024-05-27 10:36:08 3 [Note] Started replication for 's-db5' 2024-05-27 10:36:08 23 [Note] Master 's-db5': Slave SQL thread initialized, starting replication in log 'FIRST' at position 0, relay log './db1-relay-s@002ddb5.000010' position: 4 2024-05-27 10:36:08 25 [Note] Slave I/O thread: Start asynchronous replication to master 'gtid@10.76.24.77:3306' in log 'db2-binary.140871' at position 167553202 2024-05-27 10:36:08 0 [Note] /usr/sbin/mariadbd: ready for connections. Version: '10.11.5-MariaDB-log' socket: '/var/lib/mysql/mysql.sock' port: 3306 MariaDB Server 2024-05-27 10:36:08 26 [Note] Slave SQL thread initialized, starting replication in log 'db2-binary.140871' at position 4, relay log './db1-relay.098010' position: 304 2024-05-27 10:36:08 25 [Note] Slave I/O thread: connected to master 'gtid@10.76.24.77:3306',replication started in log 'db2-binary.140871' at position 167553202 2024-05-27 10:36:08 11 [Note] Detected table cache mutex contention at instance 1: 81% waits. Additional table cache instance activated. Number of instances after activation: 2. 2024-05-27 10:36:09 0 [Note] InnoDB: Buffer pool(s) load completed at 240527 10:36:09 2024-05-27 10:36:38 1217 [Note] Start binlog_dump to slave_server(2), pos(db1-binary.140171, 201093528), using_gtid(0), gtid('') 2024-05-27 10:36:38 1218 [Note] Start binlog_dump to slave_server(3), pos(db1-binary.140171, 201093528), using_gtid(0), gtid('') 2024-05-27 10:36:38 1223 [Note] Start binlog_dump to slave_server(4), pos(db1-binary.140171, 201093528), using_gtid(0), gtid('') 2024-06-01 2:00:02 1217 [Warning] Aborted connection 1217 to db: 'unconnected' user: 'gtid' host: '10.76.24.77' (Got an error writing communication packets) 2024-06-01 2:00:02 9076828 [Note] Start binlog_dump to slave_server(2), pos(db1-binary.143513, 113565358), using_gtid(0), gtid('') 2024-06-08 14:11:16 18 [ERROR] Master 's-db4': Slave I/O: Replication event checksum verification failed while reading from network, Internal MariaDB error code: 1743 2024-06-08 14:11:16 18 [ERROR] Master 's-db4': Slave I/O: Relay log write failure: could not queue event from master, Internal MariaDB error code: 1595 2024-06-08 14:11:16 18 [Note] Master 's-db4': Slave I/O thread exiting, read up to log 'db4-binary.125316', position 148106186, master 10.76.25.11:3306 2024-06-10 18:34:10 25 [ERROR] Error reading packet from server: Lost connection to server during query (server_errno=2013) 2024-06-10 18:34:10 25 [Note] Slave I/O thread: Failed reading log event, reconnecting to retry, log 'db2-binary.150974' at position 49920304 2024-06-10 18:34:10 25 [ERROR] Slave I/O: error reconnecting to master 'gtid@10.76.24.77:3306' - retry-time: 60 maximum-retries: 100000 message: Can't connect to server on '10.76.24.77' (111 "Connection refused"), Internal MariaDB error code: 2003 2024-06-10 18:34:15 9076828 [Warning] Aborted connection 9076828 to db: 'unconnected' user: 'gtid' host: '10.76.24.77' (Got an error writing communication packets) 2024-06-10 18:35:56 31570250 [Note] Start binlog_dump to slave_server(2), pos(db1-binary.150278, 71915770), using_gtid(0), gtid('') 2024-06-10 18:36:10 25 [Note] Slave: connected to master 'gtid@10.76.24.77:3306',replication resumed in log 'db2-binary.150974' at position 49920304 2024-06-11 0:20:31 31668323 [Warning] Aborted connection 31668323 to db: 'aaadb' user: 'alepoaaa' host: '10.76.24.87' (Got an error reading communication packets) 2024-06-11 0:20:31 31570080 [Warning] Aborted connection 31570080 to db: 'aaadb' user: 'alepoaaa' host: '10.76.24.87' (Got an error reading communication packets) 2024-06-11 0:20:31 31570079 [Warning] Aborted connection 31570079 to db: 'aaadb' user: 'alepoaaa' host: '10.76.24.87' (Got an error reading communication packets) 2024-06-11 0:20:31 31570078 [Warning] Aborted connection 31570078 to db: 'aaadb' user: 'alepoaaa' host: '10.76.24.87' (Got an error reading communication packets) 2024-06-11 0:20:31 31570077 [Warning] Aborted connection 31570077 to db: 'aaadb' user: 'alepoaaa' host: '10.76.24.87' (Got an error reading communication packets) 2024-06-11 0:20:31 31570075 [Warning] Aborted connection 31570075 to db: 'aaadb' user: 'alepoaaa' host: '10.76.24.87' (Got an error reading communication packets) 2024-06-11 0:20:31 31570076 [Warning] Aborted connection 31570076 to db: 'aaadb' user: 'alepoaaa' host: '10.76.24.87' (Got an error reading communication packets) 2024-06-11 0:20:31 31570074 [Warning] Aborted connection 31570074 to db: 'aaadb' user: 'alepoaaa' host: '10.76.24.87' (Got an error reading communication packets) 2024-06-11 0:20:31 31570073 [Warning] Aborted connection 31570073 to db: 'aaadb' user: 'alepoaaa' host: '10.76.24.87' (Got an error reading communication packets) 2024-06-11 0:20:31 31668321 [Warning] Aborted connection 31668321 to db: 'aaadb' user: 'alepoaaa' host: '10.76.24.87' (Got an error reading communication packets) 2024-06-11 0:20:31 31570071 [Warning] Aborted connection 31570071 to db: 'aaadb' user: 'alepoaaa' host: '10.76.24.87' (Got an error reading communication packets) 2024-06-11 0:20:31 31570070 [Warning] Aborted connection 31570070 to db: 'aaadb' user: 'alepoaaa' host: '10.76.24.87' (Got an error reading communication packets) 2024-06-11 0:20:31 31570072 [Warning] Aborted connection 31570072 to db: 'aaadb' user: 'alepoaaa' host: '10.76.24.87' (Got an error reading communication packets) 2024-06-11 0:20:31 31570069 [Warning] Aborted connection 31570069 to db: 'aaadb' user: 'alepoaaa' host: '10.76.24.87' (Got an error reading communication packets) 2024-06-11 0:20:31 31570068 [Warning] Aborted connection 31570068 to db: 'aaadb' user: 'alepoaaa' host: '10.76.24.87' (Got an error reading communication packets) 2024-06-11 0:20:31 31668320 [Warning] Aborted connection 31668320 to db: 'aaadb' user: 'alepoaaa' host: '10.76.24.87' (Got an error reading communication packets) 2024-06-11 0:20:31 31570067 [Warning] Aborted connection 31570067 to db: 'aaadb' user: 'alepoaaa' host: '10.76.24.87' (Got an error reading communication packets) 2024-06-11 0:20:31 31570066 [Warning] Aborted connection 31570066 to db: 'aaadb' user: 'alepoaaa' host: '10.76.24.87' (Got an error reading communication packets) 2024-06-11 0:20:31 31570065 [Warning] Aborted connection 31570065 to db: 'aaadb' user: 'alepoaaa' host: '10.76.24.87' (Got an error reading communication packets) 2024-06-11 0:20:31 31570063 [Warning] Aborted connection 31570063 to db: 'aaadb' user: 'alepoaaa' host: '10.76.24.87' (Got an error reading communication packets) 2024-06-11 0:20:31 31570064 [Warning] Aborted connection 31570064 to db: 'aaadb' user: 'alepoaaa' host: '10.76.24.87' (Got an error reading communication packets) 2024-06-11 0:20:31 31570060 [Warning] Aborted connection 31570060 to db: 'aaadb' user: 'alepoaaa' host: '10.76.24.87' (Got an error reading communication packets) 2024-06-11 0:20:31 31668322 [Warning] Aborted connection 31668322 to db: 'aaadb' user: 'alepoaaa' host: '10.76.24.87' (Got an error reading communication packets) 2024-06-11 0:20:31 31570062 [Warning] Aborted connection 31570062 to db: 'aaadb' user: 'alepoaaa' host: '10.76.24.87' (Got an error reading communication packets) 2024-06-11 0:20:31 31570061 [Warning] Aborted connection 31570061 to db: 'aaadb' user: 'alepoaaa' host: '10.76.24.87' (Got an error reading communication packets) 2024-06-11 0:20:31 31570059 [Warning] Aborted connection 31570059 to db: 'aaadb' user: 'alepoaaa' host: '10.76.24.87' (Got an error reading communication packets) 2024-06-11 0:20:31 31570058 [Warning] Aborted connection 31570058 to db: 'aaadb' user: 'alepoaaa' host: '10.76.24.87' (Got an error reading communication packets) 2024-06-11 0:20:31 31570055 [Warning] Aborted connection 31570055 to db: 'aaadb' user: 'alepoaaa' host: '10.76.24.87' (Got an error reading communication packets) 2024-06-11 0:20:31 31570057 [Warning] Aborted connection 31570057 to db: 'aaadb' user: 'alepoaaa' host: '10.76.24.87' (Got an error reading communication packets) 2024-06-11 0:20:31 31570054 [Warning] Aborted connection 31570054 to db: 'aaadb' user: 'alepoaaa' host: '10.76.24.87' (Got an error reading communication packets) 2024-06-11 0:20:31 31570053 [Warning] Aborted connection 31570053 to db: 'aaadb' user: 'alepoaaa' host: '10.76.24.87' (Got an error reading communication packets) 2024-06-11 0:20:31 31570052 [Warning] Aborted connection 31570052 to db: 'aaadb' user: 'alepoaaa' host: '10.76.24.87' (Got an error reading communication packets) 2024-06-11 0:20:31 31570050 [Warning] Aborted connection 31570050 to db: 'aaadb' user: 'alepoaaa' host: '10.76.24.87' (Got an error reading communication packets) 2024-06-11 0:20:31 31570051 [Warning] Aborted connection 31570051 to db: 'aaadb' user: 'alepoaaa' host: '10.76.24.87' (Got an error reading communication packets) 2024-06-11 0:20:31 31570056 [Warning] Aborted connection 31570056 to db: 'aaadb' user: 'alepoaaa' host: '10.76.24.87' (Got an error reading communication packets) 2024-06-11 0:20:31 31570048 [Warning] Aborted connection 31570048 to db: 'aaadb' user: 'alepoaaa' host: '10.76.24.87' (Got an error reading communication packets) 2024-06-11 0:20:31 31570047 [Warning] Aborted connection 31570047 to db: 'aaadb' user: 'alepoaaa' host: '10.76.24.87' (Got an error reading communication packets) 2024-06-11 0:20:31 31570045 [Warning] Aborted connection 31570045 to db: 'aaadb' user: 'alepoaaa' host: '10.76.24.87' (Got an error reading communication packets) 2024-06-11 0:20:31 31570044 [Warning] Aborted connection 31570044 to db: 'aaadb' user: 'alepoaaa' host: '10.76.24.87' (Got an error reading communication packets) 2024-06-11 0:20:31 31570046 [Warning] Aborted connection 31570046 to db: 'aaadb' user: 'alepoaaa' host: '10.76.24.87' (Got an error reading communication packets) 2024-06-11 0:20:31 31570043 [Warning] Aborted connection 31570043 to db: 'aaadb' user: 'alepoaaa' host: '10.76.24.87' (Got an error reading communication packets) 2024-06-11 0:20:31 31570041 [Warning] Aborted connection 31570041 to db: 'aaadb' user: 'alepoaaa' host: '10.76.24.87' (Got an error reading communication packets) 2024-06-11 0:20:31 31570042 [Warning] Aborted connection 31570042 to db: 'aaadb' user: 'alepoaaa' host: '10.76.24.87' (Got an error reading communication packets) 2024-06-11 0:20:31 31570040 [Warning] Aborted connection 31570040 to db: 'aaadb' user: 'alepoaaa' host: '10.76.24.87' (Got an error reading communication packets) 2024-06-11 0:20:31 31570038 [Warning] Aborted connection 31570038 to db: 'aaadb' user: 'alepoaaa' host: '10.76.24.87' (Got an error reading communication packets) 2024-06-11 0:20:31 31570037 [Warning] Aborted connection 31570037 to db: 'aaadb' user: 'alepoaaa' host: '10.76.24.87' (Got an error reading communication packets) 2024-06-11 0:20:31 31570036 [Warning] Aborted connection 31570036 to db: 'aaadb' user: 'alepoaaa' host: '10.76.24.87' (Got an error reading communication packets) 2024-06-11 0:20:31 31570035 [Warning] Aborted connection 31570035 to db: 'aaadb' user: 'alepoaaa' host: '10.76.24.87' (Got an error reading communication packets) 2024-06-11 0:20:31 31570033 [Warning] Aborted connection 31570033 to db: 'aaadb' user: 'alepoaaa' host: '10.76.24.87' (Got an error reading communication packets) 2024-06-11 0:20:31 31570034 [Warning] Aborted connection 31570034 to db: 'aaadb' user: 'alepoaaa' host: '10.76.24.87' (Got an error reading communication packets) 2024-06-11 0:20:31 31570032 [Warning] Aborted connection 31570032 to db: 'aaadb' user: 'alepoaaa' host: '10.76.24.87' (Got an error reading communication packets) 2024-06-11 0:20:31 31570031 [Warning] Aborted connection 31570031 to db: 'aaadb' user: 'alepoaaa' host: '10.76.24.87' (Got an error reading communication packets) 2024-06-11 0:20:31 31570039 [Warning] Aborted connection 31570039 to db: 'aaadb' user: 'alepoaaa' host: '10.76.24.87' (Got an error reading communication packets) 2024-06-11 0:20:31 31570030 [Warning] Aborted connection 31570030 to db: 'aaadb' user: 'alepoaaa' host: '10.76.24.87' (Got an error reading communication packets) 2024-06-11 0:20:31 31570029 [Warning] Aborted connection 31570029 to db: 'aaadb' user: 'alepoaaa' host: '10.76.24.87' (Got an error reading communication packets) 2024-06-11 0:20:31 31570028 [Warning] Aborted connection 31570028 to db: 'aaadb' user: 'alepoaaa' host: '10.76.24.87' (Got an error reading communication packets) 2024-06-11 0:20:31 31570027 [Warning] Aborted connection 31570027 to db: 'aaadb' user: 'alepoaaa' host: '10.76.24.87' (Got an error reading communication packets) 2024-06-11 0:20:31 31570026 [Warning] Aborted connection 31570026 to db: 'aaadb' user: 'alepoaaa' host: '10.76.24.87' (Got an error reading communication packets) 2024-06-11 0:20:31 31570025 [Warning] Aborted connection 31570025 to db: 'aaadb' user: 'alepoaaa' host: '10.76.24.87' (Got an error reading communication packets) 2024-06-11 0:20:31 31570024 [Warning] Aborted connection 31570024 to db: 'aaadb' user: 'alepoaaa' host: '10.76.24.87' (Got an error reading communication packets) 2024-06-11 0:20:31 31570022 [Warning] Aborted connection 31570022 to db: 'aaadb' user: 'alepoaaa' host: '10.76.24.87' (Got an error reading communication packets) 2024-06-11 0:20:31 31570023 [Warning] Aborted connection 31570023 to db: 'aaadb' user: 'alepoaaa' host: '10.76.24.87' (Got an error reading communication packets) 2024-06-11 0:20:31 31570021 [Warning] Aborted connection 31570021 to db: 'aaadb' user: 'alepoaaa' host: '10.76.24.87' (Got an error reading communication packets) 2024-06-11 0:20:31 31570049 [Warning] Aborted connection 31570049 to db: 'aaadb' user: 'alepoaaa' host: '10.76.24.87' (Got an error reading communication packets) 2024-06-11 0:20:31 31570020 [Warning] Aborted connection 31570020 to db: 'aaadb' user: 'alepoaaa' host: '10.76.24.87' (Got an error reading communication packets) 2024-06-11 0:20:31 31570018 [Warning] Aborted connection 31570018 to db: 'aaadb' user: 'alepoaaa' host: '10.76.24.87' (Got an error reading communication packets) 2024-06-11 0:20:31 31570019 [Warning] Aborted connection 31570019 to db: 'aaadb' user: 'alepoaaa' host: '10.76.24.87' (Got an error reading communication packets) 2024-06-11 0:20:31 31570017 [Warning] Aborted connection 31570017 to db: 'aaadb' user: 'alepoaaa' host: '10.76.24.87' (Got an error reading communication packets) 2024-06-11 0:20:31 31570016 [Warning] Aborted connection 31570016 to db: 'aaadb' user: 'alepoaaa' host: '10.76.24.87' (Got an error reading communication packets) 2024-06-11 0:20:31 31570015 [Warning] Aborted connection 31570015 to db: 'aaadb' user: 'alepoaaa' host: '10.76.24.87' (Got an error reading communication packets) 2024-06-11 0:20:31 31570014 [Warning] Aborted connection 31570014 to db: 'aaadb' user: 'alepoaaa' host: '10.76.24.87' (Got an error reading communication packets) 2024-06-11 0:35:25 31840698 [Warning] Aborted connection 31840698 to db: 'aaadb' user: 'alepoaaaems' host: '10.76.24.67' (Got an error reading communication packets) 2024-06-11 0:35:25 31834731 [Warning] Aborted connection 31834731 to db: 'aaadb' user: 'alepoaaaems' host: '10.76.24.67' (Got an error reading communication packets) 2024-06-11 0:35:25 31846803 [Warning] Aborted connection 31846803 to db: 'aaadb' user: 'alepoaaaems' host: '10.76.24.67' (Got an error reading communication packets) 2024-06-11 0:35:25 31832060 [Warning] Aborted connection 31832060 to db: 'aaadb' user: 'alepoaaaems' host: '10.76.24.67' (Got an error reading communication packets) 2024-06-11 0:36:00 31850644 [Warning] Aborted connection 31850644 to db: 'aaadb' user: 'alepoaaaems' host: '10.76.24.74' (Got an error reading communication packets) 2024-06-11 0:36:00 31850643 [Warning] Aborted connection 31850643 to db: 'aaadb' user: 'alepoaaaems' host: '10.76.24.74' (Got an error reading communication packets) 2024-06-11 0:36:00 31843832 [Warning] Aborted connection 31843832 to db: 'aaadb' user: 'alepoaaaems' host: '10.76.24.74' (Got an error reading communication packets) 2024-06-11 0:36:00 31843635 [Warning] Aborted connection 31843635 to db: 'aaadb' user: 'alepoaaaems' host: '10.76.24.74' (Got an error reading communication packets) 2024-06-11 1:06:05 31850810 [Warning] Aborted connection 31850810 to db: 'aaadb' user: 'alepoaaaems' host: '10.76.24.67' (Got timeout reading communication packets) 2024-06-11 1:06:47 31851257 [Warning] Aborted connection 31851257 to db: 'aaadb' user: 'alepoaaaems' host: '10.76.24.74' (Got timeout reading communication packets) 2024-06-13 0:15:15 19 [Note] Master 's-db4': Error reading relay log event: slave SQL thread was killed 2024-06-13 0:15:15 19 [Note] Master 's-db4': Slave SQL thread exiting, replication stopped in log 'db4-binary.125316' at position 148106186, master: 10.76.25.11:3306 2024-06-13 0:15:25 34087472 [Note] Master 's-db4': Slave I/O thread: Start asynchronous replication to master 'gtid@10.76.25.11:3306' in log 'db4-binary.125316' at position 148106186 2024-06-13 0:15:25 34087473 [Note] Master 's-db4': Slave SQL thread initialized, starting replication in log 'db4-binary.125316' at position 148106186, relay log './db1-relay-s@002ddb4.092499' position: 783 2024-06-13 0:15:25 34087472 [Note] Master 's-db4': Slave I/O thread: connected to master 'gtid@10.76.25.11:3306',replication started in log 'db4-binary.125316' at position 148106186 2024-06-13 0:15:25 34087472 [ERROR] Master 's-db4': Error reading packet from server: Could not find first log file name in binary log index file (server_errno=1236) 2024-06-13 0:15:25 34087472 [ERROR] Master 's-db4': Slave I/O: Got fatal error 1236 from master when reading data from binary log: 'Could not find first log file name in binary log index file', Internal MariaDB error code: 1236 2024-06-13 0:15:25 34087472 [Note] Master 's-db4': Slave I/O thread exiting, read up to log 'db4-binary.125316', position 148106186, master 10.76.25.11:3306 2024-06-13 0:20:14 31840216 [Warning] Aborted connection 31840216 to db: 'aaadb' user: 'alepoaaa' host: '10.76.24.88' (Got an error reading communication packets) 2024-06-13 0:20:14 31840211 [Warning] Aborted connection 31840211 to db: 'aaadb' user: 'alepoaaa' host: '10.76.24.88' (Got an error reading communication packets) 2024-06-13 0:20:14 31840208 [Warning] Aborted connection 31840208 to db: 'aaadb' user: 'alepoaaa' host: '10.76.24.88' (Got an error reading communication packets) 2024-06-13 0:20:14 31840206 [Warning] Aborted connection 31840206 to db: 'aaadb' user: 'alepoaaa' host: '10.76.24.88' (Got an error reading communication packets) 2024-06-13 0:20:14 31840204 [Warning] Aborted connection 31840204 to db: 'aaadb' user: 'alepoaaa' host: '10.76.24.88' (Got an error reading communication packets) 2024-06-13 0:20:14 31840203 [Warning] Aborted connection 31840203 to db: 'aaadb' user: 'alepoaaa' host: '10.76.24.88' (Got an error reading communication packets) 2024-06-13 0:20:14 31840200 [Warning] Aborted connection 31840200 to db: 'aaadb' user: 'alepoaaa' host: '10.76.24.88' (Got an error reading communication packets) 2024-06-13 0:20:14 31840199 [Warning] Aborted connection 31840199 to db: 'aaadb' user: 'alepoaaa' host: '10.76.24.88' (Got an error reading communication packets) 2024-06-13 0:20:14 31840196 [Warning] Aborted connection 31840196 to db: 'aaadb' user: 'alepoaaa' host: '10.76.24.88' (Got an error reading communication packets) 2024-06-13 0:20:14 31840193 [Warning] Aborted connection 31840193 to db: 'aaadb' user: 'alepoaaa' host: '10.76.24.88' (Got an error reading communication packets) 2024-06-13 0:20:14 31840188 [Warning] Aborted connection 31840188 to db: 'aaadb' user: 'alepoaaa' host: '10.76.24.88' (Got an error reading communication packets) 2024-06-13 0:20:14 31840185 [Warning] Aborted connection 31840185 to db: 'aaadb' user: 'alepoaaa' host: '10.76.24.88' (Got an error reading communication packets) 2024-06-13 0:20:14 31840186 [Warning] Aborted connection 31840186 to db: 'aaadb' user: 'alepoaaa' host: '10.76.24.88' (Got an error reading communication packets) 2024-06-13 0:20:14 31840201 [Warning] Aborted connection 31840201 to db: 'aaadb' user: 'alepoaaa' host: '10.76.24.88' (Got an error reading communication packets) 2024-06-13 0:20:14 31840202 [Warning] Aborted connection 31840202 to db: 'aaadb' user: 'alepoaaa' host: '10.76.24.88' (Got an error reading communication packets) 2024-06-13 0:20:14 31840215 [Warning] Aborted connection 31840215 to db: 'aaadb' user: 'alepoaaa' host: '10.76.24.88' (Got an error reading communication packets) 2024-06-13 0:20:14 31840179 [Warning] Aborted connection 31840179 to db: 'aaadb' user: 'alepoaaa' host: '10.76.24.88' (Got an error reading communication packets) 2024-06-13 0:20:14 31840176 [Warning] Aborted connection 31840176 to db: 'aaadb' user: 'alepoaaa' host: '10.76.24.88' (Got an error reading communication packets) 2024-06-13 0:20:14 31840210 [Warning] Aborted connection 31840210 to db: 'aaadb' user: 'alepoaaa' host: '10.76.24.88' (Got an error reading communication packets) 2024-06-13 0:20:14 31840170 [Warning] Aborted connection 31840170 to db: 'aaadb' user: 'alepoaaa' host: '10.76.24.88' (Got an error reading communication packets) 2024-06-13 0:20:14 31840213 [Warning] Aborted connection 31840213 to db: 'aaadb' user: 'alepoaaa' host: '10.76.24.88' (Got an error reading communication packets) 2024-06-13 0:20:14 31840165 [Warning] Aborted connection 31840165 to db: 'aaadb' user: 'alepoaaa' host: '10.76.24.88' (Got an error reading communication packets) 2024-06-13 0:20:14 31840169 [Warning] Aborted connection 31840169 to db: 'aaadb' user: 'alepoaaa' host: '10.76.24.88' (Got an error reading communication packets) 2024-06-13 0:20:14 31840168 [Warning] Aborted connection 31840168 to db: 'aaadb' user: 'alepoaaa' host: '10.76.24.88' (Got an error reading communication packets) 2024-06-13 0:20:14 31840159 [Warning] Aborted connection 31840159 to db: 'aaadb' user: 'alepoaaa' host: '10.76.24.88' (Got an error reading communication packets) 2024-06-13 0:20:14 31840189 [Warning] Aborted connection 31840189 to db: 'aaadb' user: 'alepoaaa' host: '10.76.24.88' (Got an error reading communication packets) 2024-06-13 0:20:14 31840158 [Warning] Aborted connection 31840158 to db: 'aaadb' user: 'alepoaaa' host: '10.76.24.88' (Got an error reading communication packets) 2024-06-13 0:20:14 31840154 [Warning] Aborted connection 31840154 to db: 'aaadb' user: 'alepoaaa' host: '10.76.24.88' (Got an error reading communication packets) 2024-06-13 0:20:14 31840152 [Warning] Aborted connection 31840152 to db: 'aaadb' user: 'alepoaaa' host: '10.76.24.88' (Got an error reading communication packets) 2024-06-13 0:20:14 31840207 [Warning] Aborted connection 31840207 to db: 'aaadb' user: 'alepoaaa' host: '10.76.24.88' (Got an error reading communication packets) 2024-06-13 0:20:14 31840147 [Warning] Aborted connection 31840147 to db: 'aaadb' user: 'alepoaaa' host: '10.76.24.88' (Got an error reading communication packets) 2024-06-13 0:20:14 31840156 [Warning] Aborted connection 31840156 to db: 'aaadb' user: 'alepoaaa' host: '10.76.24.88' (Got an error reading communication packets) 2024-06-13 0:20:14 31840187 [Warning] Aborted connection 31840187 to db: 'aaadb' user: 'alepoaaa' host: '10.76.24.88' (Got an error reading communication packets) 2024-06-13 0:20:14 31840205 [Warning] Aborted connection 31840205 to db: 'aaadb' user: 'alepoaaa' host: '10.76.24.88' (Got an error reading communication packets) 2024-06-13 0:20:14 31840174 [Warning] Aborted connection 31840174 to db: 'aaadb' user: 'alepoaaa' host: '10.76.24.88' (Got an error reading communication packets) 2024-06-13 0:20:14 31840171 [Warning] Aborted connection 31840171 to db: 'aaadb' user: 'alepoaaa' host: '10.76.24.88' (Got an error reading communication packets) 2024-06-13 0:20:14 31840173 [Warning] Aborted connection 31840173 to db: 'aaadb' user: 'alepoaaa' host: '10.76.24.88' (Got an error reading communication packets) 2024-06-13 0:20:14 31840212 [Warning] Aborted connection 31840212 to db: 'aaadb' user: 'alepoaaa' host: '10.76.24.88' (Got an error reading communication packets) 2024-06-13 0:20:14 31840166 [Warning] Aborted connection 31840166 to db: 'aaadb' user: 'alepoaaa' host: '10.76.24.88' (Got an error reading communication packets) 2024-06-13 0:20:14 31840198 [Warning] Aborted connection 31840198 to db: 'aaadb' user: 'alepoaaa' host: '10.76.24.88' (Got an error reading communication packets) 2024-06-13 0:20:14 31840192 [Warning] Aborted connection 31840192 to db: 'aaadb' user: 'alepoaaa' host: '10.76.24.88' (Got an error reading communication packets) 2024-06-13 0:20:14 31840163 [Warning] Aborted connection 31840163 to db: 'aaadb' user: 'alepoaaa' host: '10.76.24.88' (Got an error reading communication packets) 2024-06-13 0:20:14 31840162 [Warning] Aborted connection 31840162 to db: 'aaadb' user: 'alepoaaa' host: '10.76.24.88' (Got an error reading communication packets) 2024-06-13 0:20:14 31840190 [Warning] Aborted connection 31840190 to db: 'aaadb' user: 'alepoaaa' host: '10.76.24.88' (Got an error reading communication packets) 2024-06-13 0:20:14 31840161 [Warning] Aborted connection 31840161 to db: 'aaadb' user: 'alepoaaa' host: '10.76.24.88' (Got an error reading communication packets) 2024-06-13 0:20:14 31840209 [Warning] Aborted connection 31840209 to db: 'aaadb' user: 'alepoaaa' host: '10.76.24.88' (Got an error reading communication packets) 2024-06-13 0:20:14 31840151 [Warning] Aborted connection 31840151 to db: 'aaadb' user: 'alepoaaa' host: '10.76.24.88' (Got an error reading communication packets) 2024-06-13 0:20:14 31840150 [Warning] Aborted connection 31840150 to db: 'aaadb' user: 'alepoaaa' host: '10.76.24.88' (Got an error reading communication packets) 2024-06-13 0:20:14 31840148 [Warning] Aborted connection 31840148 to db: 'aaadb' user: 'alepoaaa' host: '10.76.24.88' (Got an error reading communication packets) 2024-06-13 0:20:14 31840182 [Warning] Aborted connection 31840182 to db: 'aaadb' user: 'alepoaaa' host: '10.76.24.88' (Got an error reading communication packets) 2024-06-13 0:20:14 31840184 [Warning] Aborted connection 31840184 to db: 'aaadb' user: 'alepoaaa' host: '10.76.24.88' (Got an error reading communication packets) 2024-06-13 0:20:14 31840228 [Warning] Aborted connection 31840228 to db: 'aaadb' user: 'alepoaaa' host: '10.76.24.88' (Got an error reading communication packets) 2024-06-13 0:20:14 31853337 [Warning] Aborted connection 31853337 to db: 'aaadb' user: 'alepoaaa' host: '10.76.24.89' (Got an error reading communication packets) 2024-06-13 0:20:14 31840637 [Warning] Aborted connection 31840637 to db: 'aaadb' user: 'alepoaaa' host: '10.76.24.89' (Got an error reading communication packets) 2024-06-13 0:20:14 31840634 [Warning] Aborted connection 31840634 to db: 'aaadb' user: 'alepoaaa' host: '10.76.24.89' (Got an error reading communication packets) 2024-06-13 0:20:14 31840633 [Warning] Aborted connection 31840633 to db: 'aaadb' user: 'alepoaaa' host: '10.76.24.89' (Got an error reading communication packets) 2024-06-13 0:20:14 31840631 [Warning] Aborted connection 31840631 to db: 'aaadb' user: 'alepoaaa' host: '10.76.24.89' (Got an error reading communication packets) 2024-06-13 0:20:14 31840632 [Warning] Aborted connection 31840632 to db: 'aaadb' user: 'alepoaaa' host: '10.76.24.89' (Got an error reading communication packets) 2024-06-13 0:20:14 31840625 [Warning] Aborted connection 31840625 to db: 'aaadb' user: 'alepoaaa' host: '10.76.24.89' (Got an error reading communication packets) 2024-06-13 0:20:14 31840624 [Warning] Aborted connection 31840624 to db: 'aaadb' user: 'alepoaaa' host: '10.76.24.89' (Got an error reading communication packets) 2024-06-13 0:20:14 31840622 [Warning] Aborted connection 31840622 to db: 'aaadb' user: 'alepoaaa' host: '10.76.24.89' (Got an error reading communication packets) 2024-06-13 0:20:14 31840621 [Warning] Aborted connection 31840621 to db: 'aaadb' user: 'alepoaaa' host: '10.76.24.89' (Got an error reading communication packets) 2024-06-13 0:20:14 31840623 [Warning] Aborted connection 31840623 to db: 'aaadb' user: 'alepoaaa' host: '10.76.24.89' (Got an error reading communication packets) 2024-06-13 0:20:14 31840612 [Warning] Aborted connection 31840612 to db: 'aaadb' user: 'alepoaaa' host: '10.76.24.89' (Got an error reading communication packets) 2024-06-13 0:20:14 31840617 [Warning] Aborted connection 31840617 to db: 'aaadb' user: 'alepoaaa' host: '10.76.24.89' (Got an error reading communication packets) 2024-06-13 0:20:14 31840609 [Warning] Aborted connection 31840609 to db: 'aaadb' user: 'alepoaaa' host: '10.76.24.89' (Got an error reading communication packets) 2024-06-13 0:20:14 31840608 [Warning] Aborted connection 31840608 to db: 'aaadb' user: 'alepoaaa' host: '10.76.24.89' (Got an error reading communication packets) 2024-06-13 0:20:14 31840605 [Warning] Aborted connection 31840605 to db: 'aaadb' user: 'alepoaaa' host: '10.76.24.89' (Got an error reading communication packets) 2024-06-13 0:20:14 31840601 [Warning] Aborted connection 31840601 to db: 'aaadb' user: 'alepoaaa' host: '10.76.24.89' (Got an error reading communication packets) 2024-06-13 0:20:14 31840615 [Warning] Aborted connection 31840615 to db: 'aaadb' user: 'alepoaaa' host: '10.76.24.89' (Got an error reading communication packets) 2024-06-13 0:20:14 31840602 [Warning] Aborted connection 31840602 to db: 'aaadb' user: 'alepoaaa' host: '10.76.24.89' (Got an error reading communication packets) 2024-06-13 0:20:14 31840629 [Warning] Aborted connection 31840629 to db: 'aaadb' user: 'alepoaaa' host: '10.76.24.89' (Got an error reading communication packets) 2024-06-13 0:20:14 31840594 [Warning] Aborted connection 31840594 to db: 'aaadb' user: 'alepoaaa' host: '10.76.24.89' (Got an error reading communication packets) 2024-06-13 0:20:14 31840613 [Warning] Aborted connection 31840613 to db: 'aaadb' user: 'alepoaaa' host: '10.76.24.89' (Got an error reading communication packets) 2024-06-13 0:20:14 31840618 [Warning] Aborted connection 31840618 to db: 'aaadb' user: 'alepoaaa' host: '10.76.24.89' (Got an error reading communication packets) 2024-06-13 0:20:14 31840593 [Warning] Aborted connection 31840593 to db: 'aaadb' user: 'alepoaaa' host: '10.76.24.89' (Got an error reading communication packets) 2024-06-13 0:20:14 31840592 [Warning] Aborted connection 31840592 to db: 'aaadb' user: 'alepoaaa' host: '10.76.24.89' (Got an error reading communication packets) 2024-06-13 0:20:14 31840585 [Warning] Aborted connection 31840585 to db: 'aaadb' user: 'alepoaaa' host: '10.76.24.89' (Got an error reading communication packets) 2024-06-13 0:20:14 31840584 [Warning] Aborted connection 31840584 to db: 'aaadb' user: 'alepoaaa' host: '10.76.24.89' (Got an error reading communication packets) 2024-06-13 0:20:14 31840582 [Warning] Aborted connection 31840582 to db: 'aaadb' user: 'alepoaaa' host: '10.76.24.89' (Got an error reading communication packets) 2024-06-13 0:20:14 31840606 [Warning] Aborted connection 31840606 to db: 'aaadb' user: 'alepoaaa' host: '10.76.24.89' (Got an error reading communication packets) 2024-06-13 0:20:14 31840577 [Warning] Aborted connection 31840577 to db: 'aaadb' user: 'alepoaaa' host: '10.76.24.89' (Got an error reading communication packets) 2024-06-13 0:20:14 31840576 [Warning] Aborted connection 31840576 to db: 'aaadb' user: 'alepoaaa' host: '10.76.24.89' (Got an error reading communication packets) 2024-06-13 0:20:14 31840569 [Warning] Aborted connection 31840569 to db: 'aaadb' user: 'alepoaaa' host: '10.76.24.89' (Got an error reading communication packets) 2024-06-13 0:20:14 31840611 [Warning] Aborted connection 31840611 to db: 'aaadb' user: 'alepoaaa' host: '10.76.24.89' (Got an error reading communication packets) 2024-06-13 0:20:14 31840588 [Warning] Aborted connection 31840588 to db: 'aaadb' user: 'alepoaaa' host: '10.76.24.89' (Got an error reading communication packets) 2024-06-13 0:20:14 31840595 [Warning] Aborted connection 31840595 to db: 'aaadb' user: 'alepoaaa' host: '10.76.24.89' (Got an error reading communication packets) 2024-06-13 0:20:14 31840586 [Warning] Aborted connection 31840586 to db: 'aaadb' user: 'alepoaaa' host: '10.76.24.89' (Got an error reading communication packets) 2024-06-13 0:20:14 31840591 [Warning] Aborted connection 31840591 to db: 'aaadb' user: 'alepoaaa' host: '10.76.24.89' (Got an error reading communication packets) 2024-06-13 0:20:14 31840614 [Warning] Aborted connection 31840614 to db: 'aaadb' user: 'alepoaaa' host: '10.76.24.89' (Got an error reading communication packets) 2024-06-13 0:20:14 31840628 [Warning] Aborted connection 31840628 to db: 'aaadb' user: 'alepoaaa' host: '10.76.24.89' (Got an error reading communication packets) 2024-06-13 0:20:14 31840581 [Warning] Aborted connection 31840581 to db: 'aaadb' user: 'alepoaaa' host: '10.76.24.89' (Got an error reading communication packets) 2024-06-13 0:20:14 31840600 [Warning] Aborted connection 31840600 to db: 'aaadb' user: 'alepoaaa' host: '10.76.24.89' (Got an error reading communication packets) 2024-06-13 0:20:14 31840578 [Warning] Aborted connection 31840578 to db: 'aaadb' user: 'alepoaaa' host: '10.76.24.89' (Got an error reading communication packets) 2024-06-13 0:20:14 31840597 [Warning] Aborted connection 31840597 to db: 'aaadb' user: 'alepoaaa' host: '10.76.24.89' (Got an error reading communication packets) 2024-06-13 0:20:14 31840598 [Warning] Aborted connection 31840598 to db: 'aaadb' user: 'alepoaaa' host: '10.76.24.89' (Got an error reading communication packets) 2024-06-13 0:20:14 31840572 [Warning] Aborted connection 31840572 to db: 'aaadb' user: 'alepoaaa' host: '10.76.24.89' (Got an error reading communication packets) 2024-06-13 0:20:14 31840590 [Warning] Aborted connection 31840590 to db: 'aaadb' user: 'alepoaaa' host: '10.76.24.89' (Got an error reading communication packets) 2024-06-13 0:20:14 31840579 [Warning] Aborted connection 31840579 to db: 'aaadb' user: 'alepoaaa' host: '10.76.24.89' (Got an error reading communication packets) 2024-06-13 0:20:14 31840652 [Warning] Aborted connection 31840652 to db: 'aaadb' user: 'alepoaaa' host: '10.76.24.89' (Got an error reading communication packets) 2024-06-13 0:20:14 31840568 [Warning] Aborted connection 31840568 to db: 'aaadb' user: 'alepoaaa' host: '10.76.24.89' (Got an error reading communication packets) 2024-06-13 0:20:14 31840607 [Warning] Aborted connection 31840607 to db: 'aaadb' user: 'alepoaaa' host: '10.76.24.89' (Got an error reading communication packets) 2024-06-13 0:20:14 31840570 [Warning] Aborted connection 31840570 to db: 'aaadb' user: 'alepoaaa' host: '10.76.24.89' (Got an error reading communication packets) 2024-06-13 0:20:14 31840610 [Warning] Aborted connection 31840610 to db: 'aaadb' user: 'alepoaaa' host: '10.76.24.89' (Got an error reading communication packets) 2024-06-13 0:20:14 31842685 [Warning] Aborted connection 31842685 to db: 'aaadb' user: 'alepoaaa' host: '10.76.24.91' (Got an error reading communication packets) 2024-06-13 0:20:14 31841172 [Warning] Aborted connection 31841172 to db: 'aaadb' user: 'alepoaaa' host: '10.76.24.91' (Got an error reading communication packets) 2024-06-13 0:20:14 31841170 [Warning] Aborted connection 31841170 to db: 'aaadb' user: 'alepoaaa' host: '10.76.24.91' (Got an error reading communication packets) 2024-06-13 0:20:14 31841174 [Warning] Aborted connection 31841174 to db: 'aaadb' user: 'alepoaaa' host: '10.76.24.91' (Got an error reading communication packets) 2024-06-13 0:20:14 31841168 [Warning] Aborted connection 31841168 to db: 'aaadb' user: 'alepoaaa' host: '10.76.24.91' (Got an error reading communication packets) 2024-06-13 0:20:14 31841169 [Warning] Aborted connection 31841169 to db: 'aaadb' user: 'alepoaaa' host: '10.76.24.91' (Got an error reading communication packets) 2024-06-13 0:20:14 31841166 [Warning] Aborted connection 31841166 to db: 'aaadb' user: 'alepoaaa' host: '10.76.24.91' (Got an error reading communication packets) 2024-06-13 0:20:14 31841162 [Warning] Aborted connection 31841162 to db: 'aaadb' user: 'alepoaaa' host: '10.76.24.91' (Got an error reading communication packets) 2024-06-13 0:20:14 31841161 [Warning] Aborted connection 31841161 to db: 'aaadb' user: 'alepoaaa' host: '10.76.24.91' (Got an error reading communication packets) 2024-06-13 0:20:14 31841165 [Warning] Aborted connection 31841165 to db: 'aaadb' user: 'alepoaaa' host: '10.76.24.91' (Got an error reading communication packets) 2024-06-13 0:20:14 31841158 [Warning] Aborted connection 31841158 to db: 'aaadb' user: 'alepoaaa' host: '10.76.24.91' (Got an error reading communication packets) 2024-06-13 0:20:14 31841157 [Warning] Aborted connection 31841157 to db: 'aaadb' user: 'alepoaaa' host: '10.76.24.91' (Got an error reading communication packets) 2024-06-13 0:20:14 31841156 [Warning] Aborted connection 31841156 to db: 'aaadb' user: 'alepoaaa' host: '10.76.24.91' (Got an error reading communication packets) 2024-06-13 0:20:14 31841154 [Warning] Aborted connection 31841154 to db: 'aaadb' user: 'alepoaaa' host: '10.76.24.91' (Got an error reading communication packets) 2024-06-13 0:20:14 31841152 [Warning] Aborted connection 31841152 to db: 'aaadb' user: 'alepoaaa' host: '10.76.24.91' (Got an error reading communication packets) 2024-06-13 0:20:14 31841150 [Warning] Aborted connection 31841150 to db: 'aaadb' user: 'alepoaaa' host: '10.76.24.91' (Got an error reading communication packets) 2024-06-13 0:20:14 31841151 [Warning] Aborted connection 31841151 to db: 'aaadb' user: 'alepoaaa' host: '10.76.24.91' (Got an error reading communication packets) 2024-06-13 0:20:14 31841145 [Warning] Aborted connection 31841145 to db: 'aaadb' user: 'alepoaaa' host: '10.76.24.91' (Got an error reading communication packets) 2024-06-13 0:20:14 31841141 [Warning] Aborted connection 31841141 to db: 'aaadb' user: 'alepoaaa' host: '10.76.24.91' (Got an error reading communication packets) 2024-06-13 0:20:14 31841139 [Warning] Aborted connection 31841139 to db: 'aaadb' user: 'alepoaaa' host: '10.76.24.91' (Got an error reading communication packets) 2024-06-13 0:20:14 31841137 [Warning] Aborted connection 31841137 to db: 'aaadb' user: 'alepoaaa' host: '10.76.24.91' (Got an error reading communication packets) 2024-06-13 0:20:14 31841135 [Warning] Aborted connection 31841135 to db: 'aaadb' user: 'alepoaaa' host: '10.76.24.91' (Got an error reading communication packets) 2024-06-13 0:20:14 31841136 [Warning] Aborted connection 31841136 to db: 'aaadb' user: 'alepoaaa' host: '10.76.24.91' (Got an error reading communication packets) 2024-06-13 0:20:14 31841131 [Warning] Aborted connection 31841131 to db: 'aaadb' user: 'alepoaaa' host: '10.76.24.91' (Got an error reading communication packets) 2024-06-13 0:20:14 31841130 [Warning] Aborted connection 31841130 to db: 'aaadb' user: 'alepoaaa' host: '10.76.24.91' (Got an error reading communication packets) 2024-06-13 0:20:14 31841134 [Warning] Aborted connection 31841134 to db: 'aaadb' user: 'alepoaaa' host: '10.76.24.91' (Got an error reading communication packets) 2024-06-13 0:20:14 31841126 [Warning] Aborted connection 31841126 to db: 'aaadb' user: 'alepoaaa' host: '10.76.24.91' (Got an error reading communication packets) 2024-06-13 0:20:14 31841124 [Warning] Aborted connection 31841124 to db: 'aaadb' user: 'alepoaaa' host: '10.76.24.91' (Got an error reading communication packets) 2024-06-13 0:20:14 31841149 [Warning] Aborted connection 31841149 to db: 'aaadb' user: 'alepoaaa' host: '10.76.24.91' (Got an error reading communication packets) 2024-06-13 0:20:14 31841117 [Warning] Aborted connection 31841117 to db: 'aaadb' user: 'alepoaaa' host: '10.76.24.91' (Got an error reading communication packets) 2024-06-13 0:20:14 31841115 [Warning] Aborted connection 31841115 to db: 'aaadb' user: 'alepoaaa' host: '10.76.24.91' (Got an error reading communication packets) 2024-06-13 0:20:14 31841119 [Warning] Aborted connection 31841119 to db: 'aaadb' user: 'alepoaaa' host: '10.76.24.91' (Got an error reading communication packets) 2024-06-13 0:20:14 31841112 [Warning] Aborted connection 31841112 to db: 'aaadb' user: 'alepoaaa' host: '10.76.24.91' (Got an error reading communication packets) 2024-06-13 0:20:14 31841159 [Warning] Aborted connection 31841159 to db: 'aaadb' user: 'alepoaaa' host: '10.76.24.91' (Got an error reading communication packets) 2024-06-13 0:20:14 31841107 [Warning] Aborted connection 31841107 to db: 'aaadb' user: 'alepoaaa' host: '10.76.24.91' (Got an error reading communication packets) 2024-06-13 0:20:14 31841105 [Warning] Aborted connection 31841105 to db: 'aaadb' user: 'alepoaaa' host: '10.76.24.91' (Got an error reading communication packets) 2024-06-13 0:20:14 31841125 [Warning] Aborted connection 31841125 to db: 'aaadb' user: 'alepoaaa' host: '10.76.24.91' (Got an error reading communication packets) 2024-06-13 0:20:14 31841148 [Warning] Aborted connection 31841148 to db: 'aaadb' user: 'alepoaaa' host: '10.76.24.91' (Got an error reading communication packets) 2024-06-13 0:20:14 31841144 [Warning] Aborted connection 31841144 to db: 'aaadb' user: 'alepoaaa' host: '10.76.24.91' (Got an error reading communication packets) 2024-06-13 0:20:14 31841184 [Warning] Aborted connection 31841184 to db: 'aaadb' user: 'alepoaaa' host: '10.76.24.91' (Got an error reading communication packets) 2024-06-13 0:20:14 31841128 [Warning] Aborted connection 31841128 to db: 'aaadb' user: 'alepoaaa' host: '10.76.24.91' (Got an error reading communication packets) 2024-06-13 0:20:14 31841140 [Warning] Aborted connection 31841140 to db: 'aaadb' user: 'alepoaaa' host: '10.76.24.91' (Got an error reading communication packets) 2024-06-13 0:20:14 31841113 [Warning] Aborted connection 31841113 to db: 'aaadb' user: 'alepoaaa' host: '10.76.24.91' (Got an error reading communication packets) 2024-06-13 0:20:14 31841142 [Warning] Aborted connection 31841142 to db: 'aaadb' user: 'alepoaaa' host: '10.76.24.91' (Got an error reading communication packets) 2024-06-13 0:20:14 31841111 [Warning] Aborted connection 31841111 to db: 'aaadb' user: 'alepoaaa' host: '10.76.24.91' (Got an error reading communication packets) 2024-06-13 0:20:14 31841133 [Warning] Aborted connection 31841133 to db: 'aaadb' user: 'alepoaaa' host: '10.76.24.91' (Got an error reading communication packets) 2024-06-13 0:20:14 31841109 [Warning] Aborted connection 31841109 to db: 'aaadb' user: 'alepoaaa' host: '10.76.24.91' (Got an error reading communication packets) 2024-06-13 0:20:14 31841108 [Warning] Aborted connection 31841108 to db: 'aaadb' user: 'alepoaaa' host: '10.76.24.91' (Got an error reading communication packets) 2024-06-13 0:20:14 31841106 [Warning] Aborted connection 31841106 to db: 'aaadb' user: 'alepoaaa' host: '10.76.24.91' (Got an error reading communication packets) 2024-06-13 0:20:14 31841123 [Warning] Aborted connection 31841123 to db: 'aaadb' user: 'alepoaaa' host: '10.76.24.91' (Got an error reading communication packets) 2024-06-13 0:20:14 31841164 [Warning] Aborted connection 31841164 to db: 'aaadb' user: 'alepoaaa' host: '10.76.24.91' (Got an error reading communication packets) 2024-06-13 0:20:14 31841121 [Warning] Aborted connection 31841121 to db: 'aaadb' user: 'alepoaaa' host: '10.76.24.91' (Got an error reading communication packets) 2024-06-13 0:20:14 31841613 [Warning] Aborted connection 31841613 to db: 'aaadb' user: 'alepoaaa' host: '10.76.24.92' (Got an error reading communication packets) 2024-06-13 0:20:14 31841582 [Warning] Aborted connection 31841582 to db: 'aaadb' user: 'alepoaaa' host: '10.76.24.92' (Got an error reading communication packets) 2024-06-13 0:20:14 31841580 [Warning] Aborted connection 31841580 to db: 'aaadb' user: 'alepoaaa' host: '10.76.24.92' (Got an error reading communication packets) 2024-06-13 0:20:14 31841579 [Warning] Aborted connection 31841579 to db: 'aaadb' user: 'alepoaaa' host: '10.76.24.92' (Got an error reading communication packets) 2024-06-13 0:20:14 31841576 [Warning] Aborted connection 31841576 to db: 'aaadb' user: 'alepoaaa' host: '10.76.24.92' (Got an error reading communication packets) 2024-06-13 0:20:14 31841575 [Warning] Aborted connection 31841575 to db: 'aaadb' user: 'alepoaaa' host: '10.76.24.92' (Got an error reading communication packets) 2024-06-13 0:20:14 31841572 [Warning] Aborted connection 31841572 to db: 'aaadb' user: 'alepoaaa' host: '10.76.24.92' (Got an error reading communication packets) 2024-06-13 0:20:14 31841570 [Warning] Aborted connection 31841570 to db: 'aaadb' user: 'alepoaaa' host: '10.76.24.92' (Got an error reading communication packets) 2024-06-13 0:20:14 31841578 [Warning] Aborted connection 31841578 to db: 'aaadb' user: 'alepoaaa' host: '10.76.24.92' (Got an error reading communication packets) 2024-06-13 0:20:14 31841565 [Warning] Aborted connection 31841565 to db: 'aaadb' user: 'alepoaaa' host: '10.76.24.92' (Got an error reading communication packets) 2024-06-13 0:20:14 31841567 [Warning] Aborted connection 31841567 to db: 'aaadb' user: 'alepoaaa' host: '10.76.24.92' (Got an error reading communication packets) 2024-06-13 0:20:14 31841556 [Warning] Aborted connection 31841556 to db: 'aaadb' user: 'alepoaaa' host: '10.76.24.92' (Got an error reading communication packets) 2024-06-13 0:20:14 31841573 [Warning] Aborted connection 31841573 to db: 'aaadb' user: 'alepoaaa' host: '10.76.24.92' (Got an error reading communication packets) 2024-06-13 0:20:14 31841552 [Warning] Aborted connection 31841552 to db: 'aaadb' user: 'alepoaaa' host: '10.76.24.92' (Got an error reading communication packets) 2024-06-13 0:20:14 31841549 [Warning] Aborted connection 31841549 to db: 'aaadb' user: 'alepoaaa' host: '10.76.24.92' (Got an error reading communication packets) 2024-06-13 0:20:14 31841551 [Warning] Aborted connection 31841551 to db: 'aaadb' user: 'alepoaaa' host: '10.76.24.92' (Got an error reading communication packets) 2024-06-13 0:20:14 31841546 [Warning] Aborted connection 31841546 to db: 'aaadb' user: 'alepoaaa' host: '10.76.24.92' (Got an error reading communication packets) 2024-06-13 0:20:14 31841547 [Warning] Aborted connection 31841547 to db: 'aaadb' user: 'alepoaaa' host: '10.76.24.92' (Got an error reading communication packets) 2024-06-13 0:20:14 31841542 [Warning] Aborted connection 31841542 to db: 'aaadb' user: 'alepoaaa' host: '10.76.24.92' (Got an error reading communication packets) 2024-06-13 0:20:14 31841539 [Warning] Aborted connection 31841539 to db: 'aaadb' user: 'alepoaaa' host: '10.76.24.92' (Got an error reading communication packets) 2024-06-13 0:20:14 31841571 [Warning] Aborted connection 31841571 to db: 'aaadb' user: 'alepoaaa' host: '10.76.24.92' (Got an error reading communication packets) 2024-06-13 0:20:14 31841536 [Warning] Aborted connection 31841536 to db: 'aaadb' user: 'alepoaaa' host: '10.76.24.92' (Got an error reading communication packets) 2024-06-13 0:20:14 31841534 [Warning] Aborted connection 31841534 to db: 'aaadb' user: 'alepoaaa' host: '10.76.24.92' (Got an error reading communication packets) 2024-06-13 0:20:14 31841563 [Warning] Aborted connection 31841563 to db: 'aaadb' user: 'alepoaaa' host: '10.76.24.92' (Got an error reading communication packets) 2024-06-13 0:20:14 31841528 [Warning] Aborted connection 31841528 to db: 'aaadb' user: 'alepoaaa' host: '10.76.24.92' (Got an error reading communication packets) 2024-06-13 0:20:14 31841529 [Warning] Aborted connection 31841529 to db: 'aaadb' user: 'alepoaaa' host: '10.76.24.92' (Got an error reading communication packets) 2024-06-13 0:20:14 31841544 [Warning] Aborted connection 31841544 to db: 'aaadb' user: 'alepoaaa' host: '10.76.24.92' (Got an error reading communication packets) 2024-06-13 0:20:14 31841561 [Warning] Aborted connection 31841561 to db: 'aaadb' user: 'alepoaaa' host: '10.76.24.92' (Got an error reading communication packets) 2024-06-13 0:20:14 31841525 [Warning] Aborted connection 31841525 to db: 'aaadb' user: 'alepoaaa' host: '10.76.24.92' (Got an error reading communication packets) 2024-06-13 0:20:14 31841559 [Warning] Aborted connection 31841559 to db: 'aaadb' user: 'alepoaaa' host: '10.76.24.92' (Got an error reading communication packets) 2024-06-13 0:20:14 31841518 [Warning] Aborted connection 31841518 to db: 'aaadb' user: 'alepoaaa' host: '10.76.24.92' (Got an error reading communication packets) 2024-06-13 0:20:14 31841538 [Warning] Aborted connection 31841538 to db: 'aaadb' user: 'alepoaaa' host: '10.76.24.92' (Got an error reading communication packets) 2024-06-13 0:20:14 31841513 [Warning] Aborted connection 31841513 to db: 'aaadb' user: 'alepoaaa' host: '10.76.24.92' (Got an error reading communication packets) 2024-06-13 0:20:14 31841523 [Warning] Aborted connection 31841523 to db: 'aaadb' user: 'alepoaaa' host: '10.76.24.92' (Got an error reading communication packets) 2024-06-13 0:20:14 31841550 [Warning] Aborted connection 31841550 to db: 'aaadb' user: 'alepoaaa' host: '10.76.24.92' (Got an error reading communication packets) 2024-06-13 0:20:14 31841514 [Warning] Aborted connection 31841514 to db: 'aaadb' user: 'alepoaaa' host: '10.76.24.92' (Got an error reading communication packets) 2024-06-13 0:20:14 31841562 [Warning] Aborted connection 31841562 to db: 'aaadb' user: 'alepoaaa' host: '10.76.24.92' (Got an error reading communication packets) 2024-06-13 0:20:14 31841532 [Warning] Aborted connection 31841532 to db: 'aaadb' user: 'alepoaaa' host: '10.76.24.92' (Got an error reading communication packets) 2024-06-13 0:20:14 31841577 [Warning] Aborted connection 31841577 to db: 'aaadb' user: 'alepoaaa' host: '10.76.24.92' (Got an error reading communication packets) 2024-06-13 0:20:14 31841531 [Warning] Aborted connection 31841531 to db: 'aaadb' user: 'alepoaaa' host: '10.76.24.92' (Got an error reading communication packets) 2024-06-13 0:20:14 31841520 [Warning] Aborted connection 31841520 to db: 'aaadb' user: 'alepoaaa' host: '10.76.24.92' (Got an error reading communication packets) 2024-06-13 0:20:14 31841519 [Warning] Aborted connection 31841519 to db: 'aaadb' user: 'alepoaaa' host: '10.76.24.92' (Got an error reading communication packets) 2024-06-13 0:20:14 31841560 [Warning] Aborted connection 31841560 to db: 'aaadb' user: 'alepoaaa' host: '10.76.24.92' (Got an error reading communication packets) 2024-06-13 0:20:14 31841545 [Warning] Aborted connection 31841545 to db: 'aaadb' user: 'alepoaaa' host: '10.76.24.92' (Got an error reading communication packets) 2024-06-13 0:20:14 31841535 [Warning] Aborted connection 31841535 to db: 'aaadb' user: 'alepoaaa' host: '10.76.24.92' (Got an error reading communication packets) 2024-06-13 0:20:14 31841558 [Warning] Aborted connection 31841558 to db: 'aaadb' user: 'alepoaaa' host: '10.76.24.92' (Got an error reading communication packets) 2024-06-13 0:20:14 31841516 [Warning] Aborted connection 31841516 to db: 'aaadb' user: 'alepoaaa' host: '10.76.24.92' (Got an error reading communication packets) 2024-06-13 0:20:14 31841543 [Warning] Aborted connection 31841543 to db: 'aaadb' user: 'alepoaaa' host: '10.76.24.92' (Got an error reading communication packets) 2024-06-13 0:20:14 31841592 [Warning] Aborted connection 31841592 to db: 'aaadb' user: 'alepoaaa' host: '10.76.24.92' (Got an error reading communication packets) 2024-06-13 0:20:14 31841522 [Warning] Aborted connection 31841522 to db: 'aaadb' user: 'alepoaaa' host: '10.76.24.92' (Got an error reading communication packets) 2024-06-13 0:20:14 31841555 [Warning] Aborted connection 31841555 to db: 'aaadb' user: 'alepoaaa' host: '10.76.24.92' (Got an error reading communication packets) 2024-06-13 0:20:14 31841521 [Warning] Aborted connection 31841521 to db: 'aaadb' user: 'alepoaaa' host: '10.76.24.92' (Got an error reading communication packets) 2024-06-13 0:20:14 31839009 [Warning] Aborted connection 31839009 to db: 'aaadb' user: 'alepoaaa' host: '10.76.24.86' (Got an error reading communication packets) 2024-06-13 0:20:14 31839006 [Warning] Aborted connection 31839006 to db: 'aaadb' user: 'alepoaaa' host: '10.76.24.86' (Got an error reading communication packets) 2024-06-13 0:20:14 31839002 [Warning] Aborted connection 31839002 to db: 'aaadb' user: 'alepoaaa' host: '10.76.24.86' (Got an error reading communication packets) 2024-06-13 0:20:14 31839005 [Warning] Aborted connection 31839005 to db: 'aaadb' user: 'alepoaaa' host: '10.76.24.86' (Got an error reading communication packets) 2024-06-13 0:20:14 31838998 [Warning] Aborted connection 31838998 to db: 'aaadb' user: 'alepoaaa' host: '10.76.24.86' (Got an error reading communication packets) 2024-06-13 0:20:14 31838996 [Warning] Aborted connection 31838996 to db: 'aaadb' user: 'alepoaaa' host: '10.76.24.86' (Got an error reading communication packets) 2024-06-13 0:20:14 31838995 [Warning] Aborted connection 31838995 to db: 'aaadb' user: 'alepoaaa' host: '10.76.24.86' (Got an error reading communication packets) 2024-06-13 0:20:14 31838999 [Warning] Aborted connection 31838999 to db: 'aaadb' user: 'alepoaaa' host: '10.76.24.86' (Got an error reading communication packets) 2024-06-13 0:20:14 31838994 [Warning] Aborted connection 31838994 to db: 'aaadb' user: 'alepoaaa' host: '10.76.24.86' (Got an error reading communication packets) 2024-06-13 0:20:14 31838983 [Warning] Aborted connection 31838983 to db: 'aaadb' user: 'alepoaaa' host: '10.76.24.86' (Got an error reading communication packets) 2024-06-13 0:20:14 31838992 [Warning] Aborted connection 31838992 to db: 'aaadb' user: 'alepoaaa' host: '10.76.24.86' (Got an error reading communication packets) 2024-06-13 0:20:14 31838982 [Warning] Aborted connection 31838982 to db: 'aaadb' user: 'alepoaaa' host: '10.76.24.86' (Got an error reading communication packets) 2024-06-13 0:20:14 31838973 [Warning] Aborted connection 31838973 to db: 'aaadb' user: 'alepoaaa' host: '10.76.24.86' (Got an error reading communication packets) 2024-06-13 0:20:14 31838970 [Warning] Aborted connection 31838970 to db: 'aaadb' user: 'alepoaaa' host: '10.76.24.86' (Got an error reading communication packets) 2024-06-13 0:20:14 31838968 [Warning] Aborted connection 31838968 to db: 'aaadb' user: 'alepoaaa' host: '10.76.24.86' (Got an error reading communication packets) 2024-06-13 0:20:14 31838967 [Warning] Aborted connection 31838967 to db: 'aaadb' user: 'alepoaaa' host: '10.76.24.86' (Got an error reading communication packets) 2024-06-13 0:20:14 31839007 [Warning] Aborted connection 31839007 to db: 'aaadb' user: 'alepoaaa' host: '10.76.24.86' (Got an error reading communication packets) 2024-06-13 0:20:14 31838965 [Warning] Aborted connection 31838965 to db: 'aaadb' user: 'alepoaaa' host: '10.76.24.86' (Got an error reading communication packets) 2024-06-13 0:20:14 31838990 [Warning] Aborted connection 31838990 to db: 'aaadb' user: 'alepoaaa' host: '10.76.24.86' (Got an error reading communication packets) 2024-06-13 0:20:14 31838961 [Warning] Aborted connection 31838961 to db: 'aaadb' user: 'alepoaaa' host: '10.76.24.86' (Got an error reading communication packets) 2024-06-13 0:20:14 31838978 [Warning] Aborted connection 31838978 to db: 'aaadb' user: 'alepoaaa' host: '10.76.24.86' (Got an error reading communication packets) 2024-06-13 0:20:14 31838955 [Warning] Aborted connection 31838955 to db: 'aaadb' user: 'alepoaaa' host: '10.76.24.86' (Got an error reading communication packets) 2024-06-13 0:20:14 31838975 [Warning] Aborted connection 31838975 to db: 'aaadb' user: 'alepoaaa' host: '10.76.24.86' (Got an error reading communication packets) 2024-06-13 0:20:14 31838952 [Warning] Aborted connection 31838952 to db: 'aaadb' user: 'alepoaaa' host: '10.76.24.86' (Got an error reading communication packets) 2024-06-13 0:20:14 31838957 [Warning] Aborted connection 31838957 to db: 'aaadb' user: 'alepoaaa' host: '10.76.24.86' (Got an error reading communication packets) 2024-06-13 0:20:14 31838949 [Warning] Aborted connection 31838949 to db: 'aaadb' user: 'alepoaaa' host: '10.76.24.86' (Got an error reading communication packets) 2024-06-13 0:20:14 31838976 [Warning] Aborted connection 31838976 to db: 'aaadb' user: 'alepoaaa' host: '10.76.24.86' (Got an error reading communication packets) 2024-06-13 0:20:14 31838945 [Warning] Aborted connection 31838945 to db: 'aaadb' user: 'alepoaaa' host: '10.76.24.86' (Got an error reading communication packets) 2024-06-13 0:20:14 31838944 [Warning] Aborted connection 31838944 to db: 'aaadb' user: 'alepoaaa' host: '10.76.24.86' (Got an error reading communication packets) 2024-06-13 0:20:14 31838981 [Warning] Aborted connection 31838981 to db: 'aaadb' user: 'alepoaaa' host: '10.76.24.86' (Got an error reading communication packets) 2024-06-13 0:20:14 31838969 [Warning] Aborted connection 31838969 to db: 'aaadb' user: 'alepoaaa' host: '10.76.24.86' (Got an error reading communication packets) 2024-06-13 0:20:14 31838953 [Warning] Aborted connection 31838953 to db: 'aaadb' user: 'alepoaaa' host: '10.76.24.86' (Got an error reading communication packets) 2024-06-13 0:20:14 31838963 [Warning] Aborted connection 31838963 to db: 'aaadb' user: 'alepoaaa' host: '10.76.24.86' (Got an error reading communication packets) 2024-06-13 0:20:14 31839025 [Warning] Aborted connection 31839025 to db: 'aaadb' user: 'alepoaaa' host: '10.76.24.86' (Got an error reading communication packets) 2024-06-13 0:20:14 31838964 [Warning] Aborted connection 31838964 to db: 'aaadb' user: 'alepoaaa' host: '10.76.24.86' (Got an error reading communication packets) 2024-06-13 0:20:14 31838962 [Warning] Aborted connection 31838962 to db: 'aaadb' user: 'alepoaaa' host: '10.76.24.86' (Got an error reading communication packets) 2024-06-13 0:20:14 31838977 [Warning] Aborted connection 31838977 to db: 'aaadb' user: 'alepoaaa' host: '10.76.24.86' (Got an error reading communication packets) 2024-06-13 0:20:14 31838987 [Warning] Aborted connection 31838987 to db: 'aaadb' user: 'alepoaaa' host: '10.76.24.86' (Got an error reading communication packets) 2024-06-13 0:20:14 31838993 [Warning] Aborted connection 31838993 to db: 'aaadb' user: 'alepoaaa' host: '10.76.24.86' (Got an error reading communication packets) 2024-06-13 0:20:14 31838956 [Warning] Aborted connection 31838956 to db: 'aaadb' user: 'alepoaaa' host: '10.76.24.86' (Got an error reading communication packets) 2024-06-13 0:20:14 31838951 [Warning] Aborted connection 31838951 to db: 'aaadb' user: 'alepoaaa' host: '10.76.24.86' (Got an error reading communication packets) 2024-06-13 0:20:14 31838950 [Warning] Aborted connection 31838950 to db: 'aaadb' user: 'alepoaaa' host: '10.76.24.86' (Got an error reading communication packets) 2024-06-13 0:20:14 31838948 [Warning] Aborted connection 31838948 to db: 'aaadb' user: 'alepoaaa' host: '10.76.24.86' (Got an error reading communication packets) 2024-06-13 0:20:14 31838947 [Warning] Aborted connection 31838947 to db: 'aaadb' user: 'alepoaaa' host: '10.76.24.86' (Got an error reading communication packets) 2024-06-13 0:20:14 31839000 [Warning] Aborted connection 31839000 to db: 'aaadb' user: 'alepoaaa' host: '10.76.24.86' (Got an error reading communication packets) 2024-06-13 0:20:14 31838984 [Warning] Aborted connection 31838984 to db: 'aaadb' user: 'alepoaaa' host: '10.76.24.86' (Got an error reading communication packets) 2024-06-13 0:20:14 31838972 [Warning] Aborted connection 31838972 to db: 'aaadb' user: 'alepoaaa' host: '10.76.24.86' (Got an error reading communication packets) 2024-06-13 0:20:14 31838943 [Warning] Aborted connection 31838943 to db: 'aaadb' user: 'alepoaaa' host: '10.76.24.86' (Got an error reading communication packets) 2024-06-13 0:20:14 31838971 [Warning] Aborted connection 31838971 to db: 'aaadb' user: 'alepoaaa' host: '10.76.24.86' (Got an error reading communication packets) 2024-06-13 0:20:14 31838960 [Warning] Aborted connection 31838960 to db: 'aaadb' user: 'alepoaaa' host: '10.76.24.86' (Got an error reading communication packets) 2024-06-13 0:20:14 31838954 [Warning] Aborted connection 31838954 to db: 'aaadb' user: 'alepoaaa' host: '10.76.24.86' (Got an error reading communication packets) 2024-06-13 0:20:14 31838946 [Warning] Aborted connection 31838946 to db: 'aaadb' user: 'alepoaaa' host: '10.76.24.86' (Got an error reading communication packets) 2024-06-13 0:20:14 31839758 [Warning] Aborted connection 31839758 to db: 'aaadb' user: 'alepoaaa' host: '10.76.24.87' (Got an error reading communication packets) 2024-06-13 0:20:14 31839725 [Warning] Aborted connection 31839725 to db: 'aaadb' user: 'alepoaaa' host: '10.76.24.87' (Got an error reading communication packets) 2024-06-13 0:20:14 31839723 [Warning] Aborted connection 31839723 to db: 'aaadb' user: 'alepoaaa' host: '10.76.24.87' (Got an error reading communication packets) 2024-06-13 0:20:14 31839722 [Warning] Aborted connection 31839722 to db: 'aaadb' user: 'alepoaaa' host: '10.76.24.87' (Got an error reading communication packets) 2024-06-13 0:20:14 31839720 [Warning] Aborted connection 31839720 to db: 'aaadb' user: 'alepoaaa' host: '10.76.24.87' (Got an error reading communication packets) 2024-06-13 0:20:14 31839721 [Warning] Aborted connection 31839721 to db: 'aaadb' user: 'alepoaaa' host: '10.76.24.87' (Got an error reading communication packets) 2024-06-13 0:20:14 31839719 [Warning] Aborted connection 31839719 to db: 'aaadb' user: 'alepoaaa' host: '10.76.24.87' (Got an error reading communication packets) 2024-06-13 0:20:14 31839714 [Warning] Aborted connection 31839714 to db: 'aaadb' user: 'alepoaaa' host: '10.76.24.87' (Got an error reading communication packets) 2024-06-13 0:20:14 31839713 [Warning] Aborted connection 31839713 to db: 'aaadb' user: 'alepoaaa' host: '10.76.24.87' (Got an error reading communication packets) 2024-06-13 0:20:14 31839710 [Warning] Aborted connection 31839710 to db: 'aaadb' user: 'alepoaaa' host: '10.76.24.87' (Got an error reading communication packets) 2024-06-13 0:20:14 31839709 [Warning] Aborted connection 31839709 to db: 'aaadb' user: 'alepoaaa' host: '10.76.24.87' (Got an error reading communication packets) 2024-06-13 0:20:14 31839705 [Warning] Aborted connection 31839705 to db: 'aaadb' user: 'alepoaaa' host: '10.76.24.87' (Got an error reading communication packets) 2024-06-13 0:20:14 31839704 [Warning] Aborted connection 31839704 to db: 'aaadb' user: 'alepoaaa' host: '10.76.24.87' (Got an error reading communication packets) 2024-06-13 0:20:14 31839703 [Warning] Aborted connection 31839703 to db: 'aaadb' user: 'alepoaaa' host: '10.76.24.87' (Got an error reading communication packets) 2024-06-13 0:20:14 31839701 [Warning] Aborted connection 31839701 to db: 'aaadb' user: 'alepoaaa' host: '10.76.24.87' (Got an error reading communication packets) 2024-06-13 0:20:14 31839699 [Warning] Aborted connection 31839699 to db: 'aaadb' user: 'alepoaaa' host: '10.76.24.87' (Got an error reading communication packets) 2024-06-13 0:20:14 31839715 [Warning] Aborted connection 31839715 to db: 'aaadb' user: 'alepoaaa' host: '10.76.24.87' (Got an error reading communication packets) 2024-06-13 0:20:14 31839696 [Warning] Aborted connection 31839696 to db: 'aaadb' user: 'alepoaaa' host: '10.76.24.87' (Got an error reading communication packets) 2024-06-13 0:20:14 31839695 [Warning] Aborted connection 31839695 to db: 'aaadb' user: 'alepoaaa' host: '10.76.24.87' (Got an error reading communication packets) 2024-06-13 0:20:14 31839702 [Warning] Aborted connection 31839702 to db: 'aaadb' user: 'alepoaaa' host: '10.76.24.87' (Got an error reading communication packets) 2024-06-13 0:20:14 31839693 [Warning] Aborted connection 31839693 to db: 'aaadb' user: 'alepoaaa' host: '10.76.24.87' (Got an error reading communication packets) 2024-06-13 0:20:14 31839716 [Warning] Aborted connection 31839716 to db: 'aaadb' user: 'alepoaaa' host: '10.76.24.87' (Got an error reading communication packets) 2024-06-13 0:20:14 31839687 [Warning] Aborted connection 31839687 to db: 'aaadb' user: 'alepoaaa' host: '10.76.24.87' (Got an error reading communication packets) 2024-06-13 0:20:14 31839686 [Warning] Aborted connection 31839686 to db: 'aaadb' user: 'alepoaaa' host: '10.76.24.87' (Got an error reading communication packets) 2024-06-13 0:20:14 31839698 [Warning] Aborted connection 31839698 to db: 'aaadb' user: 'alepoaaa' host: '10.76.24.87' (Got an error reading communication packets) 2024-06-13 0:20:14 31839682 [Warning] Aborted connection 31839682 to db: 'aaadb' user: 'alepoaaa' host: '10.76.24.87' (Got an error reading communication packets) 2024-06-13 0:20:14 31839681 [Warning] Aborted connection 31839681 to db: 'aaadb' user: 'alepoaaa' host: '10.76.24.87' (Got an error reading communication packets) 2024-06-13 0:20:14 31839678 [Warning] Aborted connection 31839678 to db: 'aaadb' user: 'alepoaaa' host: '10.76.24.87' (Got an error reading communication packets) 2024-06-13 0:20:14 31839717 [Warning] Aborted connection 31839717 to db: 'aaadb' user: 'alepoaaa' host: '10.76.24.87' (Got an error reading communication packets) 2024-06-13 0:20:14 31839675 [Warning] Aborted connection 31839675 to db: 'aaadb' user: 'alepoaaa' host: '10.76.24.87' (Got an error reading communication packets) 2024-06-13 0:20:14 31839673 [Warning] Aborted connection 31839673 to db: 'aaadb' user: 'alepoaaa' host: '10.76.24.87' (Got an error reading communication packets) 2024-06-13 0:20:14 31839674 [Warning] Aborted connection 31839674 to db: 'aaadb' user: 'alepoaaa' host: '10.76.24.87' (Got an error reading communication packets) 2024-06-13 0:20:14 31839685 [Warning] Aborted connection 31839685 to db: 'aaadb' user: 'alepoaaa' host: '10.76.24.87' (Got an error reading communication packets) 2024-06-13 0:20:14 31839683 [Warning] Aborted connection 31839683 to db: 'aaadb' user: 'alepoaaa' host: '10.76.24.87' (Got an error reading communication packets) 2024-06-13 0:20:14 31839667 [Warning] Aborted connection 31839667 to db: 'aaadb' user: 'alepoaaa' host: '10.76.24.87' (Got an error reading communication packets) 2024-06-13 0:20:14 31839665 [Warning] Aborted connection 31839665 to db: 'aaadb' user: 'alepoaaa' host: '10.76.24.87' (Got an error reading communication packets) 2024-06-13 0:20:14 31839661 [Warning] Aborted connection 31839661 to db: 'aaadb' user: 'alepoaaa' host: '10.76.24.87' (Got an error reading communication packets) 2024-06-13 0:20:14 31839662 [Warning] Aborted connection 31839662 to db: 'aaadb' user: 'alepoaaa' host: '10.76.24.87' (Got an error reading communication packets) 2024-06-13 0:20:14 31839660 [Warning] Aborted connection 31839660 to db: 'aaadb' user: 'alepoaaa' host: '10.76.24.87' (Got an error reading communication packets) 2024-06-13 0:20:14 31839688 [Warning] Aborted connection 31839688 to db: 'aaadb' user: 'alepoaaa' host: '10.76.24.87' (Got an error reading communication packets) 2024-06-13 0:20:14 31839737 [Warning] Aborted connection 31839737 to db: 'aaadb' user: 'alepoaaa' host: '10.76.24.87' (Got an error reading communication packets) 2024-06-13 0:20:14 31839712 [Warning] Aborted connection 31839712 to db: 'aaadb' user: 'alepoaaa' host: '10.76.24.87' (Got an error reading communication packets) 2024-06-13 0:20:14 31839669 [Warning] Aborted connection 31839669 to db: 'aaadb' user: 'alepoaaa' host: '10.76.24.87' (Got an error reading communication packets) 2024-06-13 0:20:14 31839664 [Warning] Aborted connection 31839664 to db: 'aaadb' user: 'alepoaaa' host: '10.76.24.87' (Got an error reading communication packets) 2024-06-13 0:20:14 31839680 [Warning] Aborted connection 31839680 to db: 'aaadb' user: 'alepoaaa' host: '10.76.24.87' (Got an error reading communication packets) 2024-06-13 0:20:14 31839697 [Warning] Aborted connection 31839697 to db: 'aaadb' user: 'alepoaaa' host: '10.76.24.87' (Got an error reading communication packets) 2024-06-13 0:20:14 31839708 [Warning] Aborted connection 31839708 to db: 'aaadb' user: 'alepoaaa' host: '10.76.24.87' (Got an error reading communication packets) 2024-06-13 0:20:14 31839666 [Warning] Aborted connection 31839666 to db: 'aaadb' user: 'alepoaaa' host: '10.76.24.87' (Got an error reading communication packets) 2024-06-13 0:20:14 31839659 [Warning] Aborted connection 31839659 to db: 'aaadb' user: 'alepoaaa' host: '10.76.24.87' (Got an error reading communication packets) 2024-06-13 0:20:14 31839672 [Warning] Aborted connection 31839672 to db: 'aaadb' user: 'alepoaaa' host: '10.76.24.87' (Got an error reading communication packets) 2024-06-13 0:20:14 31839657 [Warning] Aborted connection 31839657 to db: 'aaadb' user: 'alepoaaa' host: '10.76.24.87' (Got an error reading communication packets) 2024-06-13 0:20:14 31839670 [Warning] Aborted connection 31839670 to db: 'aaadb' user: 'alepoaaa' host: '10.76.24.87' (Got an error reading communication packets) 2024-06-13 0:20:14 31838988 [Warning] Aborted connection 31838988 to db: 'aaadb' user: 'alepoaaa' host: '10.76.24.86' (Got timeout reading communication packets) 2024-06-13 0:20:14 31839012 [Warning] Aborted connection 31839012 to db: 'aaadb' user: 'alepoaaa' host: '10.76.24.86' (Got timeout reading communication packets) 2024-06-13 0:20:14 31840571 [Warning] Aborted connection 31840571 to db: 'aaadb' user: 'alepoaaa' host: '10.76.24.89' (Got timeout reading communication packets) 2024-06-13 0:20:14 31838986 [Warning] Aborted connection 31838986 to db: 'aaadb' user: 'alepoaaa' host: '10.76.24.86' (Got timeout reading communication packets) 2024-06-13 0:20:14 31840630 [Warning] Aborted connection 31840630 to db: 'aaadb' user: 'alepoaaa' host: '10.76.24.89' (Got timeout reading communication packets) 2024-06-13 0:20:14 31840619 [Warning] Aborted connection 31840619 to db: 'aaadb' user: 'alepoaaa' host: '10.76.24.89' (Got timeout reading communication packets) 2024-06-13 0:20:14 31840580 [Warning] Aborted connection 31840580 to db: 'aaadb' user: 'alepoaaa' host: '10.76.24.89' (Got timeout reading communication packets) 2024-06-13 0:20:14 31840596 [Warning] Aborted connection 31840596 to db: 'aaadb' user: 'alepoaaa' host: '10.76.24.89' (Got timeout reading communication packets) 2024-06-13 0:20:14 31840583 [Warning] Aborted connection 31840583 to db: 'aaadb' user: 'alepoaaa' host: '10.76.24.89' (Got timeout reading communication packets) 2024-06-13 0:20:14 31840627 [Warning] Aborted connection 31840627 to db: 'aaadb' user: 'alepoaaa' host: '10.76.24.89' (Got timeout reading communication packets) 2024-06-13 0:20:14 31840599 [Warning] Aborted connection 31840599 to db: 'aaadb' user: 'alepoaaa' host: '10.76.24.89' (Got timeout reading communication packets) 2024-06-13 0:20:14 31840575 [Warning] Aborted connection 31840575 to db: 'aaadb' user: 'alepoaaa' host: '10.76.24.89' (Got timeout reading communication packets) 2024-06-13 0:20:14 31840587 [Warning] Aborted connection 31840587 to db: 'aaadb' user: 'alepoaaa' host: '10.76.24.89' (Got timeout reading communication packets) 2024-06-13 0:20:14 31840620 [Warning] Aborted connection 31840620 to db: 'aaadb' user: 'alepoaaa' host: '10.76.24.89' (Got timeout reading communication packets) 2024-06-13 0:20:14 31840603 [Warning] Aborted connection 31840603 to db: 'aaadb' user: 'alepoaaa' host: '10.76.24.89' (Got timeout reading communication packets) 2024-06-13 0:20:14 31840636 [Warning] Aborted connection 31840636 to db: 'aaadb' user: 'alepoaaa' host: '10.76.24.89' (Got timeout reading communication packets) 2024-06-13 0:20:14 31838959 [Warning] Aborted connection 31838959 to db: 'aaadb' user: 'alepoaaa' host: '10.76.24.86' (Got timeout reading communication packets) 2024-06-13 0:20:14 31839008 [Warning] Aborted connection 31839008 to db: 'aaadb' user: 'alepoaaa' host: '10.76.24.86' (Got timeout reading communication packets) 2024-06-13 0:20:14 31838966 [Warning] Aborted connection 31838966 to db: 'aaadb' user: 'alepoaaa' host: '10.76.24.86' (Got timeout reading communication packets) 2024-06-13 0:20:14 31839011 [Warning] Aborted connection 31839011 to db: 'aaadb' user: 'alepoaaa' host: '10.76.24.86' (Got timeout reading communication packets) 2024-06-13 0:20:14 31841569 [Warning] Aborted connection 31841569 to db: 'aaadb' user: 'alepoaaa' host: '10.76.24.92' (Got timeout reading communication packets) 2024-06-13 0:20:14 31841553 [Warning] Aborted connection 31841553 to db: 'aaadb' user: 'alepoaaa' host: '10.76.24.92' (Got timeout reading communication packets) 2024-06-13 0:20:15 31838980 [Warning] Aborted connection 31838980 to db: 'aaadb' user: 'alepoaaa' host: '10.76.24.86' (Got timeout reading communication packets) 2024-06-13 0:20:15 31840589 [Warning] Aborted connection 31840589 to db: 'aaadb' user: 'alepoaaa' host: '10.76.24.89' (Got timeout reading communication packets) 2024-06-13 0:20:15 31838989 [Warning] Aborted connection 31838989 to db: 'aaadb' user: 'alepoaaa' host: '10.76.24.86' (Got timeout reading communication packets) 2024-06-13 0:20:15 31840626 [Warning] Aborted connection 31840626 to db: 'aaadb' user: 'alepoaaa' host: '10.76.24.89' (Got timeout reading communication packets) 2024-06-13 0:20:15 31840604 [Warning] Aborted connection 31840604 to db: 'aaadb' user: 'alepoaaa' host: '10.76.24.89' (Got timeout reading communication packets) 2024-06-13 0:20:15 31841524 [Warning] Aborted connection 31841524 to db: 'aaadb' user: 'alepoaaa' host: '10.76.24.92' (Got timeout reading communication packets) 2024-06-13 0:20:15 31839724 [Warning] Aborted connection 31839724 to db: 'aaadb' user: 'alepoaaa' host: '10.76.24.87' (Got timeout reading communication packets) 2024-06-13 0:20:15 31840616 [Warning] Aborted connection 31840616 to db: 'aaadb' user: 'alepoaaa' host: '10.76.24.89' (Got timeout reading communication packets) 2024-06-13 0:20:15 31841533 [Warning] Aborted connection 31841533 to db: 'aaadb' user: 'alepoaaa' host: '10.76.24.92' (Got timeout reading communication packets) 2024-06-13 0:20:15 31840155 [Warning] Aborted connection 31840155 to db: 'aaadb' user: 'alepoaaa' host: '10.76.24.88' (Got timeout reading communication packets) 2024-06-13 0:20:15 31841540 [Warning] Aborted connection 31841540 to db: 'aaadb' user: 'alepoaaa' host: '10.76.24.92' (Got timeout reading communication packets) 2024-06-13 0:20:15 31839707 [Warning] Aborted connection 31839707 to db: 'aaadb' user: 'alepoaaa' host: '10.76.24.87' (Got timeout reading communication packets) 2024-06-13 0:20:15 31838991 [Warning] Aborted connection 31838991 to db: 'aaadb' user: 'alepoaaa' host: '10.76.24.86' (Got timeout reading communication packets) 2024-06-13 0:20:15 31838997 [Warning] Aborted connection 31838997 to db: 'aaadb' user: 'alepoaaa' host: '10.76.24.86' (Got timeout reading communication packets) 2024-06-13 0:20:15 31838979 [Warning] Aborted connection 31838979 to db: 'aaadb' user: 'alepoaaa' host: '10.76.24.86' (Got timeout reading communication packets) 2024-06-13 0:20:15 31839010 [Warning] Aborted connection 31839010 to db: 'aaadb' user: 'alepoaaa' host: '10.76.24.86' (Got timeout reading communication packets) 2024-06-13 0:20:15 31839825 [Warning] Aborted connection 31839825 to db: 'aaadb' user: 'alepoaaa' host: '10.76.24.86' (Got timeout reading communication packets) 2024-06-13 0:20:15 31839003 [Warning] Aborted connection 31839003 to db: 'aaadb' user: 'alepoaaa' host: '10.76.24.86' (Got timeout reading communication packets) 2024-06-13 0:20:15 31838974 [Warning] Aborted connection 31838974 to db: 'aaadb' user: 'alepoaaa' host: '10.76.24.86' (Got timeout reading communication packets) 2024-06-13 0:20:15 31839001 [Warning] Aborted connection 31839001 to db: 'aaadb' user: 'alepoaaa' host: '10.76.24.86' (Got timeout reading communication packets) 2024-06-13 0:20:15 31839004 [Warning] Aborted connection 31839004 to db: 'aaadb' user: 'alepoaaa' host: '10.76.24.86' (Got timeout reading communication packets) 2024-06-13 0:20:15 31839684 [Warning] Aborted connection 31839684 to db: 'aaadb' user: 'alepoaaa' host: '10.76.24.87' (Got timeout reading communication packets) 2024-06-13 0:20:15 31841568 [Warning] Aborted connection 31841568 to db: 'aaadb' user: 'alepoaaa' host: '10.76.24.92' (Got timeout reading communication packets) 2024-06-13 0:20:15 31841541 [Warning] Aborted connection 31841541 to db: 'aaadb' user: 'alepoaaa' host: '10.76.24.92' (Got timeout reading communication packets) 2024-06-13 0:20:15 31839689 [Warning] Aborted connection 31839689 to db: 'aaadb' user: 'alepoaaa' host: '10.76.24.87' (Got timeout reading communication packets) 2024-06-13 0:20:15 31841581 [Warning] Aborted connection 31841581 to db: 'aaadb' user: 'alepoaaa' host: '10.76.24.92' (Got timeout reading communication packets) 2024-06-13 0:20:15 31841530 [Warning] Aborted connection 31841530 to db: 'aaadb' user: 'alepoaaa' host: '10.76.24.92' (Got timeout reading communication packets) 2024-06-13 0:20:15 31841167 [Warning] Aborted connection 31841167 to db: 'aaadb' user: 'alepoaaa' host: '10.76.24.91' (Got timeout reading communication packets) 2024-06-13 0:20:15 31841146 [Warning] Aborted connection 31841146 to db: 'aaadb' user: 'alepoaaa' host: '10.76.24.91' (Got timeout reading communication packets) 2024-06-13 0:20:15 31841116 [Warning] Aborted connection 31841116 to db: 'aaadb' user: 'alepoaaa' host: '10.76.24.91' (Got timeout reading communication packets) 2024-06-13 0:20:15 31839700 [Warning] Aborted connection 31839700 to db: 'aaadb' user: 'alepoaaa' host: '10.76.24.87' (Got timeout reading communication packets) 2024-06-13 0:20:15 31839706 [Warning] Aborted connection 31839706 to db: 'aaadb' user: 'alepoaaa' host: '10.76.24.87' (Got timeout reading communication packets) 2024-06-13 0:20:15 31839711 [Warning] Aborted connection 31839711 to db: 'aaadb' user: 'alepoaaa' host: '10.76.24.87' (Got timeout reading communication packets) 2024-06-13 0:20:15 31839676 [Warning] Aborted connection 31839676 to db: 'aaadb' user: 'alepoaaa' host: '10.76.24.87' (Got timeout reading communication packets) 2024-06-13 0:20:15 31841557 [Warning] Aborted connection 31841557 to db: 'aaadb' user: 'alepoaaa' host: '10.76.24.92' (Got timeout reading communication packets) 2024-06-13 0:20:15 31841548 [Warning] Aborted connection 31841548 to db: 'aaadb' user: 'alepoaaa' host: '10.76.24.92' (Got timeout reading communication packets) 2024-06-13 0:20:15 31839677 [Warning] Aborted connection 31839677 to db: 'aaadb' user: 'alepoaaa' host: '10.76.24.87' (Got timeout reading communication packets) 2024-06-13 0:20:15 31841129 [Warning] Aborted connection 31841129 to db: 'aaadb' user: 'alepoaaa' host: '10.76.24.91' (Got timeout reading communication packets) 2024-06-13 0:20:15 31841155 [Warning] Aborted connection 31841155 to db: 'aaadb' user: 'alepoaaa' host: '10.76.24.91' (Got timeout reading communication packets) 2024-06-13 0:20:15 31841163 [Warning] Aborted connection 31841163 to db: 'aaadb' user: 'alepoaaa' host: '10.76.24.91' (Got timeout reading communication packets) 2024-06-13 0:20:15 31841173 [Warning] Aborted connection 31841173 to db: 'aaadb' user: 'alepoaaa' host: '10.76.24.91' (Got timeout reading communication packets) 2024-06-13 0:20:15 31841122 [Warning] Aborted connection 31841122 to db: 'aaadb' user: 'alepoaaa' host: '10.76.24.91' (Got timeout reading communication packets) 2024-06-13 0:20:15 31841153 [Warning] Aborted connection 31841153 to db: 'aaadb' user: 'alepoaaa' host: '10.76.24.91' (Got timeout reading communication packets) 2024-06-13 0:20:15 31841138 [Warning] Aborted connection 31841138 to db: 'aaadb' user: 'alepoaaa' host: '10.76.24.91' (Got timeout reading communication packets) 2024-06-13 0:20:15 31841171 [Warning] Aborted connection 31841171 to db: 'aaadb' user: 'alepoaaa' host: '10.76.24.91' (Got timeout reading communication packets) 2024-06-13 0:20:15 31841143 [Warning] Aborted connection 31841143 to db: 'aaadb' user: 'alepoaaa' host: '10.76.24.91' (Got timeout reading communication packets) 2024-06-13 0:20:15 31841118 [Warning] Aborted connection 31841118 to db: 'aaadb' user: 'alepoaaa' host: '10.76.24.91' (Got timeout reading communication packets) 2024-06-13 0:20:15 31841127 [Warning] Aborted connection 31841127 to db: 'aaadb' user: 'alepoaaa' host: '10.76.24.91' (Got timeout reading communication packets) 2024-06-13 0:20:15 31839694 [Warning] Aborted connection 31839694 to db: 'aaadb' user: 'alepoaaa' host: '10.76.24.87' (Got timeout reading communication packets) 2024-06-13 0:20:15 31841147 [Warning] Aborted connection 31841147 to db: 'aaadb' user: 'alepoaaa' host: '10.76.24.91' (Got timeout reading communication packets) 2024-06-13 0:20:15 31841160 [Warning] Aborted connection 31841160 to db: 'aaadb' user: 'alepoaaa' host: '10.76.24.91' (Got timeout reading communication packets) 2024-06-13 0:20:15 31841132 [Warning] Aborted connection 31841132 to db: 'aaadb' user: 'alepoaaa' host: '10.76.24.91' (Got timeout reading communication packets) 2024-06-13 0:20:15 31841120 [Warning] Aborted connection 31841120 to db: 'aaadb' user: 'alepoaaa' host: '10.76.24.91' (Got timeout reading communication packets) 2024-06-13 0:20:15 31841114 [Warning] Aborted connection 31841114 to db: 'aaadb' user: 'alepoaaa' host: '10.76.24.91' (Got timeout reading communication packets) 2024-06-13 0:20:15 31839656 [Warning] Aborted connection 31839656 to db: 'aaadb' user: 'alepoaaa' host: '10.76.24.87' (Got timeout reading communication packets) 2024-06-13 0:20:15 31840178 [Warning] Aborted connection 31840178 to db: 'aaadb' user: 'alepoaaa' host: '10.76.24.88' (Got timeout reading communication packets) 2024-06-13 0:20:15 31839671 [Warning] Aborted connection 31839671 to db: 'aaadb' user: 'alepoaaa' host: '10.76.24.87' (Got timeout reading communication packets) 2024-06-13 0:20:15 31839679 [Warning] Aborted connection 31839679 to db: 'aaadb' user: 'alepoaaa' host: '10.76.24.87' (Got timeout reading communication packets) 2024-06-13 0:20:15 31839718 [Warning] Aborted connection 31839718 to db: 'aaadb' user: 'alepoaaa' host: '10.76.24.87' (Got timeout reading communication packets) 2024-06-13 0:20:15 31840153 [Warning] Aborted connection 31840153 to db: 'aaadb' user: 'alepoaaa' host: '10.76.24.88' (Got timeout reading communication packets) 2024-06-13 0:20:15 31840180 [Warning] Aborted connection 31840180 to db: 'aaadb' user: 'alepoaaa' host: '10.76.24.88' (Got timeout reading communication packets) 2024-06-13 0:20:15 31840172 [Warning] Aborted connection 31840172 to db: 'aaadb' user: 'alepoaaa' host: '10.76.24.88' (Got timeout reading communication packets) 2024-06-13 0:20:15 31840181 [Warning] Aborted connection 31840181 to db: 'aaadb' user: 'alepoaaa' host: '10.76.24.88' (Got timeout reading communication packets) 2024-06-13 0:20:15 31840197 [Warning] Aborted connection 31840197 to db: 'aaadb' user: 'alepoaaa' host: '10.76.24.88' (Got timeout reading communication packets) 2024-06-13 0:20:15 31840149 [Warning] Aborted connection 31840149 to db: 'aaadb' user: 'alepoaaa' host: '10.76.24.88' (Got timeout reading communication packets) 2024-06-13 0:20:15 31840157 [Warning] Aborted connection 31840157 to db: 'aaadb' user: 'alepoaaa' host: '10.76.24.88' (Got timeout reading communication packets) 2024-06-13 0:20:15 31840164 [Warning] Aborted connection 31840164 to db: 'aaadb' user: 'alepoaaa' host: '10.76.24.88' (Got timeout reading communication packets) 2024-06-13 0:20:15 31840175 [Warning] Aborted connection 31840175 to db: 'aaadb' user: 'alepoaaa' host: '10.76.24.88' (Got timeout reading communication packets) 2024-06-13 0:20:15 31840191 [Warning] Aborted connection 31840191 to db: 'aaadb' user: 'alepoaaa' host: '10.76.24.88' (Got timeout reading communication packets) 2024-06-13 0:20:15 31840160 [Warning] Aborted connection 31840160 to db: 'aaadb' user: 'alepoaaa' host: '10.76.24.88' (Got timeout reading communication packets) 2024-06-13 0:20:15 31840183 [Warning] Aborted connection 31840183 to db: 'aaadb' user: 'alepoaaa' host: '10.76.24.88' (Got timeout reading communication packets) 2024-06-13 0:20:15 31840167 [Warning] Aborted connection 31840167 to db: 'aaadb' user: 'alepoaaa' host: '10.76.24.88' (Got timeout reading communication packets) 2024-06-13 0:20:15 31857646 [Warning] Aborted connection 31857646 to db: 'aaadb' user: 'alepoaaa' host: '10.76.24.88' (Got timeout reading communication packets) 2024-06-13 0:20:15 31840194 [Warning] Aborted connection 31840194 to db: 'aaadb' user: 'alepoaaa' host: '10.76.24.88' (Got timeout reading communication packets) 2024-06-13 0:20:15 31841566 [Warning] Aborted connection 31841566 to db: 'aaadb' user: 'alepoaaa' host: '10.76.24.92' (Got timeout reading communication packets) 2024-06-13 0:20:15 31841554 [Warning] Aborted connection 31841554 to db: 'aaadb' user: 'alepoaaa' host: '10.76.24.92' (Got timeout reading communication packets) 2024-06-13 0:20:15 31841574 [Warning] Aborted connection 31841574 to db: 'aaadb' user: 'alepoaaa' host: '10.76.24.92' (Got timeout reading communication packets) 2024-06-13 0:20:15 31841526 [Warning] Aborted connection 31841526 to db: 'aaadb' user: 'alepoaaa' host: '10.76.24.92' (Got timeout reading communication packets) 2024-06-13 0:20:15 31841537 [Warning] Aborted connection 31841537 to db: 'aaadb' user: 'alepoaaa' host: '10.76.24.92' (Got timeout reading communication packets) 2024-06-13 0:20:15 31841517 [Warning] Aborted connection 31841517 to db: 'aaadb' user: 'alepoaaa' host: '10.76.24.92' (Got timeout reading communication packets) 2024-06-13 0:20:15 31839691 [Warning] Aborted connection 31839691 to db: 'aaadb' user: 'alepoaaa' host: '10.76.24.87' (Got timeout reading communication packets) 2024-06-13 0:20:15 31839658 [Warning] Aborted connection 31839658 to db: 'aaadb' user: 'alepoaaa' host: '10.76.24.87' (Got timeout reading communication packets) 2024-06-13 0:20:15 31839692 [Warning] Aborted connection 31839692 to db: 'aaadb' user: 'alepoaaa' host: '10.76.24.87' (Got timeout reading communication packets) 2024-06-13 0:20:15 31839690 [Warning] Aborted connection 31839690 to db: 'aaadb' user: 'alepoaaa' host: '10.76.24.87' (Got timeout reading communication packets) 2024-06-13 0:20:18 31840635 [Warning] Aborted connection 31840635 to db: 'aaadb' user: 'alepoaaa' host: '10.76.24.89' (Got an error writing communication packets) 2024-06-13 0:20:18 31838985 [Warning] Aborted connection 31838985 to db: 'aaadb' user: 'alepoaaa' host: '10.76.24.86' (Got an error writing communication packets) 2024-06-13 0:20:18 31841110 [Warning] Aborted connection 31841110 to db: 'aaadb' user: 'alepoaaa' host: '10.76.24.91' (Got an error writing communication packets) 2024-06-13 0:20:18 31840573 [Warning] Aborted connection 31840573 to db: 'aaadb' user: 'alepoaaa' host: '10.76.24.89' (Got an error writing communication packets) 2024-06-13 0:20:18 31840214 [Warning] Aborted connection 31840214 to db: 'aaadb' user: 'alepoaaa' host: '10.76.24.88' (Got an error writing communication packets) 2024-06-13 0:20:18 31838958 [Warning] Aborted connection 31838958 to db: 'aaadb' user: 'alepoaaa' host: '10.76.24.86' (Got an error writing communication packets) 2024-06-13 0:20:18 31840195 [Warning] Aborted connection 31840195 to db: 'aaadb' user: 'alepoaaa' host: '10.76.24.88' (Got an error writing communication packets) 2024-06-13 0:20:18 31839663 [Warning] Aborted connection 31839663 to db: 'aaadb' user: 'alepoaaa' host: '10.76.24.87' (Got an error writing communication packets) 2024-06-13 0:20:18 31840177 [Warning] Aborted connection 31840177 to db: 'aaadb' user: 'alepoaaa' host: '10.76.24.88' (Got an error writing communication packets) 2024-06-13 0:20:18 31839668 [Warning] Aborted connection 31839668 to db: 'aaadb' user: 'alepoaaa' host: '10.76.24.87' (Got an error writing communication packets) 2024-06-13 0:20:18 31840574 [Warning] Aborted connection 31840574 to db: 'aaadb' user: 'alepoaaa' host: '10.76.24.89' (Got an error writing communication packets) 2024-06-13 0:20:18 31841515 [Warning] Aborted connection 31841515 to db: 'aaadb' user: 'alepoaaa' host: '10.76.24.92' (Got an error writing communication packets) 2024-06-13 0:20:18 31841527 [Warning] Aborted connection 31841527 to db: 'aaadb' user: 'alepoaaa' host: '10.76.24.92' (Got an error writing communication packets) 2024-06-13 0:20:18 31841564 [Warning] Aborted connection 31841564 to db: 'aaadb' user: 'alepoaaa' host: '10.76.24.92' (Got an error writing communication packets) 2024-06-13 0:40:19 5 [Note] Master 's-db3': Error reading relay log event: slave SQL thread was killed 2024-06-13 0:40:19 5 [Note] Master 's-db3': Slave SQL thread exiting, replication stopped in log 'FIRST' at position 0, master: :3306 2024-06-13 0:40:19 26 [Note] Slave SQL thread exiting, replication stopped in log 'db2-binary.152573' at position 64145953, master: 10.76.24.77:3306 2024-06-13 0:40:19 25 [Note] Slave I/O thread exiting, read up to log 'db2-binary.152573', position 64191013, master 10.76.24.77:3306 2024-06-13 0:40:19 21 [Note] Master 's-db2': Error reading relay log event: slave SQL thread was killed 2024-06-13 0:40:19 21 [Note] Master 's-db2': Slave SQL thread exiting, replication stopped in log 'FIRST' at position 0, master: :3306 2024-06-13 0:40:19 34087473 [Note] Master 's-db4': Error reading relay log event: slave SQL thread was killed 2024-06-13 0:40:19 34087473 [Note] Master 's-db4': Slave SQL thread exiting, replication stopped in log 'db4-binary.125316' at position 148106186, master: 10.76.25.11:3306 2024-06-13 0:40:19 23 [Note] Master 's-db5': Error reading relay log event: slave SQL thread was killed 2024-06-13 0:40:19 23 [Note] Master 's-db5': Slave SQL thread exiting, replication stopped in log 'FIRST' at position 0, master: :3306 2024-06-13 0:41:12 1223 [Warning] Aborted connection 1223 to db: 'unconnected' user: 'gtid' host: '10.76.25.11' (Got an error writing communication packets) 2024-06-13 0:51:09 34107589 [Note] Start binlog_dump to slave_server(4), pos(db1-binary.151876, 93427362), using_gtid(0), gtid('') 2024-06-13 0:51:51 34107589 [Warning] Aborted connection 34107589 to db: 'unconnected' user: 'gtid' host: '10.76.25.11' (Got an error writing communication packets) 2024-06-13 1:05:37 31570250 [Warning] Aborted connection 31570250 to db: 'unconnected' user: 'gtid' host: '10.76.24.77' (Got an error writing communication packets) 2024-06-13 2:43:56 34115803 [Note] Start binlog_dump to slave_server(4), pos(db1-binary.151870, 89613966), using_gtid(0), gtid('') 2024-06-13 2:52:26 34115803 [Warning] Aborted connection 34115803 to db: 'unconnected' user: 'gtid' host: '10.76.25.11' (Got an error writing communication packets) 2024-06-13 2:52:52 34116449 [Note] Start binlog_dump to slave_server(4), pos(db1-binary.151936, 56022692), using_gtid(0), gtid('') 2024-06-13 3:08:08 34116449 [Warning] Aborted connection 34116449 to db: 'unconnected' user: 'gtid' host: '10.76.25.11' (Got an error writing communication packets) 2024-06-13 3:10:40 34095256 [Note] Master connection name: '' Master_info_file: 'master.info' Relay_info_file: 'relay-log.info' 2024-06-13 3:10:40 34095256 [Note] 'CHANGE MASTER TO executed'. Previous state master_host='10.76.24.77', master_port='3306', master_log_file='db2-binary.152573', master_log_pos='64191013'. New state master_host='10.76.24.77', master_port='3306', master_log_file='db2-binary.152573', master_log_pos='64145953'. 2024-06-13 3:10:45 34117730 [Note] Slave I/O thread: Start asynchronous replication to master 'gtid@10.76.24.77:3306' in log 'db2-binary.152573' at position 64145953 2024-06-13 3:10:45 34117730 [Note] Slave I/O thread: connected to master 'gtid@10.76.24.77:3306',replication started in log 'db2-binary.152573' at position 64145953 2024-06-13 3:10:45 34117731 [Note] Slave SQL thread initialized, starting replication in log 'db2-binary.152573' at position 64145953, relay log './db1-relay.000001' position: 4 2024-06-13 3:11:11 34095256 [Note] Master connection name: 's-db4' Master_info_file: 'master-s@002ddb4.info' Relay_info_file: 'relay-log-s@002ddb4.info' 2024-06-13 3:11:11 34095256 [Note] 'CHANGE MASTER TO executed'. Previous state master_host='10.76.25.11', master_port='3306', master_log_file='db4-binary.125316', master_log_pos='148106186'. New state master_host='10.76.25.11', master_port='3306', master_log_file='db4-binary.129268', master_log_pos='133764218'. 2024-06-13 3:11:18 34095256 [Note] Master connection name: 's-db4' Master_info_file: 'master-s@002ddb4.info' Relay_info_file: 'relay-log-s@002ddb4.info' 2024-06-13 3:11:18 34095256 [Note] 'CHANGE MASTER TO executed'. Previous state master_host='10.76.25.11', master_port='3306', master_log_file='db4-binary.129268', master_log_pos='133764218'. New state master_host='10.76.25.11', master_port='3306', master_log_file='db4-binary.129268', master_log_pos='133764218'. 2024-06-13 3:11:29 34119351 [Note] Master 's-db4': Slave I/O thread: Start asynchronous replication to master 'gtid@10.76.25.11:3306' in log 'db4-binary.129268' at position 133764218 2024-06-13 3:11:29 34119352 [Note] Master 's-db4': Slave SQL thread initialized, starting replication in log 'db4-binary.129268' at position 133764218, relay log './db1-relay-s@002ddb4.000001' position: 4 2024-06-13 3:11:30 34119351 [Note] Master 's-db4': Slave I/O thread: connected to master 'gtid@10.76.25.11:3306',replication started in log 'db4-binary.129268' at position 133764218 2024-06-13 3:13:10 34119477 [Note] Start binlog_dump to slave_server(2), pos(db1-binary.151887, 155487382), using_gtid(0), gtid('') 2024-06-13 3:18:02 34130664 [Note] Start binlog_dump to slave_server(4), pos(db1-binary.151943, 94718593), using_gtid(0), gtid('') 2024-06-13 4:01:56 1218 [Warning] Aborted connection 1218 to db: 'unconnected' user: 'replication' host: '10.76.24.83' (Got an error writing communication packets) 240613 4:26:02 [ERROR] mysqld got signal 11 ; 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.11.5-MariaDB-log source revision: 7875294b6b74b53dd3aaa723e6cc103d2bb47b2c key_buffer_size=67108864 read_buffer_size=131072 max_used_connections=471 max_threads=802 thread_count=462 It is possible that mysqld could use up to key_buffer_size + (read_buffer_size + sort_buffer_size)*max_threads = 1831964 K bytes of memory Hope that's ok; if not, decrease some variables in the equation. Thread pointer: 0x7f1d9c878218 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 = 0x7f1f28a20b98 thread_stack 0x49000 /usr/sbin/mariadbd(my_print_stacktrace+0x2e)[0x56535226012e] mysys/stacktrace.c:216(my_print_stacktrace)[0x565351d595b5] /lib64/libpthread.so.0(+0x12cf0)[0x7f6e0724ccf0] sql/sql_yacc.yy:9072(MYSQLparse(THD*))[0x565351cdf117] sql/sql_parse.cc:10394(parse_sql(THD*, Parser_state*, Object_creation_ctx*, bool))[0x565351b0f81a] sql/sql_parse.cc:7988(mysql_parse(THD*, char*, unsigned int, Parser_state*))[0x565351b0ba1a] sql/sql_parse.cc:1896(dispatch_command(enum_server_command, THD*, char*, unsigned int, bool))[0x565351b156e6] sql/sql_parse.cc:1407(do_command(THD*, bool))[0x565351b16dab] sql/sql_connect.cc:1416(do_handle_one_connection(CONNECT*, bool))[0x565351c2a977] sql/sql_connect.cc:1318(handle_one_connection)[0x565351c2acbd] perfschema/pfs.cc:2204(MyCTX_nopad::finish(unsigned char*, unsigned int*))[0x565351f60c9d] /lib64/libpthread.so.0(+0x81ca)[0x7f6e072421ca] /lib64/libc.so.6(clone+0x43)[0x7f6e06592e73] Trying to get some variables. Some pointers may be invalid and cause the dump to abort. Query (0x7f1d9c01ee00): Select Users.UserIndex, UserID, Users.Password, GroupName, PasswordSource, UserService, UserIP, FilterName, UserActive, Users.StartDate, UserExpiryDate, CallBackNumber, CallerID, Lockout, Users.PasswordEncryptionMethod, MaxUserSessions, SkipPasswordCheck, HotlineStatus, BarringStatus, BarringReason, MaxVolumeCap, AllowedAccessTypes, CopyRadiusRequests, SubnetIP, SubnetMask, CIDR, CustomField1, CustomField2, CustomField3, CustomField4, CustomField5, CustomNumField1, CustomNumField2, CustomNumField3, CustomNumField4, CustomNumField5, SessionLimit, UserTokens, FirstLogon, FramedInterfaceId, FramedIPv6Prefix, PeriodicTimeUsage, PeriodicVolumeUsage, TimeUsageTriggerThresholds, VolumeUsageTriggerThresholds, CustomReplylist, CustomChecklist, BillingSystemCorrelationId, ChargingSystemCorrelationId, ChargingMode, LockOutTime, LockOutCount, Users.PseudoIdentity, CustomDate1, CustomDate2, CustomDate3, CustomDate4, CustomDate5, CustomField6, CustomField7, CustomField8, CustomField9, CustomField10, RestrictedLocations, MaxTimeCap, PortId, CustomNumField6, CustomNumField7, CustomNumField8, CustomNumField9, CustomNumField10,SpeedMapName,UserIPv6,NetworkService, CustomField11,CustomField12,CustomField13,CustomField14,CustomField15 , PasswordDate From Users Where UserID = '03202475657' Connection ID (thread ID): 34092255 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,hash_join_cardinality=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 unlimited unlimited bytes Max resident set unlimited unlimited bytes Max processes 2061710 2061710 processes Max open files 32768 32768 files Max locked memory 65536 65536 bytes Max address space unlimited unlimited bytes Max file locks unlimited unlimited locks Max pending signals 2061710 2061710 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: /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 2024-06-13 4:26:59 0 [Note] Starting MariaDB 10.11.5-MariaDB-log source revision 7875294b6b74b53dd3aaa723e6cc103d2bb47b2c as process 783288 2024-06-13 4:26:59 0 [Note] InnoDB: Compressed tables use zlib 1.2.11 2024-06-13 4:26:59 0 [Note] InnoDB: Number of transaction pools: 1 2024-06-13 4:26:59 0 [Note] InnoDB: Using crc32 + pclmulqdq instructions 2024-06-13 4:26:59 0 [Note] InnoDB: Using Linux native AIO 2024-06-13 4:26:59 0 [Note] InnoDB: Initializing buffer pool, total size = 300.000GiB, chunk size = 4.688GiB 2024-06-13 4:27:00 0 [Note] InnoDB: Completed initialization of buffer pool 2024-06-13 4:27:00 0 [Note] InnoDB: File system buffers for log disabled (block size=512 bytes) 2024-06-13 4:27:03 0 [Warning] InnoDB: 3873136640 bytes should have been read at 421830656 from (unknown file), but got only 2147479552. Retrying. 2024-06-13 4:27:05 0 [Note] InnoDB: Starting crash recovery from checkpoint LSN=34313048447010 2024-06-13 4:27:15 0 [Note] InnoDB: Parsed redo log up to LSN=34314009658797; to recover: 148565 pages 2024-06-13 4:27:30 0 [Note] InnoDB: Parsed redo log up to LSN=34315391254907; to recover: 164290 pages 2024-06-13 4:27:36 0 [Note] InnoDB: End of log at LSN=34316059618383 2024-06-13 4:27:39 0 [Note] InnoDB: To recover: 183472 pages 2024-06-13 4:27:51 0 [Note] InnoDB: Last binlog file './db1-binary.151978', position 897168 2024-06-13 4:27:51 0 [Note] InnoDB: 128 rollback segments are active. 2024-06-13 4:27:51 0 [Note] InnoDB: Removed temporary tablespace data file: "./ibtmp1" 2024-06-13 4:27:51 0 [Note] InnoDB: Setting file './ibtmp1' size to 12.000MiB. Physically writing the file full; Please wait ... 2024-06-13 4:27:51 0 [Note] InnoDB: File './ibtmp1' size is now 12.000MiB. 2024-06-13 4:27:51 0 [Note] InnoDB: log sequence number 34316059618383; transaction id 108098313606 2024-06-13 4:27:51 0 [Note] InnoDB: Loading buffer pool(s) from /var/lib/mysql/ib_buffer_pool 2024-06-13 4:27:51 0 [Note] Plugin 'FEEDBACK' is disabled. 2024-06-13 4:27:51 0 [Warning] 'thread-concurrency' was removed. It does nothing now and exists only for compatibility with old my.cnf files. 2024-06-13 4:27:51 0 [Warning] 'innodb-thread-concurrency' was removed. It does nothing now and exists only for compatibility with old my.cnf files. 2024-06-13 4:27:51 0 [Warning] 'innodb-log-files-in-group' was removed. It does nothing now and exists only for compatibility with old my.cnf files. 2024-06-13 4:27:51 0 [Note] Recovering after a crash using db1-binary 2024-06-13 4:27:51 0 [Note] Starting table crash recovery... 2024-06-13 4:27:51 0 [Note] Crash table recovery finished. 2024-06-13 4:27:51 0 [Note] Server socket created on IP: '0.0.0.0'. 2024-06-13 4:27:51 0 [Note] Server socket created on IP: '::'. 2024-06-13 4:27:51 0 [Warning] 'user' entry '@alepo-db2-ilb' ignored in --skip-name-resolve mode. 2024-06-13 4:27:51 0 [Warning] 'user' entry 'root@localhost.localdomain' ignored in --skip-name-resolve mode. 2024-06-13 4:27:51 0 [Warning] 'proxies_priv' entry '@% root@alepo-db2-ilb' ignored in --skip-name-resolve mode. 2024-06-13 4:27:52 3 [Note] Reading Master_info: 'master-s@002ddb3.info' Relay_info:'relay-log-s@002ddb3.info' 2024-06-13 4:27:52 3 [Note] Initialized Master_info from 'master-s@002ddb3.info' 2024-06-13 4:27:52 4 [Note] Master 's-db3': Slave I/O thread: Start asynchronous replication to master '@:3306' in log '' at position 4 2024-06-13 4:27:52 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 2024-06-13 4:27:52 4 [Note] Master 's-db3': Slave I/O thread killed while connecting to master 2024-06-13 4:27:52 4 [Note] Master 's-db3': Slave I/O thread exiting, read up to log 'FIRST', position 4, master :3306 2024-06-13 4:27:52 3 [Note] Started replication for 's-db3' 2024-06-13 4:27:52 5 [Note] Master 's-db3': Slave SQL thread initialized, starting replication in log 'FIRST' at position 0, relay log './db1-relay-s@002ddb3.000019' position: 4 2024-06-13 4:27:52 3 [Note] Reading Master_info: 'master-s@002ddb4.info' Relay_info:'relay-log-s@002ddb4.info' 2024-06-13 4:27:52 3 [Note] Initialized Master_info from 'master-s@002ddb4.info' 2024-06-13 4:27:52 18 [Note] Master 's-db4': Slave I/O thread: Start asynchronous replication to master 'gtid@10.76.25.11:3306' in log 'db4-binary.129303' at position 43544886 2024-06-13 4:27:52 3 [Note] Started replication for 's-db4' 2024-06-13 4:27:52 19 [Note] Master 's-db4': Slave SQL thread initialized, starting replication in log 'db4-binary.129303' at position 4, relay log './db1-relay-s@002ddb4.000071' position: 304 2024-06-13 4:27:52 3 [Note] Reading Master_info: 'master-s@002ddb2.info' Relay_info:'relay-log-s@002ddb2.info' 2024-06-13 4:27:52 18 [Note] Master 's-db4': Slave I/O thread: connected to master 'gtid@10.76.25.11:3306',replication started in log 'db4-binary.129303' at position 43544886 2024-06-13 4:27:52 3 [Note] Initialized Master_info from 'master-s@002ddb2.info' 2024-06-13 4:27:52 20 [Note] Master 's-db2': Slave I/O thread: Start asynchronous replication to master '@:3306' in log '' at position 4 2024-06-13 4:27:52 20 [ERROR] Master 's-db2': Slave I/O: Fatal error: Invalid (empty) username when attempting to connect to the master server. Connection attempt terminated. Internal MariaDB error code: 1593 2024-06-13 4:27:52 20 [Note] Master 's-db2': Slave I/O thread killed while connecting to master 2024-06-13 4:27:52 20 [Note] Master 's-db2': Slave I/O thread exiting, read up to log 'FIRST', position 4, master :3306 2024-06-13 4:27:52 3 [Note] Started replication for 's-db2' 2024-06-13 4:27:52 21 [Note] Master 's-db2': Slave SQL thread initialized, starting replication in log 'FIRST' at position 0, relay log './db1-relay-s@002ddb2.000018' position: 4 2024-06-13 4:27:52 3 [Note] Reading Master_info: 'master-s@002ddb5.info' Relay_info:'relay-log-s@002ddb5.info' 2024-06-13 4:27:52 3 [Note] Initialized Master_info from 'master-s@002ddb5.info' 2024-06-13 4:27:52 22 [Note] Master 's-db5': Slave I/O thread: Start asynchronous replication to master '@:3306' in log '' at position 4 2024-06-13 4:27:52 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 2024-06-13 4:27:52 22 [Note] Master 's-db5': Slave I/O thread killed while connecting to master 2024-06-13 4:27:52 22 [Note] Master 's-db5': Slave I/O thread exiting, read up to log 'FIRST', position 4, master :3306 2024-06-13 4:27:52 3 [Note] Started replication for 's-db5' 2024-06-13 4:27:52 23 [Note] Master 's-db5': Slave SQL thread initialized, starting replication in log 'FIRST' at position 0, relay log './db1-relay-s@002ddb5.000010' position: 4 2024-06-13 4:27:52 25 [Note] Slave I/O thread: Start asynchronous replication to master 'gtid@10.76.24.77:3306' in log 'db2-binary.152675' at position 60494745 2024-06-13 4:27:52 0 [Note] /usr/sbin/mariadbd: ready for connections. Version: '10.11.5-MariaDB-log' socket: '/var/lib/mysql/mysql.sock' port: 3306 MariaDB Server 2024-06-13 4:27:52 26 [Note] Slave SQL thread initialized, starting replication in log 'db2-binary.152675' at position 60494745, relay log './db1-relay.000206' position: 767 2024-06-13 4:27:52 25 [Note] Slave I/O thread: connected to master 'gtid@10.76.24.77:3306',replication started in log 'db2-binary.152675' at position 60494745 2024-06-13 4:27:52 12 [Note] Detected table cache mutex contention at instance 1: 80% waits. Additional table cache instance activated. Number of instances after activation: 2. 2024-06-13 4:27:53 0 [Note] InnoDB: Buffer pool(s) load completed at 240613 4:27:53 2024-06-13 4:28:37 1669 [Note] Start binlog_dump to slave_server(2), pos(db1-binary.151978, 1405721), using_gtid(0), gtid('') 2024-06-13 4:28:37 1671 [Note] Start binlog_dump to slave_server(4), pos(db1-binary.151978, 1405721), using_gtid(0), gtid('') 2024-06-13 4:44:43 27401 [Note] Start binlog_dump to slave_server(3), pos(db1-binary.151958, 166574237), using_gtid(0), gtid('') 2024-06-13 14:29:25 1094066 [Warning] Access denied for user 'root'@'10.76.24.17' (using password: YES) 2024-06-13 14:31:24 1097850 [Warning] Access denied for user 'root'@'10.76.24.17' (using password: YES) 2024-06-27 17:36:31 37806359 [Warning] Aborted connection 37806359 to db: 'aaadb' user: 'root' host: 'localhost' (Got an error reading communication packets) 2024-07-01 0:30:20 26 [ERROR] Error in Log_event::read_log_event(): 'Found invalid event in binary log', data_len: 414, event_type: 19 2024-07-01 0:30:20 26 [ERROR] Error reading relay log event: slave SQL thread aborted because of I/O error 2024-07-01 0:30:20 26 [ERROR] Slave SQL: Relay log read failure: Could not parse relay log event entry. The possible reasons are: the master's binary log is corrupted (you can check this by running 'mysqlbinlog' on the binary log), the slave's relay log is corrupted (you can check this by running 'mysqlbinlog' on the relay log), a network problem, or a bug in the master's or slave's MariaDB code. If you want to check the master's binary log or slave's relay log, you will be able to know their names by issuing 'SHOW SLAVE STATUS' on this slave. Internal MariaDB error code: 1594 2024-07-01 0:30:20 26 [ERROR] Error running query, slave SQL thread aborted. Fix the problem, and restart the slave SQL thread with "SLAVE START". We stopped at log 'db2-binary.165370' position 3859 2024-07-01 0:30:20 26 [Note] Slave SQL thread exiting, replication stopped in log 'db2-binary.165370' at position 24017, master: 10.76.24.77:3306 2024-07-01 0:32:17 25 [ERROR] Could not use ./db1-relay.063683 for logging (error 11). Turning logging off for the whole duration of the MariaDB server process. To turn it on again: fix the cause, shutdown the MariaDB server and restart it. 2024-07-01 0:32:17 25 [ERROR] Slave I/O: Relay log write failure: could not queue event from master, Internal MariaDB error code: 1595 2024-07-01 0:32:17 25 [Note] Slave I/O thread exiting, read up to log 'db2-binary.165371', position 4, master 10.76.24.77:3306 2024-07-01 1:25:38 46402724 [Note] Master connection name: '' Master_info_file: 'master.info' Relay_info_file: 'relay-log.info' 2024-07-01 1:25:38 46402724 [Note] Failed to delete file 'ÐOp' 240701 1:25:38 [ERROR] mysqld got signal 11 ; 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.11.5-MariaDB-log source revision: 7875294b6b74b53dd3aaa723e6cc103d2bb47b2c key_buffer_size=67108864 read_buffer_size=131072 max_used_connections=7 max_threads=802 thread_count=24 It is possible that mysqld could use up to key_buffer_size + (read_buffer_size + sort_buffer_size)*max_threads = 1831964 K bytes of memory Hope that's ok; if not, decrease some variables in the equation. Thread pointer: 0x7f7120000c58 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 = 0x7f746f50ab98 thread_stack 0x49000 /usr/sbin/mariadbd(my_print_stacktrace+0x2e)[0x55f21bee312e] mysys/stacktrace.c:216(my_print_stacktrace)[0x55f21b9dc5b5] /lib64/libpthread.so.0(+0x12cf0)[0x7fc05458ccf0] /usr/sbin/mariadbd(dirname_length+0x0)[0x55f21bec4170] mysys/mf_dirname.c:34(dirname_length)[0x55f21bec422c] mysys/mf_dirname.c:71(dirname_part)[0x55f21bec43b0] mysys/mf_format.c:40(fn_format)[0x55f21bad5de9] sql/log.cc:3129(non-virtual thunk to MYSQL_BIN_LOG::generate_new_name(char*, char const*, unsigned long))[0x55f21bacf7bd] sql/log.cc:2901(MYSQL_LOG::init_and_set_log_file_name(char const*, char const*, unsigned long, enum_log_type, cache_type))[0x55f21badd755] sql/log.cc:3803(MYSQL_BIN_LOG::open(char const*, char const*, unsigned long, cache_type, unsigned long, bool, bool))[0x55f21bae258d] sql/log.cc:4635(MYSQL_BIN_LOG::reset_logs(THD*, bool, rpl_gtid*, unsigned int, unsigned long))[0x55f21b8a17ac] sql/rpl_rli.cc:1220(purge_relay_logs(Relay_log_info*, THD*, bool, char const**))[0x55f21b7ca02f] sql/sql_repl.cc:3973(change_master(THD*, Master_info*, bool*))[0x55f21b79cdcc] sql/sql_parse.cc:4144(mysql_execute_command(THD*, bool))[0x55f21b78eb87] sql/sql_parse.cc:8035(mysql_parse(THD*, char*, unsigned int, Parser_state*))[0x55f21b7986e6] sql/sql_parse.cc:1896(dispatch_command(enum_server_command, THD*, char*, unsigned int, bool))[0x55f21b799dab] sql/sql_parse.cc:1407(do_command(THD*, bool))[0x55f21b8ad977] sql/sql_connect.cc:1416(do_handle_one_connection(CONNECT*, bool))[0x55f21b8adcbd] sql/sql_connect.cc:1318(handle_one_connection)[0x55f21bbe3c9d] /lib64/libpthread.so.0(+0x81ca)[0x7fc0545821ca] /lib64/libc.so.6(clone+0x43)[0x7fc0538d2e73] Trying to get some variables. Some pointers may be invalid and cause the dump to abort. Query (0x7f7120010aa0): CHANGE MASTER TO master_host='10.76.24.77', master_port=3306, MASTER_USER='gtid', MASTER_PASSWORD='password', master_log_file='db2-binary.165370', master_log_pos=24017 Connection ID (thread ID): 46402724 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,hash_join_cardinality=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 unlimited unlimited bytes Max resident set unlimited unlimited bytes Max processes 2061710 2061710 processes Max open files 32768 32768 files Max locked memory 65536 65536 bytes Max address space unlimited unlimited bytes Max file locks unlimited unlimited locks Max pending signals 2061710 2061710 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: /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 2024-07-01 1:26:12 0 [Note] Starting MariaDB 10.11.5-MariaDB-log source revision 7875294b6b74b53dd3aaa723e6cc103d2bb47b2c as process 1175443 2024-07-01 1:26:12 0 [Note] InnoDB: Compressed tables use zlib 1.2.11 2024-07-01 1:26:12 0 [Note] InnoDB: Number of transaction pools: 1 2024-07-01 1:26:12 0 [Note] InnoDB: Using crc32 + pclmulqdq instructions 2024-07-01 1:26:12 0 [Note] InnoDB: Using Linux native AIO 2024-07-01 1:26:12 0 [Note] InnoDB: Initializing buffer pool, total size = 300.000GiB, chunk size = 4.688GiB 2024-07-01 1:26:13 0 [Note] InnoDB: Completed initialization of buffer pool 2024-07-01 1:26:14 0 [Note] InnoDB: File system buffers for log disabled (block size=512 bytes) 2024-07-01 1:26:16 0 [Warning] InnoDB: 3195484672 bytes should have been read at 1099482624 from (unknown file), but got only 2147479552. Retrying. 2024-07-01 1:26:19 0 [Warning] InnoDB: 3360366592 bytes should have been read at 934600704 from (unknown file), but got only 2147479552. Retrying. 2024-07-01 1:26:20 0 [Note] InnoDB: Starting crash recovery from checkpoint LSN=36473923585714 2024-07-01 1:26:28 0 [Note] InnoDB: Parsed redo log up to LSN=36474685997689; to recover: 171626 pages 2024-07-01 1:26:43 0 [Note] InnoDB: Parsed redo log up to LSN=36476197688946; to recover: 186737 pages 2024-07-01 1:26:49 0 [Note] InnoDB: End of log at LSN=36476866574532 2024-07-01 1:26:52 0 [Note] InnoDB: To recover: 196027 pages 2024-07-01 1:27:07 0 [Note] InnoDB: To recover: 196027 pages 2024-07-01 1:27:22 0 [Note] InnoDB: To recover: 196027 pages 2024-07-01 1:27:30 0 [Note] InnoDB: Last binlog file './db1-binary.164678', position 164852426 2024-07-01 1:27:30 0 [Note] InnoDB: 128 rollback segments are active. 2024-07-01 1:27:30 0 [Note] InnoDB: Removed temporary tablespace data file: "./ibtmp1" 2024-07-01 1:27:30 0 [Note] InnoDB: Setting file './ibtmp1' size to 12.000MiB. Physically writing the file full; Please wait ... 2024-07-01 1:27:30 0 [Note] InnoDB: File './ibtmp1' size is now 12.000MiB. 2024-07-01 1:27:30 0 [Note] InnoDB: log sequence number 36476866574532; transaction id 113986497931 2024-07-01 1:27:30 0 [Note] InnoDB: Loading buffer pool(s) from /var/lib/mysql/ib_buffer_pool 2024-07-01 1:27:30 0 [Note] Plugin 'FEEDBACK' is disabled. 2024-07-01 1:27:30 0 [Warning] 'thread-concurrency' was removed. It does nothing now and exists only for compatibility with old my.cnf files. 2024-07-01 1:27:30 0 [Warning] 'innodb-thread-concurrency' was removed. It does nothing now and exists only for compatibility with old my.cnf files. 2024-07-01 1:27:30 0 [Warning] 'innodb-log-files-in-group' was removed. It does nothing now and exists only for compatibility with old my.cnf files. 2024-07-01 1:27:30 0 [Note] Recovering after a crash using db1-binary 2024-07-01 1:27:30 0 [Note] Starting table crash recovery... 2024-07-01 1:27:30 0 [Note] Crash table recovery finished. 2024-07-01 1:27:31 0 [Note] Server socket created on IP: '0.0.0.0'. 2024-07-01 1:27:31 0 [Note] Server socket created on IP: '::'. 2024-07-01 1:27:31 0 [Warning] 'user' entry '@alepo-db2-ilb' ignored in --skip-name-resolve mode. 2024-07-01 1:27:31 0 [Warning] 'user' entry 'root@localhost.localdomain' ignored in --skip-name-resolve mode. 2024-07-01 1:27:31 0 [Warning] 'proxies_priv' entry '@% root@alepo-db2-ilb' ignored in --skip-name-resolve mode. 2024-07-01 1:27:31 3 [Note] Reading Master_info: 'master-s@002ddb3.info' Relay_info:'relay-log-s@002ddb3.info' 2024-07-01 1:27:31 3 [Note] Initialized Master_info from 'master-s@002ddb3.info' 2024-07-01 1:27:31 4 [Note] Master 's-db3': Slave I/O thread: Start asynchronous replication to master '@:3306' in log '' at position 4 2024-07-01 1:27:31 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 2024-07-01 1:27:31 4 [Note] Master 's-db3': Slave I/O thread killed while connecting to master 2024-07-01 1:27:31 4 [Note] Master 's-db3': Slave I/O thread exiting, read up to log 'FIRST', position 4, master :3306 2024-07-01 1:27:31 3 [Note] Started replication for 's-db3' 2024-07-01 1:27:31 5 [Note] Master 's-db3': Slave SQL thread initialized, starting replication in log 'FIRST' at position 0, relay log './db1-relay-s@002ddb3.000019' position: 4 2024-07-01 1:27:31 3 [Note] Reading Master_info: 'master-s@002ddb4.info' Relay_info:'relay-log-s@002ddb4.info' 2024-07-01 1:27:31 3 [Note] Initialized Master_info from 'master-s@002ddb4.info' 2024-07-01 1:27:31 18 [Note] Master 's-db4': Slave I/O thread: Start asynchronous replication to master 'gtid@10.76.25.11:3306' in log 'db4-binary.142004' at position 32408071 2024-07-01 1:27:31 3 [Note] Started replication for 's-db4' 2024-07-01 1:27:31 19 [Note] Master 's-db4': Slave SQL thread initialized, starting replication in log 'db4-binary.142004' at position 4, relay log './db1-relay-s@002ddb4.025475' position: 304 2024-07-01 1:27:31 3 [Note] Reading Master_info: 'master-s@002ddb2.info' Relay_info:'relay-log-s@002ddb2.info' 2024-07-01 1:27:31 3 [Note] Initialized Master_info from 'master-s@002ddb2.info' 2024-07-01 1:27:31 20 [Note] Master 's-db2': Slave I/O thread: Start asynchronous replication to master '@:3306' in log '' at position 4 2024-07-01 1:27:31 20 [ERROR] Master 's-db2': Slave I/O: Fatal error: Invalid (empty) username when attempting to connect to the master server. Connection attempt terminated. Internal MariaDB error code: 1593 2024-07-01 1:27:31 20 [Note] Master 's-db2': Slave I/O thread killed while connecting to master 2024-07-01 1:27:31 20 [Note] Master 's-db2': Slave I/O thread exiting, read up to log 'FIRST', position 4, master :3306 2024-07-01 1:27:31 3 [Note] Started replication for 's-db2' 2024-07-01 1:27:31 21 [Note] Master 's-db2': Slave SQL thread initialized, starting replication in log 'FIRST' at position 0, relay log './db1-relay-s@002ddb2.000018' position: 4 2024-07-01 1:27:31 3 [Note] Reading Master_info: 'master-s@002ddb5.info' Relay_info:'relay-log-s@002ddb5.info' 2024-07-01 1:27:31 3 [Note] Initialized Master_info from 'master-s@002ddb5.info' 2024-07-01 1:27:31 22 [Note] Master 's-db5': Slave I/O thread: Start asynchronous replication to master '@:3306' in log '' at position 4 2024-07-01 1:27:31 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 2024-07-01 1:27:31 22 [Note] Master 's-db5': Slave I/O thread killed while connecting to master 2024-07-01 1:27:31 22 [Note] Master 's-db5': Slave I/O thread exiting, read up to log 'FIRST', position 4, master :3306 2024-07-01 1:27:31 3 [Note] Started replication for 's-db5' 2024-07-01 1:27:31 23 [Note] Master 's-db5': Slave SQL thread initialized, starting replication in log 'FIRST' at position 0, relay log './db1-relay-s@002ddb5.000010' position: 4 2024-07-01 1:27:31 18 [Note] Master 's-db4': Slave I/O thread: connected to master 'gtid@10.76.25.11:3306',replication started in log 'db4-binary.142004' at position 32408071 2024-07-01 1:27:31 25 [Note] Slave I/O thread: Start asynchronous replication to master 'gtid@10.76.24.77:3306' in log 'db2-binary.165370' at position 24017 2024-07-01 1:27:31 26 [Note] Slave SQL thread initialized, starting replication in log 'db2-binary.165370' at position 24017, relay log './db1-relay.063682' position: 24317 2024-07-01 1:27:31 0 [Note] /usr/sbin/mariadbd: ready for connections. Version: '10.11.5-MariaDB-log' socket: '/var/lib/mysql/mysql.sock' port: 3306 MariaDB Server 2024-07-01 1:27:31 25 [Note] Slave I/O thread: connected to master 'gtid@10.76.24.77:3306',replication started in log 'db2-binary.165370' at position 24017 2024-07-01 1:27:31 26 [ERROR] Error in Log_event::read_log_event(): 'Found invalid event in binary log', data_len: 414, event_type: 19 2024-07-01 1:27:31 26 [ERROR] Error reading relay log event: slave SQL thread aborted because of I/O error 2024-07-01 1:27:31 26 [ERROR] Slave SQL: Relay log read failure: Could not parse relay log event entry. The possible reasons are: the master's binary log is corrupted (you can check this by running 'mysqlbinlog' on the binary log), the slave's relay log is corrupted (you can check this by running 'mysqlbinlog' on the relay log), a network problem, or a bug in the master's or slave's MariaDB code. If you want to check the master's binary log or slave's relay log, you will be able to know their names by issuing 'SHOW SLAVE STATUS' on this slave. Internal MariaDB error code: 1594 2024-07-01 1:27:31 26 [ERROR] Error running query, slave SQL thread aborted. Fix the problem, and restart the slave SQL thread with "SLAVE START". We stopped at log 'db2-binary.165370' position 24017 2024-07-01 1:27:31 26 [Note] Slave SQL thread exiting, replication stopped in log 'db2-binary.165370' at position 44704, master: 10.76.24.77:3306 2024-07-01 1:27:32 0 [Note] InnoDB: Buffer pool(s) load completed at 240701 1:27:32 2024-07-01 1:27:34 25 [ERROR] Could not use ./db1-relay.063684 for logging (error 2). Turning logging off for the whole duration of the MariaDB server process. To turn it on again: fix the cause, shutdown the MariaDB server and restart it. 2024-07-01 1:27:34 25 [ERROR] Slave I/O: Relay log write failure: could not queue event from master, Internal MariaDB error code: 1595 2024-07-01 1:27:34 25 [Note] Slave I/O thread exiting, read up to log 'db2-binary.165371', position 4, master 10.76.24.77:3306 2024-07-01 1:28:03 52 [Note] Start binlog_dump to slave_server(3), pos(db1-binary.164678, 164969911), using_gtid(0), gtid('') 2024-07-01 1:28:03 51 [Note] Start binlog_dump to slave_server(2), pos(db1-binary.164678, 164969911), using_gtid(0), gtid('') 2024-07-01 1:28:04 53 [Note] Start binlog_dump to slave_server(4), pos(db1-binary.164678, 164969911), using_gtid(0), gtid('') 2024-07-01 1:30:16 27 [Note] Master connection name: '' Master_info_file: 'master.info' Relay_info_file: 'relay-log.info' 2024-07-01 1:30:16 27 [Note] Failed to delete file 'ÐO$C' 240701 1:30:16 [ERROR] mysqld got signal 11 ; 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.11.5-MariaDB-log source revision: 7875294b6b74b53dd3aaa723e6cc103d2bb47b2c key_buffer_size=67108864 read_buffer_size=131072 max_used_connections=6 max_threads=802 thread_count=23 It is possible that mysqld could use up to key_buffer_size + (read_buffer_size + sort_buffer_size)*max_threads = 1831964 K bytes of memory Hope that's ok; if not, decrease some variables in the equation. Thread pointer: 0x7f431c000c58 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 = 0x7f93600efb98 thread_stack 0x49000 /usr/sbin/mariadbd(my_print_stacktrace+0x2e)[0x55cbf7f4c12e] mysys/stacktrace.c:216(my_print_stacktrace)[0x55cbf7a455b5] /lib64/libpthread.so.0(+0x12cf0)[0x7f9375c77cf0] /usr/sbin/mariadbd(dirname_length+0x0)[0x55cbf7f2d170] mysys/mf_dirname.c:34(dirname_length)[0x55cbf7f2d22c] mysys/mf_dirname.c:71(dirname_part)[0x55cbf7f2d3b0] mysys/mf_format.c:40(fn_format)[0x55cbf7b3ede9] sql/log.cc:3129(non-virtual thunk to MYSQL_BIN_LOG::generate_new_name(char*, char const*, unsigned long))[0x55cbf7b387bd] sql/log.cc:2901(MYSQL_LOG::init_and_set_log_file_name(char const*, char const*, unsigned long, enum_log_type, cache_type))[0x55cbf7b46755] sql/log.cc:3803(MYSQL_BIN_LOG::open(char const*, char const*, unsigned long, cache_type, unsigned long, bool, bool))[0x55cbf7b4b58d] sql/log.cc:4635(MYSQL_BIN_LOG::reset_logs(THD*, bool, rpl_gtid*, unsigned int, unsigned long))[0x55cbf790a7ac] sql/rpl_rli.cc:1220(purge_relay_logs(Relay_log_info*, THD*, bool, char const**))[0x55cbf783302f] sql/sql_repl.cc:3973(change_master(THD*, Master_info*, bool*))[0x55cbf7805dcc] sql/sql_parse.cc:4144(mysql_execute_command(THD*, bool))[0x55cbf77f7b87] sql/sql_parse.cc:8035(mysql_parse(THD*, char*, unsigned int, Parser_state*))[0x55cbf78016e6] sql/sql_parse.cc:1896(dispatch_command(enum_server_command, THD*, char*, unsigned int, bool))[0x55cbf7802dab] sql/sql_parse.cc:1407(do_command(THD*, bool))[0x55cbf7916977] sql/sql_connect.cc:1416(do_handle_one_connection(CONNECT*, bool))[0x55cbf7916cbd] sql/sql_connect.cc:1318(handle_one_connection)[0x55cbf7c4cc9d] /lib64/libpthread.so.0(+0x81ca)[0x7f9375c6d1ca] /lib64/libc.so.6(clone+0x43)[0x7f9374fbde73] Trying to get some variables. Some pointers may be invalid and cause the dump to abort. Query (0x7f431c010a70): CHANGE MASTER TO master_host='10.76.24.77', master_port=3306, MASTER_USER='gtid', MASTER_PASSWORD='password', master_log_file='db2-binary.165370', master_log_pos=44704 Connection ID (thread ID): 27 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,hash_join_cardinality=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 unlimited unlimited bytes Max resident set unlimited unlimited bytes Max processes 2061710 2061710 processes Max open files 32768 32768 files Max locked memory 65536 65536 bytes Max address space unlimited unlimited bytes Max file locks unlimited unlimited locks Max pending signals 2061710 2061710 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: /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 2024-07-01 1:30:45 0 [Note] Starting MariaDB 10.11.5-MariaDB-log source revision 7875294b6b74b53dd3aaa723e6cc103d2bb47b2c as process 1176700 2024-07-01 1:30:45 0 [Note] InnoDB: Compressed tables use zlib 1.2.11 2024-07-01 1:30:45 0 [Note] InnoDB: Number of transaction pools: 1 2024-07-01 1:30:45 0 [Note] InnoDB: Using crc32 + pclmulqdq instructions 2024-07-01 1:30:45 0 [Note] InnoDB: Using Linux native AIO 2024-07-01 1:30:45 0 [Note] InnoDB: Initializing buffer pool, total size = 300.000GiB, chunk size = 4.688GiB 2024-07-01 1:30:46 0 [Note] InnoDB: Completed initialization of buffer pool 2024-07-01 1:30:47 0 [Note] InnoDB: File system buffers for log disabled (block size=512 bytes) 2024-07-01 1:30:49 0 [Warning] InnoDB: 3195484672 bytes should have been read at 1099482624 from (unknown file), but got only 2147479552. Retrying. 2024-07-01 1:30:52 0 [Warning] InnoDB: 3360366592 bytes should have been read at 934600704 from (unknown file), but got only 2147479552. Retrying. 2024-07-01 1:30:53 0 [Note] InnoDB: Starting crash recovery from checkpoint LSN=36473923585714 2024-07-01 1:31:01 0 [Note] InnoDB: Parsed redo log up to LSN=36474723900783; to recover: 172275 pages 2024-07-01 1:31:16 0 [Note] InnoDB: Parsed redo log up to LSN=36476231084366; to recover: 186991 pages 2024-07-01 1:31:22 0 [Note] InnoDB: End of log at LSN=36476867920882 2024-07-01 1:31:25 0 [Note] InnoDB: To recover: 196027 pages 2024-07-01 1:31:40 0 [Note] InnoDB: To recover: 196027 pages 2024-07-01 1:31:55 0 [Note] InnoDB: To recover: 196027 pages 2024-07-01 1:32:02 0 [Note] InnoDB: Last binlog file './db1-binary.164678', position 164833291 2024-07-01 1:32:02 0 [Note] InnoDB: 128 rollback segments are active. 2024-07-01 1:32:03 0 [Note] InnoDB: Removed temporary tablespace data file: "./ibtmp1" 2024-07-01 1:32:03 0 [Note] InnoDB: Setting file './ibtmp1' size to 12.000MiB. Physically writing the file full; Please wait ... 2024-07-01 1:32:03 0 [Note] InnoDB: File './ibtmp1' size is now 12.000MiB. 2024-07-01 1:32:03 0 [Note] InnoDB: log sequence number 36476867920882; transaction id 113986498005 2024-07-01 1:32:03 0 [Note] InnoDB: Loading buffer pool(s) from /var/lib/mysql/ib_buffer_pool 2024-07-01 1:32:03 0 [Note] Plugin 'FEEDBACK' is disabled. 2024-07-01 1:32:03 0 [Warning] 'thread-concurrency' was removed. It does nothing now and exists only for compatibility with old my.cnf files. 2024-07-01 1:32:03 0 [Warning] 'innodb-thread-concurrency' was removed. It does nothing now and exists only for compatibility with old my.cnf files. 2024-07-01 1:32:03 0 [Warning] 'innodb-log-files-in-group' was removed. It does nothing now and exists only for compatibility with old my.cnf files. 2024-07-01 1:32:03 0 [Note] Recovering after a crash using db1-binary 2024-07-01 1:32:03 0 [Note] Starting table crash recovery... 2024-07-01 1:32:03 0 [Note] Crash table recovery finished. 2024-07-01 1:32:03 0 [Note] Server socket created on IP: '0.0.0.0'. 2024-07-01 1:32:03 0 [Note] Server socket created on IP: '::'. 2024-07-01 1:32:03 0 [Warning] 'user' entry '@alepo-db2-ilb' ignored in --skip-name-resolve mode. 2024-07-01 1:32:03 0 [Warning] 'user' entry 'root@localhost.localdomain' ignored in --skip-name-resolve mode. 2024-07-01 1:32:03 0 [Warning] 'proxies_priv' entry '@% root@alepo-db2-ilb' ignored in --skip-name-resolve mode. 2024-07-01 1:32:03 3 [Note] Reading Master_info: 'master-s@002ddb3.info' Relay_info:'relay-log-s@002ddb3.info' 2024-07-01 1:32:03 3 [Note] Initialized Master_info from 'master-s@002ddb3.info' 2024-07-01 1:32:03 4 [Note] Master 's-db3': Slave I/O thread: Start asynchronous replication to master '@:3306' in log '' at position 4 2024-07-01 1:32:03 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 2024-07-01 1:32:03 4 [Note] Master 's-db3': Slave I/O thread killed while connecting to master 2024-07-01 1:32:03 4 [Note] Master 's-db3': Slave I/O thread exiting, read up to log 'FIRST', position 4, master :3306 2024-07-01 1:32:03 3 [Note] Started replication for 's-db3' 2024-07-01 1:32:03 5 [Note] Master 's-db3': Slave SQL thread initialized, starting replication in log 'FIRST' at position 0, relay log './db1-relay-s@002ddb3.000019' position: 4 2024-07-01 1:32:03 3 [Note] Reading Master_info: 'master-s@002ddb4.info' Relay_info:'relay-log-s@002ddb4.info' 2024-07-01 1:32:03 3 [Note] Initialized Master_info from 'master-s@002ddb4.info' 2024-07-01 1:32:03 18 [Note] Master 's-db4': Slave I/O thread: Start asynchronous replication to master 'gtid@10.76.25.11:3306' in log 'db4-binary.142004' at position 32428752 2024-07-01 1:32:03 3 [Note] Started replication for 's-db4' 2024-07-01 1:32:03 3 [Note] Reading Master_info: 'master-s@002ddb2.info' Relay_info:'relay-log-s@002ddb2.info' 2024-07-01 1:32:03 19 [Note] Master 's-db4': Slave SQL thread initialized, starting replication in log 'db4-binary.142004' at position 32428752, relay log './db1-relay-s@002ddb4.025478' position: 556 2024-07-01 1:32:03 3 [Note] Initialized Master_info from 'master-s@002ddb2.info' 2024-07-01 1:32:03 20 [Note] Master 's-db2': Slave I/O thread: Start asynchronous replication to master '@:3306' in log '' at position 4 2024-07-01 1:32:03 20 [ERROR] Master 's-db2': Slave I/O: Fatal error: Invalid (empty) username when attempting to connect to the master server. Connection attempt terminated. Internal MariaDB error code: 1593 2024-07-01 1:32:03 20 [Note] Master 's-db2': Slave I/O thread killed while connecting to master 2024-07-01 1:32:03 20 [Note] Master 's-db2': Slave I/O thread exiting, read up to log 'FIRST', position 4, master :3306 2024-07-01 1:32:03 3 [Note] Started replication for 's-db2' 2024-07-01 1:32:03 21 [Note] Master 's-db2': Slave SQL thread initialized, starting replication in log 'FIRST' at position 0, relay log './db1-relay-s@002ddb2.000018' position: 4 2024-07-01 1:32:03 3 [Note] Reading Master_info: 'master-s@002ddb5.info' Relay_info:'relay-log-s@002ddb5.info' 2024-07-01 1:32:03 3 [Note] Initialized Master_info from 'master-s@002ddb5.info' 2024-07-01 1:32:03 22 [Note] Master 's-db5': Slave I/O thread: Start asynchronous replication to master '@:3306' in log '' at position 4 2024-07-01 1:32:03 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 2024-07-01 1:32:03 22 [Note] Master 's-db5': Slave I/O thread killed while connecting to master 2024-07-01 1:32:03 22 [Note] Master 's-db5': Slave I/O thread exiting, read up to log 'FIRST', position 4, master :3306 2024-07-01 1:32:03 3 [Note] Started replication for 's-db5' 2024-07-01 1:32:03 23 [Note] Master 's-db5': Slave SQL thread initialized, starting replication in log 'FIRST' at position 0, relay log './db1-relay-s@002ddb5.000010' position: 4 2024-07-01 1:32:03 18 [Note] Master 's-db4': Slave I/O thread: connected to master 'gtid@10.76.25.11:3306',replication started in log 'db4-binary.142004' at position 32428752 2024-07-01 1:32:03 0 [ERROR] Failed to open the relay log './db1-relay.063683' (relay_log_pos 21243) 2024-07-01 1:32:03 0 [ERROR] Could not find target log during relay log initialization 2024-07-01 1:32:03 0 [ERROR] Failed to initialize the master info structure 2024-07-01 1:32:03 0 [Note] /usr/sbin/mariadbd: ready for connections. Version: '10.11.5-MariaDB-log' socket: '/var/lib/mysql/mysql.sock' port: 3306 MariaDB Server 2024-07-01 1:32:04 0 [Note] InnoDB: Buffer pool(s) load completed at 240701 1:32:04 2024-07-01 1:32:37 51 [Note] Start binlog_dump to slave_server(2), pos(db1-binary.164679, 21108), using_gtid(0), gtid('') 2024-07-01 1:32:37 50 [Note] Start binlog_dump to slave_server(3), pos(db1-binary.164679, 21108), using_gtid(0), gtid('') 2024-07-01 1:32:37 52 [Note] Start binlog_dump to slave_server(4), pos(db1-binary.164679, 21108), using_gtid(0), gtid('') 2024-07-01 2:00:01 1238 [Note] Start binlog_dump to slave_server(2), pos(db1-binary.164680, 423), using_gtid(0), gtid('') 2024-07-01 2:19:36 1701 [Note] Deleted Master_info file '/var/lib/mysql/master.info'. 2024-07-01 2:19:36 1701 [Note] Deleted Master_info file '/var/lib/mysql/relay-log.info'. 2024-07-01 2:19:37 1701 [Note] Master connection name: '' Master_info_file: 'master.info' Relay_info_file: 'relay-log.info' 2024-07-01 2:19:37 1701 [Note] 'CHANGE MASTER TO executed'. Previous state master_host='10.76.24.77', master_port='3306', master_log_file='', master_log_pos='4'. New state master_host='10.76.24.77', master_port='3306', master_log_file='db2-binary.165370', master_log_pos='44704'. 2024-07-01 2:19:37 1701 [Note] Previous Using_Gtid=Slave_Pos. New Using_Gtid=No 2024-07-01 2:19:41 2087 [Note] Slave I/O thread: Start asynchronous replication to master 'gtid@10.76.24.77:3306' in log 'db2-binary.165370' at position 44704 2024-07-01 2:19:41 2088 [Note] Slave SQL thread initialized, starting replication in log 'db2-binary.165370' at position 44704, relay log './db1-relay.063684' position: 4 2024-07-01 2:19:41 2087 [Note] Slave I/O thread: connected to master 'gtid@10.76.24.77:3306',replication started in log 'db2-binary.165370' at position 44704 2024-07-01 2:19:41 2088 [ERROR] Error in Log_event::read_log_event(): 'Found invalid event in binary log', data_len: 414, event_type: 19 2024-07-01 2:19:41 2088 [ERROR] Error reading relay log event: slave SQL thread aborted because of I/O error 2024-07-01 2:19:41 2088 [ERROR] Slave SQL: Relay log read failure: Could not parse relay log event entry. The possible reasons are: the master's binary log is corrupted (you can check this by running 'mysqlbinlog' on the binary log), the slave's relay log is corrupted (you can check this by running 'mysqlbinlog' on the relay log), a network problem, or a bug in the master's or slave's MariaDB code. If you want to check the master's binary log or slave's relay log, you will be able to know their names by issuing 'SHOW SLAVE STATUS' on this slave. Internal MariaDB error code: 1594 2024-07-01 2:19:41 2088 [ERROR] Error running query, slave SQL thread aborted. Fix the problem, and restart the slave SQL thread with "SLAVE START". We stopped at log 'db2-binary.165370' position 44704 2024-07-01 2:19:41 8 [Note] Detected table cache mutex contention at instance 1: 71% waits. Additional table cache instance activated. Number of instances after activation: 2. 2024-07-01 2:19:44 2087 [ERROR] Could not use ./db1-relay.063686 for logging (error 11). Turning logging off for the whole duration of the MariaDB server process. To turn it on again: fix the cause, shutdown the MariaDB server and restart it. 2024-07-01 2:19:44 2087 [ERROR] Slave I/O: Relay log write failure: could not queue event from master, Internal MariaDB error code: 1595 2024-07-01 2:19:44 2087 [Note] Slave I/O thread exiting, read up to log 'db2-binary.165371', position 4, master 10.76.24.77:3306 2024-07-01 2:19:45 2088 [Note] Slave SQL thread exiting, replication stopped in log 'db2-binary.165370' at position 63951, master: 10.76.24.77:3306 2024-07-01 2:23:34 1701 [Note] Failed to delete file 'ÐOôf' 2024-07-01 2:23:34 1701 [Note] Deleted Master_info file '/var/lib/mysql/master.info'. 2024-07-01 2:23:34 1701 [Note] Deleted Master_info file '/var/lib/mysql/relay-log.info'. 2024-07-01 2:23:35 1701 [Note] Master connection name: '' Master_info_file: 'master.info' Relay_info_file: 'relay-log.info' 2024-07-01 2:23:35 1701 [Note] 'CHANGE MASTER TO executed'. Previous state master_host='10.76.24.77', master_port='3306', master_log_file='', master_log_pos='4'. New state master_host='10.76.24.77', master_port='3306', master_log_file='db2-binary.165370', master_log_pos='63951'. 2024-07-01 2:23:35 1701 [Note] Previous Using_Gtid=Slave_Pos. New Using_Gtid=No 2024-07-01 2:23:44 2265 [Note] Slave I/O thread: Start asynchronous replication to master 'gtid@10.76.24.77:3306' in log 'db2-binary.165370' at position 63951 2024-07-01 2:23:44 2266 [Note] Slave SQL thread initialized, starting replication in log 'db2-binary.165370' at position 63951, relay log './db1-relay.063685' position: 4 2024-07-01 2:23:44 2265 [Note] Slave I/O thread: connected to master 'gtid@10.76.24.77:3306',replication started in log 'db2-binary.165370' at position 63951 2024-07-01 2:23:44 2266 [ERROR] Error in Log_event::read_log_event(): 'Found invalid event in binary log', data_len: 414, event_type: 19 2024-07-01 2:23:44 2266 [ERROR] Error reading relay log event: slave SQL thread aborted because of I/O error 2024-07-01 2:23:44 2266 [ERROR] Slave SQL: Relay log read failure: Could not parse relay log event entry. The possible reasons are: the master's binary log is corrupted (you can check this by running 'mysqlbinlog' on the binary log), the slave's relay log is corrupted (you can check this by running 'mysqlbinlog' on the relay log), a network problem, or a bug in the master's or slave's MariaDB code. If you want to check the master's binary log or slave's relay log, you will be able to know their names by issuing 'SHOW SLAVE STATUS' on this slave. Internal MariaDB error code: 1594 2024-07-01 2:23:44 2266 [ERROR] Error running query, slave SQL thread aborted. Fix the problem, and restart the slave SQL thread with "SLAVE START". We stopped at log 'db2-binary.165370' position 63951 2024-07-01 2:23:44 2266 [Note] Slave SQL thread exiting, replication stopped in log 'db2-binary.165370' at position 75698, master: 10.76.24.77:3306 2024-07-01 2:23:47 2265 [ERROR] Could not use ./db1-relay.063687 for logging (error 2). Turning logging off for the whole duration of the MariaDB server process. To turn it on again: fix the cause, shutdown the MariaDB server and restart it. 2024-07-01 2:23:47 2265 [ERROR] Slave I/O: Relay log write failure: could not queue event from master, Internal MariaDB error code: 1595 2024-07-01 2:23:47 2265 [Note] Slave I/O thread exiting, read up to log 'db2-binary.165371', position 4, master 10.76.24.77:3306 2024-07-01 3:06:44 1238 [Warning] Aborted connection 1238 to db: 'unconnected' user: 'gtid' host: '10.76.24.77' (Got an error writing communication packets) 2024-07-01 3:59:08 5229 [Note] InnoDB: Cannot close file ./aaadb/authenticationlog#P#p20240630.ibd because of 134 pending operations and pending fsync 2024-07-01 4:15:23 5191 [Warning] 'user' entry '@alepo-db2-ilb' ignored in --skip-name-resolve mode. 2024-07-01 4:15:23 5191 [Warning] 'user' entry 'root@localhost.localdomain' ignored in --skip-name-resolve mode. 2024-07-01 4:15:23 5191 [Warning] 'proxies_priv' entry '@% root@alepo-db2-ilb' ignored in --skip-name-resolve mode. 2024-07-01 4:15:42 5191 [Note] Master connection name: '' Master_info_file: 'master.info' Relay_info_file: 'relay-log.info' 2024-07-01 4:15:42 5191 [ERROR] Failed to locate old binlog or relay log files 2024-07-01 4:20:16 5191 [Warning] 'user' entry '@alepo-db2-ilb' ignored in --skip-name-resolve mode. 2024-07-01 4:20:16 5191 [Warning] 'user' entry 'root@localhost.localdomain' ignored in --skip-name-resolve mode. 2024-07-01 4:20:16 5191 [Warning] 'proxies_priv' entry '@% root@alepo-db2-ilb' ignored in --skip-name-resolve mode. 2024-07-01 4:20:16 5191 [Note] Master connection name: '' Master_info_file: 'master.info' Relay_info_file: 'relay-log.info' 2024-07-01 4:20:16 5191 [ERROR] Failed to locate old binlog or relay log files 2024-07-01 4:20:16 8008 [Note] Slave I/O thread: Start asynchronous replication to master 'gtid@10.76.24.77:3306' in log 'db2-binary.165440' at position 111968783 2024-07-01 4:20:16 8009 [ERROR] Slave SQL: Error initializing relay log position: Could not find first log during relay log initialization, Internal MariaDB error code: 1593 2024-07-01 4:20:16 8008 [Note] Slave I/O thread: connected to master 'gtid@10.76.24.77:3306',replication started in log 'db2-binary.165440' at position 111968783 240701 4:20:16 [ERROR] mysqld got signal 11 ; 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.11.5-MariaDB-log source revision: 7875294b6b74b53dd3aaa723e6cc103d2bb47b2c key_buffer_size=67108864 read_buffer_size=131072 max_used_connections=8 max_threads=802 thread_count=26 It is possible that mysqld could use up to key_buffer_size + (read_buffer_size + sort_buffer_size)*max_threads = 1831964 K bytes of memory Hope that's ok; if not, decrease some variables in the equation. Thread pointer: 0x7f6670000c58 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 = 0x7f6a70abc970 thread_stack 0x49000 /usr/sbin/mariadbd(my_print_stacktrace+0x2e)[0x55ba478a412e] mysys/stacktrace.c:216(my_print_stacktrace)[0x55ba4739d5b5] /lib64/libpthread.so.0(+0x12cf0)[0x7fb655329cf0] /lib64/libc.so.6(+0xd0249)[0x7fb654706249] /usr/sbin/mariadbd(my_b_append+0x4c)[0x55ba478885ec] psi/mysql_thread.h:785(inline_mysql_mutex_unlock)[0x55ba4749fdec] sql/log.cc:5722(MYSQL_BIN_LOG::write_event_buffer(unsigned char*, unsigned int))[0x55ba470acbd0] sql/slave.cc:7277(queue_event)[0x55ba470aef30] sql/slave.cc:5049(handle_slave_io)[0x55ba475a4c9d] /lib64/libpthread.so.0(+0x81ca)[0x7fb65531f1ca] /lib64/libc.so.6(clone+0x43)[0x7fb65466fe73] Trying to get some variables. Some pointers may be invalid and cause the dump to abort. Query (0x0): (null) Connection ID (thread ID): 8008 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,hash_join_cardinality=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. We think the query pointer is invalid, but we will try to print it anyway. Query: 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 unlimited unlimited bytes Max resident set unlimited unlimited bytes Max processes 2061710 2061710 processes Max open files 32768 32768 files Max locked memory 65536 65536 bytes Max address space unlimited unlimited bytes Max file locks unlimited unlimited locks Max pending signals 2061710 2061710 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: /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 2024-07-01 4:20:49 0 [Note] Starting MariaDB 10.11.5-MariaDB-log source revision 7875294b6b74b53dd3aaa723e6cc103d2bb47b2c as process 1208706 2024-07-01 4:20:49 0 [Note] mariadbd: Aria engine: starting recovery recovered pages: 0% 10% 31% 47% 57% 74% 85% 95% 100% (0.0 seconds); tables to flush: 2 1 0 (0.0 seconds); 2024-07-01 4:20:49 0 [Note] mariadbd: Aria engine: recovery done 2024-07-01 4:20:49 0 [Note] InnoDB: Compressed tables use zlib 1.2.11 2024-07-01 4:20:49 0 [Note] InnoDB: Number of transaction pools: 1 2024-07-01 4:20:49 0 [Note] InnoDB: Using crc32 + pclmulqdq instructions 2024-07-01 4:20:49 0 [Note] InnoDB: Using Linux native AIO 2024-07-01 4:20:49 0 [Note] InnoDB: Initializing buffer pool, total size = 300.000GiB, chunk size = 4.688GiB 2024-07-01 4:20:49 0 [Note] InnoDB: Completed initialization of buffer pool 2024-07-01 4:20:50 0 [Note] InnoDB: File system buffers for log disabled (block size=512 bytes) 2024-07-01 4:20:53 0 [Note] InnoDB: Starting crash recovery from checkpoint LSN=36526906266903 2024-07-01 4:20:54 0 [Note] InnoDB: End of log at LSN=36527063594212 2024-07-01 4:20:54 0 [Note] InnoDB: To recover: 41600 pages 2024-07-01 4:20:55 0 [Note] InnoDB: Last binlog file './db1-binary.165088', position 67926013 2024-07-01 4:20:55 0 [Note] InnoDB: 128 rollback segments are active. 2024-07-01 4:20:55 0 [Note] InnoDB: Removed temporary tablespace data file: "./ibtmp1" 2024-07-01 4:20:55 0 [Note] InnoDB: Setting file './ibtmp1' size to 12.000MiB. Physically writing the file full; Please wait ... 2024-07-01 4:20:55 0 [Note] InnoDB: File './ibtmp1' size is now 12.000MiB. 2024-07-01 4:20:55 0 [Note] InnoDB: log sequence number 36527063594212; transaction id 113986760855 2024-07-01 4:20:55 0 [Note] InnoDB: Loading buffer pool(s) from /var/lib/mysql/ib_buffer_pool 2024-07-01 4:20:55 0 [Note] Plugin 'FEEDBACK' is disabled. 2024-07-01 4:20:55 0 [Warning] 'thread-concurrency' was removed. It does nothing now and exists only for compatibility with old my.cnf files. 2024-07-01 4:20:55 0 [Warning] 'innodb-thread-concurrency' was removed. It does nothing now and exists only for compatibility with old my.cnf files. 2024-07-01 4:20:55 0 [Warning] 'innodb-log-files-in-group' was removed. It does nothing now and exists only for compatibility with old my.cnf files. 2024-07-01 4:20:55 0 [Note] Recovering after a crash using db1-binary 2024-07-01 4:20:55 0 [Note] Starting table crash recovery... 2024-07-01 4:20:55 0 [Note] Crash table recovery finished. 2024-07-01 4:20:55 0 [Note] Server socket created on IP: '0.0.0.0'. 2024-07-01 4:20:55 0 [Note] Server socket created on IP: '::'. 2024-07-01 4:20:55 0 [Warning] 'user' entry '@alepo-db2-ilb' ignored in --skip-name-resolve mode. 2024-07-01 4:20:55 0 [Warning] 'user' entry 'root@localhost.localdomain' ignored in --skip-name-resolve mode. 2024-07-01 4:20:55 0 [Warning] 'proxies_priv' entry '@% root@alepo-db2-ilb' ignored in --skip-name-resolve mode. 2024-07-01 4:20:55 3 [Note] Reading Master_info: 'master-s@002ddb3.info' Relay_info:'relay-log-s@002ddb3.info' 2024-07-01 4:20:55 3 [Note] Initialized Master_info from 'master-s@002ddb3.info' 2024-07-01 4:20:55 4 [Note] Master 's-db3': Slave I/O thread: Start asynchronous replication to master '@:3306' in log '' at position 4 2024-07-01 4:20:55 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 2024-07-01 4:20:55 4 [Note] Master 's-db3': Slave I/O thread killed while connecting to master 2024-07-01 4:20:55 4 [Note] Master 's-db3': Slave I/O thread exiting, read up to log 'FIRST', position 4, master :3306 2024-07-01 4:20:55 3 [Note] Started replication for 's-db3' 2024-07-01 4:20:55 5 [Note] Master 's-db3': Slave SQL thread initialized, starting replication in log 'FIRST' at position 0, relay log './db1-relay-s@002ddb3.000019' position: 4 2024-07-01 4:20:55 3 [Note] Reading Master_info: 'master-s@002ddb4.info' Relay_info:'relay-log-s@002ddb4.info' 2024-07-01 4:20:55 3 [Note] Initialized Master_info from 'master-s@002ddb4.info' 2024-07-01 4:20:55 18 [Note] Master 's-db4': Slave I/O thread: Start asynchronous replication to master 'gtid@10.76.25.11:3306' in log 'db4-binary.142412' at position 192852999 2024-07-01 4:20:55 3 [Note] Started replication for 's-db4' 2024-07-01 4:20:55 3 [Note] Reading Master_info: 'master-s@002ddb2.info' Relay_info:'relay-log-s@002ddb2.info' 2024-07-01 4:20:55 19 [Note] Master 's-db4': Slave SQL thread initialized, starting replication in log 'db4-binary.142412' at position 192852999, relay log './db1-relay-s@002ddb4.026296' position: 783 2024-07-01 4:20:55 3 [Note] Initialized Master_info from 'master-s@002ddb2.info' 2024-07-01 4:20:55 20 [Note] Master 's-db2': Slave I/O thread: Start asynchronous replication to master '@:3306' in log '' at position 4 2024-07-01 4:20:55 20 [ERROR] Master 's-db2': Slave I/O: Fatal error: Invalid (empty) username when attempting to connect to the master server. Connection attempt terminated. Internal MariaDB error code: 1593 2024-07-01 4:20:55 20 [Note] Master 's-db2': Slave I/O thread killed while connecting to master 2024-07-01 4:20:55 20 [Note] Master 's-db2': Slave I/O thread exiting, read up to log 'FIRST', position 4, master :3306 2024-07-01 4:20:55 3 [Note] Started replication for 's-db2' 2024-07-01 4:20:55 3 [Note] Reading Master_info: 'master-s@002ddb5.info' Relay_info:'relay-log-s@002ddb5.info' 2024-07-01 4:20:55 21 [Note] Master 's-db2': Slave SQL thread initialized, starting replication in log 'FIRST' at position 0, relay log './db1-relay-s@002ddb2.000018' position: 4 2024-07-01 4:20:55 3 [Note] Initialized Master_info from 'master-s@002ddb5.info' 2024-07-01 4:20:55 22 [Note] Master 's-db5': Slave I/O thread: Start asynchronous replication to master '@:3306' in log '' at position 4 2024-07-01 4:20:55 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 2024-07-01 4:20:55 22 [Note] Master 's-db5': Slave I/O thread killed while connecting to master 2024-07-01 4:20:55 22 [Note] Master 's-db5': Slave I/O thread exiting, read up to log 'FIRST', position 4, master :3306 2024-07-01 4:20:55 3 [Note] Started replication for 's-db5' 2024-07-01 4:20:55 23 [Note] Master 's-db5': Slave SQL thread initialized, starting replication in log 'FIRST' at position 0, relay log './db1-relay-s@002ddb5.000010' position: 4 2024-07-01 4:20:55 18 [Note] Master 's-db4': Slave I/O thread: connected to master 'gtid@10.76.25.11:3306',replication started in log 'db4-binary.142412' at position 192852999 2024-07-01 4:20:55 25 [Note] Slave I/O thread: Start asynchronous replication to master 'gtid@10.76.24.77:3306' in log 'db2-binary.165440' at position 115549064 2024-07-01 4:20:55 0 [Note] /usr/sbin/mariadbd: ready for connections. Version: '10.11.5-MariaDB-log' socket: '/var/lib/mysql/mysql.sock' port: 3306 MariaDB Server 2024-07-01 4:20:55 26 [Note] Slave SQL thread initialized, starting replication in log 'db2-binary.165370' at position 75698, relay log './db1-relay.063686' position: 12303 2024-07-01 4:20:55 26 [ERROR] Error in Log_event::read_log_event(): 'Found invalid event in binary log', data_len: 414, event_type: 19 2024-07-01 4:20:55 26 [ERROR] Error reading relay log event: slave SQL thread aborted because of I/O error 2024-07-01 4:20:55 26 [ERROR] Slave SQL: Relay log read failure: Could not parse relay log event entry. The possible reasons are: the master's binary log is corrupted (you can check this by running 'mysqlbinlog' on the binary log), the slave's relay log is corrupted (you can check this by running 'mysqlbinlog' on the relay log), a network problem, or a bug in the master's or slave's MariaDB code. If you want to check the master's binary log or slave's relay log, you will be able to know their names by issuing 'SHOW SLAVE STATUS' on this slave. Internal MariaDB error code: 1594 2024-07-01 4:20:55 26 [ERROR] Error running query, slave SQL thread aborted. Fix the problem, and restart the slave SQL thread with "SLAVE START". We stopped at log 'db2-binary.165370' position 75698 2024-07-01 4:20:55 26 [Note] Slave SQL thread exiting, replication stopped in log 'db2-binary.165370' at position 75698, master: 10.76.24.77:3306 2024-07-01 4:20:55 25 [Note] Slave I/O thread: connected to master 'gtid@10.76.24.77:3306',replication started in log 'db2-binary.165440' at position 115549064 2024-07-01 4:20:57 0 [Note] InnoDB: Buffer pool(s) load completed at 240701 4:20:57 2024-07-01 4:21:42 61 [Note] Start binlog_dump to slave_server(3), pos(db1-binary.165088, 159682744), using_gtid(0), gtid('') 2024-07-01 4:21:42 62 [Note] Start binlog_dump to slave_server(4), pos(db1-binary.165088, 159682744), using_gtid(0), gtid('') 2024-07-01 4:25:54 25 [Note] Slave I/O thread exiting, read up to log 'db2-binary.165475', position 47268107, master 10.76.24.77:3306 2024-07-01 4:27:05 247 [Note] Master connection name: '' Master_info_file: 'master.info' Relay_info_file: 'relay-log.info' 2024-07-01 4:27:06 247 [Note] 'CHANGE MASTER TO executed'. Previous state master_host='10.76.24.77', master_port='3306', master_log_file='db2-binary.165475', master_log_pos='47268107'. New state master_host='10.76.24.77', master_port='3306', master_log_file='db2-binary.165440', master_log_pos='111968783'. 2024-07-01 4:27:16 309 [Note] Slave I/O thread: Start asynchronous replication to master 'gtid@10.76.24.77:3306' in log 'db2-binary.165440' at position 111968783 2024-07-01 4:27:16 310 [Note] Slave SQL thread initialized, starting replication in log 'db2-binary.165440' at position 111968783, relay log './db1-relay.063685' position: 4 2024-07-01 4:27:16 309 [Note] Slave I/O thread: connected to master 'gtid@10.76.24.77:3306',replication started in log 'db2-binary.165440' at position 111968783 2024-07-01 4:28:28 9906 [Note] Start binlog_dump to slave_server(2), pos(db1-binary.164680, 31413), using_gtid(0), gtid('') 2024-07-01 4:36:38 9906 [Warning] Aborted connection 9906 to db: 'unconnected' user: 'gtid' host: '10.76.24.77' (Got an error writing communication packets) 2024-07-01 4:36:38 73068 [Note] Start binlog_dump to slave_server(2), pos(db1-binary.165118, 134765711), using_gtid(0), gtid('') 2024-07-01 4:36:43 73068 [Warning] Aborted connection 73068 to db: 'unconnected' user: 'gtid' host: '10.76.24.77' (Got an error writing communication packets) 2024-07-01 4:36:43 73738 [Note] Start binlog_dump to slave_server(2), pos(db1-binary.165118, 191320269), using_gtid(0), gtid('') 2024-07-01 4:36:46 73738 [Warning] Aborted connection 73738 to db: 'unconnected' user: 'gtid' host: '10.76.24.77' (Got an error writing communication packets) 2024-07-01 4:36:46 74318 [Note] Start binlog_dump to slave_server(2), pos(db1-binary.165119, 31215127), using_gtid(0), gtid('') 2024-07-01 4:36:50 74318 [Warning] Aborted connection 74318 to db: 'unconnected' user: 'gtid' host: '10.76.24.77' (Got an error writing communication packets) 2024-07-01 4:36:50 74983 [Note] Start binlog_dump to slave_server(2), pos(db1-binary.165119, 86648459), using_gtid(0), gtid('') 2024-07-01 4:37:28 74983 [Warning] Aborted connection 74983 to db: 'unconnected' user: 'gtid' host: '10.76.24.77' (Got an error writing communication packets) 2024-07-01 4:37:37 82742 [Note] Start binlog_dump to slave_server(2), pos(db1-binary.165121, 189848062), using_gtid(0), gtid('') 2024-07-01 4:37:42 82742 [Warning] Aborted connection 82742 to db: 'unconnected' user: 'gtid' host: '10.76.24.77' (Got an error writing communication packets) 2024-07-01 4:37:42 83483 [Note] Start binlog_dump to slave_server(2), pos(db1-binary.165122, 178801929), using_gtid(0), gtid('') 2024-07-01 4:37:46 83483 [Warning] Aborted connection 83483 to db: 'unconnected' user: 'gtid' host: '10.76.24.77' (Got an error writing communication packets) 2024-07-01 4:37:46 84086 [Note] Start binlog_dump to slave_server(2), pos(db1-binary.165123, 19172532), using_gtid(0), gtid('') 2024-07-01 4:37:50 84086 [Warning] Aborted connection 84086 to db: 'unconnected' user: 'gtid' host: '10.76.24.77' (Got an error writing communication packets) 2024-07-01 4:37:50 84804 [Note] Start binlog_dump to slave_server(2), pos(db1-binary.165123, 79819666), using_gtid(0), gtid('') 2024-07-01 4:37:53 84804 [Warning] Aborted connection 84804 to db: 'unconnected' user: 'gtid' host: '10.76.24.77' (Got an error writing communication packets) 2024-07-01 4:37:53 85422 [Note] Start binlog_dump to slave_server(2), pos(db1-binary.165123, 131983322), using_gtid(0), gtid('') 2024-07-01 4:38:14 88836 [Note] Start binlog_dump to slave_server(2), pos(db1-binary.165125, 467), using_gtid(0), gtid('') 2024-07-01 4:38:14 85422 [Warning] Aborted connection 85422 to db: 'unconnected' user: 'gtid' host: '10.76.24.77' (A slave with the same server_uuid/server_id as this slave has co) 2024-07-01 4:38:18 88836 [Warning] Aborted connection 88836 to db: 'unconnected' user: 'gtid' host: '10.76.24.77' (Got an error writing communication packets) 2024-07-01 4:38:18 89537 [Note] Start binlog_dump to slave_server(2), pos(db1-binary.165125, 61817954), using_gtid(0), gtid('') 2024-07-01 4:38:21 89537 [Warning] Aborted connection 89537 to db: 'unconnected' user: 'gtid' host: '10.76.24.77' (Got an error writing communication packets) 2024-07-01 4:38:21 90120 [Note] Start binlog_dump to slave_server(2), pos(db1-binary.165125, 112071830), using_gtid(0), gtid('') 2024-07-01 4:38:25 90120 [Warning] Aborted connection 90120 to db: 'unconnected' user: 'gtid' host: '10.76.24.77' (Got an error writing communication packets) 2024-07-01 4:38:25 90746 [Note] Start binlog_dump to slave_server(2), pos(db1-binary.165125, 166353681), using_gtid(0), gtid('') 2024-07-01 4:38:30 90746 [Warning] Aborted connection 90746 to db: 'unconnected' user: 'gtid' host: '10.76.24.77' (Got an error writing communication packets) 2024-07-01 4:38:30 91622 [Note] Start binlog_dump to slave_server(2), pos(db1-binary.165126, 31248465), using_gtid(0), gtid('') 2024-07-01 4:38:33 91622 [Warning] Aborted connection 91622 to db: 'unconnected' user: 'gtid' host: '10.76.24.77' (Got an error writing communication packets) 2024-07-01 4:38:33 92201 [Note] Start binlog_dump to slave_server(2), pos(db1-binary.165126, 81241287), using_gtid(0), gtid('') 2024-07-01 4:38:36 92201 [Warning] Aborted connection 92201 to db: 'unconnected' user: 'gtid' host: '10.76.24.77' (Got an error writing communication packets) 2024-07-01 4:38:36 92759 [Note] Start binlog_dump to slave_server(2), pos(db1-binary.165126, 129406095), using_gtid(0), gtid('') 2024-07-01 4:39:06 92759 [Warning] Aborted connection 92759 to db: 'unconnected' user: 'gtid' host: '10.76.24.77' (Got an error writing communication packets) 2024-07-01 4:39:09 98286 [Note] Start binlog_dump to slave_server(2), pos(db1-binary.165128, 146934194), using_gtid(0), gtid('') 2024-07-01 4:39:34 9 [ERROR] mariadbd: Can't find record in 'activesessions' 2024-07-01 4:39:34 9 [ERROR] Slave SQL: Could not execute Delete_rows_v1 event on table aaadb.activesessions; Can't find record in 'activesessions', Error_code: 1032; handler error HA_ERR_KEY_NOT_FOUND; the event's master log db2-binary.165683, end_log_pos 162602671, Gtid 0-2-18664651468, Internal MariaDB error code: 1032 2024-07-01 4:39:34 9 [Warning] Slave: Can't find record in 'activesessions' Error_code: 1032 2024-07-01 4:39:34 9 [ERROR] Error running query, slave SQL thread aborted. Fix the problem, and restart the slave SQL thread with "SLAVE START". We stopped at log 'db2-binary.165683' position 162601919 2024-07-01 4:39:34 310 [Note] Error reading relay log event: slave SQL thread was killed 2024-07-01 4:39:34 310 [Note] Slave SQL thread exiting, replication stopped in log 'db2-binary.165683' at position 162601919, master: 10.76.24.77:3306 2024-07-01 4:41:27 309 [Note] Slave I/O thread exiting, read up to log 'db2-binary.165693', position 19573666, master 10.76.24.77:3306 2024-07-01 4:41:27 100011 [Note] Slave I/O thread: Start asynchronous replication to master 'gtid@10.76.24.77:3306' in log 'db2-binary.165693' at position 19573666 2024-07-01 4:41:27 100012 [Note] Slave SQL thread initialized, starting replication in log 'db2-binary.165683' at position 162601919, relay log './db1-relay.064290' position: 9141297 2024-07-01 4:41:27 100011 [Note] Slave I/O thread: connected to master 'gtid@10.76.24.77:3306',replication started in log 'db2-binary.165693' at position 19573666 2024-07-01 4:41:27 100012 [Note] 'SQL_SLAVE_SKIP_COUNTER=100' executed at relay_log_file='./db1-relay.064290', relay_log_pos='9141297', master_log_name='db2-binary.165683', master_log_pos='162601919' and new position at relay_log_file='./db1-relay.064290', relay_log_pos='9169821', master_log_name='db2-binary.165683', master_log_pos='164603976' 2024-07-01 4:41:28 17 [ERROR] mariadbd: Can't find record in 'activesessions' 2024-07-01 4:41:28 17 [ERROR] Slave SQL: Could not execute Delete_rows_v1 event on table aaadb.activesessions; Can't find record in 'activesessions', Error_code: 1032; handler error HA_ERR_KEY_NOT_FOUND; the event's master log db2-binary.165685, end_log_pos 58316640, Gtid 0-2-18664659871, Internal MariaDB error code: 1032 2024-07-01 4:41:28 17 [Warning] Slave: Can't find record in 'activesessions' Error_code: 1032 2024-07-01 4:41:28 17 [ERROR] Error running query, slave SQL thread aborted. Fix the problem, and restart the slave SQL thread with "SLAVE START". We stopped at log 'db2-binary.165685' position 56373484 2024-07-01 4:41:28 6 [ERROR] Slave (additional info): Commit failed due to failure of an earlier commit on which this one depends Error_code: 1964 2024-07-01 4:41:28 6 [Warning] Slave: Commit failed due to failure of an earlier commit on which this one depends Error_code: 1964 2024-07-01 4:41:28 6 [ERROR] Error running query, slave SQL thread aborted. Fix the problem, and restart the slave SQL thread with "SLAVE START". We stopped at log 'db2-binary.165685' position 56373484 2024-07-01 4:41:28 16 [ERROR] Slave (additional info): Commit failed due to failure of an earlier commit on which this one depends Error_code: 1964 2024-07-01 4:41:28 16 [Warning] Slave: Commit failed due to failure of an earlier commit on which this one depends Error_code: 1964 2024-07-01 4:41:28 16 [ERROR] Error running query, slave SQL thread aborted. Fix the problem, and restart the slave SQL thread with "SLAVE START". We stopped at log 'db2-binary.165685' position 56373484 2024-07-01 4:41:28 11 [ERROR] Slave (additional info): Commit failed due to failure of an earlier commit on which this one depends Error_code: 1964 2024-07-01 4:41:28 11 [Warning] Slave: Commit failed due to failure of an earlier commit on which this one depends Error_code: 1964 2024-07-01 4:41:28 11 [ERROR] Error running query, slave SQL thread aborted. Fix the problem, and restart the slave SQL thread with "SLAVE START". We stopped at log 'db2-binary.165685' position 56373484 2024-07-01 4:41:28 13 [ERROR] Slave (additional info): Commit failed due to failure of an earlier commit on which this one depends Error_code: 1964 2024-07-01 4:41:28 13 [Warning] Slave: Commit failed due to failure of an earlier commit on which this one depends Error_code: 1964 2024-07-01 4:41:28 13 [ERROR] Error running query, slave SQL thread aborted. Fix the problem, and restart the slave SQL thread with "SLAVE START". We stopped at log 'db2-binary.165685' position 56373484 2024-07-01 4:41:28 9 [ERROR] Slave (additional info): Commit failed due to failure of an earlier commit on which this one depends Error_code: 1964 2024-07-01 4:41:28 9 [Warning] Slave: Commit failed due to failure of an earlier commit on which this one depends Error_code: 1964 2024-07-01 4:41:28 9 [ERROR] Error running query, slave SQL thread aborted. Fix the problem, and restart the slave SQL thread with "SLAVE START". We stopped at log 'db2-binary.165685' position 56373484 2024-07-01 4:41:28 12 [ERROR] Slave (additional info): Commit failed due to failure of an earlier commit on which this one depends Error_code: 1964 2024-07-01 4:41:28 12 [Warning] Slave: Commit failed due to failure of an earlier commit on which this one depends Error_code: 1964 2024-07-01 4:41:28 12 [ERROR] Error running query, slave SQL thread aborted. Fix the problem, and restart the slave SQL thread with "SLAVE START". We stopped at log 'db2-binary.165685' position 56373484 2024-07-01 4:41:28 10 [ERROR] Slave (additional info): Commit failed due to failure of an earlier commit on which this one depends Error_code: 1964 2024-07-01 4:41:28 10 [Warning] Slave: Commit failed due to failure of an earlier commit on which this one depends Error_code: 1964 2024-07-01 4:41:28 10 [ERROR] Error running query, slave SQL thread aborted. Fix the problem, and restart the slave SQL thread with "SLAVE START". We stopped at log 'db2-binary.165685' position 56373484 2024-07-01 4:41:28 8 [ERROR] Slave (additional info): Commit failed due to failure of an earlier commit on which this one depends Error_code: 1964 2024-07-01 4:41:28 8 [Warning] Slave: Commit failed due to failure of an earlier commit on which this one depends Error_code: 1964 2024-07-01 4:41:28 8 [ERROR] Error running query, slave SQL thread aborted. Fix the problem, and restart the slave SQL thread with "SLAVE START". We stopped at log 'db2-binary.165685' position 56373484 2024-07-01 4:41:28 15 [ERROR] Slave (additional info): Commit failed due to failure of an earlier commit on which this one depends Error_code: 1964 2024-07-01 4:41:28 15 [Warning] Slave: Commit failed due to failure of an earlier commit on which this one depends Error_code: 1964 2024-07-01 4:41:28 15 [ERROR] Error running query, slave SQL thread aborted. Fix the problem, and restart the slave SQL thread with "SLAVE START". We stopped at log 'db2-binary.165685' position 56373484 2024-07-01 4:41:28 7 [ERROR] Slave (additional info): Commit failed due to failure of an earlier commit on which this one depends Error_code: 1964 2024-07-01 4:41:28 7 [Warning] Slave: Commit failed due to failure of an earlier commit on which this one depends Error_code: 1964 2024-07-01 4:41:28 7 [ERROR] Error running query, slave SQL thread aborted. Fix the problem, and restart the slave SQL thread with "SLAVE START". We stopped at log 'db2-binary.165685' position 56373484 2024-07-01 4:41:28 14 [ERROR] Slave (additional info): Commit failed due to failure of an earlier commit on which this one depends Error_code: 1964 2024-07-01 4:41:28 14 [Warning] Slave: Commit failed due to failure of an earlier commit on which this one depends Error_code: 1964 2024-07-01 4:41:28 14 [ERROR] Error running query, slave SQL thread aborted. Fix the problem, and restart the slave SQL thread with "SLAVE START". We stopped at log 'db2-binary.165685' position 56373484 2024-07-01 4:41:28 100012 [Note] Slave SQL thread exiting, replication stopped in log 'db2-binary.165685' at position 56373484, master: 10.76.24.77:3306 2024-07-01 4:43:50 100275 [Note] Start binlog_dump to slave_server(2), pos(db1-binary.165129, 126335055), using_gtid(0), gtid('') 2024-07-01 4:54:44 100011 [Note] Slave I/O thread exiting, read up to log 'db2-binary.165897', position 164363797, master 10.76.24.77:3306 2024-07-01 4:54:44 100745 [Note] Slave I/O thread: Start asynchronous replication to master 'gtid@10.76.24.77:3306' in log 'db2-binary.165897' at position 164363797 2024-07-01 4:54:44 100746 [Note] Slave SQL thread initialized, starting replication in log 'db2-binary.165685' at position 56373484, relay log './db1-relay.064294' position: 2848072 2024-07-01 4:54:44 100745 [Note] Slave I/O thread: connected to master 'gtid@10.76.24.77:3306',replication started in log 'db2-binary.165897' at position 164363797 2024-07-01 4:54:44 100746 [Note] 'SQL_SLAVE_SKIP_COUNTER=100' executed at relay_log_file='./db1-relay.064294', relay_log_pos='2848072', master_log_name='db2-binary.165685', master_log_pos='56373484' and new position at relay_log_file='./db1-relay.064294', relay_log_pos='2880603', master_log_name='db2-binary.165685', master_log_pos='58348428' 2024-07-01 4:54:45 15 [ERROR] mariadbd: Can't find record in 'activesessions' 2024-07-01 4:54:45 15 [ERROR] Slave SQL: Could not execute Delete_rows_v1 event on table aaadb.activesessions; Can't find record in 'activesessions', Error_code: 1032; handler error HA_ERR_KEY_NOT_FOUND; the event's master log db2-binary.165686, end_log_pos 31737413, Gtid 0-2-18664675992, Internal MariaDB error code: 1032 2024-07-01 4:54:45 15 [Warning] Slave: Can't find record in 'activesessions' Error_code: 1032 2024-07-01 4:54:45 15 [ERROR] Error running query, slave SQL thread aborted. Fix the problem, and restart the slave SQL thread with "SLAVE START". We stopped at log 'db2-binary.165686' position 31736682 2024-07-01 4:54:45 8 [ERROR] Slave (additional info): Commit failed due to failure of an earlier commit on which this one depends Error_code: 1964 2024-07-01 4:54:45 8 [Warning] Slave: Commit failed due to failure of an earlier commit on which this one depends Error_code: 1964 2024-07-01 4:54:45 8 [ERROR] Error running query, slave SQL thread aborted. Fix the problem, and restart the slave SQL thread with "SLAVE START". We stopped at log 'db2-binary.165686' position 31736682 2024-07-01 4:54:45 10 [ERROR] Slave (additional info): Commit failed due to failure of an earlier commit on which this one depends Error_code: 1964 2024-07-01 4:54:45 10 [Warning] Slave: Commit failed due to failure of an earlier commit on which this one depends Error_code: 1964 2024-07-01 4:54:45 10 [ERROR] Error running query, slave SQL thread aborted. Fix the problem, and restart the slave SQL thread with "SLAVE START". We stopped at log 'db2-binary.165686' position 31736682 2024-07-01 4:54:45 12 [ERROR] Slave (additional info): Commit failed due to failure of an earlier commit on which this one depends Error_code: 1964 2024-07-01 4:54:45 12 [Warning] Slave: Commit failed due to failure of an earlier commit on which this one depends Error_code: 1964 2024-07-01 4:54:45 12 [ERROR] Error running query, slave SQL thread aborted. Fix the problem, and restart the slave SQL thread with "SLAVE START". We stopped at log 'db2-binary.165686' position 31736682 2024-07-01 4:54:45 9 [ERROR] Slave (additional info): Commit failed due to failure of an earlier commit on which this one depends Error_code: 1964 2024-07-01 4:54:45 9 [Warning] Slave: Commit failed due to failure of an earlier commit on which this one depends Error_code: 1964 2024-07-01 4:54:45 9 [ERROR] Error running query, slave SQL thread aborted. Fix the problem, and restart the slave SQL thread with "SLAVE START". We stopped at log 'db2-binary.165686' position 31736682 2024-07-01 4:54:45 13 [ERROR] Slave (additional info): Commit failed due to failure of an earlier commit on which this one depends Error_code: 1964 2024-07-01 4:54:45 13 [Warning] Slave: Commit failed due to failure of an earlier commit on which this one depends Error_code: 1964 2024-07-01 4:54:45 13 [ERROR] Error running query, slave SQL thread aborted. Fix the problem, and restart the slave SQL thread with "SLAVE START". We stopped at log 'db2-binary.165686' position 31736682 2024-07-01 4:54:45 11 [ERROR] Slave (additional info): Commit failed due to failure of an earlier commit on which this one depends Error_code: 1964 2024-07-01 4:54:45 11 [Warning] Slave: Commit failed due to failure of an earlier commit on which this one depends Error_code: 1964 2024-07-01 4:54:45 11 [ERROR] Error running query, slave SQL thread aborted. Fix the problem, and restart the slave SQL thread with "SLAVE START". We stopped at log 'db2-binary.165686' position 31736682 2024-07-01 4:54:45 16 [ERROR] Slave (additional info): Commit failed due to failure of an earlier commit on which this one depends Error_code: 1964 2024-07-01 4:54:45 16 [Warning] Slave: Commit failed due to failure of an earlier commit on which this one depends Error_code: 1964 2024-07-01 4:54:45 16 [ERROR] Error running query, slave SQL thread aborted. Fix the problem, and restart the slave SQL thread with "SLAVE START". We stopped at log 'db2-binary.165686' position 31736682 2024-07-01 4:54:45 6 [ERROR] Slave (additional info): Commit failed due to failure of an earlier commit on which this one depends Error_code: 1964 2024-07-01 4:54:45 6 [Warning] Slave: Commit failed due to failure of an earlier commit on which this one depends Error_code: 1964 2024-07-01 4:54:45 6 [ERROR] Error running query, slave SQL thread aborted. Fix the problem, and restart the slave SQL thread with "SLAVE START". We stopped at log 'db2-binary.165686' position 31736682 2024-07-01 4:54:45 17 [ERROR] Slave (additional info): Commit failed due to failure of an earlier commit on which this one depends Error_code: 1964 2024-07-01 4:54:45 17 [Warning] Slave: Commit failed due to failure of an earlier commit on which this one depends Error_code: 1964 2024-07-01 4:54:45 17 [ERROR] Error running query, slave SQL thread aborted. Fix the problem, and restart the slave SQL thread with "SLAVE START". We stopped at log 'db2-binary.165686' position 31736682 2024-07-01 4:54:45 14 [ERROR] Slave (additional info): Commit failed due to failure of an earlier commit on which this one depends Error_code: 1964 2024-07-01 4:54:45 14 [Warning] Slave: Commit failed due to failure of an earlier commit on which this one depends Error_code: 1964 2024-07-01 4:54:45 14 [ERROR] Error running query, slave SQL thread aborted. Fix the problem, and restart the slave SQL thread with "SLAVE START". We stopped at log 'db2-binary.165686' position 31736682 2024-07-01 4:54:45 7 [ERROR] Slave (additional info): Commit failed due to failure of an earlier commit on which this one depends Error_code: 1964 2024-07-01 4:54:45 7 [Warning] Slave: Commit failed due to failure of an earlier commit on which this one depends Error_code: 1964 2024-07-01 4:54:45 7 [ERROR] Error running query, slave SQL thread aborted. Fix the problem, and restart the slave SQL thread with "SLAVE START". We stopped at log 'db2-binary.165686' position 31736682 2024-07-01 4:54:45 100746 [Note] Slave SQL thread exiting, replication stopped in log 'db2-binary.165686' at position 31736682, master: 10.76.24.77:3306 2024-07-01 4:55:00 100745 [Note] Slave I/O thread exiting, read up to log 'db2-binary.165897', position 189267819, master 10.76.24.77:3306 2024-07-01 4:55:00 101049 [Note] Slave I/O thread: Start asynchronous replication to master 'gtid@10.76.24.77:3306' in log 'db2-binary.165897' at position 189267819 2024-07-01 4:55:00 101050 [Note] Slave SQL thread initialized, starting replication in log 'db2-binary.165686' at position 31736682, relay log './db1-relay.064296' position: 1751872 2024-07-01 4:55:00 101049 [Note] Slave I/O thread: connected to master 'gtid@10.76.24.77:3306',replication started in log 'db2-binary.165897' at position 189267819 2024-07-01 4:55:00 101050 [Note] 'SQL_SLAVE_SKIP_COUNTER=100' executed at relay_log_file='./db1-relay.064296', relay_log_pos='1751872', master_log_name='db2-binary.165686', master_log_pos='31736682' and new position at relay_log_file='./db1-relay.064296', relay_log_pos='1771799', master_log_name='db2-binary.165686', master_log_pos='31756609' 2024-07-01 4:55:00 16 [ERROR] mariadbd: Can't find record in 'activesessions' 2024-07-01 4:55:00 16 [ERROR] Slave SQL: Could not execute Delete_rows_v1 event on table aaadb.activesessions; Can't find record in 'activesessions', Error_code: 1032; handler error HA_ERR_KEY_NOT_FOUND; the event's master log db2-binary.165686, end_log_pos 36015329, Gtid 0-2-18664676241, Internal MariaDB error code: 1032 2024-07-01 4:55:00 16 [Warning] Slave: Can't find record in 'activesessions' Error_code: 1032 2024-07-01 4:55:00 16 [ERROR] Error running query, slave SQL thread aborted. Fix the problem, and restart the slave SQL thread with "SLAVE START". We stopped at log 'db2-binary.165686' position 36014592 2024-07-01 4:55:00 11 [ERROR] Slave (additional info): Commit failed due to failure of an earlier commit on which this one depends Error_code: 1964 2024-07-01 4:55:00 11 [Warning] Slave: Commit failed due to failure of an earlier commit on which this one depends Error_code: 1964 2024-07-01 4:55:00 11 [ERROR] Error running query, slave SQL thread aborted. Fix the problem, and restart the slave SQL thread with "SLAVE START". We stopped at log 'db2-binary.165686' position 36014592 2024-07-01 4:55:00 13 [ERROR] Slave (additional info): Commit failed due to failure of an earlier commit on which this one depends Error_code: 1964 2024-07-01 4:55:00 13 [Warning] Slave: Commit failed due to failure of an earlier commit on which this one depends Error_code: 1964 2024-07-01 4:55:00 13 [ERROR] Error running query, slave SQL thread aborted. Fix the problem, and restart the slave SQL thread with "SLAVE START". We stopped at log 'db2-binary.165686' position 36014592 2024-07-01 4:55:00 9 [ERROR] Slave (additional info): Commit failed due to failure of an earlier commit on which this one depends Error_code: 1964 2024-07-01 4:55:00 9 [Warning] Slave: Commit failed due to failure of an earlier commit on which this one depends Error_code: 1964 2024-07-01 4:55:00 9 [ERROR] Error running query, slave SQL thread aborted. Fix the problem, and restart the slave SQL thread with "SLAVE START". We stopped at log 'db2-binary.165686' position 36014592 2024-07-01 4:55:00 12 [ERROR] Slave (additional info): Commit failed due to failure of an earlier commit on which this one depends Error_code: 1964 2024-07-01 4:55:00 12 [Warning] Slave: Commit failed due to failure of an earlier commit on which this one depends Error_code: 1964 2024-07-01 4:55:00 12 [ERROR] Error running query, slave SQL thread aborted. Fix the problem, and restart the slave SQL thread with "SLAVE START". We stopped at log 'db2-binary.165686' position 36014592 2024-07-01 4:55:00 10 [ERROR] Slave (additional info): Commit failed due to failure of an earlier commit on which this one depends Error_code: 1964 2024-07-01 4:55:00 10 [Warning] Slave: Commit failed due to failure of an earlier commit on which this one depends Error_code: 1964 2024-07-01 4:55:00 10 [ERROR] Error running query, slave SQL thread aborted. Fix the problem, and restart the slave SQL thread with "SLAVE START". We stopped at log 'db2-binary.165686' position 36014592 2024-07-01 4:55:00 8 [ERROR] Slave (additional info): Commit failed due to failure of an earlier commit on which this one depends Error_code: 1964 2024-07-01 4:55:00 8 [Warning] Slave: Commit failed due to failure of an earlier commit on which this one depends Error_code: 1964 2024-07-01 4:55:00 8 [ERROR] Error running query, slave SQL thread aborted. Fix the problem, and restart the slave SQL thread with "SLAVE START". We stopped at log 'db2-binary.165686' position 36014592 2024-07-01 4:55:00 15 [ERROR] Slave (additional info): Commit failed due to failure of an earlier commit on which this one depends Error_code: 1964 2024-07-01 4:55:00 15 [Warning] Slave: Commit failed due to failure of an earlier commit on which this one depends Error_code: 1964 2024-07-01 4:55:00 15 [ERROR] Error running query, slave SQL thread aborted. Fix the problem, and restart the slave SQL thread with "SLAVE START". We stopped at log 'db2-binary.165686' position 36014592 2024-07-01 4:55:00 7 [ERROR] Slave (additional info): Commit failed due to failure of an earlier commit on which this one depends Error_code: 1964 2024-07-01 4:55:00 7 [Warning] Slave: Commit failed due to failure of an earlier commit on which this one depends Error_code: 1964 2024-07-01 4:55:00 7 [ERROR] Error running query, slave SQL thread aborted. Fix the problem, and restart the slave SQL thread with "SLAVE START". We stopped at log 'db2-binary.165686' position 36014592 2024-07-01 4:55:00 14 [ERROR] Slave (additional info): Commit failed due to failure of an earlier commit on which this one depends Error_code: 1964 2024-07-01 4:55:00 14 [Warning] Slave: Commit failed due to failure of an earlier commit on which this one depends Error_code: 1964 2024-07-01 4:55:00 14 [ERROR] Error running query, slave SQL thread aborted. Fix the problem, and restart the slave SQL thread with "SLAVE START". We stopped at log 'db2-binary.165686' position 36014592 2024-07-01 4:55:00 17 [ERROR] Slave (additional info): Commit failed due to failure of an earlier commit on which this one depends Error_code: 1964 2024-07-01 4:55:00 17 [Warning] Slave: Commit failed due to failure of an earlier commit on which this one depends Error_code: 1964 2024-07-01 4:55:00 17 [ERROR] Error running query, slave SQL thread aborted. Fix the problem, and restart the slave SQL thread with "SLAVE START". We stopped at log 'db2-binary.165686' position 36014592 2024-07-01 4:55:00 6 [ERROR] Slave (additional info): Commit failed due to failure of an earlier commit on which this one depends Error_code: 1964 2024-07-01 4:55:00 6 [Warning] Slave: Commit failed due to failure of an earlier commit on which this one depends Error_code: 1964 2024-07-01 4:55:00 6 [ERROR] Error running query, slave SQL thread aborted. Fix the problem, and restart the slave SQL thread with "SLAVE START". We stopped at log 'db2-binary.165686' position 36014592 2024-07-01 4:55:00 101050 [Note] Slave SQL thread exiting, replication stopped in log 'db2-binary.165686' at position 36014592, master: 10.76.24.77:3306 2024-07-01 4:55:09 101049 [Note] Slave I/O thread exiting, read up to log 'db2-binary.165897', position 205339647, master 10.76.24.77:3306 2024-07-01 4:55:09 101065 [Note] Slave I/O thread: Start asynchronous replication to master 'gtid@10.76.24.77:3306' in log 'db2-binary.165897' at position 205339647 2024-07-01 4:55:09 101066 [Note] Slave SQL thread initialized, starting replication in log 'db2-binary.165686' at position 36014592, relay log './db1-relay.064296' position: 2031369 2024-07-01 4:55:09 101065 [Note] Slave I/O thread: connected to master 'gtid@10.76.24.77:3306',replication started in log 'db2-binary.165897' at position 205339647 2024-07-01 4:55:09 101066 [Note] 'SQL_SLAVE_SKIP_COUNTER=100' executed at relay_log_file='./db1-relay.064296', relay_log_pos='2031369', master_log_name='db2-binary.165686', master_log_pos='36014592' and new position at relay_log_file='./db1-relay.064296', relay_log_pos='2058209', master_log_name='db2-binary.165686', master_log_pos='38040370' 2024-07-01 4:55:09 11 [ERROR] mariadbd: Can't find record in 'activesessions' 2024-07-01 4:55:09 11 [ERROR] Slave SQL: Could not execute Delete_rows_v1 event on table aaadb.activesessions; Can't find record in 'activesessions', Error_code: 1032; handler error HA_ERR_KEY_NOT_FOUND; the event's master log db2-binary.165686, end_log_pos 38212067, Gtid 0-2-18664676376, Internal MariaDB error code: 1032 2024-07-01 4:55:09 11 [Warning] Slave: Can't find record in 'activesessions' Error_code: 1032 2024-07-01 4:55:09 11 [ERROR] Error running query, slave SQL thread aborted. Fix the problem, and restart the slave SQL thread with "SLAVE START". We stopped at log 'db2-binary.165686' position 38211331 2024-07-01 4:55:09 16 [ERROR] Slave (additional info): Commit failed due to failure of an earlier commit on which this one depends Error_code: 1964 2024-07-01 4:55:09 16 [Warning] Slave: Commit failed due to failure of an earlier commit on which this one depends Error_code: 1964 2024-07-01 4:55:09 16 [ERROR] Error running query, slave SQL thread aborted. Fix the problem, and restart the slave SQL thread with "SLAVE START". We stopped at log 'db2-binary.165686' position 38211331 2024-07-01 4:55:09 6 [ERROR] Slave (additional info): Commit failed due to failure of an earlier commit on which this one depends Error_code: 1964 2024-07-01 4:55:09 6 [Warning] Slave: Commit failed due to failure of an earlier commit on which this one depends Error_code: 1964 2024-07-01 4:55:09 6 [ERROR] Error running query, slave SQL thread aborted. Fix the problem, and restart the slave SQL thread with "SLAVE START". We stopped at log 'db2-binary.165686' position 38211331 2024-07-01 4:55:09 17 [ERROR] Slave (additional info): Commit failed due to failure of an earlier commit on which this one depends Error_code: 1964 2024-07-01 4:55:09 17 [Warning] Slave: Commit failed due to failure of an earlier commit on which this one depends Error_code: 1964 2024-07-01 4:55:09 17 [ERROR] Error running query, slave SQL thread aborted. Fix the problem, and restart the slave SQL thread with "SLAVE START". We stopped at log 'db2-binary.165686' position 38211331 2024-07-01 4:55:09 14 [ERROR] Slave (additional info): Commit failed due to failure of an earlier commit on which this one depends Error_code: 1964 2024-07-01 4:55:09 14 [Warning] Slave: Commit failed due to failure of an earlier commit on which this one depends Error_code: 1964 2024-07-01 4:55:09 14 [ERROR] Error running query, slave SQL thread aborted. Fix the problem, and restart the slave SQL thread with "SLAVE START". We stopped at log 'db2-binary.165686' position 38211331 2024-07-01 4:55:09 7 [ERROR] Slave (additional info): Commit failed due to failure of an earlier commit on which this one depends Error_code: 1964 2024-07-01 4:55:09 7 [Warning] Slave: Commit failed due to failure of an earlier commit on which this one depends Error_code: 1964 2024-07-01 4:55:09 7 [ERROR] Error running query, slave SQL thread aborted. Fix the problem, and restart the slave SQL thread with "SLAVE START". We stopped at log 'db2-binary.165686' position 38211331 2024-07-01 4:55:09 15 [ERROR] Slave (additional info): Commit failed due to failure of an earlier commit on which this one depends Error_code: 1964 2024-07-01 4:55:09 15 [Warning] Slave: Commit failed due to failure of an earlier commit on which this one depends Error_code: 1964 2024-07-01 4:55:09 15 [ERROR] Error running query, slave SQL thread aborted. Fix the problem, and restart the slave SQL thread with "SLAVE START". We stopped at log 'db2-binary.165686' position 38211331 2024-07-01 4:55:09 8 [ERROR] Slave (additional info): Commit failed due to failure of an earlier commit on which this one depends Error_code: 1964 2024-07-01 4:55:09 8 [Warning] Slave: Commit failed due to failure of an earlier commit on which this one depends Error_code: 1964 2024-07-01 4:55:09 8 [ERROR] Error running query, slave SQL thread aborted. Fix the problem, and restart the slave SQL thread with "SLAVE START". We stopped at log 'db2-binary.165686' position 38211331 2024-07-01 4:55:09 10 [ERROR] Slave (additional info): Commit failed due to failure of an earlier commit on which this one depends Error_code: 1964 2024-07-01 4:55:09 10 [Warning] Slave: Commit failed due to failure of an earlier commit on which this one depends Error_code: 1964 2024-07-01 4:55:09 10 [ERROR] Error running query, slave SQL thread aborted. Fix the problem, and restart the slave SQL thread with "SLAVE START". We stopped at log 'db2-binary.165686' position 38211331 2024-07-01 4:55:09 12 [ERROR] Slave (additional info): Commit failed due to failure of an earlier commit on which this one depends Error_code: 1964 2024-07-01 4:55:09 12 [Warning] Slave: Commit failed due to failure of an earlier commit on which this one depends Error_code: 1964 2024-07-01 4:55:09 12 [ERROR] Error running query, slave SQL thread aborted. Fix the problem, and restart the slave SQL thread with "SLAVE START". We stopped at log 'db2-binary.165686' position 38211331 2024-07-01 4:55:09 9 [ERROR] Slave (additional info): Commit failed due to failure of an earlier commit on which this one depends Error_code: 1964 2024-07-01 4:55:09 9 [Warning] Slave: Commit failed due to failure of an earlier commit on which this one depends Error_code: 1964 2024-07-01 4:55:09 9 [ERROR] Error running query, slave SQL thread aborted. Fix the problem, and restart the slave SQL thread with "SLAVE START". We stopped at log 'db2-binary.165686' position 38211331 2024-07-01 4:55:09 13 [ERROR] Slave (additional info): Commit failed due to failure of an earlier commit on which this one depends Error_code: 1964 2024-07-01 4:55:09 13 [Warning] Slave: Commit failed due to failure of an earlier commit on which this one depends Error_code: 1964 2024-07-01 4:55:09 13 [ERROR] Error running query, slave SQL thread aborted. Fix the problem, and restart the slave SQL thread with "SLAVE START". We stopped at log 'db2-binary.165686' position 38211331 2024-07-01 4:55:09 101066 [Note] Slave SQL thread exiting, replication stopped in log 'db2-binary.165686' at position 38211331, master: 10.76.24.77:3306 2024-07-01 4:55:15 101065 [Note] Slave I/O thread exiting, read up to log 'db2-binary.165898', position 4928651, master 10.76.24.77:3306 2024-07-01 4:55:15 101075 [Note] Slave I/O thread: Start asynchronous replication to master 'gtid@10.76.24.77:3306' in log 'db2-binary.165898' at position 4928651 2024-07-01 4:55:15 101076 [Note] Slave SQL thread initialized, starting replication in log 'db2-binary.165686' at position 38211331, relay log './db1-relay.064296' position: 2229170 2024-07-01 4:55:15 101075 [Note] Slave I/O thread: connected to master 'gtid@10.76.24.77:3306',replication started in log 'db2-binary.165898' at position 4928651 2024-07-01 4:55:15 101076 [Note] 'SQL_SLAVE_SKIP_COUNTER=100' executed at relay_log_file='./db1-relay.064296', relay_log_pos='2229170', master_log_name='db2-binary.165686', master_log_pos='38211331' and new position at relay_log_file='./db1-relay.064296', relay_log_pos='2250193', master_log_name='db2-binary.165686', master_log_pos='38232354' 2024-07-01 4:55:15 7 [ERROR] mariadbd: Can't find record in 'activesessions' 2024-07-01 4:55:15 7 [ERROR] Slave SQL: Could not execute Delete_rows_v1 event on table aaadb.activesessions; Can't find record in 'activesessions', Error_code: 1032; handler error HA_ERR_KEY_NOT_FOUND; the event's master log db2-binary.165686, end_log_pos 44862382, Gtid 0-2-18664676864, Internal MariaDB error code: 1032 2024-07-01 4:55:15 7 [Warning] Slave: Can't find record in 'activesessions' Error_code: 1032 2024-07-01 4:55:15 7 [ERROR] Error running query, slave SQL thread aborted. Fix the problem, and restart the slave SQL thread with "SLAVE START". We stopped at log 'db2-binary.165686' position 44861651 2024-07-01 4:55:15 14 [ERROR] Slave (additional info): Commit failed due to failure of an earlier commit on which this one depends Error_code: 1964 2024-07-01 4:55:15 14 [Warning] Slave: Commit failed due to failure of an earlier commit on which this one depends Error_code: 1964 2024-07-01 4:55:15 14 [ERROR] Error running query, slave SQL thread aborted. Fix the problem, and restart the slave SQL thread with "SLAVE START". We stopped at log 'db2-binary.165686' position 44861651 2024-07-01 4:55:15 17 [ERROR] Slave (additional info): Commit failed due to failure of an earlier commit on which this one depends Error_code: 1964 2024-07-01 4:55:15 17 [Warning] Slave: Commit failed due to failure of an earlier commit on which this one depends Error_code: 1964 2024-07-01 4:55:15 17 [ERROR] Error running query, slave SQL thread aborted. Fix the problem, and restart the slave SQL thread with "SLAVE START". We stopped at log 'db2-binary.165686' position 44861651 2024-07-01 4:55:15 6 [ERROR] Slave (additional info): Commit failed due to failure of an earlier commit on which this one depends Error_code: 1964 2024-07-01 4:55:15 6 [Warning] Slave: Commit failed due to failure of an earlier commit on which this one depends Error_code: 1964 2024-07-01 4:55:15 6 [ERROR] Error running query, slave SQL thread aborted. Fix the problem, and restart the slave SQL thread with "SLAVE START". We stopped at log 'db2-binary.165686' position 44861651 2024-07-01 4:55:15 16 [ERROR] Slave (additional info): Commit failed due to failure of an earlier commit on which this one depends Error_code: 1964 2024-07-01 4:55:15 16 [Warning] Slave: Commit failed due to failure of an earlier commit on which this one depends Error_code: 1964 2024-07-01 4:55:15 16 [ERROR] Error running query, slave SQL thread aborted. Fix the problem, and restart the slave SQL thread with "SLAVE START". We stopped at log 'db2-binary.165686' position 44861651 2024-07-01 4:55:15 11 [ERROR] Slave (additional info): Commit failed due to failure of an earlier commit on which this one depends Error_code: 1964 2024-07-01 4:55:15 11 [Warning] Slave: Commit failed due to failure of an earlier commit on which this one depends Error_code: 1964 2024-07-01 4:55:15 11 [ERROR] Error running query, slave SQL thread aborted. Fix the problem, and restart the slave SQL thread with "SLAVE START". We stopped at log 'db2-binary.165686' position 44861651 2024-07-01 4:55:15 13 [ERROR] Slave (additional info): Commit failed due to failure of an earlier commit on which this one depends Error_code: 1964 2024-07-01 4:55:15 13 [Warning] Slave: Commit failed due to failure of an earlier commit on which this one depends Error_code: 1964 2024-07-01 4:55:15 13 [ERROR] Error running query, slave SQL thread aborted. Fix the problem, and restart the slave SQL thread with "SLAVE START". We stopped at log 'db2-binary.165686' position 44861651 2024-07-01 4:55:15 9 [ERROR] Slave (additional info): Commit failed due to failure of an earlier commit on which this one depends Error_code: 1964 2024-07-01 4:55:15 9 [Warning] Slave: Commit failed due to failure of an earlier commit on which this one depends Error_code: 1964 2024-07-01 4:55:15 9 [ERROR] Error running query, slave SQL thread aborted. Fix the problem, and restart the slave SQL thread with "SLAVE START". We stopped at log 'db2-binary.165686' position 44861651 2024-07-01 4:55:15 12 [ERROR] Slave (additional info): Commit failed due to failure of an earlier commit on which this one depends Error_code: 1964 2024-07-01 4:55:15 12 [Warning] Slave: Commit failed due to failure of an earlier commit on which this one depends Error_code: 1964 2024-07-01 4:55:15 12 [ERROR] Error running query, slave SQL thread aborted. Fix the problem, and restart the slave SQL thread with "SLAVE START". We stopped at log 'db2-binary.165686' position 44861651 2024-07-01 4:55:15 10 [ERROR] Slave (additional info): Commit failed due to failure of an earlier commit on which this one depends Error_code: 1964 2024-07-01 4:55:15 10 [Warning] Slave: Commit failed due to failure of an earlier commit on which this one depends Error_code: 1964 2024-07-01 4:55:15 10 [ERROR] Error running query, slave SQL thread aborted. Fix the problem, and restart the slave SQL thread with "SLAVE START". We stopped at log 'db2-binary.165686' position 44861651 2024-07-01 4:55:15 8 [ERROR] Slave (additional info): Commit failed due to failure of an earlier commit on which this one depends Error_code: 1964 2024-07-01 4:55:15 8 [Warning] Slave: Commit failed due to failure of an earlier commit on which this one depends Error_code: 1964 2024-07-01 4:55:15 8 [ERROR] Error running query, slave SQL thread aborted. Fix the problem, and restart the slave SQL thread with "SLAVE START". We stopped at log 'db2-binary.165686' position 44861651 2024-07-01 4:55:15 15 [ERROR] Slave (additional info): Commit failed due to failure of an earlier commit on which this one depends Error_code: 1964 2024-07-01 4:55:15 15 [Warning] Slave: Commit failed due to failure of an earlier commit on which this one depends Error_code: 1964 2024-07-01 4:55:15 15 [ERROR] Error running query, slave SQL thread aborted. Fix the problem, and restart the slave SQL thread with "SLAVE START". We stopped at log 'db2-binary.165686' position 44861651 2024-07-01 4:55:16 101076 [Note] Slave SQL thread exiting, replication stopped in log 'db2-binary.165686' at position 44861651, master: 10.76.24.77:3306 2024-07-01 4:55:23 101075 [Note] Slave I/O thread exiting, read up to log 'db2-binary.165898', position 16619273, master 10.76.24.77:3306 2024-07-01 4:55:23 101090 [Note] Slave I/O thread: Start asynchronous replication to master 'gtid@10.76.24.77:3306' in log 'db2-binary.165898' at position 16619273 2024-07-01 4:55:23 101091 [Note] Slave SQL thread initialized, starting replication in log 'db2-binary.165686' at position 44861651, relay log './db1-relay.064296' position: 2882668 2024-07-01 4:55:23 101090 [Note] Slave I/O thread: connected to master 'gtid@10.76.24.77:3306',replication started in log 'db2-binary.165898' at position 16619273 2024-07-01 4:55:23 101091 [Note] 'SQL_SLAVE_SKIP_COUNTER=100' executed at relay_log_file='./db1-relay.064296', relay_log_pos='2882668', master_log_name='db2-binary.165686', master_log_pos='44861651' and new position at relay_log_file='./db1-relay.064296', relay_log_pos='2901579', master_log_name='db2-binary.165686', master_log_pos='44880562' 2024-07-01 4:55:23 13 [ERROR] mariadbd: Can't find record in 'activesessions' 2024-07-01 4:55:23 13 [ERROR] Slave SQL: Could not execute Delete_rows_v1 event on table aaadb.activesessions; Can't find record in 'activesessions', Error_code: 1032; handler error HA_ERR_KEY_NOT_FOUND; the event's master log db2-binary.165686, end_log_pos 49138661, Gtid 0-2-18664677099, Internal MariaDB error code: 1032 2024-07-01 4:55:23 13 [Warning] Slave: Can't find record in 'activesessions' Error_code: 1032 2024-07-01 4:55:23 13 [ERROR] Error running query, slave SQL thread aborted. Fix the problem, and restart the slave SQL thread with "SLAVE START". We stopped at log 'db2-binary.165686' position 49137929 2024-07-01 4:55:23 11 [ERROR] Slave (additional info): Commit failed due to failure of an earlier commit on which this one depends Error_code: 1964 2024-07-01 4:55:23 11 [Warning] Slave: Commit failed due to failure of an earlier commit on which this one depends Error_code: 1964 2024-07-01 4:55:23 11 [ERROR] Error running query, slave SQL thread aborted. Fix the problem, and restart the slave SQL thread with "SLAVE START". We stopped at log 'db2-binary.165686' position 49137929 2024-07-01 4:55:23 16 [ERROR] Slave (additional info): Commit failed due to failure of an earlier commit on which this one depends Error_code: 1964 2024-07-01 4:55:23 16 [Warning] Slave: Commit failed due to failure of an earlier commit on which this one depends Error_code: 1964 2024-07-01 4:55:23 16 [ERROR] Error running query, slave SQL thread aborted. Fix the problem, and restart the slave SQL thread with "SLAVE START". We stopped at log 'db2-binary.165686' position 49137929 2024-07-01 4:55:23 6 [ERROR] Slave (additional info): Commit failed due to failure of an earlier commit on which this one depends Error_code: 1964 2024-07-01 4:55:23 6 [Warning] Slave: Commit failed due to failure of an earlier commit on which this one depends Error_code: 1964 2024-07-01 4:55:23 6 [ERROR] Error running query, slave SQL thread aborted. Fix the problem, and restart the slave SQL thread with "SLAVE START". We stopped at log 'db2-binary.165686' position 49137929 2024-07-01 4:55:23 17 [ERROR] Slave (additional info): Commit failed due to failure of an earlier commit on which this one depends Error_code: 1964 2024-07-01 4:55:23 17 [Warning] Slave: Commit failed due to failure of an earlier commit on which this one depends Error_code: 1964 2024-07-01 4:55:23 17 [ERROR] Error running query, slave SQL thread aborted. Fix the problem, and restart the slave SQL thread with "SLAVE START". We stopped at log 'db2-binary.165686' position 49137929 2024-07-01 4:55:23 14 [ERROR] Slave (additional info): Commit failed due to failure of an earlier commit on which this one depends Error_code: 1964 2024-07-01 4:55:23 14 [Warning] Slave: Commit failed due to failure of an earlier commit on which this one depends Error_code: 1964 2024-07-01 4:55:23 14 [ERROR] Error running query, slave SQL thread aborted. Fix the problem, and restart the slave SQL thread with "SLAVE START". We stopped at log 'db2-binary.165686' position 49137929 2024-07-01 4:55:23 7 [ERROR] Slave (additional info): Commit failed due to failure of an earlier commit on which this one depends Error_code: 1964 2024-07-01 4:55:23 7 [Warning] Slave: Commit failed due to failure of an earlier commit on which this one depends Error_code: 1964 2024-07-01 4:55:23 7 [ERROR] Error running query, slave SQL thread aborted. Fix the problem, and restart the slave SQL thread with "SLAVE START". We stopped at log 'db2-binary.165686' position 49137929 2024-07-01 4:55:23 15 [ERROR] Slave (additional info): Commit failed due to failure of an earlier commit on which this one depends Error_code: 1964 2024-07-01 4:55:23 15 [Warning] Slave: Commit failed due to failure of an earlier commit on which this one depends Error_code: 1964 2024-07-01 4:55:23 15 [ERROR] Error running query, slave SQL thread aborted. Fix the problem, and restart the slave SQL thread with "SLAVE START". We stopped at log 'db2-binary.165686' position 49137929 2024-07-01 4:55:23 8 [ERROR] Slave (additional info): Commit failed due to failure of an earlier commit on which this one depends Error_code: 1964 2024-07-01 4:55:23 8 [Warning] Slave: Commit failed due to failure of an earlier commit on which this one depends Error_code: 1964 2024-07-01 4:55:23 8 [ERROR] Error running query, slave SQL thread aborted. Fix the problem, and restart the slave SQL thread with "SLAVE START". We stopped at log 'db2-binary.165686' position 49137929 2024-07-01 4:55:23 10 [ERROR] Slave (additional info): Commit failed due to failure of an earlier commit on which this one depends Error_code: 1964 2024-07-01 4:55:23 10 [Warning] Slave: Commit failed due to failure of an earlier commit on which this one depends Error_code: 1964 2024-07-01 4:55:23 10 [ERROR] Error running query, slave SQL thread aborted. Fix the problem, and restart the slave SQL thread with "SLAVE START". We stopped at log 'db2-binary.165686' position 49137929 2024-07-01 4:55:23 12 [ERROR] Slave (additional info): Commit failed due to failure of an earlier commit on which this one depends Error_code: 1964 2024-07-01 4:55:23 12 [Warning] Slave: Commit failed due to failure of an earlier commit on which this one depends Error_code: 1964 2024-07-01 4:55:23 12 [ERROR] Error running query, slave SQL thread aborted. Fix the problem, and restart the slave SQL thread with "SLAVE START". We stopped at log 'db2-binary.165686' position 49137929 2024-07-01 4:55:23 9 [ERROR] Slave (additional info): Commit failed due to failure of an earlier commit on which this one depends Error_code: 1964 2024-07-01 4:55:23 9 [Warning] Slave: Commit failed due to failure of an earlier commit on which this one depends Error_code: 1964 2024-07-01 4:55:23 9 [ERROR] Error running query, slave SQL thread aborted. Fix the problem, and restart the slave SQL thread with "SLAVE START". We stopped at log 'db2-binary.165686' position 49137929 2024-07-01 4:55:23 101091 [Note] Slave SQL thread exiting, replication stopped in log 'db2-binary.165686' at position 49137929, master: 10.76.24.77:3306 2024-07-01 4:55:29 101090 [Note] Slave I/O thread exiting, read up to log 'db2-binary.165898', position 28047641, master 10.76.24.77:3306 2024-07-01 4:55:29 101100 [Note] Slave I/O thread: Start asynchronous replication to master 'gtid@10.76.24.77:3306' in log 'db2-binary.165898' at position 28047641 2024-07-01 4:55:29 101101 [Note] Slave SQL thread initialized, starting replication in log 'db2-binary.165686' at position 49137929, relay log './db1-relay.064296' position: 3160358 2024-07-01 4:55:29 101100 [Note] Slave I/O thread: connected to master 'gtid@10.76.24.77:3306',replication started in log 'db2-binary.165898' at position 28047641 2024-07-01 4:55:29 101101 [Note] 'SQL_SLAVE_SKIP_COUNTER=100' executed at relay_log_file='./db1-relay.064296', relay_log_pos='3160358', master_log_name='db2-binary.165686', master_log_pos='49137929' and new position at relay_log_file='./db1-relay.064296', relay_log_pos='3175611', master_log_name='db2-binary.165686', master_log_pos='49153182' 2024-07-01 4:55:29 14 [ERROR] mariadbd: Can't find record in 'activesessions' 2024-07-01 4:55:29 14 [ERROR] Slave SQL: Could not execute Delete_rows_v1 event on table aaadb.activesessions; Can't find record in 'activesessions', Error_code: 1032; handler error HA_ERR_KEY_NOT_FOUND; the event's master log db2-binary.165686, end_log_pos 53473147, Gtid 0-2-18664677388, Internal MariaDB error code: 1032 2024-07-01 4:55:29 14 [Warning] Slave: Can't find record in 'activesessions' Error_code: 1032 2024-07-01 4:55:29 14 [ERROR] Error running query, slave SQL thread aborted. Fix the problem, and restart the slave SQL thread with "SLAVE START". We stopped at log 'db2-binary.165686' position 53472413 2024-07-01 4:55:29 17 [ERROR] Slave (additional info): Commit failed due to failure of an earlier commit on which this one depends Error_code: 1964 2024-07-01 4:55:29 17 [Warning] Slave: Commit failed due to failure of an earlier commit on which this one depends Error_code: 1964 2024-07-01 4:55:29 17 [ERROR] Error running query, slave SQL thread aborted. Fix the problem, and restart the slave SQL thread with "SLAVE START". We stopped at log 'db2-binary.165686' position 53472413 2024-07-01 4:55:29 6 [ERROR] Slave (additional info): Commit failed due to failure of an earlier commit on which this one depends Error_code: 1964 2024-07-01 4:55:29 6 [Warning] Slave: Commit failed due to failure of an earlier commit on which this one depends Error_code: 1964 2024-07-01 4:55:29 6 [ERROR] Error running query, slave SQL thread aborted. Fix the problem, and restart the slave SQL thread with "SLAVE START". We stopped at log 'db2-binary.165686' position 53472413 2024-07-01 4:55:29 16 [ERROR] Slave (additional info): Commit failed due to failure of an earlier commit on which this one depends Error_code: 1964 2024-07-01 4:55:29 16 [Warning] Slave: Commit failed due to failure of an earlier commit on which this one depends Error_code: 1964 2024-07-01 4:55:29 16 [ERROR] Error running query, slave SQL thread aborted. Fix the problem, and restart the slave SQL thread with "SLAVE START". We stopped at log 'db2-binary.165686' position 53472413 2024-07-01 4:55:29 11 [ERROR] Slave (additional info): Commit failed due to failure of an earlier commit on which this one depends Error_code: 1964 2024-07-01 4:55:29 11 [Warning] Slave: Commit failed due to failure of an earlier commit on which this one depends Error_code: 1964 2024-07-01 4:55:29 11 [ERROR] Error running query, slave SQL thread aborted. Fix the problem, and restart the slave SQL thread with "SLAVE START". We stopped at log 'db2-binary.165686' position 53472413 2024-07-01 4:55:29 13 [ERROR] Slave (additional info): Commit failed due to failure of an earlier commit on which this one depends Error_code: 1964 2024-07-01 4:55:29 13 [Warning] Slave: Commit failed due to failure of an earlier commit on which this one depends Error_code: 1964 2024-07-01 4:55:29 13 [ERROR] Error running query, slave SQL thread aborted. Fix the problem, and restart the slave SQL thread with "SLAVE START". We stopped at log 'db2-binary.165686' position 53472413 2024-07-01 4:55:29 9 [ERROR] Slave (additional info): Commit failed due to failure of an earlier commit on which this one depends Error_code: 1964 2024-07-01 4:55:29 9 [Warning] Slave: Commit failed due to failure of an earlier commit on which this one depends Error_code: 1964 2024-07-01 4:55:29 9 [ERROR] Error running query, slave SQL thread aborted. Fix the problem, and restart the slave SQL thread with "SLAVE START". We stopped at log 'db2-binary.165686' position 53472413 2024-07-01 4:55:29 12 [ERROR] Slave (additional info): Commit failed due to failure of an earlier commit on which this one depends Error_code: 1964 2024-07-01 4:55:29 12 [Warning] Slave: Commit failed due to failure of an earlier commit on which this one depends Error_code: 1964 2024-07-01 4:55:29 12 [ERROR] Error running query, slave SQL thread aborted. Fix the problem, and restart the slave SQL thread with "SLAVE START". We stopped at log 'db2-binary.165686' position 53472413 2024-07-01 4:55:29 10 [ERROR] Slave (additional info): Commit failed due to failure of an earlier commit on which this one depends Error_code: 1964 2024-07-01 4:55:29 10 [Warning] Slave: Commit failed due to failure of an earlier commit on which this one depends Error_code: 1964 2024-07-01 4:55:29 10 [ERROR] Error running query, slave SQL thread aborted. Fix the problem, and restart the slave SQL thread with "SLAVE START". We stopped at log 'db2-binary.165686' position 53472413 2024-07-01 4:55:29 8 [ERROR] Slave (additional info): Commit failed due to failure of an earlier commit on which this one depends Error_code: 1964 2024-07-01 4:55:29 8 [Warning] Slave: Commit failed due to failure of an earlier commit on which this one depends Error_code: 1964 2024-07-01 4:55:29 8 [ERROR] Error running query, slave SQL thread aborted. Fix the problem, and restart the slave SQL thread with "SLAVE START". We stopped at log 'db2-binary.165686' position 53472413 2024-07-01 4:55:29 15 [ERROR] Slave (additional info): Commit failed due to failure of an earlier commit on which this one depends Error_code: 1964 2024-07-01 4:55:29 15 [Warning] Slave: Commit failed due to failure of an earlier commit on which this one depends Error_code: 1964 2024-07-01 4:55:29 15 [ERROR] Error running query, slave SQL thread aborted. Fix the problem, and restart the slave SQL thread with "SLAVE START". We stopped at log 'db2-binary.165686' position 53472413 2024-07-01 4:55:29 7 [ERROR] Slave (additional info): Commit failed due to failure of an earlier commit on which this one depends Error_code: 1964 2024-07-01 4:55:29 7 [Warning] Slave: Commit failed due to failure of an earlier commit on which this one depends Error_code: 1964 2024-07-01 4:55:29 7 [ERROR] Error running query, slave SQL thread aborted. Fix the problem, and restart the slave SQL thread with "SLAVE START". We stopped at log 'db2-binary.165686' position 53472413 2024-07-01 4:55:29 101101 [Note] Slave SQL thread exiting, replication stopped in log 'db2-binary.165686' at position 53472413, master: 10.76.24.77:3306 2024-07-01 4:55:35 101100 [Note] Slave I/O thread exiting, read up to log 'db2-binary.165898', position 38765308, master 10.76.24.77:3306 2024-07-01 4:55:35 101114 [Note] Slave I/O thread: Start asynchronous replication to master 'gtid@10.76.24.77:3306' in log 'db2-binary.165898' at position 38765308 2024-07-01 4:55:35 101115 [Note] Slave SQL thread initialized, starting replication in log 'db2-binary.165686' at position 53472413, relay log './db1-relay.064296' position: 3497706 2024-07-01 4:55:35 101114 [Note] Slave I/O thread: connected to master 'gtid@10.76.24.77:3306',replication started in log 'db2-binary.165898' at position 38765308 2024-07-01 4:55:35 101115 [Note] 'SQL_SLAVE_SKIP_COUNTER=100' executed at relay_log_file='./db1-relay.064296', relay_log_pos='3497706', master_log_name='db2-binary.165686', master_log_pos='53472413' and new position at relay_log_file='./db1-relay.064296', relay_log_pos='3515368', master_log_name='db2-binary.165686', master_log_pos='55488777' 2024-07-01 4:55:35 15 [ERROR] mariadbd: Can't find record in 'activesessions' 2024-07-01 4:55:35 15 [ERROR] Slave SQL: Could not execute Delete_rows_v1 event on table aaadb.activesessions; Can't find record in 'activesessions', Error_code: 1032; handler error HA_ERR_KEY_NOT_FOUND; the event's master log db2-binary.165686, end_log_pos 55623900, Gtid 0-2-18664677515, Internal MariaDB error code: 1032 2024-07-01 4:55:35 15 [Warning] Slave: Can't find record in 'activesessions' Error_code: 1032 2024-07-01 4:55:35 15 [ERROR] Error running query, slave SQL thread aborted. Fix the problem, and restart the slave SQL thread with "SLAVE START". We stopped at log 'db2-binary.165686' position 55623170 2024-07-01 4:55:35 8 [ERROR] Slave (additional info): Commit failed due to failure of an earlier commit on which this one depends Error_code: 1964 2024-07-01 4:55:35 8 [Warning] Slave: Commit failed due to failure of an earlier commit on which this one depends Error_code: 1964 2024-07-01 4:55:35 8 [ERROR] Error running query, slave SQL thread aborted. Fix the problem, and restart the slave SQL thread with "SLAVE START". We stopped at log 'db2-binary.165686' position 55623170 2024-07-01 4:55:35 10 [ERROR] Slave (additional info): Commit failed due to failure of an earlier commit on which this one depends Error_code: 1964 2024-07-01 4:55:35 10 [Warning] Slave: Commit failed due to failure of an earlier commit on which this one depends Error_code: 1964 2024-07-01 4:55:35 10 [ERROR] Error running query, slave SQL thread aborted. Fix the problem, and restart the slave SQL thread with "SLAVE START". We stopped at log 'db2-binary.165686' position 55623170 2024-07-01 4:55:35 12 [ERROR] Slave (additional info): Commit failed due to failure of an earlier commit on which this one depends Error_code: 1964 2024-07-01 4:55:35 12 [Warning] Slave: Commit failed due to failure of an earlier commit on which this one depends Error_code: 1964 2024-07-01 4:55:35 12 [ERROR] Error running query, slave SQL thread aborted. Fix the problem, and restart the slave SQL thread with "SLAVE START". We stopped at log 'db2-binary.165686' position 55623170 2024-07-01 4:55:35 9 [ERROR] Slave (additional info): Commit failed due to failure of an earlier commit on which this one depends Error_code: 1964 2024-07-01 4:55:35 9 [Warning] Slave: Commit failed due to failure of an earlier commit on which this one depends Error_code: 1964 2024-07-01 4:55:35 9 [ERROR] Error running query, slave SQL thread aborted. Fix the problem, and restart the slave SQL thread with "SLAVE START". We stopped at log 'db2-binary.165686' position 55623170 2024-07-01 4:55:35 13 [ERROR] Slave (additional info): Commit failed due to failure of an earlier commit on which this one depends Error_code: 1964 2024-07-01 4:55:35 13 [Warning] Slave: Commit failed due to failure of an earlier commit on which this one depends Error_code: 1964 2024-07-01 4:55:35 13 [ERROR] Error running query, slave SQL thread aborted. Fix the problem, and restart the slave SQL thread with "SLAVE START". We stopped at log 'db2-binary.165686' position 55623170 2024-07-01 4:55:35 11 [ERROR] Slave (additional info): Commit failed due to failure of an earlier commit on which this one depends Error_code: 1964 2024-07-01 4:55:35 11 [Warning] Slave: Commit failed due to failure of an earlier commit on which this one depends Error_code: 1964 2024-07-01 4:55:35 11 [ERROR] Error running query, slave SQL thread aborted. Fix the problem, and restart the slave SQL thread with "SLAVE START". We stopped at log 'db2-binary.165686' position 55623170 2024-07-01 4:55:35 16 [ERROR] Slave (additional info): Commit failed due to failure of an earlier commit on which this one depends Error_code: 1964 2024-07-01 4:55:35 16 [Warning] Slave: Commit failed due to failure of an earlier commit on which this one depends Error_code: 1964 2024-07-01 4:55:35 16 [ERROR] Error running query, slave SQL thread aborted. Fix the problem, and restart the slave SQL thread with "SLAVE START". We stopped at log 'db2-binary.165686' position 55623170 2024-07-01 4:55:35 6 [ERROR] Slave (additional info): Commit failed due to failure of an earlier commit on which this one depends Error_code: 1964 2024-07-01 4:55:35 6 [Warning] Slave: Commit failed due to failure of an earlier commit on which this one depends Error_code: 1964 2024-07-01 4:55:35 6 [ERROR] Error running query, slave SQL thread aborted. Fix the problem, and restart the slave SQL thread with "SLAVE START". We stopped at log 'db2-binary.165686' position 55623170 2024-07-01 4:55:35 17 [ERROR] Slave (additional info): Commit failed due to failure of an earlier commit on which this one depends Error_code: 1964 2024-07-01 4:55:35 17 [Warning] Slave: Commit failed due to failure of an earlier commit on which this one depends Error_code: 1964 2024-07-01 4:55:35 17 [ERROR] Error running query, slave SQL thread aborted. Fix the problem, and restart the slave SQL thread with "SLAVE START". We stopped at log 'db2-binary.165686' position 55623170 2024-07-01 4:55:35 14 [ERROR] Slave (additional info): Commit failed due to failure of an earlier commit on which this one depends Error_code: 1964 2024-07-01 4:55:35 14 [Warning] Slave: Commit failed due to failure of an earlier commit on which this one depends Error_code: 1964 2024-07-01 4:55:35 14 [ERROR] Error running query, slave SQL thread aborted. Fix the problem, and restart the slave SQL thread with "SLAVE START". We stopped at log 'db2-binary.165686' position 55623170 2024-07-01 4:55:35 7 [ERROR] Slave (additional info): Commit failed due to failure of an earlier commit on which this one depends Error_code: 1964 2024-07-01 4:55:35 7 [Warning] Slave: Commit failed due to failure of an earlier commit on which this one depends Error_code: 1964 2024-07-01 4:55:35 7 [ERROR] Error running query, slave SQL thread aborted. Fix the problem, and restart the slave SQL thread with "SLAVE START". We stopped at log 'db2-binary.165686' position 55623170 2024-07-01 4:55:35 101115 [Note] Slave SQL thread exiting, replication stopped in log 'db2-binary.165686' at position 55623170, master: 10.76.24.77:3306 2024-07-01 4:55:42 101114 [Note] Slave I/O thread exiting, read up to log 'db2-binary.165898', position 50025369, master 10.76.24.77:3306 2024-07-01 4:55:42 101123 [Note] Slave I/O thread: Start asynchronous replication to master 'gtid@10.76.24.77:3306' in log 'db2-binary.165898' at position 50025369 2024-07-01 4:55:42 101124 [Note] Slave SQL thread initialized, starting replication in log 'db2-binary.165686' at position 55623170, relay log './db1-relay.064296' position: 3649761 2024-07-01 4:55:42 101123 [Note] Slave I/O thread: connected to master 'gtid@10.76.24.77:3306',replication started in log 'db2-binary.165898' at position 50025369 2024-07-01 4:55:42 101124 [Note] 'SQL_SLAVE_SKIP_COUNTER=100' executed at relay_log_file='./db1-relay.064296', relay_log_pos='3649761', master_log_name='db2-binary.165686', master_log_pos='55623170' and new position at relay_log_file='./db1-relay.064296', relay_log_pos='3678587', master_log_name='db2-binary.165686', master_log_pos='55651996' 2024-07-01 4:55:42 6 [ERROR] mariadbd: Can't find record in 'activesessions' 2024-07-01 4:55:42 6 [ERROR] Slave SQL: Could not execute Delete_rows_v1 event on table aaadb.activesessions; Can't find record in 'activesessions', Error_code: 1032; handler error HA_ERR_KEY_NOT_FOUND; the event's master log db2-binary.165686, end_log_pos 57689501, Gtid 0-2-18664677568, Internal MariaDB error code: 1032 2024-07-01 4:55:42 6 [Warning] Slave: Can't find record in 'activesessions' Error_code: 1032 2024-07-01 4:55:42 6 [ERROR] Error running query, slave SQL thread aborted. Fix the problem, and restart the slave SQL thread with "SLAVE START". We stopped at log 'db2-binary.165686' position 57688762 2024-07-01 4:55:42 16 [ERROR] Slave (additional info): Commit failed due to failure of an earlier commit on which this one depends Error_code: 1964 2024-07-01 4:55:42 16 [Warning] Slave: Commit failed due to failure of an earlier commit on which this one depends Error_code: 1964 2024-07-01 4:55:42 16 [ERROR] Error running query, slave SQL thread aborted. Fix the problem, and restart the slave SQL thread with "SLAVE START". We stopped at log 'db2-binary.165686' position 57688762 2024-07-01 4:55:42 11 [ERROR] Slave (additional info): Commit failed due to failure of an earlier commit on which this one depends Error_code: 1964 2024-07-01 4:55:42 11 [Warning] Slave: Commit failed due to failure of an earlier commit on which this one depends Error_code: 1964 2024-07-01 4:55:42 11 [ERROR] Error running query, slave SQL thread aborted. Fix the problem, and restart the slave SQL thread with "SLAVE START". We stopped at log 'db2-binary.165686' position 57688762 2024-07-01 4:55:42 13 [ERROR] Slave (additional info): Commit failed due to failure of an earlier commit on which this one depends Error_code: 1964 2024-07-01 4:55:42 13 [Warning] Slave: Commit failed due to failure of an earlier commit on which this one depends Error_code: 1964 2024-07-01 4:55:42 13 [ERROR] Error running query, slave SQL thread aborted. Fix the problem, and restart the slave SQL thread with "SLAVE START". We stopped at log 'db2-binary.165686' position 57688762 2024-07-01 4:55:42 9 [ERROR] Slave (additional info): Commit failed due to failure of an earlier commit on which this one depends Error_code: 1964 2024-07-01 4:55:42 9 [Warning] Slave: Commit failed due to failure of an earlier commit on which this one depends Error_code: 1964 2024-07-01 4:55:42 9 [ERROR] Error running query, slave SQL thread aborted. Fix the problem, and restart the slave SQL thread with "SLAVE START". We stopped at log 'db2-binary.165686' position 57688762 2024-07-01 4:55:42 12 [ERROR] Slave (additional info): Commit failed due to failure of an earlier commit on which this one depends Error_code: 1964 2024-07-01 4:55:42 12 [Warning] Slave: Commit failed due to failure of an earlier commit on which this one depends Error_code: 1964 2024-07-01 4:55:42 12 [ERROR] Error running query, slave SQL thread aborted. Fix the problem, and restart the slave SQL thread with "SLAVE START". We stopped at log 'db2-binary.165686' position 57688762 2024-07-01 4:55:42 10 [ERROR] Slave (additional info): Commit failed due to failure of an earlier commit on which this one depends Error_code: 1964 2024-07-01 4:55:42 10 [Warning] Slave: Commit failed due to failure of an earlier commit on which this one depends Error_code: 1964 2024-07-01 4:55:42 10 [ERROR] Error running query, slave SQL thread aborted. Fix the problem, and restart the slave SQL thread with "SLAVE START". We stopped at log 'db2-binary.165686' position 57688762 2024-07-01 4:55:42 8 [ERROR] Slave (additional info): Commit failed due to failure of an earlier commit on which this one depends Error_code: 1964 2024-07-01 4:55:42 8 [Warning] Slave: Commit failed due to failure of an earlier commit on which this one depends Error_code: 1964 2024-07-01 4:55:42 8 [ERROR] Error running query, slave SQL thread aborted. Fix the problem, and restart the slave SQL thread with "SLAVE START". We stopped at log 'db2-binary.165686' position 57688762 2024-07-01 4:55:42 15 [ERROR] Slave (additional info): Commit failed due to failure of an earlier commit on which this one depends Error_code: 1964 2024-07-01 4:55:42 15 [Warning] Slave: Commit failed due to failure of an earlier commit on which this one depends Error_code: 1964 2024-07-01 4:55:42 15 [ERROR] Error running query, slave SQL thread aborted. Fix the problem, and restart the slave SQL thread with "SLAVE START". We stopped at log 'db2-binary.165686' position 57688762 2024-07-01 4:55:42 7 [ERROR] Slave (additional info): Commit failed due to failure of an earlier commit on which this one depends Error_code: 1964 2024-07-01 4:55:42 7 [Warning] Slave: Commit failed due to failure of an earlier commit on which this one depends Error_code: 1964 2024-07-01 4:55:42 7 [ERROR] Error running query, slave SQL thread aborted. Fix the problem, and restart the slave SQL thread with "SLAVE START". We stopped at log 'db2-binary.165686' position 57688762 2024-07-01 4:55:42 14 [ERROR] Slave (additional info): Commit failed due to failure of an earlier commit on which this one depends Error_code: 1964 2024-07-01 4:55:42 14 [Warning] Slave: Commit failed due to failure of an earlier commit on which this one depends Error_code: 1964 2024-07-01 4:55:42 14 [ERROR] Error running query, slave SQL thread aborted. Fix the problem, and restart the slave SQL thread with "SLAVE START". We stopped at log 'db2-binary.165686' position 57688762 2024-07-01 4:55:42 17 [ERROR] Slave (additional info): Commit failed due to failure of an earlier commit on which this one depends Error_code: 1964 2024-07-01 4:55:42 17 [Warning] Slave: Commit failed due to failure of an earlier commit on which this one depends Error_code: 1964 2024-07-01 4:55:42 17 [ERROR] Error running query, slave SQL thread aborted. Fix the problem, and restart the slave SQL thread with "SLAVE START". We stopped at log 'db2-binary.165686' position 57688762 2024-07-01 4:55:42 101124 [Note] Slave SQL thread exiting, replication stopped in log 'db2-binary.165686' at position 57688762, master: 10.76.24.77:3306 2024-07-01 4:55:48 101123 [Note] Slave I/O thread exiting, read up to log 'db2-binary.165898', position 61026274, master 10.76.24.77:3306 2024-07-01 4:55:48 101130 [Note] Slave I/O thread: Start asynchronous replication to master 'gtid@10.76.24.77:3306' in log 'db2-binary.165898' at position 61026274 2024-07-01 4:55:48 101131 [Note] Slave SQL thread initialized, starting replication in log 'db2-binary.165686' at position 57688762, relay log './db1-relay.064296' position: 3716224 2024-07-01 4:55:48 101130 [Note] Slave I/O thread: connected to master 'gtid@10.76.24.77:3306',replication started in log 'db2-binary.165898' at position 61026274 2024-07-01 4:55:48 101131 [Note] 'SQL_SLAVE_SKIP_COUNTER=100' executed at relay_log_file='./db1-relay.064296', relay_log_pos='3716224', master_log_name='db2-binary.165686', master_log_pos='57688762' and new position at relay_log_file='./db1-relay.064296', relay_log_pos='3734314', master_log_name='db2-binary.165686', master_log_pos='57706852' 2024-07-01 4:55:48 8 [ERROR] mariadbd: Can't find record in 'activesessions' 2024-07-01 4:55:48 8 [ERROR] Slave SQL: Could not execute Delete_rows_v1 event on table aaadb.activesessions; Can't find record in 'activesessions', Error_code: 1032; handler error HA_ERR_KEY_NOT_FOUND; the event's master log db2-binary.165686, end_log_pos 70942354, Gtid 0-2-18664678518, Internal MariaDB error code: 1032 2024-07-01 4:55:48 8 [Warning] Slave: Can't find record in 'activesessions' Error_code: 1032 2024-07-01 4:55:48 8 [ERROR] Error running query, slave SQL thread aborted. Fix the problem, and restart the slave SQL thread with "SLAVE START". We stopped at log 'db2-binary.165686' position 70941614 2024-07-01 4:55:48 10 [ERROR] Slave (additional info): Commit failed due to failure of an earlier commit on which this one depends Error_code: 1964 2024-07-01 4:55:48 10 [Warning] Slave: Commit failed due to failure of an earlier commit on which this one depends Error_code: 1964 2024-07-01 4:55:48 10 [ERROR] Error running query, slave SQL thread aborted. Fix the problem, and restart the slave SQL thread with "SLAVE START". We stopped at log 'db2-binary.165686' position 70941614 2024-07-01 4:55:48 12 [ERROR] Slave (additional info): Commit failed due to failure of an earlier commit on which this one depends Error_code: 1964 2024-07-01 4:55:48 12 [Warning] Slave: Commit failed due to failure of an earlier commit on which this one depends Error_code: 1964 2024-07-01 4:55:48 12 [ERROR] Error running query, slave SQL thread aborted. Fix the problem, and restart the slave SQL thread with "SLAVE START". We stopped at log 'db2-binary.165686' position 70941614 2024-07-01 4:55:48 9 [ERROR] Slave (additional info): Commit failed due to failure of an earlier commit on which this one depends Error_code: 1964 2024-07-01 4:55:48 9 [Warning] Slave: Commit failed due to failure of an earlier commit on which this one depends Error_code: 1964 2024-07-01 4:55:48 9 [ERROR] Error running query, slave SQL thread aborted. Fix the problem, and restart the slave SQL thread with "SLAVE START". We stopped at log 'db2-binary.165686' position 70941614 2024-07-01 4:55:48 13 [ERROR] Slave (additional info): Commit failed due to failure of an earlier commit on which this one depends Error_code: 1964 2024-07-01 4:55:48 13 [Warning] Slave: Commit failed due to failure of an earlier commit on which this one depends Error_code: 1964 2024-07-01 4:55:48 13 [ERROR] Error running query, slave SQL thread aborted. Fix the problem, and restart the slave SQL thread with "SLAVE START". We stopped at log 'db2-binary.165686' position 70941614 2024-07-01 4:55:48 11 [ERROR] Slave (additional info): Commit failed due to failure of an earlier commit on which this one depends Error_code: 1964 2024-07-01 4:55:48 11 [Warning] Slave: Commit failed due to failure of an earlier commit on which this one depends Error_code: 1964 2024-07-01 4:55:48 11 [ERROR] Error running query, slave SQL thread aborted. Fix the problem, and restart the slave SQL thread with "SLAVE START". We stopped at log 'db2-binary.165686' position 70941614 2024-07-01 4:55:48 16 [ERROR] Slave (additional info): Commit failed due to failure of an earlier commit on which this one depends Error_code: 1964 2024-07-01 4:55:48 16 [Warning] Slave: Commit failed due to failure of an earlier commit on which this one depends Error_code: 1964 2024-07-01 4:55:48 16 [ERROR] Error running query, slave SQL thread aborted. Fix the problem, and restart the slave SQL thread with "SLAVE START". We stopped at log 'db2-binary.165686' position 70941614 2024-07-01 4:55:48 6 [ERROR] Slave (additional info): Commit failed due to failure of an earlier commit on which this one depends Error_code: 1964 2024-07-01 4:55:48 6 [Warning] Slave: Commit failed due to failure of an earlier commit on which this one depends Error_code: 1964 2024-07-01 4:55:48 6 [ERROR] Error running query, slave SQL thread aborted. Fix the problem, and restart the slave SQL thread with "SLAVE START". We stopped at log 'db2-binary.165686' position 70941614 2024-07-01 4:55:48 17 [ERROR] Slave (additional info): Commit failed due to failure of an earlier commit on which this one depends Error_code: 1964 2024-07-01 4:55:48 17 [Warning] Slave: Commit failed due to failure of an earlier commit on which this one depends Error_code: 1964 2024-07-01 4:55:48 17 [ERROR] Error running query, slave SQL thread aborted. Fix the problem, and restart the slave SQL thread with "SLAVE START". We stopped at log 'db2-binary.165686' position 70941614 2024-07-01 4:55:48 14 [ERROR] Slave (additional info): Commit failed due to failure of an earlier commit on which this one depends Error_code: 1964 2024-07-01 4:55:48 14 [Warning] Slave: Commit failed due to failure of an earlier commit on which this one depends Error_code: 1964 2024-07-01 4:55:48 14 [ERROR] Error running query, slave SQL thread aborted. Fix the problem, and restart the slave SQL thread with "SLAVE START". We stopped at log 'db2-binary.165686' position 70941614 2024-07-01 4:55:48 7 [ERROR] Slave (additional info): Commit failed due to failure of an earlier commit on which this one depends Error_code: 1964 2024-07-01 4:55:48 7 [Warning] Slave: Commit failed due to failure of an earlier commit on which this one depends Error_code: 1964 2024-07-01 4:55:48 7 [ERROR] Error running query, slave SQL thread aborted. Fix the problem, and restart the slave SQL thread with "SLAVE START". We stopped at log 'db2-binary.165686' position 70941614 2024-07-01 4:55:48 15 [ERROR] Slave (additional info): Commit failed due to failure of an earlier commit on which this one depends Error_code: 1964 2024-07-01 4:55:48 15 [Warning] Slave: Commit failed due to failure of an earlier commit on which this one depends Error_code: 1964 2024-07-01 4:55:48 15 [ERROR] Error running query, slave SQL thread aborted. Fix the problem, and restart the slave SQL thread with "SLAVE START". We stopped at log 'db2-binary.165686' position 70941614 2024-07-01 4:55:48 101131 [Note] Slave SQL thread exiting, replication stopped in log 'db2-binary.165686' at position 70941614, master: 10.76.24.77:3306 2024-07-01 4:55:55 101130 [Note] Slave I/O thread exiting, read up to log 'db2-binary.165898', position 72899538, master 10.76.24.77:3306 2024-07-01 4:55:55 101156 [Note] Slave I/O thread: Start asynchronous replication to master 'gtid@10.76.24.77:3306' in log 'db2-binary.165898' at position 72899538 2024-07-01 4:55:55 101157 [Note] Slave SQL thread initialized, starting replication in log 'db2-binary.165686' at position 70941614, relay log './db1-relay.064296' position: 4975188 2024-07-01 4:55:55 101156 [Note] Slave I/O thread: connected to master 'gtid@10.76.24.77:3306',replication started in log 'db2-binary.165898' at position 72899538 2024-07-01 4:55:55 101157 [Note] 'SQL_SLAVE_SKIP_COUNTER=100' executed at relay_log_file='./db1-relay.064296', relay_log_pos='4975188', master_log_name='db2-binary.165686', master_log_pos='70941614' and new position at relay_log_file='./db1-relay.064296', relay_log_pos='4993230', master_log_name='db2-binary.165686', master_log_pos='72958781' 2024-07-01 4:55:56 7 [ERROR] mariadbd: Can't find record in 'activesessions' 2024-07-01 4:55:56 7 [ERROR] Slave SQL: Could not execute Delete_rows_v1 event on table aaadb.activesessions; Can't find record in 'activesessions', Error_code: 1032; handler error HA_ERR_KEY_NOT_FOUND; the event's master log db2-binary.165686, end_log_pos 142491326, Gtid 0-2-18664683432, Internal MariaDB error code: 1032 2024-07-01 4:55:56 7 [Warning] Slave: Can't find record in 'activesessions' Error_code: 1032 2024-07-01 4:55:56 7 [ERROR] Error running query, slave SQL thread aborted. Fix the problem, and restart the slave SQL thread with "SLAVE START". We stopped at log 'db2-binary.165686' position 142490595 2024-07-01 4:55:56 14 [ERROR] Slave (additional info): Commit failed due to failure of an earlier commit on which this one depends Error_code: 1964 2024-07-01 4:55:56 14 [Warning] Slave: Commit failed due to failure of an earlier commit on which this one depends Error_code: 1964 2024-07-01 4:55:56 14 [ERROR] Error running query, slave SQL thread aborted. Fix the problem, and restart the slave SQL thread with "SLAVE START". We stopped at log 'db2-binary.165686' position 142490595 2024-07-01 4:55:56 17 [ERROR] Slave (additional info): Commit failed due to failure of an earlier commit on which this one depends Error_code: 1964 2024-07-01 4:55:56 17 [Warning] Slave: Commit failed due to failure of an earlier commit on which this one depends Error_code: 1964 2024-07-01 4:55:56 17 [ERROR] Error running query, slave SQL thread aborted. Fix the problem, and restart the slave SQL thread with "SLAVE START". We stopped at log 'db2-binary.165686' position 142490595 2024-07-01 4:55:56 6 [ERROR] Slave (additional info): Commit failed due to failure of an earlier commit on which this one depends Error_code: 1964 2024-07-01 4:55:56 6 [Warning] Slave: Commit failed due to failure of an earlier commit on which this one depends Error_code: 1964 2024-07-01 4:55:56 6 [ERROR] Error running query, slave SQL thread aborted. Fix the problem, and restart the slave SQL thread with "SLAVE START". We stopped at log 'db2-binary.165686' position 142490595 2024-07-01 4:55:56 16 [ERROR] Slave (additional info): Commit failed due to failure of an earlier commit on which this one depends Error_code: 1964 2024-07-01 4:55:56 16 [Warning] Slave: Commit failed due to failure of an earlier commit on which this one depends Error_code: 1964 2024-07-01 4:55:56 16 [ERROR] Error running query, slave SQL thread aborted. Fix the problem, and restart the slave SQL thread with "SLAVE START". We stopped at log 'db2-binary.165686' position 142490595 2024-07-01 4:55:56 11 [ERROR] Slave (additional info): Commit failed due to failure of an earlier commit on which this one depends Error_code: 1964 2024-07-01 4:55:56 11 [Warning] Slave: Commit failed due to failure of an earlier commit on which this one depends Error_code: 1964 2024-07-01 4:55:56 11 [ERROR] Error running query, slave SQL thread aborted. Fix the problem, and restart the slave SQL thread with "SLAVE START". We stopped at log 'db2-binary.165686' position 142490595 2024-07-01 4:55:56 13 [ERROR] Slave (additional info): Commit failed due to failure of an earlier commit on which this one depends Error_code: 1964 2024-07-01 4:55:56 13 [Warning] Slave: Commit failed due to failure of an earlier commit on which this one depends Error_code: 1964 2024-07-01 4:55:56 13 [ERROR] Error running query, slave SQL thread aborted. Fix the problem, and restart the slave SQL thread with "SLAVE START". We stopped at log 'db2-binary.165686' position 142490595 2024-07-01 4:55:56 9 [ERROR] Slave (additional info): Commit failed due to failure of an earlier commit on which this one depends Error_code: 1964 2024-07-01 4:55:56 9 [Warning] Slave: Commit failed due to failure of an earlier commit on which this one depends Error_code: 1964 2024-07-01 4:55:56 9 [ERROR] Error running query, slave SQL thread aborted. Fix the problem, and restart the slave SQL thread with "SLAVE START". We stopped at log 'db2-binary.165686' position 142490595 2024-07-01 4:55:56 12 [ERROR] Slave (additional info): Commit failed due to failure of an earlier commit on which this one depends Error_code: 1964 2024-07-01 4:55:56 12 [Warning] Slave: Commit failed due to failure of an earlier commit on which this one depends Error_code: 1964 2024-07-01 4:55:56 12 [ERROR] Error running query, slave SQL thread aborted. Fix the problem, and restart the slave SQL thread with "SLAVE START". We stopped at log 'db2-binary.165686' position 142490595 2024-07-01 4:55:56 10 [ERROR] Slave (additional info): Commit failed due to failure of an earlier commit on which this one depends Error_code: 1964 2024-07-01 4:55:56 10 [Warning] Slave: Commit failed due to failure of an earlier commit on which this one depends Error_code: 1964 2024-07-01 4:55:56 10 [ERROR] Error running query, slave SQL thread aborted. Fix the problem, and restart the slave SQL thread with "SLAVE START". We stopped at log 'db2-binary.165686' position 142490595 2024-07-01 4:55:56 8 [ERROR] Slave (additional info): Commit failed due to failure of an earlier commit on which this one depends Error_code: 1964 2024-07-01 4:55:56 8 [Warning] Slave: Commit failed due to failure of an earlier commit on which this one depends Error_code: 1964 2024-07-01 4:55:56 8 [ERROR] Error running query, slave SQL thread aborted. Fix the problem, and restart the slave SQL thread with "SLAVE START". We stopped at log 'db2-binary.165686' position 142490595 2024-07-01 4:55:56 15 [ERROR] Slave (additional info): Commit failed due to failure of an earlier commit on which this one depends Error_code: 1964 2024-07-01 4:55:56 15 [Warning] Slave: Commit failed due to failure of an earlier commit on which this one depends Error_code: 1964 2024-07-01 4:55:56 15 [ERROR] Error running query, slave SQL thread aborted. Fix the problem, and restart the slave SQL thread with "SLAVE START". We stopped at log 'db2-binary.165686' position 142490595 2024-07-01 4:55:56 101157 [Note] Slave SQL thread exiting, replication stopped in log 'db2-binary.165686' at position 142490595, master: 10.76.24.77:3306 2024-07-01 4:56:03 101156 [Note] Slave I/O thread exiting, read up to log 'db2-binary.165898', position 85174657, master 10.76.24.77:3306 2024-07-01 4:56:03 101253 [Note] Slave I/O thread: Start asynchronous replication to master 'gtid@10.76.24.77:3306' in log 'db2-binary.165898' at position 85174657 2024-07-01 4:56:03 101254 [Note] Slave SQL thread initialized, starting replication in log 'db2-binary.165686' at position 142490595, relay log './db1-relay.064296' position: 12557673 2024-07-01 4:56:03 101253 [Note] Slave I/O thread: connected to master 'gtid@10.76.24.77:3306',replication started in log 'db2-binary.165898' at position 85174657 2024-07-01 4:56:03 101254 [Note] 'SQL_SLAVE_SKIP_COUNTER=100' executed at relay_log_file='./db1-relay.064296', relay_log_pos='12557673', master_log_name='db2-binary.165686', master_log_pos='142490595' and new position at relay_log_file='./db1-relay.064296', relay_log_pos='12586618', master_log_name='db2-binary.165686', master_log_pos='142519540' 2024-07-01 4:56:03 9 [ERROR] mariadbd: Can't find record in 'activesessions' 2024-07-01 4:56:03 9 [ERROR] Slave SQL: Could not execute Delete_rows_v1 event on table aaadb.activesessions; Can't find record in 'activesessions', Error_code: 1032; handler error HA_ERR_KEY_NOT_FOUND; the event's master log db2-binary.165686, end_log_pos 144889197, Gtid 0-2-18664683728, Internal MariaDB error code: 1032 2024-07-01 4:56:03 9 [Warning] Slave: Can't find record in 'activesessions' Error_code: 1032 2024-07-01 4:56:03 9 [ERROR] Error running query, slave SQL thread aborted. Fix the problem, and restart the slave SQL thread with "SLAVE START". We stopped at log 'db2-binary.165686' position 144888484 2024-07-01 4:56:03 13 [ERROR] Slave (additional info): Commit failed due to failure of an earlier commit on which this one depends Error_code: 1964 2024-07-01 4:56:03 13 [Warning] Slave: Commit failed due to failure of an earlier commit on which this one depends Error_code: 1964 2024-07-01 4:56:03 13 [ERROR] Error running query, slave SQL thread aborted. Fix the problem, and restart the slave SQL thread with "SLAVE START". We stopped at log 'db2-binary.165686' position 144888484 2024-07-01 4:56:03 11 [ERROR] Slave (additional info): Commit failed due to failure of an earlier commit on which this one depends Error_code: 1964 2024-07-01 4:56:03 11 [Warning] Slave: Commit failed due to failure of an earlier commit on which this one depends Error_code: 1964 2024-07-01 4:56:03 11 [ERROR] Error running query, slave SQL thread aborted. Fix the problem, and restart the slave SQL thread with "SLAVE START". We stopped at log 'db2-binary.165686' position 144888484 2024-07-01 4:56:03 16 [ERROR] Slave (additional info): Commit failed due to failure of an earlier commit on which this one depends Error_code: 1964 2024-07-01 4:56:03 16 [Warning] Slave: Commit failed due to failure of an earlier commit on which this one depends Error_code: 1964 2024-07-01 4:56:03 16 [ERROR] Error running query, slave SQL thread aborted. Fix the problem, and restart the slave SQL thread with "SLAVE START". We stopped at log 'db2-binary.165686' position 144888484 2024-07-01 4:56:03 6 [ERROR] Slave (additional info): Commit failed due to failure of an earlier commit on which this one depends Error_code: 1964 2024-07-01 4:56:03 6 [Warning] Slave: Commit failed due to failure of an earlier commit on which this one depends Error_code: 1964 2024-07-01 4:56:03 6 [ERROR] Error running query, slave SQL thread aborted. Fix the problem, and restart the slave SQL thread with "SLAVE START". We stopped at log 'db2-binary.165686' position 144888484 2024-07-01 4:56:03 17 [ERROR] Slave (additional info): Commit failed due to failure of an earlier commit on which this one depends Error_code: 1964 2024-07-01 4:56:03 17 [Warning] Slave: Commit failed due to failure of an earlier commit on which this one depends Error_code: 1964 2024-07-01 4:56:03 17 [ERROR] Error running query, slave SQL thread aborted. Fix the problem, and restart the slave SQL thread with "SLAVE START". We stopped at log 'db2-binary.165686' position 144888484 2024-07-01 4:56:03 14 [ERROR] Slave (additional info): Commit failed due to failure of an earlier commit on which this one depends Error_code: 1964 2024-07-01 4:56:03 14 [Warning] Slave: Commit failed due to failure of an earlier commit on which this one depends Error_code: 1964 2024-07-01 4:56:03 14 [ERROR] Error running query, slave SQL thread aborted. Fix the problem, and restart the slave SQL thread with "SLAVE START". We stopped at log 'db2-binary.165686' position 144888484 2024-07-01 4:56:03 7 [ERROR] Slave (additional info): Commit failed due to failure of an earlier commit on which this one depends Error_code: 1964 2024-07-01 4:56:03 7 [Warning] Slave: Commit failed due to failure of an earlier commit on which this one depends Error_code: 1964 2024-07-01 4:56:03 7 [ERROR] Error running query, slave SQL thread aborted. Fix the problem, and restart the slave SQL thread with "SLAVE START". We stopped at log 'db2-binary.165686' position 144888484 2024-07-01 4:56:03 15 [ERROR] Slave (additional info): Commit failed due to failure of an earlier commit on which this one depends Error_code: 1964 2024-07-01 4:56:03 15 [Warning] Slave: Commit failed due to failure of an earlier commit on which this one depends Error_code: 1964 2024-07-01 4:56:03 15 [ERROR] Error running query, slave SQL thread aborted. Fix the problem, and restart the slave SQL thread with "SLAVE START". We stopped at log 'db2-binary.165686' position 144888484 2024-07-01 4:56:03 8 [ERROR] Slave (additional info): Commit failed due to failure of an earlier commit on which this one depends Error_code: 1964 2024-07-01 4:56:03 8 [Warning] Slave: Commit failed due to failure of an earlier commit on which this one depends Error_code: 1964 2024-07-01 4:56:03 8 [ERROR] Error running query, slave SQL thread aborted. Fix the problem, and restart the slave SQL thread with "SLAVE START". We stopped at log 'db2-binary.165686' position 144888484 2024-07-01 4:56:03 10 [ERROR] Slave (additional info): Commit failed due to failure of an earlier commit on which this one depends Error_code: 1964 2024-07-01 4:56:03 10 [Warning] Slave: Commit failed due to failure of an earlier commit on which this one depends Error_code: 1964 2024-07-01 4:56:03 10 [ERROR] Error running query, slave SQL thread aborted. Fix the problem, and restart the slave SQL thread with "SLAVE START". We stopped at log 'db2-binary.165686' position 144888484 2024-07-01 4:56:03 12 [ERROR] Slave (additional info): Commit failed due to failure of an earlier commit on which this one depends Error_code: 1964 2024-07-01 4:56:03 12 [Warning] Slave: Commit failed due to failure of an earlier commit on which this one depends Error_code: 1964 2024-07-01 4:56:03 12 [ERROR] Error running query, slave SQL thread aborted. Fix the problem, and restart the slave SQL thread with "SLAVE START". We stopped at log 'db2-binary.165686' position 144888484 2024-07-01 4:56:03 101254 [Note] Slave SQL thread exiting, replication stopped in log 'db2-binary.165686' at position 144888484, master: 10.76.24.77:3306 2024-07-01 4:56:09 101253 [Note] Slave I/O thread exiting, read up to log 'db2-binary.165898', position 94374523, master 10.76.24.77:3306 2024-07-01 4:56:09 101267 [Note] Slave I/O thread: Start asynchronous replication to master 'gtid@10.76.24.77:3306' in log 'db2-binary.165898' at position 94374523 2024-07-01 4:56:09 101268 [Note] Slave SQL thread initialized, starting replication in log 'db2-binary.165686' at position 144888484, relay log './db1-relay.064296' position: 12956772 2024-07-01 4:56:09 101267 [Note] Slave I/O thread: connected to master 'gtid@10.76.24.77:3306',replication started in log 'db2-binary.165898' at position 94374523 2024-07-01 4:56:09 101268 [Note] 'SQL_SLAVE_SKIP_COUNTER=100' executed at relay_log_file='./db1-relay.064296', relay_log_pos='12956772', master_log_name='db2-binary.165686', master_log_pos='144888484' and new position at relay_log_file='./db1-relay.064296', relay_log_pos='12977061', master_log_name='db2-binary.165686', master_log_pos='144908773' 2024-07-01 4:56:09 13 [ERROR] mariadbd: Can't find record in 'activesessions' 2024-07-01 4:56:09 13 [ERROR] Slave SQL: Could not execute Delete_rows_v1 event on table aaadb.activesessions; Can't find record in 'activesessions', Error_code: 1032; handler error HA_ERR_KEY_NOT_FOUND; the event's master log db2-binary.165686, end_log_pos 147032672, Gtid 0-2-18664683844, Internal MariaDB error code: 1032 2024-07-01 4:56:09 13 [Warning] Slave: Can't find record in 'activesessions' Error_code: 1032 2024-07-01 4:56:09 13 [ERROR] Error running query, slave SQL thread aborted. Fix the problem, and restart the slave SQL thread with "SLAVE START". We stopped at log 'db2-binary.165686' position 147031940 2024-07-01 4:56:09 9 [ERROR] Slave (additional info): Commit failed due to failure of an earlier commit on which this one depends Error_code: 1964 2024-07-01 4:56:09 9 [Warning] Slave: Commit failed due to failure of an earlier commit on which this one depends Error_code: 1964 2024-07-01 4:56:09 9 [ERROR] Error running query, slave SQL thread aborted. Fix the problem, and restart the slave SQL thread with "SLAVE START". We stopped at log 'db2-binary.165686' position 147031940 2024-07-01 4:56:09 12 [ERROR] Slave (additional info): Commit failed due to failure of an earlier commit on which this one depends Error_code: 1964 2024-07-01 4:56:09 12 [Warning] Slave: Commit failed due to failure of an earlier commit on which this one depends Error_code: 1964 2024-07-01 4:56:09 12 [ERROR] Error running query, slave SQL thread aborted. Fix the problem, and restart the slave SQL thread with "SLAVE START". We stopped at log 'db2-binary.165686' position 147031940 2024-07-01 4:56:09 10 [ERROR] Slave (additional info): Commit failed due to failure of an earlier commit on which this one depends Error_code: 1964 2024-07-01 4:56:09 10 [Warning] Slave: Commit failed due to failure of an earlier commit on which this one depends Error_code: 1964 2024-07-01 4:56:09 10 [ERROR] Error running query, slave SQL thread aborted. Fix the problem, and restart the slave SQL thread with "SLAVE START". We stopped at log 'db2-binary.165686' position 147031940 2024-07-01 4:56:09 8 [ERROR] Slave (additional info): Commit failed due to failure of an earlier commit on which this one depends Error_code: 1964 2024-07-01 4:56:09 8 [Warning] Slave: Commit failed due to failure of an earlier commit on which this one depends Error_code: 1964 2024-07-01 4:56:09 8 [ERROR] Error running query, slave SQL thread aborted. Fix the problem, and restart the slave SQL thread with "SLAVE START". We stopped at log 'db2-binary.165686' position 147031940 2024-07-01 4:56:09 15 [ERROR] Slave (additional info): Commit failed due to failure of an earlier commit on which this one depends Error_code: 1964 2024-07-01 4:56:09 15 [Warning] Slave: Commit failed due to failure of an earlier commit on which this one depends Error_code: 1964 2024-07-01 4:56:09 15 [ERROR] Error running query, slave SQL thread aborted. Fix the problem, and restart the slave SQL thread with "SLAVE START". We stopped at log 'db2-binary.165686' position 147031940 2024-07-01 4:56:09 7 [ERROR] Slave (additional info): Commit failed due to failure of an earlier commit on which this one depends Error_code: 1964 2024-07-01 4:56:09 7 [Warning] Slave: Commit failed due to failure of an earlier commit on which this one depends Error_code: 1964 2024-07-01 4:56:09 7 [ERROR] Error running query, slave SQL thread aborted. Fix the problem, and restart the slave SQL thread with "SLAVE START". We stopped at log 'db2-binary.165686' position 147031940 2024-07-01 4:56:09 14 [ERROR] Slave (additional info): Commit failed due to failure of an earlier commit on which this one depends Error_code: 1964 2024-07-01 4:56:09 14 [Warning] Slave: Commit failed due to failure of an earlier commit on which this one depends Error_code: 1964 2024-07-01 4:56:09 14 [ERROR] Error running query, slave SQL thread aborted. Fix the problem, and restart the slave SQL thread with "SLAVE START". We stopped at log 'db2-binary.165686' position 147031940 2024-07-01 4:56:09 17 [ERROR] Slave (additional info): Commit failed due to failure of an earlier commit on which this one depends Error_code: 1964 2024-07-01 4:56:09 17 [Warning] Slave: Commit failed due to failure of an earlier commit on which this one depends Error_code: 1964 2024-07-01 4:56:09 17 [ERROR] Error running query, slave SQL thread aborted. Fix the problem, and restart the slave SQL thread with "SLAVE START". We stopped at log 'db2-binary.165686' position 147031940 2024-07-01 4:56:09 6 [ERROR] Slave (additional info): Commit failed due to failure of an earlier commit on which this one depends Error_code: 1964 2024-07-01 4:56:09 6 [Warning] Slave: Commit failed due to failure of an earlier commit on which this one depends Error_code: 1964 2024-07-01 4:56:09 6 [ERROR] Error running query, slave SQL thread aborted. Fix the problem, and restart the slave SQL thread with "SLAVE START". We stopped at log 'db2-binary.165686' position 147031940 2024-07-01 4:56:09 16 [ERROR] Slave (additional info): Commit failed due to failure of an earlier commit on which this one depends Error_code: 1964 2024-07-01 4:56:09 16 [Warning] Slave: Commit failed due to failure of an earlier commit on which this one depends Error_code: 1964 2024-07-01 4:56:09 16 [ERROR] Error running query, slave SQL thread aborted. Fix the problem, and restart the slave SQL thread with "SLAVE START". We stopped at log 'db2-binary.165686' position 147031940 2024-07-01 4:56:09 11 [ERROR] Slave (additional info): Commit failed due to failure of an earlier commit on which this one depends Error_code: 1964 2024-07-01 4:56:09 11 [Warning] Slave: Commit failed due to failure of an earlier commit on which this one depends Error_code: 1964 2024-07-01 4:56:09 11 [ERROR] Error running query, slave SQL thread aborted. Fix the problem, and restart the slave SQL thread with "SLAVE START". We stopped at log 'db2-binary.165686' position 147031940 2024-07-01 4:56:09 101268 [Note] Slave SQL thread exiting, replication stopped in log 'db2-binary.165686' at position 147031940, master: 10.76.24.77:3306 2024-07-01 4:56:16 101267 [Note] Slave I/O thread exiting, read up to log 'db2-binary.165898', position 105057008, master 10.76.24.77:3306 2024-07-01 4:56:16 101278 [Note] Slave I/O thread: Start asynchronous replication to master 'gtid@10.76.24.77:3306' in log 'db2-binary.165898' at position 105057008 2024-07-01 4:56:16 101279 [Note] Slave SQL thread initialized, starting replication in log 'db2-binary.165686' at position 147031940, relay log './db1-relay.064296' position: 13101580 2024-07-01 4:56:16 101278 [Note] Slave I/O thread: connected to master 'gtid@10.76.24.77:3306',replication started in log 'db2-binary.165898' at position 105057008 2024-07-01 4:56:16 101279 [Note] 'SQL_SLAVE_SKIP_COUNTER=100' executed at relay_log_file='./db1-relay.064296', relay_log_pos='13101580', master_log_name='db2-binary.165686', master_log_pos='147031940' and new position at relay_log_file='./db1-relay.064296', relay_log_pos='13121223', master_log_name='db2-binary.165686', master_log_pos='147051583' 2024-07-01 4:56:20 15 [ERROR] mariadbd: Can't find record in 'activesessions' 2024-07-01 4:56:20 15 [ERROR] Slave SQL: Could not execute Delete_rows_v1 event on table aaadb.activesessions; Can't find record in 'activesessions', Error_code: 1032; handler error HA_ERR_KEY_NOT_FOUND; the event's master log db2-binary.165688, end_log_pos 207330638, Gtid 0-2-18664714937, Internal MariaDB error code: 1032 2024-07-01 4:56:20 15 [Warning] Slave: Can't find record in 'activesessions' Error_code: 1032 2024-07-01 4:56:20 15 [ERROR] Error running query, slave SQL thread aborted. Fix the problem, and restart the slave SQL thread with "SLAVE START". We stopped at log 'db2-binary.165688' position 207329912 2024-07-01 4:56:20 8 [ERROR] Slave (additional info): Commit failed due to failure of an earlier commit on which this one depends Error_code: 1964 2024-07-01 4:56:20 8 [Warning] Slave: Commit failed due to failure of an earlier commit on which this one depends Error_code: 1964 2024-07-01 4:56:20 8 [ERROR] Error running query, slave SQL thread aborted. Fix the problem, and restart the slave SQL thread with "SLAVE START". We stopped at log 'db2-binary.165688' position 207329912 2024-07-01 4:56:20 10 [ERROR] Slave (additional info): Commit failed due to failure of an earlier commit on which this one depends Error_code: 1964 2024-07-01 4:56:20 10 [Warning] Slave: Commit failed due to failure of an earlier commit on which this one depends Error_code: 1964 2024-07-01 4:56:20 10 [ERROR] Error running query, slave SQL thread aborted. Fix the problem, and restart the slave SQL thread with "SLAVE START". We stopped at log 'db2-binary.165688' position 207329912 2024-07-01 4:56:20 12 [ERROR] Slave (additional info): Commit failed due to failure of an earlier commit on which this one depends Error_code: 1964 2024-07-01 4:56:20 12 [Warning] Slave: Commit failed due to failure of an earlier commit on which this one depends Error_code: 1964 2024-07-01 4:56:20 12 [ERROR] Error running query, slave SQL thread aborted. Fix the problem, and restart the slave SQL thread with "SLAVE START". We stopped at log 'db2-binary.165688' position 207329912 2024-07-01 4:56:20 9 [ERROR] Slave (additional info): Commit failed due to failure of an earlier commit on which this one depends Error_code: 1964 2024-07-01 4:56:20 9 [Warning] Slave: Commit failed due to failure of an earlier commit on which this one depends Error_code: 1964 2024-07-01 4:56:20 9 [ERROR] Error running query, slave SQL thread aborted. Fix the problem, and restart the slave SQL thread with "SLAVE START". We stopped at log 'db2-binary.165688' position 207329912 2024-07-01 4:56:20 13 [ERROR] Slave (additional info): Commit failed due to failure of an earlier commit on which this one depends Error_code: 1964 2024-07-01 4:56:20 13 [Warning] Slave: Commit failed due to failure of an earlier commit on which this one depends Error_code: 1964 2024-07-01 4:56:20 13 [ERROR] Error running query, slave SQL thread aborted. Fix the problem, and restart the slave SQL thread with "SLAVE START". We stopped at log 'db2-binary.165688' position 207329912 2024-07-01 4:56:20 11 [ERROR] Slave (additional info): Commit failed due to failure of an earlier commit on which this one depends Error_code: 1964 2024-07-01 4:56:20 11 [Warning] Slave: Commit failed due to failure of an earlier commit on which this one depends Error_code: 1964 2024-07-01 4:56:20 11 [ERROR] Error running query, slave SQL thread aborted. Fix the problem, and restart the slave SQL thread with "SLAVE START". We stopped at log 'db2-binary.165688' position 207329912 2024-07-01 4:56:20 16 [ERROR] Slave (additional info): Commit failed due to failure of an earlier commit on which this one depends Error_code: 1964 2024-07-01 4:56:20 16 [Warning] Slave: Commit failed due to failure of an earlier commit on which this one depends Error_code: 1964 2024-07-01 4:56:20 16 [ERROR] Error running query, slave SQL thread aborted. Fix the problem, and restart the slave SQL thread with "SLAVE START". We stopped at log 'db2-binary.165688' position 207329912 2024-07-01 4:56:20 6 [ERROR] Slave (additional info): Commit failed due to failure of an earlier commit on which this one depends Error_code: 1964 2024-07-01 4:56:20 6 [Warning] Slave: Commit failed due to failure of an earlier commit on which this one depends Error_code: 1964 2024-07-01 4:56:20 6 [ERROR] Error running query, slave SQL thread aborted. Fix the problem, and restart the slave SQL thread with "SLAVE START". We stopped at log 'db2-binary.165688' position 207329912 2024-07-01 4:56:20 17 [ERROR] Slave (additional info): Commit failed due to failure of an earlier commit on which this one depends Error_code: 1964 2024-07-01 4:56:20 17 [Warning] Slave: Commit failed due to failure of an earlier commit on which this one depends Error_code: 1964 2024-07-01 4:56:20 17 [ERROR] Error running query, slave SQL thread aborted. Fix the problem, and restart the slave SQL thread with "SLAVE START". We stopped at log 'db2-binary.165688' position 207329912 2024-07-01 4:56:20 14 [ERROR] Slave (additional info): Commit failed due to failure of an earlier commit on which this one depends Error_code: 1964 2024-07-01 4:56:20 14 [Warning] Slave: Commit failed due to failure of an earlier commit on which this one depends Error_code: 1964 2024-07-01 4:56:20 14 [ERROR] Error running query, slave SQL thread aborted. Fix the problem, and restart the slave SQL thread with "SLAVE START". We stopped at log 'db2-binary.165688' position 207329912 2024-07-01 4:56:20 7 [ERROR] Slave (additional info): Commit failed due to failure of an earlier commit on which this one depends Error_code: 1964 2024-07-01 4:56:20 7 [Warning] Slave: Commit failed due to failure of an earlier commit on which this one depends Error_code: 1964 2024-07-01 4:56:20 7 [ERROR] Error running query, slave SQL thread aborted. Fix the problem, and restart the slave SQL thread with "SLAVE START". We stopped at log 'db2-binary.165688' position 207329912 2024-07-01 4:56:21 101279 [Note] Slave SQL thread exiting, replication stopped in log 'db2-binary.165688' at position 207329912, master: 10.76.24.77:3306 2024-07-01 4:56:28 101278 [Note] Slave I/O thread exiting, read up to log 'db2-binary.165898', position 124978281, master 10.76.24.77:3306 2024-07-01 4:56:28 101874 [Note] Slave I/O thread: Start asynchronous replication to master 'gtid@10.76.24.77:3306' in log 'db2-binary.165898' at position 124978281 2024-07-01 4:56:28 101874 [Note] Slave I/O thread: connected to master 'gtid@10.76.24.77:3306',replication started in log 'db2-binary.165898' at position 124978281 2024-07-01 4:56:28 101875 [Note] Slave SQL thread initialized, starting replication in log 'db2-binary.165688' at position 207329912, relay log './db1-relay.064300' position: 17478477 2024-07-01 4:56:28 101875 [Note] 'SQL_SLAVE_SKIP_COUNTER=100' executed at relay_log_file='./db1-relay.064300', relay_log_pos='17478477', master_log_name='db2-binary.165688', master_log_pos='207329912' and new position at relay_log_file='./db1-relay.064300', relay_log_pos='17504362', master_log_name='db2-binary.165688', master_log_pos='207355797' 2024-07-01 4:56:28 12 [ERROR] mariadbd: Can't find record in 'activesessions' 2024-07-01 4:56:28 12 [ERROR] Slave SQL: Could not execute Delete_rows_v1 event on table aaadb.activesessions; Can't find record in 'activesessions', Error_code: 1032; handler error HA_ERR_KEY_NOT_FOUND; the event's master log db2-binary.165689, end_log_pos 4620286, Gtid 0-2-18664715569, Internal MariaDB error code: 1032 2024-07-01 4:56:28 12 [Warning] Slave: Can't find record in 'activesessions' Error_code: 1032 2024-07-01 4:56:28 12 [ERROR] Error running query, slave SQL thread aborted. Fix the problem, and restart the slave SQL thread with "SLAVE START". We stopped at log 'db2-binary.165689' position 4619552 2024-07-01 4:56:28 10 [ERROR] Slave (additional info): Commit failed due to failure of an earlier commit on which this one depends Error_code: 1964 2024-07-01 4:56:28 10 [Warning] Slave: Commit failed due to failure of an earlier commit on which this one depends Error_code: 1964 2024-07-01 4:56:28 10 [ERROR] Error running query, slave SQL thread aborted. Fix the problem, and restart the slave SQL thread with "SLAVE START". We stopped at log 'db2-binary.165689' position 4619552 2024-07-01 4:56:28 8 [ERROR] Slave (additional info): Commit failed due to failure of an earlier commit on which this one depends Error_code: 1964 2024-07-01 4:56:28 8 [Warning] Slave: Commit failed due to failure of an earlier commit on which this one depends Error_code: 1964 2024-07-01 4:56:28 8 [ERROR] Error running query, slave SQL thread aborted. Fix the problem, and restart the slave SQL thread with "SLAVE START". We stopped at log 'db2-binary.165689' position 4619552 2024-07-01 4:56:28 15 [ERROR] Slave (additional info): Commit failed due to failure of an earlier commit on which this one depends Error_code: 1964 2024-07-01 4:56:28 15 [Warning] Slave: Commit failed due to failure of an earlier commit on which this one depends Error_code: 1964 2024-07-01 4:56:28 15 [ERROR] Error running query, slave SQL thread aborted. Fix the problem, and restart the slave SQL thread with "SLAVE START". We stopped at log 'db2-binary.165689' position 4619552 2024-07-01 4:56:28 7 [ERROR] Slave (additional info): Commit failed due to failure of an earlier commit on which this one depends Error_code: 1964 2024-07-01 4:56:28 7 [Warning] Slave: Commit failed due to failure of an earlier commit on which this one depends Error_code: 1964 2024-07-01 4:56:28 7 [ERROR] Error running query, slave SQL thread aborted. Fix the problem, and restart the slave SQL thread with "SLAVE START". We stopped at log 'db2-binary.165689' position 4619552 2024-07-01 4:56:28 14 [ERROR] Slave (additional info): Commit failed due to failure of an earlier commit on which this one depends Error_code: 1964 2024-07-01 4:56:28 14 [Warning] Slave: Commit failed due to failure of an earlier commit on which this one depends Error_code: 1964 2024-07-01 4:56:28 14 [ERROR] Error running query, slave SQL thread aborted. Fix the problem, and restart the slave SQL thread with "SLAVE START". We stopped at log 'db2-binary.165689' position 4619552 2024-07-01 4:56:28 17 [ERROR] Slave (additional info): Commit failed due to failure of an earlier commit on which this one depends Error_code: 1964 2024-07-01 4:56:28 17 [Warning] Slave: Commit failed due to failure of an earlier commit on which this one depends Error_code: 1964 2024-07-01 4:56:28 17 [ERROR] Error running query, slave SQL thread aborted. Fix the problem, and restart the slave SQL thread with "SLAVE START". We stopped at log 'db2-binary.165689' position 4619552 2024-07-01 4:56:28 6 [ERROR] Slave (additional info): Commit failed due to failure of an earlier commit on which this one depends Error_code: 1964 2024-07-01 4:56:28 6 [Warning] Slave: Commit failed due to failure of an earlier commit on which this one depends Error_code: 1964 2024-07-01 4:56:28 6 [ERROR] Error running query, slave SQL thread aborted. Fix the problem, and restart the slave SQL thread with "SLAVE START". We stopped at log 'db2-binary.165689' position 4619552 2024-07-01 4:56:28 16 [ERROR] Slave (additional info): Commit failed due to failure of an earlier commit on which this one depends Error_code: 1964 2024-07-01 4:56:28 16 [Warning] Slave: Commit failed due to failure of an earlier commit on which this one depends Error_code: 1964 2024-07-01 4:56:28 16 [ERROR] Error running query, slave SQL thread aborted. Fix the problem, and restart the slave SQL thread with "SLAVE START". We stopped at log 'db2-binary.165689' position 4619552 2024-07-01 4:56:28 11 [ERROR] Slave (additional info): Commit failed due to failure of an earlier commit on which this one depends Error_code: 1964 2024-07-01 4:56:28 11 [Warning] Slave: Commit failed due to failure of an earlier commit on which this one depends Error_code: 1964 2024-07-01 4:56:28 11 [ERROR] Error running query, slave SQL thread aborted. Fix the problem, and restart the slave SQL thread with "SLAVE START". We stopped at log 'db2-binary.165689' position 4619552 2024-07-01 4:56:28 13 [ERROR] Slave (additional info): Commit failed due to failure of an earlier commit on which this one depends Error_code: 1964 2024-07-01 4:56:28 13 [Warning] Slave: Commit failed due to failure of an earlier commit on which this one depends Error_code: 1964 2024-07-01 4:56:28 13 [ERROR] Error running query, slave SQL thread aborted. Fix the problem, and restart the slave SQL thread with "SLAVE START". We stopped at log 'db2-binary.165689' position 4619552 2024-07-01 4:56:28 9 [ERROR] Slave (additional info): Commit failed due to failure of an earlier commit on which this one depends Error_code: 1964 2024-07-01 4:56:28 9 [Warning] Slave: Commit failed due to failure of an earlier commit on which this one depends Error_code: 1964 2024-07-01 4:56:28 9 [ERROR] Error running query, slave SQL thread aborted. Fix the problem, and restart the slave SQL thread with "SLAVE START". We stopped at log 'db2-binary.165689' position 4619552 2024-07-01 4:56:28 101875 [Note] Slave SQL thread exiting, replication stopped in log 'db2-binary.165689' at position 4619552, master: 10.76.24.77:3306 2024-07-01 4:56:36 101874 [Note] Slave I/O thread exiting, read up to log 'db2-binary.165898', position 137985852, master 10.76.24.77:3306 2024-07-01 4:56:36 101894 [Note] Slave I/O thread: Start asynchronous replication to master 'gtid@10.76.24.77:3306' in log 'db2-binary.165898' at position 137985852 2024-07-01 4:56:36 101895 [Note] Slave SQL thread initialized, starting replication in log 'db2-binary.165689' at position 4619552, relay log './db1-relay.064302' position: 623867 2024-07-01 4:56:36 101894 [Note] Slave I/O thread: connected to master 'gtid@10.76.24.77:3306',replication started in log 'db2-binary.165898' at position 137985852 2024-07-01 4:56:36 101895 [Note] 'SQL_SLAVE_SKIP_COUNTER=100' executed at relay_log_file='./db1-relay.064302', relay_log_pos='623867', master_log_name='db2-binary.165689', master_log_pos='4619552' and new position at relay_log_file='./db1-relay.064302', relay_log_pos='643195', master_log_name='db2-binary.165689', master_log_pos='6636952' 2024-07-01 4:56:36 11 [ERROR] mariadbd: Can't find record in 'activesessions' 2024-07-01 4:56:36 11 [ERROR] Slave SQL: Could not execute Delete_rows_v1 event on table aaadb.activesessions; Can't find record in 'activesessions', Error_code: 1032; handler error HA_ERR_KEY_NOT_FOUND; the event's master log db2-binary.165689, end_log_pos 6811511, Gtid 0-2-18664715725, Internal MariaDB error code: 1032 2024-07-01 4:56:36 11 [Warning] Slave: Can't find record in 'activesessions' Error_code: 1032 2024-07-01 4:56:36 11 [ERROR] Error running query, slave SQL thread aborted. Fix the problem, and restart the slave SQL thread with "SLAVE START". We stopped at log 'db2-binary.165689' position 6810767 2024-07-01 4:56:36 16 [ERROR] Slave (additional info): Commit failed due to failure of an earlier commit on which this one depends Error_code: 1964 2024-07-01 4:56:36 16 [Warning] Slave: Commit failed due to failure of an earlier commit on which this one depends Error_code: 1964 2024-07-01 4:56:36 16 [ERROR] Error running query, slave SQL thread aborted. Fix the problem, and restart the slave SQL thread with "SLAVE START". We stopped at log 'db2-binary.165689' position 6810767 2024-07-01 4:56:36 6 [ERROR] Slave (additional info): Commit failed due to failure of an earlier commit on which this one depends Error_code: 1964 2024-07-01 4:56:36 6 [Warning] Slave: Commit failed due to failure of an earlier commit on which this one depends Error_code: 1964 2024-07-01 4:56:36 6 [ERROR] Error running query, slave SQL thread aborted. Fix the problem, and restart the slave SQL thread with "SLAVE START". We stopped at log 'db2-binary.165689' position 6810767 2024-07-01 4:56:36 17 [ERROR] Slave (additional info): Commit failed due to failure of an earlier commit on which this one depends Error_code: 1964 2024-07-01 4:56:36 17 [Warning] Slave: Commit failed due to failure of an earlier commit on which this one depends Error_code: 1964 2024-07-01 4:56:36 17 [ERROR] Error running query, slave SQL thread aborted. Fix the problem, and restart the slave SQL thread with "SLAVE START". We stopped at log 'db2-binary.165689' position 6810767 2024-07-01 4:56:36 14 [ERROR] Slave (additional info): Commit failed due to failure of an earlier commit on which this one depends Error_code: 1964 2024-07-01 4:56:36 14 [Warning] Slave: Commit failed due to failure of an earlier commit on which this one depends Error_code: 1964 2024-07-01 4:56:36 14 [ERROR] Error running query, slave SQL thread aborted. Fix the problem, and restart the slave SQL thread with "SLAVE START". We stopped at log 'db2-binary.165689' position 6810767 2024-07-01 4:56:36 7 [ERROR] Slave (additional info): Commit failed due to failure of an earlier commit on which this one depends Error_code: 1964 2024-07-01 4:56:36 7 [Warning] Slave: Commit failed due to failure of an earlier commit on which this one depends Error_code: 1964 2024-07-01 4:56:36 7 [ERROR] Error running query, slave SQL thread aborted. Fix the problem, and restart the slave SQL thread with "SLAVE START". We stopped at log 'db2-binary.165689' position 6810767 2024-07-01 4:56:36 15 [ERROR] Slave (additional info): Commit failed due to failure of an earlier commit on which this one depends Error_code: 1964 2024-07-01 4:56:36 15 [Warning] Slave: Commit failed due to failure of an earlier commit on which this one depends Error_code: 1964 2024-07-01 4:56:36 15 [ERROR] Error running query, slave SQL thread aborted. Fix the problem, and restart the slave SQL thread with "SLAVE START". We stopped at log 'db2-binary.165689' position 6810767 2024-07-01 4:56:36 8 [ERROR] Slave (additional info): Commit failed due to failure of an earlier commit on which this one depends Error_code: 1964 2024-07-01 4:56:36 8 [Warning] Slave: Commit failed due to failure of an earlier commit on which this one depends Error_code: 1964 2024-07-01 4:56:36 8 [ERROR] Error running query, slave SQL thread aborted. Fix the problem, and restart the slave SQL thread with "SLAVE START". We stopped at log 'db2-binary.165689' position 6810767 2024-07-01 4:56:36 10 [ERROR] Slave (additional info): Commit failed due to failure of an earlier commit on which this one depends Error_code: 1964 2024-07-01 4:56:36 10 [Warning] Slave: Commit failed due to failure of an earlier commit on which this one depends Error_code: 1964 2024-07-01 4:56:36 10 [ERROR] Error running query, slave SQL thread aborted. Fix the problem, and restart the slave SQL thread with "SLAVE START". We stopped at log 'db2-binary.165689' position 6810767 2024-07-01 4:56:36 12 [ERROR] Slave (additional info): Commit failed due to failure of an earlier commit on which this one depends Error_code: 1964 2024-07-01 4:56:36 12 [Warning] Slave: Commit failed due to failure of an earlier commit on which this one depends Error_code: 1964 2024-07-01 4:56:36 12 [ERROR] Error running query, slave SQL thread aborted. Fix the problem, and restart the slave SQL thread with "SLAVE START". We stopped at log 'db2-binary.165689' position 6810767 2024-07-01 4:56:36 9 [ERROR] Slave (additional info): Commit failed due to failure of an earlier commit on which this one depends Error_code: 1964 2024-07-01 4:56:36 9 [Warning] Slave: Commit failed due to failure of an earlier commit on which this one depends Error_code: 1964 2024-07-01 4:56:36 9 [ERROR] Error running query, slave SQL thread aborted. Fix the problem, and restart the slave SQL thread with "SLAVE START". We stopped at log 'db2-binary.165689' position 6810767 2024-07-01 4:56:36 13 [ERROR] Slave (additional info): Commit failed due to failure of an earlier commit on which this one depends Error_code: 1964 2024-07-01 4:56:36 13 [Warning] Slave: Commit failed due to failure of an earlier commit on which this one depends Error_code: 1964 2024-07-01 4:56:36 13 [ERROR] Error running query, slave SQL thread aborted. Fix the problem, and restart the slave SQL thread with "SLAVE START". We stopped at log 'db2-binary.165689' position 6810767 2024-07-01 4:56:36 101895 [Note] Slave SQL thread exiting, replication stopped in log 'db2-binary.165689' at position 6810767, master: 10.76.24.77:3306 2024-07-01 4:56:42 101894 [Note] Slave I/O thread exiting, read up to log 'db2-binary.165898', position 148079397, master 10.76.24.77:3306 2024-07-01 4:56:42 101903 [Note] Slave I/O thread: Start asynchronous replication to master 'gtid@10.76.24.77:3306' in log 'db2-binary.165898' at position 148079397 2024-07-01 4:56:42 101904 [Note] Slave SQL thread initialized, starting replication in log 'db2-binary.165689' at position 6810767, relay log './db1-relay.064302' position: 817010 2024-07-01 4:56:42 101903 [Note] Slave I/O thread: connected to master 'gtid@10.76.24.77:3306',replication started in log 'db2-binary.165898' at position 148079397 2024-07-01 4:56:42 101904 [Note] 'SQL_SLAVE_SKIP_COUNTER=100' executed at relay_log_file='./db1-relay.064302', relay_log_pos='817010', master_log_name='db2-binary.165689', master_log_pos='6810767' and new position at relay_log_file='./db1-relay.064302', relay_log_pos='839979', master_log_name='db2-binary.165689', master_log_pos='6833736' 2024-07-01 4:56:42 7 [ERROR] mariadbd: Can't find record in 'activesessions' 2024-07-01 4:56:42 7 [ERROR] Slave SQL: Could not execute Delete_rows_v1 event on table aaadb.activesessions; Can't find record in 'activesessions', Error_code: 1032; handler error HA_ERR_KEY_NOT_FOUND; the event's master log db2-binary.165689, end_log_pos 19795103, Gtid 0-2-18664716564, Internal MariaDB error code: 1032 2024-07-01 4:56:42 7 [Warning] Slave: Can't find record in 'activesessions' Error_code: 1032 2024-07-01 4:56:42 7 [ERROR] Error running query, slave SQL thread aborted. Fix the problem, and restart the slave SQL thread with "SLAVE START". We stopped at log 'db2-binary.165689' position 19794378 2024-07-01 4:56:42 14 [ERROR] Slave (additional info): Commit failed due to failure of an earlier commit on which this one depends Error_code: 1964 2024-07-01 4:56:42 14 [Warning] Slave: Commit failed due to failure of an earlier commit on which this one depends Error_code: 1964 2024-07-01 4:56:42 14 [ERROR] Error running query, slave SQL thread aborted. Fix the problem, and restart the slave SQL thread with "SLAVE START". We stopped at log 'db2-binary.165689' position 19794378 2024-07-01 4:56:42 17 [ERROR] Slave (additional info): Commit failed due to failure of an earlier commit on which this one depends Error_code: 1964 2024-07-01 4:56:42 17 [Warning] Slave: Commit failed due to failure of an earlier commit on which this one depends Error_code: 1964 2024-07-01 4:56:42 17 [ERROR] Error running query, slave SQL thread aborted. Fix the problem, and restart the slave SQL thread with "SLAVE START". We stopped at log 'db2-binary.165689' position 19794378 2024-07-01 4:56:42 6 [ERROR] Slave (additional info): Commit failed due to failure of an earlier commit on which this one depends Error_code: 1964 2024-07-01 4:56:42 6 [Warning] Slave: Commit failed due to failure of an earlier commit on which this one depends Error_code: 1964 2024-07-01 4:56:42 6 [ERROR] Error running query, slave SQL thread aborted. Fix the problem, and restart the slave SQL thread with "SLAVE START". We stopped at log 'db2-binary.165689' position 19794378 2024-07-01 4:56:42 16 [ERROR] Slave (additional info): Commit failed due to failure of an earlier commit on which this one depends Error_code: 1964 2024-07-01 4:56:42 16 [Warning] Slave: Commit failed due to failure of an earlier commit on which this one depends Error_code: 1964 2024-07-01 4:56:42 16 [ERROR] Error running query, slave SQL thread aborted. Fix the problem, and restart the slave SQL thread with "SLAVE START". We stopped at log 'db2-binary.165689' position 19794378 2024-07-01 4:56:42 11 [ERROR] Slave (additional info): Commit failed due to failure of an earlier commit on which this one depends Error_code: 1964 2024-07-01 4:56:42 11 [Warning] Slave: Commit failed due to failure of an earlier commit on which this one depends Error_code: 1964 2024-07-01 4:56:42 11 [ERROR] Error running query, slave SQL thread aborted. Fix the problem, and restart the slave SQL thread with "SLAVE START". We stopped at log 'db2-binary.165689' position 19794378 2024-07-01 4:56:42 13 [ERROR] Slave (additional info): Commit failed due to failure of an earlier commit on which this one depends Error_code: 1964 2024-07-01 4:56:42 13 [Warning] Slave: Record has changed since last read in table 'activesessions' Error_code: 1020 2024-07-01 4:56:42 13 [Warning] Slave: Deadlock found when trying to get lock; try restarting transaction Error_code: 1213 2024-07-01 4:56:42 13 [Warning] Slave: Commit failed due to failure of an earlier commit on which this one depends Error_code: 1964 2024-07-01 4:56:42 13 [ERROR] Error running query, slave SQL thread aborted. Fix the problem, and restart the slave SQL thread with "SLAVE START". We stopped at log 'db2-binary.165689' position 19794378 2024-07-01 4:56:42 9 [ERROR] Slave (additional info): Commit failed due to failure of an earlier commit on which this one depends Error_code: 1964 2024-07-01 4:56:42 9 [Warning] Slave: Commit failed due to failure of an earlier commit on which this one depends Error_code: 1964 2024-07-01 4:56:42 9 [ERROR] Error running query, slave SQL thread aborted. Fix the problem, and restart the slave SQL thread with "SLAVE START". We stopped at log 'db2-binary.165689' position 19794378 2024-07-01 4:56:42 12 [ERROR] Slave (additional info): Commit failed due to failure of an earlier commit on which this one depends Error_code: 1964 2024-07-01 4:56:42 12 [Warning] Slave: Commit failed due to failure of an earlier commit on which this one depends Error_code: 1964 2024-07-01 4:56:42 12 [ERROR] Error running query, slave SQL thread aborted. Fix the problem, and restart the slave SQL thread with "SLAVE START". We stopped at log 'db2-binary.165689' position 19794378 2024-07-01 4:56:42 10 [ERROR] Slave (additional info): Commit failed due to failure of an earlier commit on which this one depends Error_code: 1964 2024-07-01 4:56:42 10 [Warning] Slave: Commit failed due to failure of an earlier commit on which this one depends Error_code: 1964 2024-07-01 4:56:42 10 [ERROR] Error running query, slave SQL thread aborted. Fix the problem, and restart the slave SQL thread with "SLAVE START". We stopped at log 'db2-binary.165689' position 19794378 2024-07-01 4:56:42 8 [ERROR] Slave (additional info): Commit failed due to failure of an earlier commit on which this one depends Error_code: 1964 2024-07-01 4:56:42 8 [Warning] Slave: Commit failed due to failure of an earlier commit on which this one depends Error_code: 1964 2024-07-01 4:56:42 8 [ERROR] Error running query, slave SQL thread aborted. Fix the problem, and restart the slave SQL thread with "SLAVE START". We stopped at log 'db2-binary.165689' position 19794378 2024-07-01 4:56:42 15 [ERROR] Slave (additional info): Commit failed due to failure of an earlier commit on which this one depends Error_code: 1964 2024-07-01 4:56:42 15 [Warning] Slave: Commit failed due to failure of an earlier commit on which this one depends Error_code: 1964 2024-07-01 4:56:42 15 [ERROR] Error running query, slave SQL thread aborted. Fix the problem, and restart the slave SQL thread with "SLAVE START". We stopped at log 'db2-binary.165689' position 19794378 2024-07-01 4:56:42 101904 [Note] Slave SQL thread exiting, replication stopped in log 'db2-binary.165689' at position 19794378, master: 10.76.24.77:3306 2024-07-01 4:56:47 101903 [Note] Slave I/O thread exiting, read up to log 'db2-binary.165898', position 157442583, master 10.76.24.77:3306 2024-07-01 4:56:47 101926 [Note] Slave I/O thread: Start asynchronous replication to master 'gtid@10.76.24.77:3306' in log 'db2-binary.165898' at position 157442583 2024-07-01 4:56:47 101927 [Note] Slave SQL thread initialized, starting replication in log 'db2-binary.165689' at position 19794378, relay log './db1-relay.064302' position: 1808669 2024-07-01 4:56:47 101926 [Note] Slave I/O thread: connected to master 'gtid@10.76.24.77:3306',replication started in log 'db2-binary.165898' at position 157442583 2024-07-01 4:56:47 101927 [Note] 'SQL_SLAVE_SKIP_COUNTER=100' executed at relay_log_file='./db1-relay.064302', relay_log_pos='1808669', master_log_name='db2-binary.165689', master_log_pos='19794378' and new position at relay_log_file='./db1-relay.064302', relay_log_pos='1834136', master_log_name='db2-binary.165689', master_log_pos='19819845' 2024-07-01 4:56:47 7 [ERROR] mariadbd: Can't find record in 'activesessions' 2024-07-01 4:56:47 7 [ERROR] Slave SQL: Could not execute Delete_rows_v1 event on table aaadb.activesessions; Can't find record in 'activesessions', Error_code: 1032; handler error HA_ERR_KEY_NOT_FOUND; the event's master log db2-binary.165689, end_log_pos 19899825, Gtid 0-2-18664716641, Internal MariaDB error code: 1032 2024-07-01 4:56:47 7 [Warning] Slave: Can't find record in 'activesessions' Error_code: 1032 2024-07-01 4:56:47 7 [ERROR] Error running query, slave SQL thread aborted. Fix the problem, and restart the slave SQL thread with "SLAVE START". We stopped at log 'db2-binary.165689' position 19899089 2024-07-01 4:56:47 15 [ERROR] Slave (additional info): Commit failed due to failure of an earlier commit on which this one depends Error_code: 1964 2024-07-01 4:56:47 15 [Warning] Slave: Commit failed due to failure of an earlier commit on which this one depends Error_code: 1964 2024-07-01 4:56:47 15 [ERROR] Error running query, slave SQL thread aborted. Fix the problem, and restart the slave SQL thread with "SLAVE START". We stopped at log 'db2-binary.165689' position 19899089 2024-07-01 4:56:47 8 [ERROR] Slave (additional info): Commit failed due to failure of an earlier commit on which this one depends Error_code: 1964 2024-07-01 4:56:47 8 [Warning] Slave: Commit failed due to failure of an earlier commit on which this one depends Error_code: 1964 2024-07-01 4:56:47 8 [ERROR] Error running query, slave SQL thread aborted. Fix the problem, and restart the slave SQL thread with "SLAVE START". We stopped at log 'db2-binary.165689' position 19899089 2024-07-01 4:56:47 10 [ERROR] Slave (additional info): Commit failed due to failure of an earlier commit on which this one depends Error_code: 1964 2024-07-01 4:56:47 10 [Warning] Slave: Commit failed due to failure of an earlier commit on which this one depends Error_code: 1964 2024-07-01 4:56:47 10 [ERROR] Error running query, slave SQL thread aborted. Fix the problem, and restart the slave SQL thread with "SLAVE START". We stopped at log 'db2-binary.165689' position 19899089 2024-07-01 4:56:47 12 [ERROR] Slave (additional info): Commit failed due to failure of an earlier commit on which this one depends Error_code: 1964 2024-07-01 4:56:47 12 [Warning] Slave: Commit failed due to failure of an earlier commit on which this one depends Error_code: 1964 2024-07-01 4:56:47 12 [ERROR] Error running query, slave SQL thread aborted. Fix the problem, and restart the slave SQL thread with "SLAVE START". We stopped at log 'db2-binary.165689' position 19899089 2024-07-01 4:56:47 9 [ERROR] Slave (additional info): Commit failed due to failure of an earlier commit on which this one depends Error_code: 1964 2024-07-01 4:56:47 9 [Warning] Slave: Commit failed due to failure of an earlier commit on which this one depends Error_code: 1964 2024-07-01 4:56:47 9 [ERROR] Error running query, slave SQL thread aborted. Fix the problem, and restart the slave SQL thread with "SLAVE START". We stopped at log 'db2-binary.165689' position 19899089 2024-07-01 4:56:47 13 [ERROR] Slave (additional info): Commit failed due to failure of an earlier commit on which this one depends Error_code: 1964 2024-07-01 4:56:47 13 [Warning] Slave: Commit failed due to failure of an earlier commit on which this one depends Error_code: 1964 2024-07-01 4:56:47 13 [ERROR] Error running query, slave SQL thread aborted. Fix the problem, and restart the slave SQL thread with "SLAVE START". We stopped at log 'db2-binary.165689' position 19899089 2024-07-01 4:56:47 11 [ERROR] Slave (additional info): Commit failed due to failure of an earlier commit on which this one depends Error_code: 1964 2024-07-01 4:56:47 11 [Warning] Slave: Commit failed due to failure of an earlier commit on which this one depends Error_code: 1964 2024-07-01 4:56:47 11 [ERROR] Error running query, slave SQL thread aborted. Fix the problem, and restart the slave SQL thread with "SLAVE START". We stopped at log 'db2-binary.165689' position 19899089 2024-07-01 4:56:47 16 [ERROR] Slave (additional info): Commit failed due to failure of an earlier commit on which this one depends Error_code: 1964 2024-07-01 4:56:47 16 [Warning] Slave: Commit failed due to failure of an earlier commit on which this one depends Error_code: 1964 2024-07-01 4:56:47 16 [ERROR] Error running query, slave SQL thread aborted. Fix the problem, and restart the slave SQL thread with "SLAVE START". We stopped at log 'db2-binary.165689' position 19899089 2024-07-01 4:56:47 6 [ERROR] Slave (additional info): Commit failed due to failure of an earlier commit on which this one depends Error_code: 1964 2024-07-01 4:56:47 6 [Warning] Slave: Commit failed due to failure of an earlier commit on which this one depends Error_code: 1964 2024-07-01 4:56:47 6 [ERROR] Error running query, slave SQL thread aborted. Fix the problem, and restart the slave SQL thread with "SLAVE START". We stopped at log 'db2-binary.165689' position 19899089 2024-07-01 4:56:47 17 [ERROR] Slave (additional info): Commit failed due to failure of an earlier commit on which this one depends Error_code: 1964 2024-07-01 4:56:47 17 [Warning] Slave: Commit failed due to failure of an earlier commit on which this one depends Error_code: 1964 2024-07-01 4:56:47 17 [ERROR] Error running query, slave SQL thread aborted. Fix the problem, and restart the slave SQL thread with "SLAVE START". We stopped at log 'db2-binary.165689' position 19899089 2024-07-01 4:56:47 14 [ERROR] Slave (additional info): Commit failed due to failure of an earlier commit on which this one depends Error_code: 1964 2024-07-01 4:56:47 14 [Warning] Slave: Commit failed due to failure of an earlier commit on which this one depends Error_code: 1964 2024-07-01 4:56:47 14 [ERROR] Error running query, slave SQL thread aborted. Fix the problem, and restart the slave SQL thread with "SLAVE START". We stopped at log 'db2-binary.165689' position 19899089 2024-07-01 4:56:47 101927 [Note] Slave SQL thread exiting, replication stopped in log 'db2-binary.165689' at position 19899089, master: 10.76.24.77:3306 2024-07-01 4:56:53 101926 [Note] Slave I/O thread exiting, read up to log 'db2-binary.165898', position 165906385, master 10.76.24.77:3306 2024-07-01 4:56:53 101932 [Note] Slave I/O thread: Start asynchronous replication to master 'gtid@10.76.24.77:3306' in log 'db2-binary.165898' at position 165906385 2024-07-01 4:56:53 101933 [Note] Slave SQL thread initialized, starting replication in log 'db2-binary.165689' at position 19899089, relay log './db1-relay.064302' position: 1913380 2024-07-01 4:56:53 101932 [Note] Slave I/O thread: connected to master 'gtid@10.76.24.77:3306',replication started in log 'db2-binary.165898' at position 165906385 2024-07-01 4:56:53 101933 [Note] 'SQL_SLAVE_SKIP_COUNTER=100' executed at relay_log_file='./db1-relay.064302', relay_log_pos='1913380', master_log_name='db2-binary.165689', master_log_pos='19899089' and new position at relay_log_file='./db1-relay.064302', relay_log_pos='1936550', master_log_name='db2-binary.165689', master_log_pos='21920861' 2024-07-01 4:56:55 8 [ERROR] mariadbd: Can't find record in 'activesessions' 2024-07-01 4:56:55 8 [ERROR] Slave SQL: Could not execute Delete_rows_v1 event on table aaadb.activesessions; Can't find record in 'activesessions', Error_code: 1032; handler error HA_ERR_KEY_NOT_FOUND; the event's master log db2-binary.165691, end_log_pos 128874871, Gtid 0-2-18664737281, Internal MariaDB error code: 1032 2024-07-01 4:56:55 8 [Warning] Slave: Can't find record in 'activesessions' Error_code: 1032 2024-07-01 4:56:55 8 [ERROR] Error running query, slave SQL thread aborted. Fix the problem, and restart the slave SQL thread with "SLAVE START". We stopped at log 'db2-binary.165691' position 128874109 2024-07-01 4:56:55 15 [ERROR] Slave (additional info): Commit failed due to failure of an earlier commit on which this one depends Error_code: 1964 2024-07-01 4:56:55 15 [Warning] Slave: Commit failed due to failure of an earlier commit on which this one depends Error_code: 1964 2024-07-01 4:56:55 15 [ERROR] Error running query, slave SQL thread aborted. Fix the problem, and restart the slave SQL thread with "SLAVE START". We stopped at log 'db2-binary.165691' position 128874109 2024-07-01 4:56:55 7 [ERROR] Slave (additional info): Commit failed due to failure of an earlier commit on which this one depends Error_code: 1964 2024-07-01 4:56:55 7 [Warning] Slave: Commit failed due to failure of an earlier commit on which this one depends Error_code: 1964 2024-07-01 4:56:55 7 [ERROR] Error running query, slave SQL thread aborted. Fix the problem, and restart the slave SQL thread with "SLAVE START". We stopped at log 'db2-binary.165691' position 128874109 2024-07-01 4:56:55 14 [ERROR] Slave (additional info): Commit failed due to failure of an earlier commit on which this one depends Error_code: 1964 2024-07-01 4:56:55 14 [Warning] Slave: Commit failed due to failure of an earlier commit on which this one depends Error_code: 1964 2024-07-01 4:56:55 14 [ERROR] Error running query, slave SQL thread aborted. Fix the problem, and restart the slave SQL thread with "SLAVE START". We stopped at log 'db2-binary.165691' position 128874109 2024-07-01 4:56:55 17 [ERROR] Slave (additional info): Commit failed due to failure of an earlier commit on which this one depends Error_code: 1964 2024-07-01 4:56:55 17 [Warning] Slave: Commit failed due to failure of an earlier commit on which this one depends Error_code: 1964 2024-07-01 4:56:55 17 [ERROR] Error running query, slave SQL thread aborted. Fix the problem, and restart the slave SQL thread with "SLAVE START". We stopped at log 'db2-binary.165691' position 128874109 2024-07-01 4:56:55 6 [ERROR] Slave (additional info): Commit failed due to failure of an earlier commit on which this one depends Error_code: 1964 2024-07-01 4:56:55 6 [Warning] Slave: Commit failed due to failure of an earlier commit on which this one depends Error_code: 1964 2024-07-01 4:56:55 6 [ERROR] Error running query, slave SQL thread aborted. Fix the problem, and restart the slave SQL thread with "SLAVE START". We stopped at log 'db2-binary.165691' position 128874109 2024-07-01 4:56:55 16 [ERROR] Slave (additional info): Commit failed due to failure of an earlier commit on which this one depends Error_code: 1964 2024-07-01 4:56:55 16 [Warning] Slave: Commit failed due to failure of an earlier commit on which this one depends Error_code: 1964 2024-07-01 4:56:55 16 [ERROR] Error running query, slave SQL thread aborted. Fix the problem, and restart the slave SQL thread with "SLAVE START". We stopped at log 'db2-binary.165691' position 128874109 2024-07-01 4:56:55 11 [ERROR] Slave (additional info): Commit failed due to failure of an earlier commit on which this one depends Error_code: 1964 2024-07-01 4:56:55 11 [Warning] Slave: Commit failed due to failure of an earlier commit on which this one depends Error_code: 1964 2024-07-01 4:56:55 11 [ERROR] Error running query, slave SQL thread aborted. Fix the problem, and restart the slave SQL thread with "SLAVE START". We stopped at log 'db2-binary.165691' position 128874109 2024-07-01 4:56:55 13 [ERROR] Slave (additional info): Commit failed due to failure of an earlier commit on which this one depends Error_code: 1964 2024-07-01 4:56:55 13 [Warning] Slave: Commit failed due to failure of an earlier commit on which this one depends Error_code: 1964 2024-07-01 4:56:55 13 [ERROR] Error running query, slave SQL thread aborted. Fix the problem, and restart the slave SQL thread with "SLAVE START". We stopped at log 'db2-binary.165691' position 128874109 2024-07-01 4:56:55 9 [ERROR] Slave (additional info): Commit failed due to failure of an earlier commit on which this one depends Error_code: 1964 2024-07-01 4:56:55 9 [Warning] Slave: Commit failed due to failure of an earlier commit on which this one depends Error_code: 1964 2024-07-01 4:56:55 9 [ERROR] Error running query, slave SQL thread aborted. Fix the problem, and restart the slave SQL thread with "SLAVE START". We stopped at log 'db2-binary.165691' position 128874109 2024-07-01 4:56:55 12 [ERROR] Slave (additional info): Commit failed due to failure of an earlier commit on which this one depends Error_code: 1964 2024-07-01 4:56:55 12 [Warning] Slave: Commit failed due to failure of an earlier commit on which this one depends Error_code: 1964 2024-07-01 4:56:55 12 [ERROR] Error running query, slave SQL thread aborted. Fix the problem, and restart the slave SQL thread with "SLAVE START". We stopped at log 'db2-binary.165691' position 128874109 2024-07-01 4:56:55 10 [ERROR] Slave (additional info): Commit failed due to failure of an earlier commit on which this one depends Error_code: 1964 2024-07-01 4:56:55 10 [Warning] Slave: Commit failed due to failure of an earlier commit on which this one depends Error_code: 1964 2024-07-01 4:56:55 10 [ERROR] Error running query, slave SQL thread aborted. Fix the problem, and restart the slave SQL thread with "SLAVE START". We stopped at log 'db2-binary.165691' position 128874109 2024-07-01 4:56:55 101933 [Note] Slave SQL thread exiting, replication stopped in log 'db2-binary.165691' at position 128874109, master: 10.76.24.77:3306 2024-07-01 4:57:06 101932 [Note] Slave I/O thread exiting, read up to log 'db2-binary.165898', position 188623935, master 10.76.24.77:3306 2024-07-01 4:57:06 102336 [Note] Slave I/O thread: Start asynchronous replication to master 'gtid@10.76.24.77:3306' in log 'db2-binary.165898' at position 188623935 2024-07-01 4:57:06 102337 [Note] Slave SQL thread initialized, starting replication in log 'db2-binary.165691' at position 128874109, relay log './db1-relay.064306' position: 8966464 2024-07-01 4:57:06 102336 [Note] Slave I/O thread: connected to master 'gtid@10.76.24.77:3306',replication started in log 'db2-binary.165898' at position 188623935 2024-07-01 4:57:06 102337 [Note] 'SQL_SLAVE_SKIP_COUNTER=100' executed at relay_log_file='./db1-relay.064306', relay_log_pos='8966464', master_log_name='db2-binary.165691', master_log_pos='128874109' and new position at relay_log_file='./db1-relay.064306', relay_log_pos='8998747', master_log_name='db2-binary.165691', master_log_pos='128906392' 2024-07-01 4:57:07 7 [ERROR] mariadbd: Can't find record in 'activesessions' 2024-07-01 4:57:07 7 [ERROR] Slave SQL: Could not execute Delete_rows_v1 event on table aaadb.activesessions; Can't find record in 'activesessions', Error_code: 1032; handler error HA_ERR_KEY_NOT_FOUND; the event's master log db2-binary.165692, end_log_pos 49795891, Gtid 0-2-18664742849, Internal MariaDB error code: 1032 2024-07-01 4:57:07 7 [Warning] Slave: Can't find record in 'activesessions' Error_code: 1032 2024-07-01 4:57:07 7 [ERROR] Error running query, slave SQL thread aborted. Fix the problem, and restart the slave SQL thread with "SLAVE START". We stopped at log 'db2-binary.165692' position 49795148 2024-07-01 4:57:07 15 [ERROR] Slave (additional info): Commit failed due to failure of an earlier commit on which this one depends Error_code: 1964 2024-07-01 4:57:07 15 [Warning] Slave: Commit failed due to failure of an earlier commit on which this one depends Error_code: 1964 2024-07-01 4:57:07 15 [ERROR] Error running query, slave SQL thread aborted. Fix the problem, and restart the slave SQL thread with "SLAVE START". We stopped at log 'db2-binary.165692' position 49795148 2024-07-01 4:57:07 8 [ERROR] Slave (additional info): Commit failed due to failure of an earlier commit on which this one depends Error_code: 1964 2024-07-01 4:57:07 8 [Warning] Slave: Commit failed due to failure of an earlier commit on which this one depends Error_code: 1964 2024-07-01 4:57:07 8 [ERROR] Error running query, slave SQL thread aborted. Fix the problem, and restart the slave SQL thread with "SLAVE START". We stopped at log 'db2-binary.165692' position 49795148 2024-07-01 4:57:07 10 [ERROR] Slave (additional info): Commit failed due to failure of an earlier commit on which this one depends Error_code: 1964 2024-07-01 4:57:07 10 [Warning] Slave: Commit failed due to failure of an earlier commit on which this one depends Error_code: 1964 2024-07-01 4:57:07 10 [ERROR] Error running query, slave SQL thread aborted. Fix the problem, and restart the slave SQL thread with "SLAVE START". We stopped at log 'db2-binary.165692' position 49795148 2024-07-01 4:57:07 12 [ERROR] Slave (additional info): Commit failed due to failure of an earlier commit on which this one depends Error_code: 1964 2024-07-01 4:57:07 12 [Warning] Slave: Commit failed due to failure of an earlier commit on which this one depends Error_code: 1964 2024-07-01 4:57:07 12 [ERROR] Error running query, slave SQL thread aborted. Fix the problem, and restart the slave SQL thread with "SLAVE START". We stopped at log 'db2-binary.165692' position 49795148 2024-07-01 4:57:07 9 [ERROR] Slave (additional info): Commit failed due to failure of an earlier commit on which this one depends Error_code: 1964 2024-07-01 4:57:07 9 [Warning] Slave: Commit failed due to failure of an earlier commit on which this one depends Error_code: 1964 2024-07-01 4:57:07 9 [ERROR] Error running query, slave SQL thread aborted. Fix the problem, and restart the slave SQL thread with "SLAVE START". We stopped at log 'db2-binary.165692' position 49795148 2024-07-01 4:57:07 13 [ERROR] Slave (additional info): Commit failed due to failure of an earlier commit on which this one depends Error_code: 1964 2024-07-01 4:57:07 13 [Warning] Slave: Commit failed due to failure of an earlier commit on which this one depends Error_code: 1964 2024-07-01 4:57:07 13 [ERROR] Error running query, slave SQL thread aborted. Fix the problem, and restart the slave SQL thread with "SLAVE START". We stopped at log 'db2-binary.165692' position 49795148 2024-07-01 4:57:07 11 [ERROR] Slave (additional info): Commit failed due to failure of an earlier commit on which this one depends Error_code: 1964 2024-07-01 4:57:07 11 [Warning] Slave: Commit failed due to failure of an earlier commit on which this one depends Error_code: 1964 2024-07-01 4:57:07 11 [ERROR] Error running query, slave SQL thread aborted. Fix the problem, and restart the slave SQL thread with "SLAVE START". We stopped at log 'db2-binary.165692' position 49795148 2024-07-01 4:57:07 16 [ERROR] Slave (additional info): Commit failed due to failure of an earlier commit on which this one depends Error_code: 1964 2024-07-01 4:57:07 16 [Warning] Slave: Commit failed due to failure of an earlier commit on which this one depends Error_code: 1964 2024-07-01 4:57:07 16 [ERROR] Error running query, slave SQL thread aborted. Fix the problem, and restart the slave SQL thread with "SLAVE START". We stopped at log 'db2-binary.165692' position 49795148 2024-07-01 4:57:07 6 [ERROR] Slave (additional info): Commit failed due to failure of an earlier commit on which this one depends Error_code: 1964 2024-07-01 4:57:07 6 [Warning] Slave: Commit failed due to failure of an earlier commit on which this one depends Error_code: 1964 2024-07-01 4:57:07 6 [ERROR] Error running query, slave SQL thread aborted. Fix the problem, and restart the slave SQL thread with "SLAVE START". We stopped at log 'db2-binary.165692' position 49795148 2024-07-01 4:57:07 17 [ERROR] Slave (additional info): Commit failed due to failure of an earlier commit on which this one depends Error_code: 1964 2024-07-01 4:57:07 17 [Warning] Slave: Commit failed due to failure of an earlier commit on which this one depends Error_code: 1964 2024-07-01 4:57:07 17 [ERROR] Error running query, slave SQL thread aborted. Fix the problem, and restart the slave SQL thread with "SLAVE START". We stopped at log 'db2-binary.165692' position 49795148 2024-07-01 4:57:07 14 [ERROR] Slave (additional info): Commit failed due to failure of an earlier commit on which this one depends Error_code: 1964 2024-07-01 4:57:07 14 [Warning] Slave: Commit failed due to failure of an earlier commit on which this one depends Error_code: 1964 2024-07-01 4:57:07 14 [ERROR] Error running query, slave SQL thread aborted. Fix the problem, and restart the slave SQL thread with "SLAVE START". We stopped at log 'db2-binary.165692' position 49795148 2024-07-01 4:57:07 102337 [Note] Slave SQL thread exiting, replication stopped in log 'db2-binary.165692' at position 49795148, master: 10.76.24.77:3306 2024-07-01 4:57:12 102336 [Note] Slave I/O thread exiting, read up to log 'db2-binary.165898', position 198436600, master 10.76.24.77:3306 2024-07-01 4:57:12 102447 [Note] Slave I/O thread: Start asynchronous replication to master 'gtid@10.76.24.77:3306' in log 'db2-binary.165898' at position 198436600 2024-07-01 4:57:12 102448 [Note] Slave SQL thread initialized, starting replication in log 'db2-binary.165692' at position 49795148, relay log './db1-relay.064308' position: 3839377 2024-07-01 4:57:12 102447 [Note] Slave I/O thread: connected to master 'gtid@10.76.24.77:3306',replication started in log 'db2-binary.165898' at position 198436600 2024-07-01 4:57:12 102448 [Note] 'SQL_SLAVE_SKIP_COUNTER=100' executed at relay_log_file='./db1-relay.064308', relay_log_pos='3839377', master_log_name='db2-binary.165692', master_log_pos='49795148' and new position at relay_log_file='./db1-relay.064308', relay_log_pos='3873332', master_log_name='db2-binary.165692', master_log_pos='51827101' 2024-07-01 4:57:12 8 [Warning] Slave SQL: Could not execute Write_rows_v1 event on table aaadb.activesessions; Duplicate entry 'HWI-GJR011031264000000f6b4eAAAbR63401030VDSL' for key 'PRIMARY', Error_code: 1062; handler error HA_ERR_FOUND_DUPP_KEY; the event's master log db2-binary.165692, end_log_pos 51828786, Gtid 0-2-18664742869, Internal MariaDB error code: 1062 2024-07-01 4:57:16 6 [ERROR] mariadbd: Can't find record in 'activesessions' 2024-07-01 4:57:16 6 [ERROR] Slave SQL: Could not execute Delete_rows_v1 event on table aaadb.activesessions; Can't find record in 'activesessions', Error_code: 1032; handler error HA_ERR_KEY_NOT_FOUND; the event's master log db2-binary.165695, end_log_pos 136581592, Gtid 0-2-18664773978, Internal MariaDB error code: 1032 2024-07-01 4:57:16 6 [Warning] Slave: Can't find record in 'activesessions' Error_code: 1032 2024-07-01 4:57:16 6 [ERROR] Error running query, slave SQL thread aborted. Fix the problem, and restart the slave SQL thread with "SLAVE START". We stopped at log 'db2-binary.165695' position 136580824 2024-07-01 4:57:16 16 [ERROR] Slave (additional info): Commit failed due to failure of an earlier commit on which this one depends Error_code: 1964 2024-07-01 4:57:16 16 [Warning] Slave: Commit failed due to failure of an earlier commit on which this one depends Error_code: 1964 2024-07-01 4:57:16 16 [ERROR] Error running query, slave SQL thread aborted. Fix the problem, and restart the slave SQL thread with "SLAVE START". We stopped at log 'db2-binary.165695' position 136580824 2024-07-01 4:57:16 11 [ERROR] Slave (additional info): Commit failed due to failure of an earlier commit on which this one depends Error_code: 1964 2024-07-01 4:57:16 11 [Warning] Slave: Commit failed due to failure of an earlier commit on which this one depends Error_code: 1964 2024-07-01 4:57:16 11 [ERROR] Error running query, slave SQL thread aborted. Fix the problem, and restart the slave SQL thread with "SLAVE START". We stopped at log 'db2-binary.165695' position 136580824 2024-07-01 4:57:16 13 [ERROR] Slave (additional info): Commit failed due to failure of an earlier commit on which this one depends Error_code: 1964 2024-07-01 4:57:16 13 [Warning] Slave: Commit failed due to failure of an earlier commit on which this one depends Error_code: 1964 2024-07-01 4:57:16 13 [ERROR] Error running query, slave SQL thread aborted. Fix the problem, and restart the slave SQL thread with "SLAVE START". We stopped at log 'db2-binary.165695' position 136580824 2024-07-01 4:57:16 9 [ERROR] Slave (additional info): Commit failed due to failure of an earlier commit on which this one depends Error_code: 1964 2024-07-01 4:57:16 9 [Warning] Slave: Commit failed due to failure of an earlier commit on which this one depends Error_code: 1964 2024-07-01 4:57:16 9 [ERROR] Error running query, slave SQL thread aborted. Fix the problem, and restart the slave SQL thread with "SLAVE START". We stopped at log 'db2-binary.165695' position 136580824 2024-07-01 4:57:16 12 [ERROR] Slave (additional info): Commit failed due to failure of an earlier commit on which this one depends Error_code: 1964 2024-07-01 4:57:16 12 [Warning] Slave: Commit failed due to failure of an earlier commit on which this one depends Error_code: 1964 2024-07-01 4:57:16 12 [ERROR] Error running query, slave SQL thread aborted. Fix the problem, and restart the slave SQL thread with "SLAVE START". We stopped at log 'db2-binary.165695' position 136580824 2024-07-01 4:57:16 10 [ERROR] Slave (additional info): Commit failed due to failure of an earlier commit on which this one depends Error_code: 1964 2024-07-01 4:57:16 10 [Warning] Slave: Commit failed due to failure of an earlier commit on which this one depends Error_code: 1964 2024-07-01 4:57:16 10 [ERROR] Error running query, slave SQL thread aborted. Fix the problem, and restart the slave SQL thread with "SLAVE START". We stopped at log 'db2-binary.165695' position 136580824 2024-07-01 4:57:16 8 [ERROR] Slave (additional info): Commit failed due to failure of an earlier commit on which this one depends Error_code: 1964 2024-07-01 4:57:16 8 [Warning] Slave: Commit failed due to failure of an earlier commit on which this one depends Error_code: 1964 2024-07-01 4:57:16 8 [ERROR] Error running query, slave SQL thread aborted. Fix the problem, and restart the slave SQL thread with "SLAVE START". We stopped at log 'db2-binary.165695' position 136580824 2024-07-01 4:57:16 15 [ERROR] Slave (additional info): Commit failed due to failure of an earlier commit on which this one depends Error_code: 1964 2024-07-01 4:57:16 15 [Warning] Slave: Commit failed due to failure of an earlier commit on which this one depends Error_code: 1964 2024-07-01 4:57:16 15 [ERROR] Error running query, slave SQL thread aborted. Fix the problem, and restart the slave SQL thread with "SLAVE START". We stopped at log 'db2-binary.165695' position 136580824 2024-07-01 4:57:16 7 [ERROR] Slave (additional info): Commit failed due to failure of an earlier commit on which this one depends Error_code: 1964 2024-07-01 4:57:16 7 [Warning] Slave: Commit failed due to failure of an earlier commit on which this one depends Error_code: 1964 2024-07-01 4:57:16 7 [ERROR] Error running query, slave SQL thread aborted. Fix the problem, and restart the slave SQL thread with "SLAVE START". We stopped at log 'db2-binary.165695' position 136580824 2024-07-01 4:57:16 14 [ERROR] Slave (additional info): Commit failed due to failure of an earlier commit on which this one depends Error_code: 1964 2024-07-01 4:57:16 14 [Warning] Slave: Commit failed due to failure of an earlier commit on which this one depends Error_code: 1964 2024-07-01 4:57:16 14 [ERROR] Error running query, slave SQL thread aborted. Fix the problem, and restart the slave SQL thread with "SLAVE START". We stopped at log 'db2-binary.165695' position 136580824 2024-07-01 4:57:16 17 [ERROR] Slave (additional info): Commit failed due to failure of an earlier commit on which this one depends Error_code: 1964 2024-07-01 4:57:16 17 [Warning] Slave: Commit failed due to failure of an earlier commit on which this one depends Error_code: 1964 2024-07-01 4:57:16 17 [ERROR] Error running query, slave SQL thread aborted. Fix the problem, and restart the slave SQL thread with "SLAVE START". We stopped at log 'db2-binary.165695' position 136580824 2024-07-01 4:57:16 102448 [Note] Slave SQL thread exiting, replication stopped in log 'db2-binary.165695' at position 136580824, master: 10.76.24.77:3306 2024-07-01 4:57:25 102447 [Note] Slave I/O thread exiting, read up to log 'db2-binary.165899', position 8496984, master 10.76.24.77:3306 2024-07-01 4:57:25 103046 [Note] Slave I/O thread: Start asynchronous replication to master 'gtid@10.76.24.77:3306' in log 'db2-binary.165899' at position 8496984 2024-07-01 4:57:25 103047 [Note] Slave SQL thread initialized, starting replication in log 'db2-binary.165695' at position 136580824, relay log './db1-relay.064315' position: 10660520 2024-07-01 4:57:25 103046 [Note] Slave I/O thread: connected to master 'gtid@10.76.24.77:3306',replication started in log 'db2-binary.165899' at position 8496984 2024-07-01 4:57:25 103047 [Note] 'SQL_SLAVE_SKIP_COUNTER=100' executed at relay_log_file='./db1-relay.064315', relay_log_pos='10660520', master_log_name='db2-binary.165695', master_log_pos='136580824' and new position at relay_log_file='./db1-relay.064315', relay_log_pos='10691754', master_log_name='db2-binary.165695', master_log_pos='136612058' 2024-07-01 4:57:25 13 [ERROR] mariadbd: Can't find record in 'activesessions' 2024-07-01 4:57:25 13 [ERROR] Slave SQL: Could not execute Delete_rows_v1 event on table aaadb.activesessions; Can't find record in 'activesessions', Error_code: 1032; handler error HA_ERR_KEY_NOT_FOUND; the event's master log db2-binary.165695, end_log_pos 184296364, Gtid 0-2-18664776103, Internal MariaDB error code: 1032 2024-07-01 4:57:25 13 [Warning] Slave: Can't find record in 'activesessions' Error_code: 1032 2024-07-01 4:57:25 13 [ERROR] Error running query, slave SQL thread aborted. Fix the problem, and restart the slave SQL thread with "SLAVE START". We stopped at log 'db2-binary.165695' position 184295609 2024-07-01 4:57:25 11 [ERROR] Slave (additional info): Commit failed due to failure of an earlier commit on which this one depends Error_code: 1964 2024-07-01 4:57:25 11 [Warning] Slave: Commit failed due to failure of an earlier commit on which this one depends Error_code: 1964 2024-07-01 4:57:25 11 [ERROR] Error running query, slave SQL thread aborted. Fix the problem, and restart the slave SQL thread with "SLAVE START". We stopped at log 'db2-binary.165695' position 184295609 2024-07-01 4:57:25 16 [ERROR] Slave (additional info): Commit failed due to failure of an earlier commit on which this one depends Error_code: 1964 2024-07-01 4:57:25 16 [Warning] Slave: Commit failed due to failure of an earlier commit on which this one depends Error_code: 1964 2024-07-01 4:57:25 16 [ERROR] Error running query, slave SQL thread aborted. Fix the problem, and restart the slave SQL thread with "SLAVE START". We stopped at log 'db2-binary.165695' position 184295609 2024-07-01 4:57:25 6 [ERROR] Slave (additional info): Commit failed due to failure of an earlier commit on which this one depends Error_code: 1964 2024-07-01 4:57:25 6 [Warning] Slave: Commit failed due to failure of an earlier commit on which this one depends Error_code: 1964 2024-07-01 4:57:25 6 [ERROR] Error running query, slave SQL thread aborted. Fix the problem, and restart the slave SQL thread with "SLAVE START". We stopped at log 'db2-binary.165695' position 184295609 2024-07-01 4:57:25 17 [ERROR] Slave (additional info): Commit failed due to failure of an earlier commit on which this one depends Error_code: 1964 2024-07-01 4:57:25 17 [Warning] Slave: Commit failed due to failure of an earlier commit on which this one depends Error_code: 1964 2024-07-01 4:57:25 17 [ERROR] Error running query, slave SQL thread aborted. Fix the problem, and restart the slave SQL thread with "SLAVE START". We stopped at log 'db2-binary.165695' position 184295609 2024-07-01 4:57:25 14 [ERROR] Slave (additional info): Commit failed due to failure of an earlier commit on which this one depends Error_code: 1964 2024-07-01 4:57:25 14 [Warning] Slave: Commit failed due to failure of an earlier commit on which this one depends Error_code: 1964 2024-07-01 4:57:25 14 [ERROR] Error running query, slave SQL thread aborted. Fix the problem, and restart the slave SQL thread with "SLAVE START". We stopped at log 'db2-binary.165695' position 184295609 2024-07-01 4:57:25 7 [ERROR] Slave (additional info): Commit failed due to failure of an earlier commit on which this one depends Error_code: 1964 2024-07-01 4:57:25 7 [Warning] Slave: Commit failed due to failure of an earlier commit on which this one depends Error_code: 1964 2024-07-01 4:57:25 7 [ERROR] Error running query, slave SQL thread aborted. Fix the problem, and restart the slave SQL thread with "SLAVE START". We stopped at log 'db2-binary.165695' position 184295609 2024-07-01 4:57:25 15 [ERROR] Slave (additional info): Commit failed due to failure of an earlier commit on which this one depends Error_code: 1964 2024-07-01 4:57:25 15 [Warning] Slave: Commit failed due to failure of an earlier commit on which this one depends Error_code: 1964 2024-07-01 4:57:25 15 [ERROR] Error running query, slave SQL thread aborted. Fix the problem, and restart the slave SQL thread with "SLAVE START". We stopped at log 'db2-binary.165695' position 184295609 2024-07-01 4:57:25 8 [ERROR] Slave (additional info): Commit failed due to failure of an earlier commit on which this one depends Error_code: 1964 2024-07-01 4:57:25 8 [Warning] Slave: Commit failed due to failure of an earlier commit on which this one depends Error_code: 1964 2024-07-01 4:57:25 8 [ERROR] Error running query, slave SQL thread aborted. Fix the problem, and restart the slave SQL thread with "SLAVE START". We stopped at log 'db2-binary.165695' position 184295609 2024-07-01 4:57:25 10 [ERROR] Slave (additional info): Commit failed due to failure of an earlier commit on which this one depends Error_code: 1964 2024-07-01 4:57:25 10 [Warning] Slave: Commit failed due to failure of an earlier commit on which this one depends Error_code: 1964 2024-07-01 4:57:25 10 [ERROR] Error running query, slave SQL thread aborted. Fix the problem, and restart the slave SQL thread with "SLAVE START". We stopped at log 'db2-binary.165695' position 184295609 2024-07-01 4:57:25 12 [ERROR] Slave (additional info): Commit failed due to failure of an earlier commit on which this one depends Error_code: 1964 2024-07-01 4:57:25 12 [Warning] Slave: Commit failed due to failure of an earlier commit on which this one depends Error_code: 1964 2024-07-01 4:57:25 12 [ERROR] Error running query, slave SQL thread aborted. Fix the problem, and restart the slave SQL thread with "SLAVE START". We stopped at log 'db2-binary.165695' position 184295609 2024-07-01 4:57:25 9 [ERROR] Slave (additional info): Commit failed due to failure of an earlier commit on which this one depends Error_code: 1964 2024-07-01 4:57:25 9 [Warning] Slave: Commit failed due to failure of an earlier commit on which this one depends Error_code: 1964 2024-07-01 4:57:25 9 [ERROR] Error running query, slave SQL thread aborted. Fix the problem, and restart the slave SQL thread with "SLAVE START". We stopped at log 'db2-binary.165695' position 184295609 2024-07-01 4:57:25 103047 [Note] Slave SQL thread exiting, replication stopped in log 'db2-binary.165695' at position 184295609, master: 10.76.24.77:3306 2024-07-01 4:57:32 103046 [Note] Slave I/O thread exiting, read up to log 'db2-binary.165899', position 20145472, master 10.76.24.77:3306 2024-07-01 4:57:32 103093 [Note] Slave I/O thread: Start asynchronous replication to master 'gtid@10.76.24.77:3306' in log 'db2-binary.165899' at position 20145472 2024-07-01 4:57:32 103094 [Note] Slave SQL thread initialized, starting replication in log 'db2-binary.165695' at position 184295609, relay log './db1-relay.064315' position: 14400303 2024-07-01 4:57:32 103093 [Note] Slave I/O thread: connected to master 'gtid@10.76.24.77:3306',replication started in log 'db2-binary.165899' at position 20145472 2024-07-01 4:57:32 103094 [Note] 'SQL_SLAVE_SKIP_COUNTER=100' executed at relay_log_file='./db1-relay.064315', relay_log_pos='14400303', master_log_name='db2-binary.165695', master_log_pos='184295609' and new position at relay_log_file='./db1-relay.064315', relay_log_pos='14431474', master_log_name='db2-binary.165695', master_log_pos='186325153' 2024-07-01 4:57:34 14 [ERROR] mariadbd: Can't find record in 'activesessions' 2024-07-01 4:57:34 14 [ERROR] Slave SQL: Could not execute Delete_rows_v1 event on table aaadb.activesessions; Can't find record in 'activesessions', Error_code: 1032; handler error HA_ERR_KEY_NOT_FOUND; the event's master log db2-binary.165697, end_log_pos 73284865, Gtid 0-2-18664788434, Internal MariaDB error code: 1032 2024-07-01 4:57:34 14 [Warning] Slave: Can't find record in 'activesessions' Error_code: 1032 2024-07-01 4:57:34 14 [ERROR] Error running query, slave SQL thread aborted. Fix the problem, and restart the slave SQL thread with "SLAVE START". We stopped at log 'db2-binary.165697' position 73284113 2024-07-01 4:57:34 17 [ERROR] Slave (additional info): Commit failed due to failure of an earlier commit on which this one depends Error_code: 1964 2024-07-01 4:57:34 17 [Warning] Slave: Commit failed due to failure of an earlier commit on which this one depends Error_code: 1964 2024-07-01 4:57:34 17 [ERROR] Error running query, slave SQL thread aborted. Fix the problem, and restart the slave SQL thread with "SLAVE START". We stopped at log 'db2-binary.165697' position 73284113 2024-07-01 4:57:34 6 [ERROR] Slave (additional info): Commit failed due to failure of an earlier commit on which this one depends Error_code: 1964 2024-07-01 4:57:34 6 [Warning] Slave: Commit failed due to failure of an earlier commit on which this one depends Error_code: 1964 2024-07-01 4:57:34 6 [ERROR] Error running query, slave SQL thread aborted. Fix the problem, and restart the slave SQL thread with "SLAVE START". We stopped at log 'db2-binary.165697' position 73284113 2024-07-01 4:57:34 16 [ERROR] Slave (additional info): Commit failed due to failure of an earlier commit on which this one depends Error_code: 1964 2024-07-01 4:57:34 16 [Warning] Slave: Commit failed due to failure of an earlier commit on which this one depends Error_code: 1964 2024-07-01 4:57:34 16 [ERROR] Error running query, slave SQL thread aborted. Fix the problem, and restart the slave SQL thread with "SLAVE START". We stopped at log 'db2-binary.165697' position 73284113 2024-07-01 4:57:34 11 [ERROR] Slave (additional info): Commit failed due to failure of an earlier commit on which this one depends Error_code: 1964 2024-07-01 4:57:34 11 [Warning] Slave: Commit failed due to failure of an earlier commit on which this one depends Error_code: 1964 2024-07-01 4:57:34 11 [ERROR] Error running query, slave SQL thread aborted. Fix the problem, and restart the slave SQL thread with "SLAVE START". We stopped at log 'db2-binary.165697' position 73284113 2024-07-01 4:57:34 13 [ERROR] Slave (additional info): Commit failed due to failure of an earlier commit on which this one depends Error_code: 1964 2024-07-01 4:57:34 13 [Warning] Slave: Commit failed due to failure of an earlier commit on which this one depends Error_code: 1964 2024-07-01 4:57:34 13 [ERROR] Error running query, slave SQL thread aborted. Fix the problem, and restart the slave SQL thread with "SLAVE START". We stopped at log 'db2-binary.165697' position 73284113 2024-07-01 4:57:34 9 [ERROR] Slave (additional info): Commit failed due to failure of an earlier commit on which this one depends Error_code: 1964 2024-07-01 4:57:34 9 [Warning] Slave: Commit failed due to failure of an earlier commit on which this one depends Error_code: 1964 2024-07-01 4:57:34 9 [ERROR] Error running query, slave SQL thread aborted. Fix the problem, and restart the slave SQL thread with "SLAVE START". We stopped at log 'db2-binary.165697' position 73284113 2024-07-01 4:57:34 12 [ERROR] Slave (additional info): Commit failed due to failure of an earlier commit on which this one depends Error_code: 1964 2024-07-01 4:57:34 12 [Warning] Slave: Commit failed due to failure of an earlier commit on which this one depends Error_code: 1964 2024-07-01 4:57:34 12 [ERROR] Error running query, slave SQL thread aborted. Fix the problem, and restart the slave SQL thread with "SLAVE START". We stopped at log 'db2-binary.165697' position 73284113 2024-07-01 4:57:34 10 [ERROR] Slave (additional info): Commit failed due to failure of an earlier commit on which this one depends Error_code: 1964 2024-07-01 4:57:34 10 [Warning] Slave: Commit failed due to failure of an earlier commit on which this one depends Error_code: 1964 2024-07-01 4:57:34 10 [ERROR] Error running query, slave SQL thread aborted. Fix the problem, and restart the slave SQL thread with "SLAVE START". We stopped at log 'db2-binary.165697' position 73284113 2024-07-01 4:57:34 8 [ERROR] Slave (additional info): Commit failed due to failure of an earlier commit on which this one depends Error_code: 1964 2024-07-01 4:57:34 8 [Warning] Slave: Commit failed due to failure of an earlier commit on which this one depends Error_code: 1964 2024-07-01 4:57:34 8 [ERROR] Error running query, slave SQL thread aborted. Fix the problem, and restart the slave SQL thread with "SLAVE START". We stopped at log 'db2-binary.165697' position 73284113 2024-07-01 4:57:34 15 [ERROR] Slave (additional info): Commit failed due to failure of an earlier commit on which this one depends Error_code: 1964 2024-07-01 4:57:34 15 [Warning] Slave: Commit failed due to failure of an earlier commit on which this one depends Error_code: 1964 2024-07-01 4:57:34 15 [ERROR] Error running query, slave SQL thread aborted. Fix the problem, and restart the slave SQL thread with "SLAVE START". We stopped at log 'db2-binary.165697' position 73284113 2024-07-01 4:57:34 7 [ERROR] Slave (additional info): Commit failed due to failure of an earlier commit on which this one depends Error_code: 1964 2024-07-01 4:57:34 7 [Warning] Slave: Commit failed due to failure of an earlier commit on which this one depends Error_code: 1964 2024-07-01 4:57:34 7 [ERROR] Error running query, slave SQL thread aborted. Fix the problem, and restart the slave SQL thread with "SLAVE START". We stopped at log 'db2-binary.165697' position 73284113 2024-07-01 4:57:34 103094 [Note] Slave SQL thread exiting, replication stopped in log 'db2-binary.165697' at position 73284113, master: 10.76.24.77:3306 2024-07-01 4:57:50 103093 [Note] Slave I/O thread exiting, read up to log 'db2-binary.165899', position 49284109, master 10.76.24.77:3306 2024-07-01 4:57:50 103342 [Note] Slave I/O thread: Start asynchronous replication to master 'gtid@10.76.24.77:3306' in log 'db2-binary.165899' at position 49284109 2024-07-01 4:57:50 103343 [Note] Slave SQL thread initialized, starting replication in log 'db2-binary.165697' at position 73284113, relay log './db1-relay.064319' position: 5297388 2024-07-01 4:57:50 103342 [Note] Slave I/O thread: connected to master 'gtid@10.76.24.77:3306',replication started in log 'db2-binary.165899' at position 49284109 2024-07-01 4:57:50 103343 [Note] 'SQL_SLAVE_SKIP_COUNTER=100' executed at relay_log_file='./db1-relay.064319', relay_log_pos='5297388', master_log_name='db2-binary.165697', master_log_pos='73284113' and new position at relay_log_file='./db1-relay.064319', relay_log_pos='5330077', master_log_name='db2-binary.165697', master_log_pos='73316802' 2024-07-01 4:57:50 17 [ERROR] mariadbd: Can't find record in 'activesessions' 2024-07-01 4:57:50 17 [ERROR] Slave SQL: Could not execute Delete_rows_v1 event on table aaadb.activesessions; Can't find record in 'activesessions', Error_code: 1032; handler error HA_ERR_KEY_NOT_FOUND; the event's master log db2-binary.165697, end_log_pos 75339624, Gtid 0-2-18664788470, Internal MariaDB error code: 1032 2024-07-01 4:57:50 17 [Warning] Slave: Can't find record in 'activesessions' Error_code: 1032 2024-07-01 4:57:50 17 [ERROR] Error running query, slave SQL thread aborted. Fix the problem, and restart the slave SQL thread with "SLAVE START". We stopped at log 'db2-binary.165697' position 75338875 2024-07-01 4:57:50 14 [ERROR] Slave (additional info): Commit failed due to failure of an earlier commit on which this one depends Error_code: 1964 2024-07-01 4:57:50 14 [Warning] Slave: Commit failed due to failure of an earlier commit on which this one depends Error_code: 1964 2024-07-01 4:57:50 14 [ERROR] Error running query, slave SQL thread aborted. Fix the problem, and restart the slave SQL thread with "SLAVE START". We stopped at log 'db2-binary.165697' position 75338875 2024-07-01 4:57:50 7 [ERROR] Slave (additional info): Commit failed due to failure of an earlier commit on which this one depends Error_code: 1964 2024-07-01 4:57:50 7 [Warning] Slave: Commit failed due to failure of an earlier commit on which this one depends Error_code: 1964 2024-07-01 4:57:50 7 [ERROR] Error running query, slave SQL thread aborted. Fix the problem, and restart the slave SQL thread with "SLAVE START". We stopped at log 'db2-binary.165697' position 75338875 2024-07-01 4:57:50 15 [ERROR] Slave (additional info): Commit failed due to failure of an earlier commit on which this one depends Error_code: 1964 2024-07-01 4:57:50 15 [Warning] Slave: Commit failed due to failure of an earlier commit on which this one depends Error_code: 1964 2024-07-01 4:57:50 15 [ERROR] Error running query, slave SQL thread aborted. Fix the problem, and restart the slave SQL thread with "SLAVE START". We stopped at log 'db2-binary.165697' position 75338875 2024-07-01 4:57:50 8 [ERROR] Slave (additional info): Commit failed due to failure of an earlier commit on which this one depends Error_code: 1964 2024-07-01 4:57:50 8 [Warning] Slave: Commit failed due to failure of an earlier commit on which this one depends Error_code: 1964 2024-07-01 4:57:50 8 [ERROR] Error running query, slave SQL thread aborted. Fix the problem, and restart the slave SQL thread with "SLAVE START". We stopped at log 'db2-binary.165697' position 75338875 2024-07-01 4:57:50 10 [ERROR] Slave (additional info): Commit failed due to failure of an earlier commit on which this one depends Error_code: 1964 2024-07-01 4:57:50 10 [Warning] Slave: Commit failed due to failure of an earlier commit on which this one depends Error_code: 1964 2024-07-01 4:57:50 10 [ERROR] Error running query, slave SQL thread aborted. Fix the problem, and restart the slave SQL thread with "SLAVE START". We stopped at log 'db2-binary.165697' position 75338875 2024-07-01 4:57:50 12 [ERROR] Slave (additional info): Commit failed due to failure of an earlier commit on which this one depends Error_code: 1964 2024-07-01 4:57:50 12 [Warning] Slave: Commit failed due to failure of an earlier commit on which this one depends Error_code: 1964 2024-07-01 4:57:50 12 [ERROR] Error running query, slave SQL thread aborted. Fix the problem, and restart the slave SQL thread with "SLAVE START". We stopped at log 'db2-binary.165697' position 75338875 2024-07-01 4:57:50 9 [ERROR] Slave (additional info): Commit failed due to failure of an earlier commit on which this one depends Error_code: 1964 2024-07-01 4:57:50 9 [Warning] Slave: Commit failed due to failure of an earlier commit on which this one depends Error_code: 1964 2024-07-01 4:57:50 9 [ERROR] Error running query, slave SQL thread aborted. Fix the problem, and restart the slave SQL thread with "SLAVE START". We stopped at log 'db2-binary.165697' position 75338875 2024-07-01 4:57:50 13 [ERROR] Slave (additional info): Commit failed due to failure of an earlier commit on which this one depends Error_code: 1964 2024-07-01 4:57:50 13 [Warning] Slave: Commit failed due to failure of an earlier commit on which this one depends Error_code: 1964 2024-07-01 4:57:50 13 [ERROR] Error running query, slave SQL thread aborted. Fix the problem, and restart the slave SQL thread with "SLAVE START". We stopped at log 'db2-binary.165697' position 75338875 2024-07-01 4:57:50 11 [ERROR] Slave (additional info): Commit failed due to failure of an earlier commit on which this one depends Error_code: 1964 2024-07-01 4:57:50 11 [Warning] Slave: Commit failed due to failure of an earlier commit on which this one depends Error_code: 1964 2024-07-01 4:57:50 11 [ERROR] Error running query, slave SQL thread aborted. Fix the problem, and restart the slave SQL thread with "SLAVE START". We stopped at log 'db2-binary.165697' position 75338875 2024-07-01 4:57:50 16 [ERROR] Slave (additional info): Commit failed due to failure of an earlier commit on which this one depends Error_code: 1964 2024-07-01 4:57:50 16 [Warning] Slave: Commit failed due to failure of an earlier commit on which this one depends Error_code: 1964 2024-07-01 4:57:50 16 [ERROR] Error running query, slave SQL thread aborted. Fix the problem, and restart the slave SQL thread with "SLAVE START". We stopped at log 'db2-binary.165697' position 75338875 2024-07-01 4:57:50 6 [ERROR] Slave (additional info): Commit failed due to failure of an earlier commit on which this one depends Error_code: 1964 2024-07-01 4:57:50 6 [Warning] Slave: Commit failed due to failure of an earlier commit on which this one depends Error_code: 1964 2024-07-01 4:57:50 6 [ERROR] Error running query, slave SQL thread aborted. Fix the problem, and restart the slave SQL thread with "SLAVE START". We stopped at log 'db2-binary.165697' position 75338875 2024-07-01 4:57:50 103343 [Note] Slave SQL thread exiting, replication stopped in log 'db2-binary.165697' at position 75338875, master: 10.76.24.77:3306 2024-07-01 4:57:57 103342 [Note] Slave I/O thread exiting, read up to log 'db2-binary.165899', position 60921646, master 10.76.24.77:3306 2024-07-01 4:57:57 103348 [Note] Slave I/O thread: Start asynchronous replication to master 'gtid@10.76.24.77:3306' in log 'db2-binary.165899' at position 60921646 2024-07-01 4:57:57 103349 [Note] Slave SQL thread initialized, starting replication in log 'db2-binary.165697' at position 75338875, relay log './db1-relay.064319' position: 5353078 2024-07-01 4:57:57 103348 [Note] Slave I/O thread: connected to master 'gtid@10.76.24.77:3306',replication started in log 'db2-binary.165899' at position 60921646 2024-07-01 4:57:57 103349 [Note] 'SQL_SLAVE_SKIP_COUNTER=100' executed at relay_log_file='./db1-relay.064319', relay_log_pos='5353078', master_log_name='db2-binary.165697', master_log_pos='75338875' and new position at relay_log_file='./db1-relay.064319', relay_log_pos='5384650', master_log_name='db2-binary.165697', master_log_pos='75370447' 2024-07-01 4:57:57 17 [ERROR] mariadbd: Can't find record in 'activesessions' 2024-07-01 4:57:57 17 [ERROR] Slave SQL: Could not execute Delete_rows_v1 event on table aaadb.activesessions; Can't find record in 'activesessions', Error_code: 1032; handler error HA_ERR_KEY_NOT_FOUND; the event's master log db2-binary.165697, end_log_pos 90596287, Gtid 0-2-18664789191, Internal MariaDB error code: 1032 2024-07-01 4:57:57 17 [Warning] Slave: Can't find record in 'activesessions' Error_code: 1032 2024-07-01 4:57:57 17 [ERROR] Error running query, slave SQL thread aborted. Fix the problem, and restart the slave SQL thread with "SLAVE START". We stopped at log 'db2-binary.165697' position 90595541 2024-07-01 4:57:57 6 [ERROR] Slave (additional info): Commit failed due to failure of an earlier commit on which this one depends Error_code: 1964 2024-07-01 4:57:57 6 [Warning] Slave: Commit failed due to failure of an earlier commit on which this one depends Error_code: 1964 2024-07-01 4:57:57 6 [ERROR] Error running query, slave SQL thread aborted. Fix the problem, and restart the slave SQL thread with "SLAVE START". We stopped at log 'db2-binary.165697' position 90595541 2024-07-01 4:57:57 16 [ERROR] Slave (additional info): Commit failed due to failure of an earlier commit on which this one depends Error_code: 1964 2024-07-01 4:57:57 16 [Warning] Slave: Commit failed due to failure of an earlier commit on which this one depends Error_code: 1964 2024-07-01 4:57:57 16 [ERROR] Error running query, slave SQL thread aborted. Fix the problem, and restart the slave SQL thread with "SLAVE START". We stopped at log 'db2-binary.165697' position 90595541 2024-07-01 4:57:57 11 [ERROR] Slave (additional info): Commit failed due to failure of an earlier commit on which this one depends Error_code: 1964 2024-07-01 4:57:57 11 [Warning] Slave: Commit failed due to failure of an earlier commit on which this one depends Error_code: 1964 2024-07-01 4:57:57 11 [ERROR] Error running query, slave SQL thread aborted. Fix the problem, and restart the slave SQL thread with "SLAVE START". We stopped at log 'db2-binary.165697' position 90595541 2024-07-01 4:57:57 13 [ERROR] Slave (additional info): Commit failed due to failure of an earlier commit on which this one depends Error_code: 1964 2024-07-01 4:57:57 13 [Warning] Slave: Commit failed due to failure of an earlier commit on which this one depends Error_code: 1964 2024-07-01 4:57:57 13 [ERROR] Error running query, slave SQL thread aborted. Fix the problem, and restart the slave SQL thread with "SLAVE START". We stopped at log 'db2-binary.165697' position 90595541 2024-07-01 4:57:57 9 [ERROR] Slave (additional info): Commit failed due to failure of an earlier commit on which this one depends Error_code: 1964 2024-07-01 4:57:57 9 [Warning] Slave: Commit failed due to failure of an earlier commit on which this one depends Error_code: 1964 2024-07-01 4:57:57 9 [ERROR] Error running query, slave SQL thread aborted. Fix the problem, and restart the slave SQL thread with "SLAVE START". We stopped at log 'db2-binary.165697' position 90595541 2024-07-01 4:57:57 12 [ERROR] Slave (additional info): Commit failed due to failure of an earlier commit on which this one depends Error_code: 1964 2024-07-01 4:57:57 12 [Warning] Slave: Commit failed due to failure of an earlier commit on which this one depends Error_code: 1964 2024-07-01 4:57:57 12 [ERROR] Error running query, slave SQL thread aborted. Fix the problem, and restart the slave SQL thread with "SLAVE START". We stopped at log 'db2-binary.165697' position 90595541 2024-07-01 4:57:57 10 [ERROR] Slave (additional info): Commit failed due to failure of an earlier commit on which this one depends Error_code: 1964 2024-07-01 4:57:57 10 [Warning] Slave: Commit failed due to failure of an earlier commit on which this one depends Error_code: 1964 2024-07-01 4:57:57 10 [ERROR] Error running query, slave SQL thread aborted. Fix the problem, and restart the slave SQL thread with "SLAVE START". We stopped at log 'db2-binary.165697' position 90595541 2024-07-01 4:57:57 8 [ERROR] Slave (additional info): Commit failed due to failure of an earlier commit on which this one depends Error_code: 1964 2024-07-01 4:57:57 8 [Warning] Slave: Commit failed due to failure of an earlier commit on which this one depends Error_code: 1964 2024-07-01 4:57:57 8 [ERROR] Error running query, slave SQL thread aborted. Fix the problem, and restart the slave SQL thread with "SLAVE START". We stopped at log 'db2-binary.165697' position 90595541 2024-07-01 4:57:57 15 [ERROR] Slave (additional info): Commit failed due to failure of an earlier commit on which this one depends Error_code: 1964 2024-07-01 4:57:57 15 [Warning] Slave: Commit failed due to failure of an earlier commit on which this one depends Error_code: 1964 2024-07-01 4:57:57 15 [ERROR] Error running query, slave SQL thread aborted. Fix the problem, and restart the slave SQL thread with "SLAVE START". We stopped at log 'db2-binary.165697' position 90595541 2024-07-01 4:57:57 7 [ERROR] Slave (additional info): Commit failed due to failure of an earlier commit on which this one depends Error_code: 1964 2024-07-01 4:57:57 7 [Warning] Slave: Commit failed due to failure of an earlier commit on which this one depends Error_code: 1964 2024-07-01 4:57:57 7 [ERROR] Error running query, slave SQL thread aborted. Fix the problem, and restart the slave SQL thread with "SLAVE START". We stopped at log 'db2-binary.165697' position 90595541 2024-07-01 4:57:57 14 [ERROR] Slave (additional info): Commit failed due to failure of an earlier commit on which this one depends Error_code: 1964 2024-07-01 4:57:57 14 [Warning] Slave: Commit failed due to failure of an earlier commit on which this one depends Error_code: 1964 2024-07-01 4:57:57 14 [ERROR] Error running query, slave SQL thread aborted. Fix the problem, and restart the slave SQL thread with "SLAVE START". We stopped at log 'db2-binary.165697' position 90595541 2024-07-01 4:57:57 8 [ERROR] Slave (additional info): Commit failed due to failure of an earlier commit on which this one depends Error_code: 1964 2024-07-01 4:57:57 8 [Warning] Slave: Commit failed due to failure of an earlier commit on which this one depends Error_code: 1964 2024-07-01 4:57:57 8 [Warning] Slave: Commit failed due to failure of an earlier commit on which this one depends Error_code: 1964 2024-07-01 4:57:57 8 [Warning] Slave: Commit failed due to failure of an earlier commit on which this one depends Error_code: 1964 2024-07-01 4:57:57 8 [Warning] Slave: Commit failed due to failure of an earlier commit on which this one depends Error_code: 1964 2024-07-01 4:57:57 8 [Warning] Slave: Commit failed due to failure of an earlier commit on which this one depends Error_code: 1964 2024-07-01 4:57:57 8 [Warning] Slave: Commit failed due to failure of an earlier commit on which this one depends Error_code: 1964 2024-07-01 4:57:57 8 [Warning] Slave: Commit failed due to failure of an earlier commit on which this one depends Error_code: 1964 2024-07-01 4:57:57 8 [Warning] Slave: Commit failed due to failure of an earlier commit on which this one depends Error_code: 1964 2024-07-01 4:57:57 8 [Warning] Slave: Commit failed due to failure of an earlier commit on which this one depends Error_code: 1964 2024-07-01 4:57:57 8 [Warning] Slave: Commit failed due to failure of an earlier commit on which this one depends Error_code: 1964 2024-07-01 4:57:57 8 [Warning] Slave: Commit failed due to failure of an earlier commit on which this one depends Error_code: 1964 2024-07-01 4:57:57 8 [Warning] Slave: Commit failed due to failure of an earlier commit on which this one depends Error_code: 1964 2024-07-01 4:57:57 8 [Warning] Slave: Commit failed due to failure of an earlier commit on which this one depends Error_code: 1964 2024-07-01 4:57:57 8 [Warning] Slave: Commit failed due to failure of an earlier commit on which this one depends Error_code: 1964 2024-07-01 4:57:57 8 [Warning] Slave: Commit failed due to failure of an earlier commit on which this one depends Error_code: 1964 2024-07-01 4:57:57 8 [Warning] Slave: Commit failed due to failure of an earlier commit on which this one depends Error_code: 1964 2024-07-01 4:57:57 8 [Warning] Slave: Commit failed due to failure of an earlier commit on which this one depends Error_code: 1964 2024-07-01 4:57:57 8 [Warning] Slave: Commit failed due to failure of an earlier commit on which this one depends Error_code: 1964 2024-07-01 4:57:57 8 [Warning] Slave: Commit failed due to failure of an earlier commit on which this one depends Error_code: 1964 2024-07-01 4:57:57 8 [Warning] Slave: Commit failed due to failure of an earlier commit on which this one depends Error_code: 1964 2024-07-01 4:57:57 8 [Warning] Slave: Commit failed due to failure of an earlier commit on which this one depends Error_code: 1964 2024-07-01 4:57:57 8 [Warning] Slave: Commit failed due to failure of an earlier commit on which this one depends Error_code: 1964 2024-07-01 4:57:57 8 [Warning] Slave: Commit failed due to failure of an earlier commit on which this one depends Error_code: 1964 2024-07-01 4:57:57 8 [Warning] Slave: Commit failed due to failure of an earlier commit on which this one depends Error_code: 1964 2024-07-01 4:57:57 8 [Warning] Slave: Commit failed due to failure of an earlier commit on which this one depends Error_code: 1964 2024-07-01 4:57:57 8 [Warning] Slave: Commit failed due to failure of an earlier commit on which this one depends Error_code: 1964 2024-07-01 4:57:57 8 [Warning] Slave: Commit failed due to failure of an earlier commit on which this one depends Error_code: 1964 2024-07-01 4:57:57 8 [Warning] Slave: Commit failed due to failure of an earlier commit on which this one depends Error_code: 1964 2024-07-01 4:57:57 8 [Warning] Slave: Commit failed due to failure of an earlier commit on which this one depends Error_code: 1964 2024-07-01 4:57:57 8 [Warning] Slave: Commit failed due to failure of an earlier commit on which this one depends Error_code: 1964 2024-07-01 4:57:57 8 [Warning] Slave: Commit failed due to failure of an earlier commit on which this one depends Error_code: 1964 2024-07-01 4:57:57 8 [Warning] Slave: Commit failed due to failure of an earlier commit on which this one depends Error_code: 1964 2024-07-01 4:57:57 8 [Warning] Slave: Commit failed due to failure of an earlier commit on which this one depends Error_code: 1964 2024-07-01 4:57:57 8 [Warning] Slave: Commit failed due to failure of an earlier commit on which this one depends Error_code: 1964 2024-07-01 4:57:57 8 [Warning] Slave: Commit failed due to failure of an earlier commit on which this one depends Error_code: 1964 2024-07-01 4:57:57 8 [Warning] Slave: Commit failed due to failure of an earlier commit on which this one depends Error_code: 1964 2024-07-01 4:57:57 8 [Warning] Slave: Commit failed due to failure of an earlier commit on which this one depends Error_code: 1964 2024-07-01 4:57:57 8 [Warning] Slave: Commit failed due to failure of an earlier commit on which this one depends Error_code: 1964 2024-07-01 4:57:57 8 [Warning] Slave: Commit failed due to failure of an earlier commit on which this one depends Error_code: 1964 2024-07-01 4:57:57 8 [Warning] Slave: Commit failed due to failure of an earlier commit on which this one depends Error_code: 1964 2024-07-01 4:57:57 8 [Warning] Slave: Commit failed due to failure of an earlier commit on which this one depends Error_code: 1964 2024-07-01 4:57:57 8 [Warning] Slave: Commit failed due to failure of an earlier commit on which this one depends Error_code: 1964 2024-07-01 4:57:57 8 [Warning] Slave: Commit failed due to failure of an earlier commit on which this one depends Error_code: 1964 2024-07-01 4:57:57 8 [Warning] Slave: Commit failed due to failure of an earlier commit on which this one depends Error_code: 1964 2024-07-01 4:57:57 8 [Warning] Slave: Commit failed due to failure of an earlier commit on which this one depends Error_code: 1964 2024-07-01 4:57:57 8 [Warning] Slave: Commit failed due to failure of an earlier commit on which this one depends Error_code: 1964 2024-07-01 4:57:57 8 [Warning] Slave: Commit failed due to failure of an earlier commit on which this one depends Error_code: 1964 2024-07-01 4:57:57 8 [Warning] Slave: Commit failed due to failure of an earlier commit on which this one depends Error_code: 1964 2024-07-01 4:57:57 8 [Warning] Slave: Commit failed due to failure of an earlier commit on which this one depends Error_code: 1964 2024-07-01 4:57:57 8 [Warning] Slave: Commit failed due to failure of an earlier commit on which this one depends Error_code: 1964 2024-07-01 4:57:57 8 [Warning] Slave: Commit failed due to failure of an earlier commit on which this one depends Error_code: 1964 2024-07-01 4:57:57 8 [Warning] Slave: Commit failed due to failure of an earlier commit on which this one depends Error_code: 1964 2024-07-01 4:57:57 8 [Warning] Slave: Commit failed due to failure of an earlier commit on which this one depends Error_code: 1964 2024-07-01 4:57:57 8 [Warning] Slave: Commit failed due to failure of an earlier commit on which this one depends Error_code: 1964 2024-07-01 4:57:57 8 [Warning] Slave: Commit failed due to failure of an earlier commit on which this one depends Error_code: 1964 2024-07-01 4:57:57 8 [Warning] Slave: Commit failed due to failure of an earlier commit on which this one depends Error_code: 1964 2024-07-01 4:57:57 8 [Warning] Slave: Commit failed due to failure of an earlier commit on which this one depends Error_code: 1964 2024-07-01 4:57:57 8 [Warning] Slave: Commit failed due to failure of an earlier commit on which this one depends Error_code: 1964 2024-07-01 4:57:57 8 [Warning] Slave: Commit failed due to failure of an earlier commit on which this one depends Error_code: 1964 2024-07-01 4:57:57 8 [Warning] Slave: Commit failed due to failure of an earlier commit on which this one depends Error_code: 1964 2024-07-01 4:57:57 8 [Warning] Slave: Commit failed due to failure of an earlier commit on which this one depends Error_code: 1964 2024-07-01 4:57:57 8 [Warning] Slave: Commit failed due to failure of an earlier commit on which this one depends Error_code: 1964 2024-07-01 4:57:57 8 [Warning] Slave: Commit failed due to failure of an earlier commit on which this one depends Error_code: 1964 2024-07-01 4:57:57 8 [Warning] Slave: Commit failed due to failure of an earlier commit on which this one depends Error_code: 1964 2024-07-01 4:57:57 8 [ERROR] Error running query, slave SQL thread aborted. Fix the problem, and restart the slave SQL thread with "SLAVE START". We stopped at log 'db2-binary.165697' position 90595541 2024-07-01 4:57:57 103349 [Note] Slave SQL thread exiting, replication stopped in log 'db2-binary.165697' at position 90595541, master: 10.76.24.77:3306 2024-07-01 4:58:02 103348 [Note] Slave I/O thread exiting, read up to log 'db2-binary.165899', position 70739434, master 10.76.24.77:3306 2024-07-01 4:58:02 103368 [Note] Slave I/O thread: Start asynchronous replication to master 'gtid@10.76.24.77:3306' in log 'db2-binary.165899' at position 70739434 2024-07-01 4:58:02 103369 [Note] Slave SQL thread initialized, starting replication in log 'db2-binary.165697' at position 90595541, relay log './db1-relay.064319' position: 6614683 2024-07-01 4:58:02 103368 [Note] Slave I/O thread: connected to master 'gtid@10.76.24.77:3306',replication started in log 'db2-binary.165899' at position 70739434 2024-07-01 4:58:02 103369 [Note] 'SQL_SLAVE_SKIP_COUNTER=100' executed at relay_log_file='./db1-relay.064319', relay_log_pos='6614683', master_log_name='db2-binary.165697', master_log_pos='90595541' and new position at relay_log_file='./db1-relay.064319', relay_log_pos='6647550', master_log_name='db2-binary.165697', master_log_pos='90628408' 2024-07-01 4:58:03 9 [ERROR] mariadbd: Can't find record in 'activesessions' 2024-07-01 4:58:03 9 [ERROR] Slave SQL: Could not execute Delete_rows_v1 event on table aaadb.activesessions; Can't find record in 'activesessions', Error_code: 1032; handler error HA_ERR_KEY_NOT_FOUND; the event's master log db2-binary.165697, end_log_pos 202330979, Gtid 0-2-18664793706, Internal MariaDB error code: 1032 2024-07-01 4:58:03 9 [Warning] Slave: Can't find record in 'activesessions' Error_code: 1032 2024-07-01 4:58:03 9 [ERROR] Error running query, slave SQL thread aborted. Fix the problem, and restart the slave SQL thread with "SLAVE START". We stopped at log 'db2-binary.165697' position 202330221 2024-07-01 4:58:03 13 [ERROR] Slave (additional info): Commit failed due to failure of an earlier commit on which this one depends Error_code: 1964 2024-07-01 4:58:03 13 [Warning] Slave: Commit failed due to failure of an earlier commit on which this one depends Error_code: 1964 2024-07-01 4:58:03 13 [ERROR] Error running query, slave SQL thread aborted. Fix the problem, and restart the slave SQL thread with "SLAVE START". We stopped at log 'db2-binary.165697' position 202330221 2024-07-01 4:58:03 11 [ERROR] Slave (additional info): Commit failed due to failure of an earlier commit on which this one depends Error_code: 1964 2024-07-01 4:58:03 11 [Warning] Slave: Commit failed due to failure of an earlier commit on which this one depends Error_code: 1964 2024-07-01 4:58:03 11 [ERROR] Error running query, slave SQL thread aborted. Fix the problem, and restart the slave SQL thread with "SLAVE START". We stopped at log 'db2-binary.165697' position 202330221 2024-07-01 4:58:03 16 [ERROR] Slave (additional info): Commit failed due to failure of an earlier commit on which this one depends Error_code: 1964 2024-07-01 4:58:03 16 [Warning] Slave: Commit failed due to failure of an earlier commit on which this one depends Error_code: 1964 2024-07-01 4:58:03 16 [ERROR] Error running query, slave SQL thread aborted. Fix the problem, and restart the slave SQL thread with "SLAVE START". We stopped at log 'db2-binary.165697' position 202330221 2024-07-01 4:58:03 6 [ERROR] Slave (additional info): Commit failed due to failure of an earlier commit on which this one depends Error_code: 1964 2024-07-01 4:58:03 6 [Warning] Slave: Commit failed due to failure of an earlier commit on which this one depends Error_code: 1964 2024-07-01 4:58:03 6 [ERROR] Error running query, slave SQL thread aborted. Fix the problem, and restart the slave SQL thread with "SLAVE START". We stopped at log 'db2-binary.165697' position 202330221 2024-07-01 4:58:03 17 [ERROR] Slave (additional info): Commit failed due to failure of an earlier commit on which this one depends Error_code: 1964 2024-07-01 4:58:03 17 [Warning] Slave: Commit failed due to failure of an earlier commit on which this one depends Error_code: 1964 2024-07-01 4:58:03 17 [ERROR] Error running query, slave SQL thread aborted. Fix the problem, and restart the slave SQL thread with "SLAVE START". We stopped at log 'db2-binary.165697' position 202330221 2024-07-01 4:58:03 14 [ERROR] Slave (additional info): Commit failed due to failure of an earlier commit on which this one depends Error_code: 1964 2024-07-01 4:58:03 14 [Warning] Slave: Commit failed due to failure of an earlier commit on which this one depends Error_code: 1964 2024-07-01 4:58:03 14 [ERROR] Error running query, slave SQL thread aborted. Fix the problem, and restart the slave SQL thread with "SLAVE START". We stopped at log 'db2-binary.165697' position 202330221 2024-07-01 4:58:03 7 [ERROR] Slave (additional info): Commit failed due to failure of an earlier commit on which this one depends Error_code: 1964 2024-07-01 4:58:03 7 [Warning] Slave: Commit failed due to failure of an earlier commit on which this one depends Error_code: 1964 2024-07-01 4:58:03 7 [ERROR] Error running query, slave SQL thread aborted. Fix the problem, and restart the slave SQL thread with "SLAVE START". We stopped at log 'db2-binary.165697' position 202330221 2024-07-01 4:58:03 15 [ERROR] Slave (additional info): Commit failed due to failure of an earlier commit on which this one depends Error_code: 1964 2024-07-01 4:58:03 15 [Warning] Slave: Commit failed due to failure of an earlier commit on which this one depends Error_code: 1964 2024-07-01 4:58:03 15 [ERROR] Error running query, slave SQL thread aborted. Fix the problem, and restart the slave SQL thread with "SLAVE START". We stopped at log 'db2-binary.165697' position 202330221 2024-07-01 4:58:03 8 [ERROR] Slave (additional info): Commit failed due to failure of an earlier commit on which this one depends Error_code: 1964 2024-07-01 4:58:03 8 [Warning] Slave: Commit failed due to failure of an earlier commit on which this one depends Error_code: 1964 2024-07-01 4:58:03 8 [ERROR] Error running query, slave SQL thread aborted. Fix the problem, and restart the slave SQL thread with "SLAVE START". We stopped at log 'db2-binary.165697' position 202330221 2024-07-01 4:58:03 10 [ERROR] Slave (additional info): Commit failed due to failure of an earlier commit on which this one depends Error_code: 1964 2024-07-01 4:58:03 10 [Warning] Slave: Commit failed due to failure of an earlier commit on which this one depends Error_code: 1964 2024-07-01 4:58:03 10 [ERROR] Error running query, slave SQL thread aborted. Fix the problem, and restart the slave SQL thread with "SLAVE START". We stopped at log 'db2-binary.165697' position 202330221 2024-07-01 4:58:03 12 [ERROR] Slave (additional info): Commit failed due to failure of an earlier commit on which this one depends Error_code: 1964 2024-07-01 4:58:03 12 [Warning] Slave: Commit failed due to failure of an earlier commit on which this one depends Error_code: 1964 2024-07-01 4:58:03 12 [ERROR] Error running query, slave SQL thread aborted. Fix the problem, and restart the slave SQL thread with "SLAVE START". We stopped at log 'db2-binary.165697' position 202330221 2024-07-01 4:58:03 103369 [Note] Slave SQL thread exiting, replication stopped in log 'db2-binary.165697' at position 202330221, master: 10.76.24.77:3306 2024-07-01 4:58:09 103368 [Note] Slave I/O thread exiting, read up to log 'db2-binary.165899', position 82357220, master 10.76.24.77:3306 2024-07-01 4:58:09 103462 [Note] Slave I/O thread: Start asynchronous replication to master 'gtid@10.76.24.77:3306' in log 'db2-binary.165899' at position 82357220 2024-07-01 4:58:09 103463 [Note] Slave SQL thread initialized, starting replication in log 'db2-binary.165697' at position 202330221, relay log './db1-relay.064319' position: 14391346 2024-07-01 4:58:09 103462 [Note] Slave I/O thread: connected to master 'gtid@10.76.24.77:3306',replication started in log 'db2-binary.165899' at position 82357220 2024-07-01 4:58:09 103463 [Note] 'SQL_SLAVE_SKIP_COUNTER=100' executed at relay_log_file='./db1-relay.064319', relay_log_pos='14391346', master_log_name='db2-binary.165697', master_log_pos='202330221' and new position at relay_log_file='./db1-relay.064319', relay_log_pos='14420694', master_log_name='db2-binary.165697', master_log_pos='202359569' 2024-07-01 4:58:09 16 [ERROR] mariadbd: Can't find record in 'activesessions' 2024-07-01 4:58:09 16 [ERROR] Slave SQL: Could not execute Delete_rows_v1 event on table aaadb.activesessions; Can't find record in 'activesessions', Error_code: 1032; handler error HA_ERR_KEY_NOT_FOUND; the event's master log db2-binary.165698, end_log_pos 62959500, Gtid 0-2-18664796808, Internal MariaDB error code: 1032 2024-07-01 4:58:09 16 [Warning] Slave: Can't find record in 'activesessions' Error_code: 1032 2024-07-01 4:58:09 16 [ERROR] Error running query, slave SQL thread aborted. Fix the problem, and restart the slave SQL thread with "SLAVE START". We stopped at log 'db2-binary.165698' position 62958743 2024-07-01 4:58:09 11 [ERROR] Slave (additional info): Commit failed due to failure of an earlier commit on which this one depends Error_code: 1964 2024-07-01 4:58:09 11 [Warning] Slave: Commit failed due to failure of an earlier commit on which this one depends Error_code: 1964 2024-07-01 4:58:09 11 [ERROR] Error running query, slave SQL thread aborted. Fix the problem, and restart the slave SQL thread with "SLAVE START". We stopped at log 'db2-binary.165698' position 62958743 2024-07-01 4:58:09 13 [ERROR] Slave (additional info): Commit failed due to failure of an earlier commit on which this one depends Error_code: 1964 2024-07-01 4:58:09 13 [Warning] Slave: Commit failed due to failure of an earlier commit on which this one depends Error_code: 1964 2024-07-01 4:58:09 13 [ERROR] Error running query, slave SQL thread aborted. Fix the problem, and restart the slave SQL thread with "SLAVE START". We stopped at log 'db2-binary.165698' position 62958743 2024-07-01 4:58:09 9 [ERROR] Slave (additional info): Commit failed due to failure of an earlier commit on which this one depends Error_code: 1964 2024-07-01 4:58:09 9 [Warning] Slave: Commit failed due to failure of an earlier commit on which this one depends Error_code: 1964 2024-07-01 4:58:09 9 [ERROR] Error running query, slave SQL thread aborted. Fix the problem, and restart the slave SQL thread with "SLAVE START". We stopped at log 'db2-binary.165698' position 62958743 2024-07-01 4:58:09 12 [ERROR] Slave (additional info): Commit failed due to failure of an earlier commit on which this one depends Error_code: 1964 2024-07-01 4:58:09 12 [Warning] Slave: Commit failed due to failure of an earlier commit on which this one depends Error_code: 1964 2024-07-01 4:58:09 12 [ERROR] Error running query, slave SQL thread aborted. Fix the problem, and restart the slave SQL thread with "SLAVE START". We stopped at log 'db2-binary.165698' position 62958743 2024-07-01 4:58:09 10 [ERROR] Slave (additional info): Commit failed due to failure of an earlier commit on which this one depends Error_code: 1964 2024-07-01 4:58:09 10 [Warning] Slave: Commit failed due to failure of an earlier commit on which this one depends Error_code: 1964 2024-07-01 4:58:09 10 [ERROR] Error running query, slave SQL thread aborted. Fix the problem, and restart the slave SQL thread with "SLAVE START". We stopped at log 'db2-binary.165698' position 62958743 2024-07-01 4:58:09 8 [ERROR] Slave (additional info): Commit failed due to failure of an earlier commit on which this one depends Error_code: 1964 2024-07-01 4:58:09 8 [Warning] Slave: Commit failed due to failure of an earlier commit on which this one depends Error_code: 1964 2024-07-01 4:58:09 8 [ERROR] Error running query, slave SQL thread aborted. Fix the problem, and restart the slave SQL thread with "SLAVE START". We stopped at log 'db2-binary.165698' position 62958743 2024-07-01 4:58:09 15 [ERROR] Slave (additional info): Commit failed due to failure of an earlier commit on which this one depends Error_code: 1964 2024-07-01 4:58:09 15 [Warning] Slave: Commit failed due to failure of an earlier commit on which this one depends Error_code: 1964 2024-07-01 4:58:09 15 [ERROR] Error running query, slave SQL thread aborted. Fix the problem, and restart the slave SQL thread with "SLAVE START". We stopped at log 'db2-binary.165698' position 62958743 2024-07-01 4:58:09 7 [ERROR] Slave (additional info): Commit failed due to failure of an earlier commit on which this one depends Error_code: 1964 2024-07-01 4:58:09 7 [Warning] Slave: Commit failed due to failure of an earlier commit on which this one depends Error_code: 1964 2024-07-01 4:58:09 7 [ERROR] Error running query, slave SQL thread aborted. Fix the problem, and restart the slave SQL thread with "SLAVE START". We stopped at log 'db2-binary.165698' position 62958743 2024-07-01 4:58:09 14 [ERROR] Slave (additional info): Commit failed due to failure of an earlier commit on which this one depends Error_code: 1964 2024-07-01 4:58:09 14 [Warning] Slave: Commit failed due to failure of an earlier commit on which this one depends Error_code: 1964 2024-07-01 4:58:09 14 [ERROR] Error running query, slave SQL thread aborted. Fix the problem, and restart the slave SQL thread with "SLAVE START". We stopped at log 'db2-binary.165698' position 62958743 2024-07-01 4:58:09 17 [ERROR] Slave (additional info): Commit failed due to failure of an earlier commit on which this one depends Error_code: 1964 2024-07-01 4:58:09 17 [Warning] Slave: Commit failed due to failure of an earlier commit on which this one depends Error_code: 1964 2024-07-01 4:58:09 17 [ERROR] Error running query, slave SQL thread aborted. Fix the problem, and restart the slave SQL thread with "SLAVE START". We stopped at log 'db2-binary.165698' position 62958743 2024-07-01 4:58:09 6 [ERROR] Slave (additional info): Commit failed due to failure of an earlier commit on which this one depends Error_code: 1964 2024-07-01 4:58:09 6 [Warning] Slave: Commit failed due to failure of an earlier commit on which this one depends Error_code: 1964 2024-07-01 4:58:09 6 [ERROR] Error running query, slave SQL thread aborted. Fix the problem, and restart the slave SQL thread with "SLAVE START". We stopped at log 'db2-binary.165698' position 62958743 2024-07-01 4:58:09 103463 [Note] Slave SQL thread exiting, replication stopped in log 'db2-binary.165698' at position 62958743, master: 10.76.24.77:3306 2024-07-01 4:58:16 103462 [Note] Slave I/O thread exiting, read up to log 'db2-binary.165899', position 93707005, master 10.76.24.77:3306 2024-07-01 4:58:16 103530 [Note] Slave I/O thread: Start asynchronous replication to master 'gtid@10.76.24.77:3306' in log 'db2-binary.165899' at position 93707005 2024-07-01 4:58:16 103531 [Note] Slave SQL thread initialized, starting replication in log 'db2-binary.165698' at position 62958743, relay log './db1-relay.064321' position: 4975273 2024-07-01 4:58:16 103530 [Note] Slave I/O thread: connected to master 'gtid@10.76.24.77:3306',replication started in log 'db2-binary.165899' at position 93707005 2024-07-01 4:58:16 103531 [Note] 'SQL_SLAVE_SKIP_COUNTER=100' executed at relay_log_file='./db1-relay.064321', relay_log_pos='4975273', master_log_name='db2-binary.165698', master_log_pos='62958743' and new position at relay_log_file='./db1-relay.064321', relay_log_pos='5007425', master_log_name='db2-binary.165698', master_log_pos='64990289' 2024-07-01 4:58:20 10 [ERROR] mariadbd: Can't find record in 'activesessions' 2024-07-01 4:58:20 10 [ERROR] Slave SQL: Could not execute Delete_rows_v1 event on table aaadb.activesessions; Can't find record in 'activesessions', Error_code: 1032; handler error HA_ERR_KEY_NOT_FOUND; the event's master log db2-binary.165702, end_log_pos 193312719, Gtid 0-2-18664829675, Internal MariaDB error code: 1032 2024-07-01 4:58:20 10 [Warning] Slave: Can't find record in 'activesessions' Error_code: 1032 2024-07-01 4:58:20 10 [ERROR] Error running query, slave SQL thread aborted. Fix the problem, and restart the slave SQL thread with "SLAVE START". We stopped at log 'db2-binary.165702' position 193311970 2024-07-01 4:58:20 12 [ERROR] Slave (additional info): Commit failed due to failure of an earlier commit on which this one depends Error_code: 1964 2024-07-01 4:58:20 12 [Warning] Slave: Commit failed due to failure of an earlier commit on which this one depends Error_code: 1964 2024-07-01 4:58:20 12 [ERROR] Error running query, slave SQL thread aborted. Fix the problem, and restart the slave SQL thread with "SLAVE START". We stopped at log 'db2-binary.165702' position 193311970 2024-07-01 4:58:20 9 [ERROR] Slave (additional info): Commit failed due to failure of an earlier commit on which this one depends Error_code: 1964 2024-07-01 4:58:20 9 [Warning] Slave: Commit failed due to failure of an earlier commit on which this one depends Error_code: 1964 2024-07-01 4:58:20 9 [ERROR] Error running query, slave SQL thread aborted. Fix the problem, and restart the slave SQL thread with "SLAVE START". We stopped at log 'db2-binary.165702' position 193311970 2024-07-01 4:58:20 13 [ERROR] Slave (additional info): Commit failed due to failure of an earlier commit on which this one depends Error_code: 1964 2024-07-01 4:58:20 13 [Warning] Slave: Commit failed due to failure of an earlier commit on which this one depends Error_code: 1964 2024-07-01 4:58:20 13 [ERROR] Error running query, slave SQL thread aborted. Fix the problem, and restart the slave SQL thread with "SLAVE START". We stopped at log 'db2-binary.165702' position 193311970 2024-07-01 4:58:20 11 [ERROR] Slave (additional info): Commit failed due to failure of an earlier commit on which this one depends Error_code: 1964 2024-07-01 4:58:20 11 [Warning] Slave: Commit failed due to failure of an earlier commit on which this one depends Error_code: 1964 2024-07-01 4:58:20 11 [ERROR] Error running query, slave SQL thread aborted. Fix the problem, and restart the slave SQL thread with "SLAVE START". We stopped at log 'db2-binary.165702' position 193311970 2024-07-01 4:58:20 16 [ERROR] Slave (additional info): Commit failed due to failure of an earlier commit on which this one depends Error_code: 1964 2024-07-01 4:58:20 16 [Warning] Slave: Commit failed due to failure of an earlier commit on which this one depends Error_code: 1964 2024-07-01 4:58:20 16 [ERROR] Error running query, slave SQL thread aborted. Fix the problem, and restart the slave SQL thread with "SLAVE START". We stopped at log 'db2-binary.165702' position 193311970 2024-07-01 4:58:20 6 [ERROR] Slave (additional info): Commit failed due to failure of an earlier commit on which this one depends Error_code: 1964 2024-07-01 4:58:20 6 [Warning] Slave: Commit failed due to failure of an earlier commit on which this one depends Error_code: 1964 2024-07-01 4:58:20 6 [ERROR] Error running query, slave SQL thread aborted. Fix the problem, and restart the slave SQL thread with "SLAVE START". We stopped at log 'db2-binary.165702' position 193311970 2024-07-01 4:58:20 17 [ERROR] Slave (additional info): Commit failed due to failure of an earlier commit on which this one depends Error_code: 1964 2024-07-01 4:58:20 17 [Warning] Slave: Commit failed due to failure of an earlier commit on which this one depends Error_code: 1964 2024-07-01 4:58:20 17 [ERROR] Error running query, slave SQL thread aborted. Fix the problem, and restart the slave SQL thread with "SLAVE START". We stopped at log 'db2-binary.165702' position 193311970 2024-07-01 4:58:20 14 [ERROR] Slave (additional info): Commit failed due to failure of an earlier commit on which this one depends Error_code: 1964 2024-07-01 4:58:20 14 [Warning] Slave: Commit failed due to failure of an earlier commit on which this one depends Error_code: 1964 2024-07-01 4:58:20 14 [ERROR] Error running query, slave SQL thread aborted. Fix the problem, and restart the slave SQL thread with "SLAVE START". We stopped at log 'db2-binary.165702' position 193311970 2024-07-01 4:58:20 7 [ERROR] Slave (additional info): Commit failed due to failure of an earlier commit on which this one depends Error_code: 1964 2024-07-01 4:58:20 7 [Warning] Slave: Commit failed due to failure of an earlier commit on which this one depends Error_code: 1964 2024-07-01 4:58:20 7 [ERROR] Error running query, slave SQL thread aborted. Fix the problem, and restart the slave SQL thread with "SLAVE START". We stopped at log 'db2-binary.165702' position 193311970 2024-07-01 4:58:20 15 [ERROR] Slave (additional info): Commit failed due to failure of an earlier commit on which this one depends Error_code: 1964 2024-07-01 4:58:20 15 [Warning] Slave: Commit failed due to failure of an earlier commit on which this one depends Error_code: 1964 2024-07-01 4:58:20 15 [ERROR] Error running query, slave SQL thread aborted. Fix the problem, and restart the slave SQL thread with "SLAVE START". We stopped at log 'db2-binary.165702' position 193311970 2024-07-01 4:58:20 8 [ERROR] Slave (additional info): Commit failed due to failure of an earlier commit on which this one depends Error_code: 1964 2024-07-01 4:58:20 8 [Warning] Slave: Commit failed due to failure of an earlier commit on which this one depends Error_code: 1964 2024-07-01 4:58:20 8 [ERROR] Error running query, slave SQL thread aborted. Fix the problem, and restart the slave SQL thread with "SLAVE START". We stopped at log 'db2-binary.165702' position 193311970 2024-07-01 4:58:20 103531 [Note] Slave SQL thread exiting, replication stopped in log 'db2-binary.165702' at position 193311970, master: 10.76.24.77:3306 2024-07-01 4:58:39 103530 [Note] Slave I/O thread exiting, read up to log 'db2-binary.165899', position 132711782, master 10.76.24.77:3306 2024-07-01 4:58:39 104172 [Note] Slave I/O thread: Start asynchronous replication to master 'gtid@10.76.24.77:3306' in log 'db2-binary.165899' at position 132711782 2024-07-01 4:58:39 104173 [Note] Slave SQL thread initialized, starting replication in log 'db2-binary.165702' at position 193311970, relay log './db1-relay.064329' position: 9364694 2024-07-01 4:58:39 104172 [Note] Slave I/O thread: connected to master 'gtid@10.76.24.77:3306',replication started in log 'db2-binary.165899' at position 132711782 2024-07-01 4:58:39 104173 [Note] 'SQL_SLAVE_SKIP_COUNTER=100' executed at relay_log_file='./db1-relay.064329', relay_log_pos='9364694', master_log_name='db2-binary.165702', master_log_pos='193311970' and new position at relay_log_file='./db1-relay.064329', relay_log_pos='9392299', master_log_name='db2-binary.165702', master_log_pos='195339184' 2024-07-01 5:04:53 17 [ERROR] mariadbd: Can't find record in 'activesessions' 2024-07-01 5:04:53 17 [ERROR] Slave SQL: Could not execute Delete_rows_v1 event on table aaadb.activesessions; Can't find record in 'activesessions', Error_code: 1032; handler error HA_ERR_KEY_NOT_FOUND; the event's master log db2-binary.165902, end_log_pos 169447586, Gtid 0-2-18666113113, Internal MariaDB error code: 1032 2024-07-01 5:04:53 17 [Warning] Slave: Can't find record in 'activesessions' Error_code: 1032 2024-07-01 5:04:53 17 [ERROR] Error running query, slave SQL thread aborted. Fix the problem, and restart the slave SQL thread with "SLAVE START". We stopped at log 'db2-binary.165902' position 169446839 2024-07-01 5:04:53 104173 [Note] Error reading relay log event: slave SQL thread was killed 2024-07-01 5:04:53 104173 [Note] Slave SQL thread exiting, replication stopped in log 'db2-binary.165902' at position 169446839, master: 10.76.24.77:3306 2024-07-01 5:08:17 104172 [Note] Slave I/O thread exiting, read up to log 'db2-binary.165904', position 69323547, master 10.76.24.77:3306 2024-07-01 5:08:17 130639 [Note] Slave I/O thread: Start asynchronous replication to master 'gtid@10.76.24.77:3306' in log 'db2-binary.165904' at position 69323547 2024-07-01 5:08:17 130640 [Note] Slave SQL thread initialized, starting replication in log 'db2-binary.165902' at position 169446839, relay log './db1-relay.064769' position: 35229591 2024-07-01 5:08:17 130639 [Note] Slave I/O thread: connected to master 'gtid@10.76.24.77:3306',replication started in log 'db2-binary.165904' at position 69323547 2024-07-01 5:08:17 130640 [Note] 'SQL_SLAVE_SKIP_COUNTER=100' executed at relay_log_file='./db1-relay.064769', relay_log_pos='35229591', master_log_name='db2-binary.165902', master_log_pos='169446839' and new position at relay_log_file='./db1-relay.064769', relay_log_pos='35261036', master_log_name='db2-binary.165902', master_log_pos='169478284' 2024-07-01 5:08:20 6 [ERROR] mariadbd: Can't find record in 'activesessions' 2024-07-01 5:08:20 6 [ERROR] Slave SQL: Could not execute Delete_rows_v1 event on table aaadb.activesessions; Can't find record in 'activesessions', Error_code: 1032; handler error HA_ERR_KEY_NOT_FOUND; the event's master log db2-binary.165903, end_log_pos 7877854, Gtid 0-2-18666142871, Internal MariaDB error code: 1032 2024-07-01 5:08:20 6 [Warning] Slave: Can't find record in 'activesessions' Error_code: 1032 2024-07-01 5:08:20 6 [ERROR] Error running query, slave SQL thread aborted. Fix the problem, and restart the slave SQL thread with "SLAVE START". We stopped at log 'db2-binary.165903' position 7877158 2024-07-01 5:08:20 15 [ERROR] Slave (additional info): Commit failed due to failure of an earlier commit on which this one depends Error_code: 1964 2024-07-01 5:08:20 15 [Warning] Slave: Commit failed due to failure of an earlier commit on which this one depends Error_code: 1964 2024-07-01 5:08:20 15 [ERROR] Error running query, slave SQL thread aborted. Fix the problem, and restart the slave SQL thread with "SLAVE START". We stopped at log 'db2-binary.165903' position 7877158 2024-07-01 5:08:20 10 [ERROR] Slave (additional info): Commit failed due to failure of an earlier commit on which this one depends Error_code: 1964 2024-07-01 5:08:20 10 [Warning] Slave: Commit failed due to failure of an earlier commit on which this one depends Error_code: 1964 2024-07-01 5:08:20 10 [ERROR] Error running query, slave SQL thread aborted. Fix the problem, and restart the slave SQL thread with "SLAVE START". We stopped at log 'db2-binary.165903' position 7877158 2024-07-01 5:08:20 14 [ERROR] Slave (additional info): Commit failed due to failure of an earlier commit on which this one depends Error_code: 1964 2024-07-01 5:08:20 14 [Warning] Slave: Commit failed due to failure of an earlier commit on which this one depends Error_code: 1964 2024-07-01 5:08:20 14 [ERROR] Error running query, slave SQL thread aborted. Fix the problem, and restart the slave SQL thread with "SLAVE START". We stopped at log 'db2-binary.165903' position 7877158 2024-07-01 5:08:20 11 [ERROR] Slave (additional info): Commit failed due to failure of an earlier commit on which this one depends Error_code: 1964 2024-07-01 5:08:20 11 [Warning] Slave: Commit failed due to failure of an earlier commit on which this one depends Error_code: 1964 2024-07-01 5:08:20 11 [ERROR] Error running query, slave SQL thread aborted. Fix the problem, and restart the slave SQL thread with "SLAVE START". We stopped at log 'db2-binary.165903' position 7877158 2024-07-01 5:08:20 13 [ERROR] Slave (additional info): Commit failed due to failure of an earlier commit on which this one depends Error_code: 1964 2024-07-01 5:08:20 13 [Warning] Slave: Commit failed due to failure of an earlier commit on which this one depends Error_code: 1964 2024-07-01 5:08:20 13 [ERROR] Error running query, slave SQL thread aborted. Fix the problem, and restart the slave SQL thread with "SLAVE START". We stopped at log 'db2-binary.165903' position 7877158 2024-07-01 5:08:20 16 [ERROR] Slave (additional info): Commit failed due to failure of an earlier commit on which this one depends Error_code: 1964 2024-07-01 5:08:20 16 [Warning] Slave: Commit failed due to failure of an earlier commit on which this one depends Error_code: 1964 2024-07-01 5:08:20 16 [ERROR] Error running query, slave SQL thread aborted. Fix the problem, and restart the slave SQL thread with "SLAVE START". We stopped at log 'db2-binary.165903' position 7877158 2024-07-01 5:08:20 12 [ERROR] Slave (additional info): Commit failed due to failure of an earlier commit on which this one depends Error_code: 1964 2024-07-01 5:08:20 12 [Warning] Slave: Commit failed due to failure of an earlier commit on which this one depends Error_code: 1964 2024-07-01 5:08:20 12 [ERROR] Error running query, slave SQL thread aborted. Fix the problem, and restart the slave SQL thread with "SLAVE START". We stopped at log 'db2-binary.165903' position 7877158 2024-07-01 5:08:20 9 [ERROR] Slave (additional info): Commit failed due to failure of an earlier commit on which this one depends Error_code: 1964 2024-07-01 5:08:20 9 [Warning] Slave: Commit failed due to failure of an earlier commit on which this one depends Error_code: 1964 2024-07-01 5:08:20 9 [ERROR] Error running query, slave SQL thread aborted. Fix the problem, and restart the slave SQL thread with "SLAVE START". We stopped at log 'db2-binary.165903' position 7877158 2024-07-01 5:08:20 8 [ERROR] Slave (additional info): Commit failed due to failure of an earlier commit on which this one depends Error_code: 1964 2024-07-01 5:08:20 8 [Warning] Slave: Commit failed due to failure of an earlier commit on which this one depends Error_code: 1964 2024-07-01 5:08:20 8 [ERROR] Error running query, slave SQL thread aborted. Fix the problem, and restart the slave SQL thread with "SLAVE START". We stopped at log 'db2-binary.165903' position 7877158 2024-07-01 5:08:20 17 [ERROR] Slave (additional info): Commit failed due to failure of an earlier commit on which this one depends Error_code: 1964 2024-07-01 5:08:20 17 [Warning] Slave: Commit failed due to failure of an earlier commit on which this one depends Error_code: 1964 2024-07-01 5:08:20 17 [ERROR] Error running query, slave SQL thread aborted. Fix the problem, and restart the slave SQL thread with "SLAVE START". We stopped at log 'db2-binary.165903' position 7877158 2024-07-01 5:08:20 7 [ERROR] Slave (additional info): Commit failed due to failure of an earlier commit on which this one depends Error_code: 1964 2024-07-01 5:08:20 7 [Warning] Slave: Commit failed due to failure of an earlier commit on which this one depends Error_code: 1964 2024-07-01 5:08:20 7 [ERROR] Error running query, slave SQL thread aborted. Fix the problem, and restart the slave SQL thread with "SLAVE START". We stopped at log 'db2-binary.165903' position 7877158 2024-07-01 5:08:20 130640 [Note] Slave SQL thread exiting, replication stopped in log 'db2-binary.165903' at position 7877158, master: 10.76.24.77:3306 2024-07-01 5:08:30 130639 [Note] Slave I/O thread exiting, read up to log 'db2-binary.165904', position 89681464, master 10.76.24.77:3306 2024-07-01 5:08:30 131208 [Note] Slave I/O thread: Start asynchronous replication to master 'gtid@10.76.24.77:3306' in log 'db2-binary.165904' at position 89681464 2024-07-01 5:08:30 131209 [Note] Slave SQL thread initialized, starting replication in log 'db2-binary.165903' at position 7877158, relay log './db1-relay.064772' position: 7877458 2024-07-01 5:08:30 131208 [Note] Slave I/O thread: connected to master 'gtid@10.76.24.77:3306',replication started in log 'db2-binary.165904' at position 89681464 2024-07-01 5:08:30 131209 [Note] 'SQL_SLAVE_SKIP_COUNTER=100' executed at relay_log_file='./db1-relay.064772', relay_log_pos='7877458', master_log_name='db2-binary.165903', master_log_pos='7877158' and new position at relay_log_file='./db1-relay.064772', relay_log_pos='7896139', master_log_name='db2-binary.165903', master_log_pos='7895839' 2024-07-01 5:08:30 14 [ERROR] mariadbd: Can't find record in 'activesessions' 2024-07-01 5:08:30 14 [ERROR] Slave SQL: Could not execute Delete_rows_v1 event on table aaadb.activesessions; Can't find record in 'activesessions', Error_code: 1032; handler error HA_ERR_KEY_NOT_FOUND; the event's master log db2-binary.165903, end_log_pos 7943319, Gtid 0-2-18666142940, Internal MariaDB error code: 1032 2024-07-01 5:08:30 14 [Warning] Slave: Can't find record in 'activesessions' Error_code: 1032 2024-07-01 5:08:30 14 [ERROR] Error running query, slave SQL thread aborted. Fix the problem, and restart the slave SQL thread with "SLAVE START". We stopped at log 'db2-binary.165903' position 7942595 2024-07-01 5:08:30 10 [ERROR] Slave (additional info): Commit failed due to failure of an earlier commit on which this one depends Error_code: 1964 2024-07-01 5:08:30 10 [Warning] Slave: Commit failed due to failure of an earlier commit on which this one depends Error_code: 1964 2024-07-01 5:08:30 10 [ERROR] Error running query, slave SQL thread aborted. Fix the problem, and restart the slave SQL thread with "SLAVE START". We stopped at log 'db2-binary.165903' position 7942595 2024-07-01 5:08:30 15 [ERROR] Slave (additional info): Commit failed due to failure of an earlier commit on which this one depends Error_code: 1964 2024-07-01 5:08:30 15 [Warning] Slave: Commit failed due to failure of an earlier commit on which this one depends Error_code: 1964 2024-07-01 5:08:30 15 [ERROR] Error running query, slave SQL thread aborted. Fix the problem, and restart the slave SQL thread with "SLAVE START". We stopped at log 'db2-binary.165903' position 7942595 2024-07-01 5:08:30 6 [ERROR] Slave (additional info): Commit failed due to failure of an earlier commit on which this one depends Error_code: 1964 2024-07-01 5:08:30 6 [Warning] Slave: Commit failed due to failure of an earlier commit on which this one depends Error_code: 1964 2024-07-01 5:08:30 6 [ERROR] Error running query, slave SQL thread aborted. Fix the problem, and restart the slave SQL thread with "SLAVE START". We stopped at log 'db2-binary.165903' position 7942595 2024-07-01 5:08:30 7 [ERROR] Slave (additional info): Commit failed due to failure of an earlier commit on which this one depends Error_code: 1964 2024-07-01 5:08:30 7 [Warning] Slave: Commit failed due to failure of an earlier commit on which this one depends Error_code: 1964 2024-07-01 5:08:30 7 [ERROR] Error running query, slave SQL thread aborted. Fix the problem, and restart the slave SQL thread with "SLAVE START". We stopped at log 'db2-binary.165903' position 7942595 2024-07-01 5:08:30 17 [ERROR] Slave (additional info): Commit failed due to failure of an earlier commit on which this one depends Error_code: 1964 2024-07-01 5:08:30 17 [Warning] Slave: Commit failed due to failure of an earlier commit on which this one depends Error_code: 1964 2024-07-01 5:08:30 17 [ERROR] Error running query, slave SQL thread aborted. Fix the problem, and restart the slave SQL thread with "SLAVE START". We stopped at log 'db2-binary.165903' position 7942595 2024-07-01 5:08:30 8 [ERROR] Slave (additional info): Commit failed due to failure of an earlier commit on which this one depends Error_code: 1964 2024-07-01 5:08:30 8 [Warning] Slave: Commit failed due to failure of an earlier commit on which this one depends Error_code: 1964 2024-07-01 5:08:30 8 [ERROR] Error running query, slave SQL thread aborted. Fix the problem, and restart the slave SQL thread with "SLAVE START". We stopped at log 'db2-binary.165903' position 7942595 2024-07-01 5:08:30 9 [ERROR] Slave (additional info): Commit failed due to failure of an earlier commit on which this one depends Error_code: 1964 2024-07-01 5:08:30 9 [Warning] Slave: Commit failed due to failure of an earlier commit on which this one depends Error_code: 1964 2024-07-01 5:08:30 9 [ERROR] Error running query, slave SQL thread aborted. Fix the problem, and restart the slave SQL thread with "SLAVE START". We stopped at log 'db2-binary.165903' position 7942595 2024-07-01 5:08:30 12 [ERROR] Slave (additional info): Commit failed due to failure of an earlier commit on which this one depends Error_code: 1964 2024-07-01 5:08:30 12 [Warning] Slave: Commit failed due to failure of an earlier commit on which this one depends Error_code: 1964 2024-07-01 5:08:30 12 [ERROR] Error running query, slave SQL thread aborted. Fix the problem, and restart the slave SQL thread with "SLAVE START". We stopped at log 'db2-binary.165903' position 7942595 2024-07-01 5:08:30 16 [ERROR] Slave (additional info): Commit failed due to failure of an earlier commit on which this one depends Error_code: 1964 2024-07-01 5:08:30 16 [Warning] Slave: Commit failed due to failure of an earlier commit on which this one depends Error_code: 1964 2024-07-01 5:08:30 16 [ERROR] Error running query, slave SQL thread aborted. Fix the problem, and restart the slave SQL thread with "SLAVE START". We stopped at log 'db2-binary.165903' position 7942595 2024-07-01 5:08:30 13 [ERROR] Slave (additional info): Commit failed due to failure of an earlier commit on which this one depends Error_code: 1964 2024-07-01 5:08:30 13 [Warning] Slave: Commit failed due to failure of an earlier commit on which this one depends Error_code: 1964 2024-07-01 5:08:30 13 [ERROR] Error running query, slave SQL thread aborted. Fix the problem, and restart the slave SQL thread with "SLAVE START". We stopped at log 'db2-binary.165903' position 7942595 2024-07-01 5:08:30 11 [ERROR] Slave (additional info): Commit failed due to failure of an earlier commit on which this one depends Error_code: 1964 2024-07-01 5:08:30 11 [Warning] Slave: Commit failed due to failure of an earlier commit on which this one depends Error_code: 1964 2024-07-01 5:08:30 11 [ERROR] Error running query, slave SQL thread aborted. Fix the problem, and restart the slave SQL thread with "SLAVE START". We stopped at log 'db2-binary.165903' position 7942595 2024-07-01 5:08:30 131209 [Note] Slave SQL thread exiting, replication stopped in log 'db2-binary.165903' at position 7942595, master: 10.76.24.77:3306 2024-07-01 5:08:36 131208 [Note] Slave I/O thread exiting, read up to log 'db2-binary.165904', position 98695599, master 10.76.24.77:3306 2024-07-01 5:08:36 131216 [Note] Slave I/O thread: Start asynchronous replication to master 'gtid@10.76.24.77:3306' in log 'db2-binary.165904' at position 98695599 2024-07-01 5:08:36 131216 [Note] Slave I/O thread: connected to master 'gtid@10.76.24.77:3306',replication started in log 'db2-binary.165904' at position 98695599 2024-07-01 5:08:36 131217 [Note] Slave SQL thread initialized, starting replication in log 'db2-binary.165903' at position 7942595, relay log './db1-relay.064772' position: 7942895 2024-07-01 5:08:36 131217 [Note] 'SQL_SLAVE_SKIP_COUNTER=100' executed at relay_log_file='./db1-relay.064772', relay_log_pos='7942895', master_log_name='db2-binary.165903', master_log_pos='7942595' and new position at relay_log_file='./db1-relay.064772', relay_log_pos='7967930', master_log_name='db2-binary.165903', master_log_pos='7967630' 2024-07-01 5:08:36 10 [ERROR] mariadbd: Can't find record in 'activesessions' 2024-07-01 5:08:36 10 [ERROR] Slave SQL: Could not execute Delete_rows_v1 event on table aaadb.activesessions; Can't find record in 'activesessions', Error_code: 1032; handler error HA_ERR_KEY_NOT_FOUND; the event's master log db2-binary.165903, end_log_pos 7972590, Gtid 0-2-18666142963, Internal MariaDB error code: 1032 2024-07-01 5:08:36 10 [Warning] Slave: Can't find record in 'activesessions' Error_code: 1032 2024-07-01 5:08:36 10 [ERROR] Error running query, slave SQL thread aborted. Fix the problem, and restart the slave SQL thread with "SLAVE START". We stopped at log 'db2-binary.165903' position 7971850 2024-07-01 5:08:36 14 [ERROR] Slave (additional info): Commit failed due to failure of an earlier commit on which this one depends Error_code: 1964 2024-07-01 5:08:36 14 [Warning] Slave: Commit failed due to failure of an earlier commit on which this one depends Error_code: 1964 2024-07-01 5:08:36 14 [ERROR] Error running query, slave SQL thread aborted. Fix the problem, and restart the slave SQL thread with "SLAVE START". We stopped at log 'db2-binary.165903' position 7971850 2024-07-01 5:08:36 11 [ERROR] Slave (additional info): Commit failed due to failure of an earlier commit on which this one depends Error_code: 1964 2024-07-01 5:08:36 11 [Warning] Slave: Commit failed due to failure of an earlier commit on which this one depends Error_code: 1964 2024-07-01 5:08:36 11 [ERROR] Error running query, slave SQL thread aborted. Fix the problem, and restart the slave SQL thread with "SLAVE START". We stopped at log 'db2-binary.165903' position 7971850 2024-07-01 5:08:36 13 [ERROR] Slave (additional info): Commit failed due to failure of an earlier commit on which this one depends Error_code: 1964 2024-07-01 5:08:36 13 [Warning] Slave: Commit failed due to failure of an earlier commit on which this one depends Error_code: 1964 2024-07-01 5:08:36 13 [ERROR] Error running query, slave SQL thread aborted. Fix the problem, and restart the slave SQL thread with "SLAVE START". We stopped at log 'db2-binary.165903' position 7971850 2024-07-01 5:08:36 16 [ERROR] Slave (additional info): Commit failed due to failure of an earlier commit on which this one depends Error_code: 1964 2024-07-01 5:08:36 16 [Warning] Slave: Commit failed due to failure of an earlier commit on which this one depends Error_code: 1964 2024-07-01 5:08:36 16 [ERROR] Error running query, slave SQL thread aborted. Fix the problem, and restart the slave SQL thread with "SLAVE START". We stopped at log 'db2-binary.165903' position 7971850 2024-07-01 5:08:36 12 [ERROR] Slave (additional info): Commit failed due to failure of an earlier commit on which this one depends Error_code: 1964 2024-07-01 5:08:36 12 [Warning] Slave: Commit failed due to failure of an earlier commit on which this one depends Error_code: 1964 2024-07-01 5:08:36 12 [ERROR] Error running query, slave SQL thread aborted. Fix the problem, and restart the slave SQL thread with "SLAVE START". We stopped at log 'db2-binary.165903' position 7971850 2024-07-01 5:08:36 9 [ERROR] Slave (additional info): Commit failed due to failure of an earlier commit on which this one depends Error_code: 1964 2024-07-01 5:08:36 9 [Warning] Slave: Commit failed due to failure of an earlier commit on which this one depends Error_code: 1964 2024-07-01 5:08:36 9 [ERROR] Error running query, slave SQL thread aborted. Fix the problem, and restart the slave SQL thread with "SLAVE START". We stopped at log 'db2-binary.165903' position 7971850 2024-07-01 5:08:36 8 [ERROR] Slave (additional info): Commit failed due to failure of an earlier commit on which this one depends Error_code: 1964 2024-07-01 5:08:36 8 [Warning] Slave: Commit failed due to failure of an earlier commit on which this one depends Error_code: 1964 2024-07-01 5:08:36 8 [ERROR] Error running query, slave SQL thread aborted. Fix the problem, and restart the slave SQL thread with "SLAVE START". We stopped at log 'db2-binary.165903' position 7971850 2024-07-01 5:08:36 17 [ERROR] Slave (additional info): Commit failed due to failure of an earlier commit on which this one depends Error_code: 1964 2024-07-01 5:08:36 17 [Warning] Slave: Commit failed due to failure of an earlier commit on which this one depends Error_code: 1964 2024-07-01 5:08:36 17 [ERROR] Error running query, slave SQL thread aborted. Fix the problem, and restart the slave SQL thread with "SLAVE START". We stopped at log 'db2-binary.165903' position 7971850 2024-07-01 5:08:36 7 [ERROR] Slave (additional info): Commit failed due to failure of an earlier commit on which this one depends Error_code: 1964 2024-07-01 5:08:36 7 [Warning] Slave: Commit failed due to failure of an earlier commit on which this one depends Error_code: 1964 2024-07-01 5:08:36 7 [ERROR] Error running query, slave SQL thread aborted. Fix the problem, and restart the slave SQL thread with "SLAVE START". We stopped at log 'db2-binary.165903' position 7971850 2024-07-01 5:08:36 6 [ERROR] Slave (additional info): Commit failed due to failure of an earlier commit on which this one depends Error_code: 1964 2024-07-01 5:08:36 6 [Warning] Slave: Commit failed due to failure of an earlier commit on which this one depends Error_code: 1964 2024-07-01 5:08:36 6 [ERROR] Error running query, slave SQL thread aborted. Fix the problem, and restart the slave SQL thread with "SLAVE START". We stopped at log 'db2-binary.165903' position 7971850 2024-07-01 5:08:36 15 [ERROR] Slave (additional info): Commit failed due to failure of an earlier commit on which this one depends Error_code: 1964 2024-07-01 5:08:36 15 [Warning] Slave: Commit failed due to failure of an earlier commit on which this one depends Error_code: 1964 2024-07-01 5:08:36 15 [ERROR] Error running query, slave SQL thread aborted. Fix the problem, and restart the slave SQL thread with "SLAVE START". We stopped at log 'db2-binary.165903' position 7971850 2024-07-01 5:08:36 131217 [Note] Slave SQL thread exiting, replication stopped in log 'db2-binary.165903' at position 7971850, master: 10.76.24.77:3306 2024-07-01 5:10:32 131216 [Note] Slave I/O thread exiting, read up to log 'db2-binary.165905', position 59280154, master 10.76.24.77:3306 2024-07-01 5:10:32 131304 [Note] Slave I/O thread: Start asynchronous replication to master 'gtid@10.76.24.77:3306' in log 'db2-binary.165905' at position 59280154 2024-07-01 5:10:32 131305 [Note] Slave SQL thread initialized, starting replication in log 'db2-binary.165903' at position 7971850, relay log './db1-relay.064772' position: 7972150 2024-07-01 5:10:32 131304 [Note] Slave I/O thread: connected to master 'gtid@10.76.24.77:3306',replication started in log 'db2-binary.165905' at position 59280154 2024-07-01 5:10:32 131305 [Note] 'SQL_SLAVE_SKIP_COUNTER=100' executed at relay_log_file='./db1-relay.064772', relay_log_pos='7972150', master_log_name='db2-binary.165903', master_log_pos='7971850' and new position at relay_log_file='./db1-relay.064772', relay_log_pos='8003575', master_log_name='db2-binary.165903', master_log_pos='8003275' 2024-07-01 5:10:32 11 [ERROR] mariadbd: Can't find record in 'activesessions' 2024-07-01 5:10:32 11 [ERROR] Slave SQL: Could not execute Delete_rows_v1 event on table aaadb.activesessions; Can't find record in 'activesessions', Error_code: 1032; handler error HA_ERR_KEY_NOT_FOUND; the event's master log db2-binary.165903, end_log_pos 8031588, Gtid 0-2-18666143012, Internal MariaDB error code: 1032 2024-07-01 5:10:32 11 [Warning] Slave: Can't find record in 'activesessions' Error_code: 1032 2024-07-01 5:10:32 11 [ERROR] Error running query, slave SQL thread aborted. Fix the problem, and restart the slave SQL thread with "SLAVE START". We stopped at log 'db2-binary.165903' position 8030852 2024-07-01 5:10:32 14 [ERROR] Slave (additional info): Commit failed due to failure of an earlier commit on which this one depends Error_code: 1964 2024-07-01 5:10:32 14 [Warning] Slave: Commit failed due to failure of an earlier commit on which this one depends Error_code: 1964 2024-07-01 5:10:32 14 [ERROR] Error running query, slave SQL thread aborted. Fix the problem, and restart the slave SQL thread with "SLAVE START". We stopped at log 'db2-binary.165903' position 8030852 2024-07-01 5:10:32 10 [ERROR] Slave (additional info): Commit failed due to failure of an earlier commit on which this one depends Error_code: 1964 2024-07-01 5:10:32 10 [Warning] Slave: Commit failed due to failure of an earlier commit on which this one depends Error_code: 1964 2024-07-01 5:10:32 10 [ERROR] Error running query, slave SQL thread aborted. Fix the problem, and restart the slave SQL thread with "SLAVE START". We stopped at log 'db2-binary.165903' position 8030852 2024-07-01 5:10:32 15 [ERROR] Slave (additional info): Commit failed due to failure of an earlier commit on which this one depends Error_code: 1964 2024-07-01 5:10:32 15 [Warning] Slave: Commit failed due to failure of an earlier commit on which this one depends Error_code: 1964 2024-07-01 5:10:32 15 [ERROR] Error running query, slave SQL thread aborted. Fix the problem, and restart the slave SQL thread with "SLAVE START". We stopped at log 'db2-binary.165903' position 8030852 2024-07-01 5:10:32 6 [ERROR] Slave (additional info): Commit failed due to failure of an earlier commit on which this one depends Error_code: 1964 2024-07-01 5:10:32 6 [Warning] Slave: Commit failed due to failure of an earlier commit on which this one depends Error_code: 1964 2024-07-01 5:10:32 6 [ERROR] Error running query, slave SQL thread aborted. Fix the problem, and restart the slave SQL thread with "SLAVE START". We stopped at log 'db2-binary.165903' position 8030852 2024-07-01 5:10:32 7 [ERROR] Slave (additional info): Commit failed due to failure of an earlier commit on which this one depends Error_code: 1964 2024-07-01 5:10:32 7 [Warning] Slave: Commit failed due to failure of an earlier commit on which this one depends Error_code: 1964 2024-07-01 5:10:32 7 [ERROR] Error running query, slave SQL thread aborted. Fix the problem, and restart the slave SQL thread with "SLAVE START". We stopped at log 'db2-binary.165903' position 8030852 2024-07-01 5:10:32 17 [ERROR] Slave (additional info): Commit failed due to failure of an earlier commit on which this one depends Error_code: 1964 2024-07-01 5:10:32 17 [Warning] Slave: Commit failed due to failure of an earlier commit on which this one depends Error_code: 1964 2024-07-01 5:10:32 17 [ERROR] Error running query, slave SQL thread aborted. Fix the problem, and restart the slave SQL thread with "SLAVE START". We stopped at log 'db2-binary.165903' position 8030852 2024-07-01 5:10:32 8 [ERROR] Slave (additional info): Commit failed due to failure of an earlier commit on which this one depends Error_code: 1964 2024-07-01 5:10:32 8 [Warning] Slave: Commit failed due to failure of an earlier commit on which this one depends Error_code: 1964 2024-07-01 5:10:32 8 [ERROR] Error running query, slave SQL thread aborted. Fix the problem, and restart the slave SQL thread with "SLAVE START". We stopped at log 'db2-binary.165903' position 8030852 2024-07-01 5:10:32 9 [ERROR] Slave (additional info): Commit failed due to failure of an earlier commit on which this one depends Error_code: 1964 2024-07-01 5:10:32 9 [Warning] Slave: Commit failed due to failure of an earlier commit on which this one depends Error_code: 1964 2024-07-01 5:10:32 9 [ERROR] Error running query, slave SQL thread aborted. Fix the problem, and restart the slave SQL thread with "SLAVE START". We stopped at log 'db2-binary.165903' position 8030852 2024-07-01 5:10:32 12 [ERROR] Slave (additional info): Commit failed due to failure of an earlier commit on which this one depends Error_code: 1964 2024-07-01 5:10:32 12 [Warning] Slave: Commit failed due to failure of an earlier commit on which this one depends Error_code: 1964 2024-07-01 5:10:32 12 [ERROR] Error running query, slave SQL thread aborted. Fix the problem, and restart the slave SQL thread with "SLAVE START". We stopped at log 'db2-binary.165903' position 8030852 2024-07-01 5:10:32 16 [ERROR] Slave (additional info): Commit failed due to failure of an earlier commit on which this one depends Error_code: 1964 2024-07-01 5:10:32 16 [Warning] Slave: Commit failed due to failure of an earlier commit on which this one depends Error_code: 1964 2024-07-01 5:10:32 16 [ERROR] Error running query, slave SQL thread aborted. Fix the problem, and restart the slave SQL thread with "SLAVE START". We stopped at log 'db2-binary.165903' position 8030852 2024-07-01 5:10:32 13 [ERROR] Slave (additional info): Commit failed due to failure of an earlier commit on which this one depends Error_code: 1964 2024-07-01 5:10:32 13 [Warning] Slave: Commit failed due to failure of an earlier commit on which this one depends Error_code: 1964 2024-07-01 5:10:32 13 [ERROR] Error running query, slave SQL thread aborted. Fix the problem, and restart the slave SQL thread with "SLAVE START". We stopped at log 'db2-binary.165903' position 8030852 2024-07-01 5:10:32 131305 [Note] Slave SQL thread exiting, replication stopped in log 'db2-binary.165903' at position 8030852, master: 10.76.24.77:3306 2024-07-01 5:10:39 131304 [Note] Slave I/O thread exiting, read up to log 'db2-binary.165905', position 68968368, master 10.76.24.77:3306 2024-07-01 5:10:39 131310 [Note] Slave I/O thread: Start asynchronous replication to master 'gtid@10.76.24.77:3306' in log 'db2-binary.165905' at position 68968368 2024-07-01 5:10:39 131311 [Note] Slave SQL thread initialized, starting replication in log 'db2-binary.165903' at position 8030852, relay log './db1-relay.064772' position: 8031152 2024-07-01 5:10:39 131310 [Note] Slave I/O thread: connected to master 'gtid@10.76.24.77:3306',replication started in log 'db2-binary.165905' at position 68968368 2024-07-01 5:10:39 131311 [Note] 'SQL_SLAVE_SKIP_COUNTER=100' executed at relay_log_file='./db1-relay.064772', relay_log_pos='8031152', master_log_name='db2-binary.165903', master_log_pos='8030852' and new position at relay_log_file='./db1-relay.064772', relay_log_pos='8059022', master_log_name='db2-binary.165903', master_log_pos='8058722' 2024-07-01 5:10:39 9 [ERROR] mariadbd: Can't find record in 'activesessions' 2024-07-01 5:10:39 9 [ERROR] Slave SQL: Could not execute Delete_rows_v1 event on table aaadb.activesessions; Can't find record in 'activesessions', Error_code: 1032; handler error HA_ERR_KEY_NOT_FOUND; the event's master log db2-binary.165903, end_log_pos 8194378, Gtid 0-2-18666143129, Internal MariaDB error code: 1032 2024-07-01 5:10:39 9 [Warning] Slave: Can't find record in 'activesessions' Error_code: 1032 2024-07-01 5:10:39 9 [ERROR] Error running query, slave SQL thread aborted. Fix the problem, and restart the slave SQL thread with "SLAVE START". We stopped at log 'db2-binary.165903' position 8193643 2024-07-01 5:10:39 8 [ERROR] Slave (additional info): Commit failed due to failure of an earlier commit on which this one depends Error_code: 1964 2024-07-01 5:10:39 8 [Warning] Slave: Commit failed due to failure of an earlier commit on which this one depends Error_code: 1964 2024-07-01 5:10:39 8 [ERROR] Error running query, slave SQL thread aborted. Fix the problem, and restart the slave SQL thread with "SLAVE START". We stopped at log 'db2-binary.165903' position 8193643 2024-07-01 5:10:39 17 [ERROR] Slave (additional info): Commit failed due to failure of an earlier commit on which this one depends Error_code: 1964 2024-07-01 5:10:39 17 [Warning] Slave: Commit failed due to failure of an earlier commit on which this one depends Error_code: 1964 2024-07-01 5:10:39 17 [ERROR] Error running query, slave SQL thread aborted. Fix the problem, and restart the slave SQL thread with "SLAVE START". We stopped at log 'db2-binary.165903' position 8193643 2024-07-01 5:10:39 7 [ERROR] Slave (additional info): Commit failed due to failure of an earlier commit on which this one depends Error_code: 1964 2024-07-01 5:10:39 7 [Warning] Slave: Commit failed due to failure of an earlier commit on which this one depends Error_code: 1964 2024-07-01 5:10:39 7 [ERROR] Error running query, slave SQL thread aborted. Fix the problem, and restart the slave SQL thread with "SLAVE START". We stopped at log 'db2-binary.165903' position 8193643 2024-07-01 5:10:39 6 [ERROR] Slave (additional info): Commit failed due to failure of an earlier commit on which this one depends Error_code: 1964 2024-07-01 5:10:39 6 [Warning] Slave: Commit failed due to failure of an earlier commit on which this one depends Error_code: 1964 2024-07-01 5:10:39 6 [ERROR] Error running query, slave SQL thread aborted. Fix the problem, and restart the slave SQL thread with "SLAVE START". We stopped at log 'db2-binary.165903' position 8193643 2024-07-01 5:10:39 15 [ERROR] Slave (additional info): Commit failed due to failure of an earlier commit on which this one depends Error_code: 1964 2024-07-01 5:10:39 15 [Warning] Slave: Commit failed due to failure of an earlier commit on which this one depends Error_code: 1964 2024-07-01 5:10:39 15 [ERROR] Error running query, slave SQL thread aborted. Fix the problem, and restart the slave SQL thread with "SLAVE START". We stopped at log 'db2-binary.165903' position 8193643 2024-07-01 5:10:39 10 [ERROR] Slave (additional info): Commit failed due to failure of an earlier commit on which this one depends Error_code: 1964 2024-07-01 5:10:39 10 [Warning] Slave: Commit failed due to failure of an earlier commit on which this one depends Error_code: 1964 2024-07-01 5:10:39 10 [ERROR] Error running query, slave SQL thread aborted. Fix the problem, and restart the slave SQL thread with "SLAVE START". We stopped at log 'db2-binary.165903' position 8193643 2024-07-01 5:10:39 14 [ERROR] Slave (additional info): Commit failed due to failure of an earlier commit on which this one depends Error_code: 1964 2024-07-01 5:10:39 14 [Warning] Slave: Commit failed due to failure of an earlier commit on which this one depends Error_code: 1964 2024-07-01 5:10:39 14 [ERROR] Error running query, slave SQL thread aborted. Fix the problem, and restart the slave SQL thread with "SLAVE START". We stopped at log 'db2-binary.165903' position 8193643 2024-07-01 5:10:39 11 [ERROR] Slave (additional info): Commit failed due to failure of an earlier commit on which this one depends Error_code: 1964 2024-07-01 5:10:39 11 [Warning] Slave: Commit failed due to failure of an earlier commit on which this one depends Error_code: 1964 2024-07-01 5:10:39 11 [ERROR] Error running query, slave SQL thread aborted. Fix the problem, and restart the slave SQL thread with "SLAVE START". We stopped at log 'db2-binary.165903' position 8193643 2024-07-01 5:10:39 13 [ERROR] Slave (additional info): Commit failed due to failure of an earlier commit on which this one depends Error_code: 1964 2024-07-01 5:10:39 13 [Warning] Slave: Commit failed due to failure of an earlier commit on which this one depends Error_code: 1964 2024-07-01 5:10:39 13 [ERROR] Error running query, slave SQL thread aborted. Fix the problem, and restart the slave SQL thread with "SLAVE START". We stopped at log 'db2-binary.165903' position 8193643 2024-07-01 5:10:39 16 [ERROR] Slave (additional info): Commit failed due to failure of an earlier commit on which this one depends Error_code: 1964 2024-07-01 5:10:39 16 [Warning] Slave: Commit failed due to failure of an earlier commit on which this one depends Error_code: 1964 2024-07-01 5:10:39 16 [ERROR] Error running query, slave SQL thread aborted. Fix the problem, and restart the slave SQL thread with "SLAVE START". We stopped at log 'db2-binary.165903' position 8193643 2024-07-01 5:10:39 12 [ERROR] Slave (additional info): Commit failed due to failure of an earlier commit on which this one depends Error_code: 1964 2024-07-01 5:10:39 12 [Warning] Slave: Commit failed due to failure of an earlier commit on which this one depends Error_code: 1964 2024-07-01 5:10:39 12 [ERROR] Error running query, slave SQL thread aborted. Fix the problem, and restart the slave SQL thread with "SLAVE START". We stopped at log 'db2-binary.165903' position 8193643 2024-07-01 5:10:39 131311 [Note] Slave SQL thread exiting, replication stopped in log 'db2-binary.165903' at position 8193643, master: 10.76.24.77:3306 2024-07-01 5:10:44 131310 [Note] Slave I/O thread exiting, read up to log 'db2-binary.165905', position 77928482, master 10.76.24.77:3306 2024-07-01 5:10:44 131318 [Note] Slave I/O thread: Start asynchronous replication to master 'gtid@10.76.24.77:3306' in log 'db2-binary.165905' at position 77928482 2024-07-01 5:10:44 131319 [Note] Slave SQL thread initialized, starting replication in log 'db2-binary.165903' at position 8193643, relay log './db1-relay.064772' position: 8193943 2024-07-01 5:10:44 131318 [Note] Slave I/O thread: connected to master 'gtid@10.76.24.77:3306',replication started in log 'db2-binary.165905' at position 77928482 2024-07-01 5:10:44 131319 [Note] 'SQL_SLAVE_SKIP_COUNTER=100' executed at relay_log_file='./db1-relay.064772', relay_log_pos='8193943', master_log_name='db2-binary.165903', master_log_pos='8193643' and new position at relay_log_file='./db1-relay.064772', relay_log_pos='8212386', master_log_name='db2-binary.165903', master_log_pos='8212086' 2024-07-01 5:10:44 14 [ERROR] mariadbd: Can't find record in 'activesessions' 2024-07-01 5:10:44 14 [ERROR] Slave SQL: Could not execute Delete_rows_v1 event on table aaadb.activesessions; Can't find record in 'activesessions', Error_code: 1032; handler error HA_ERR_KEY_NOT_FOUND; the event's master log db2-binary.165903, end_log_pos 8390471, Gtid 0-2-18666143269, Internal MariaDB error code: 1032 2024-07-01 5:10:44 14 [Warning] Slave: Can't find record in 'activesessions' Error_code: 1032 2024-07-01 5:10:44 14 [ERROR] Error running query, slave SQL thread aborted. Fix the problem, and restart the slave SQL thread with "SLAVE START". We stopped at log 'db2-binary.165903' position 8389738 2024-07-01 5:10:44 10 [ERROR] Slave (additional info): Commit failed due to failure of an earlier commit on which this one depends Error_code: 1964 2024-07-01 5:10:44 10 [Warning] Slave: Commit failed due to failure of an earlier commit on which this one depends Error_code: 1964 2024-07-01 5:10:44 10 [ERROR] Error running query, slave SQL thread aborted. Fix the problem, and restart the slave SQL thread with "SLAVE START". We stopped at log 'db2-binary.165903' position 8389738 2024-07-01 5:10:44 15 [ERROR] Slave (additional info): Commit failed due to failure of an earlier commit on which this one depends Error_code: 1964 2024-07-01 5:10:44 15 [Warning] Slave: Commit failed due to failure of an earlier commit on which this one depends Error_code: 1964 2024-07-01 5:10:44 15 [ERROR] Error running query, slave SQL thread aborted. Fix the problem, and restart the slave SQL thread with "SLAVE START". We stopped at log 'db2-binary.165903' position 8389738 2024-07-01 5:10:44 6 [ERROR] Slave (additional info): Commit failed due to failure of an earlier commit on which this one depends Error_code: 1964 2024-07-01 5:10:44 6 [Warning] Slave: Commit failed due to failure of an earlier commit on which this one depends Error_code: 1964 2024-07-01 5:10:44 6 [ERROR] Error running query, slave SQL thread aborted. Fix the problem, and restart the slave SQL thread with "SLAVE START". We stopped at log 'db2-binary.165903' position 8389738 2024-07-01 5:10:44 7 [ERROR] Slave (additional info): Commit failed due to failure of an earlier commit on which this one depends Error_code: 1964 2024-07-01 5:10:44 7 [Warning] Slave: Commit failed due to failure of an earlier commit on which this one depends Error_code: 1964 2024-07-01 5:10:44 7 [ERROR] Error running query, slave SQL thread aborted. Fix the problem, and restart the slave SQL thread with "SLAVE START". We stopped at log 'db2-binary.165903' position 8389738 2024-07-01 5:10:44 17 [ERROR] Slave (additional info): Commit failed due to failure of an earlier commit on which this one depends Error_code: 1964 2024-07-01 5:10:44 17 [Warning] Slave: Commit failed due to failure of an earlier commit on which this one depends Error_code: 1964 2024-07-01 5:10:44 17 [ERROR] Error running query, slave SQL thread aborted. Fix the problem, and restart the slave SQL thread with "SLAVE START". We stopped at log 'db2-binary.165903' position 8389738 2024-07-01 5:10:44 8 [ERROR] Slave (additional info): Commit failed due to failure of an earlier commit on which this one depends Error_code: 1964 2024-07-01 5:10:44 8 [Warning] Slave: Commit failed due to failure of an earlier commit on which this one depends Error_code: 1964 2024-07-01 5:10:44 8 [ERROR] Error running query, slave SQL thread aborted. Fix the problem, and restart the slave SQL thread with "SLAVE START". We stopped at log 'db2-binary.165903' position 8389738 2024-07-01 5:10:44 9 [ERROR] Slave (additional info): Commit failed due to failure of an earlier commit on which this one depends Error_code: 1964 2024-07-01 5:10:44 9 [Warning] Slave: Commit failed due to failure of an earlier commit on which this one depends Error_code: 1964 2024-07-01 5:10:44 9 [ERROR] Error running query, slave SQL thread aborted. Fix the problem, and restart the slave SQL thread with "SLAVE START". We stopped at log 'db2-binary.165903' position 8389738 2024-07-01 5:10:44 12 [ERROR] Slave (additional info): Commit failed due to failure of an earlier commit on which this one depends Error_code: 1964 2024-07-01 5:10:44 12 [Warning] Slave: Commit failed due to failure of an earlier commit on which this one depends Error_code: 1964 2024-07-01 5:10:44 12 [ERROR] Error running query, slave SQL thread aborted. Fix the problem, and restart the slave SQL thread with "SLAVE START". We stopped at log 'db2-binary.165903' position 8389738 2024-07-01 5:10:44 16 [ERROR] Slave (additional info): Commit failed due to failure of an earlier commit on which this one depends Error_code: 1964 2024-07-01 5:10:44 16 [Warning] Slave: Commit failed due to failure of an earlier commit on which this one depends Error_code: 1964 2024-07-01 5:10:44 16 [ERROR] Error running query, slave SQL thread aborted. Fix the problem, and restart the slave SQL thread with "SLAVE START". We stopped at log 'db2-binary.165903' position 8389738 2024-07-01 5:10:44 13 [ERROR] Slave (additional info): Commit failed due to failure of an earlier commit on which this one depends Error_code: 1964 2024-07-01 5:10:44 13 [Warning] Slave: Commit failed due to failure of an earlier commit on which this one depends Error_code: 1964 2024-07-01 5:10:44 13 [ERROR] Error running query, slave SQL thread aborted. Fix the problem, and restart the slave SQL thread with "SLAVE START". We stopped at log 'db2-binary.165903' position 8389738 2024-07-01 5:10:44 11 [ERROR] Slave (additional info): Commit failed due to failure of an earlier commit on which this one depends Error_code: 1964 2024-07-01 5:10:44 11 [Warning] Slave: Commit failed due to failure of an earlier commit on which this one depends Error_code: 1964 2024-07-01 5:10:44 11 [ERROR] Error running query, slave SQL thread aborted. Fix the problem, and restart the slave SQL thread with "SLAVE START". We stopped at log 'db2-binary.165903' position 8389738 2024-07-01 5:10:44 131319 [Note] Slave SQL thread exiting, replication stopped in log 'db2-binary.165903' at position 8389738, master: 10.76.24.77:3306 2024-07-01 5:10:50 131318 [Note] Slave I/O thread exiting, read up to log 'db2-binary.165905', position 86692221, master 10.76.24.77:3306 2024-07-01 5:10:50 131327 [Note] Slave I/O thread: Start asynchronous replication to master 'gtid@10.76.24.77:3306' in log 'db2-binary.165905' at position 86692221 2024-07-01 5:10:50 131328 [Note] Slave SQL thread initialized, starting replication in log 'db2-binary.165903' at position 8389738, relay log './db1-relay.064772' position: 8390038 2024-07-01 5:10:50 131327 [Note] Slave I/O thread: connected to master 'gtid@10.76.24.77:3306',replication started in log 'db2-binary.165905' at position 86692221 2024-07-01 5:10:50 131328 [Note] 'SQL_SLAVE_SKIP_COUNTER=100' executed at relay_log_file='./db1-relay.064772', relay_log_pos='8390038', master_log_name='db2-binary.165903', master_log_pos='8389738' and new position at relay_log_file='./db1-relay.064772', relay_log_pos='8421404', master_log_name='db2-binary.165903', master_log_pos='8421104' 2024-07-01 5:10:50 16 [ERROR] mariadbd: Can't find record in 'activesessions' 2024-07-01 5:10:50 16 [ERROR] Slave SQL: Could not execute Delete_rows_v1 event on table aaadb.activesessions; Can't find record in 'activesessions', Error_code: 1032; handler error HA_ERR_KEY_NOT_FOUND; the event's master log db2-binary.165903, end_log_pos 8530290, Gtid 0-2-18666143363, Internal MariaDB error code: 1032 2024-07-01 5:10:50 16 [Warning] Slave: Can't find record in 'activesessions' Error_code: 1032 2024-07-01 5:10:50 16 [ERROR] Error running query, slave SQL thread aborted. Fix the problem, and restart the slave SQL thread with "SLAVE START". We stopped at log 'db2-binary.165903' position 8529563 2024-07-01 5:10:50 12 [ERROR] Slave (additional info): Commit failed due to failure of an earlier commit on which this one depends Error_code: 1964 2024-07-01 5:10:50 12 [Warning] Slave: Commit failed due to failure of an earlier commit on which this one depends Error_code: 1964 2024-07-01 5:10:50 12 [ERROR] Error running query, slave SQL thread aborted. Fix the problem, and restart the slave SQL thread with "SLAVE START". We stopped at log 'db2-binary.165903' position 8529563 2024-07-01 5:10:50 9 [ERROR] Slave (additional info): Commit failed due to failure of an earlier commit on which this one depends Error_code: 1964 2024-07-01 5:10:50 9 [Warning] Slave: Commit failed due to failure of an earlier commit on which this one depends Error_code: 1964 2024-07-01 5:10:50 9 [ERROR] Error running query, slave SQL thread aborted. Fix the problem, and restart the slave SQL thread with "SLAVE START". We stopped at log 'db2-binary.165903' position 8529563 2024-07-01 5:10:50 8 [ERROR] Slave (additional info): Commit failed due to failure of an earlier commit on which this one depends Error_code: 1964 2024-07-01 5:10:50 8 [Warning] Slave: Commit failed due to failure of an earlier commit on which this one depends Error_code: 1964 2024-07-01 5:10:50 8 [ERROR] Error running query, slave SQL thread aborted. Fix the problem, and restart the slave SQL thread with "SLAVE START". We stopped at log 'db2-binary.165903' position 8529563 2024-07-01 5:10:50 17 [ERROR] Slave (additional info): Commit failed due to failure of an earlier commit on which this one depends Error_code: 1964 2024-07-01 5:10:50 17 [Warning] Slave: Commit failed due to failure of an earlier commit on which this one depends Error_code: 1964 2024-07-01 5:10:50 17 [ERROR] Error running query, slave SQL thread aborted. Fix the problem, and restart the slave SQL thread with "SLAVE START". We stopped at log 'db2-binary.165903' position 8529563 2024-07-01 5:10:50 7 [ERROR] Slave (additional info): Commit failed due to failure of an earlier commit on which this one depends Error_code: 1964 2024-07-01 5:10:50 7 [Warning] Slave: Commit failed due to failure of an earlier commit on which this one depends Error_code: 1964 2024-07-01 5:10:50 7 [ERROR] Error running query, slave SQL thread aborted. Fix the problem, and restart the slave SQL thread with "SLAVE START". We stopped at log 'db2-binary.165903' position 8529563 2024-07-01 5:10:50 6 [ERROR] Slave (additional info): Commit failed due to failure of an earlier commit on which this one depends Error_code: 1964 2024-07-01 5:10:50 6 [Warning] Slave: Commit failed due to failure of an earlier commit on which this one depends Error_code: 1964 2024-07-01 5:10:50 6 [ERROR] Error running query, slave SQL thread aborted. Fix the problem, and restart the slave SQL thread with "SLAVE START". We stopped at log 'db2-binary.165903' position 8529563 2024-07-01 5:10:50 15 [ERROR] Slave (additional info): Commit failed due to failure of an earlier commit on which this one depends Error_code: 1964 2024-07-01 5:10:50 15 [Warning] Slave: Commit failed due to failure of an earlier commit on which this one depends Error_code: 1964 2024-07-01 5:10:50 15 [ERROR] Error running query, slave SQL thread aborted. Fix the problem, and restart the slave SQL thread with "SLAVE START". We stopped at log 'db2-binary.165903' position 8529563 2024-07-01 5:10:50 10 [ERROR] Slave (additional info): Commit failed due to failure of an earlier commit on which this one depends Error_code: 1964 2024-07-01 5:10:50 10 [Warning] Slave: Commit failed due to failure of an earlier commit on which this one depends Error_code: 1964 2024-07-01 5:10:50 10 [ERROR] Error running query, slave SQL thread aborted. Fix the problem, and restart the slave SQL thread with "SLAVE START". We stopped at log 'db2-binary.165903' position 8529563 2024-07-01 5:10:50 14 [ERROR] Slave (additional info): Commit failed due to failure of an earlier commit on which this one depends Error_code: 1964 2024-07-01 5:10:50 14 [Warning] Slave: Commit failed due to failure of an earlier commit on which this one depends Error_code: 1964 2024-07-01 5:10:50 14 [ERROR] Error running query, slave SQL thread aborted. Fix the problem, and restart the slave SQL thread with "SLAVE START". We stopped at log 'db2-binary.165903' position 8529563 2024-07-01 5:10:50 11 [ERROR] Slave (additional info): Commit failed due to failure of an earlier commit on which this one depends Error_code: 1964 2024-07-01 5:10:50 11 [Warning] Slave: Commit failed due to failure of an earlier commit on which this one depends Error_code: 1964 2024-07-01 5:10:50 11 [ERROR] Error running query, slave SQL thread aborted. Fix the problem, and restart the slave SQL thread with "SLAVE START". We stopped at log 'db2-binary.165903' position 8529563 2024-07-01 5:10:50 13 [ERROR] Slave (additional info): Commit failed due to failure of an earlier commit on which this one depends Error_code: 1964 2024-07-01 5:10:50 13 [Warning] Slave: Commit failed due to failure of an earlier commit on which this one depends Error_code: 1964 2024-07-01 5:10:50 13 [ERROR] Error running query, slave SQL thread aborted. Fix the problem, and restart the slave SQL thread with "SLAVE START". We stopped at log 'db2-binary.165903' position 8529563 2024-07-01 5:10:50 131328 [Note] Slave SQL thread exiting, replication stopped in log 'db2-binary.165903' at position 8529563, master: 10.76.24.77:3306 2024-07-01 5:10:55 131327 [Note] Slave I/O thread exiting, read up to log 'db2-binary.165905', position 94568096, master 10.76.24.77:3306 2024-07-01 5:10:55 131336 [Note] Slave I/O thread: Start asynchronous replication to master 'gtid@10.76.24.77:3306' in log 'db2-binary.165905' at position 94568096 2024-07-01 5:10:55 131337 [Note] Slave SQL thread initialized, starting replication in log 'db2-binary.165903' at position 8529563, relay log './db1-relay.064772' position: 8529863 2024-07-01 5:10:55 131336 [Note] Slave I/O thread: connected to master 'gtid@10.76.24.77:3306',replication started in log 'db2-binary.165905' at position 94568096 2024-07-01 5:10:55 131337 [Note] 'SQL_SLAVE_SKIP_COUNTER=100' executed at relay_log_file='./db1-relay.064772', relay_log_pos='8529863', master_log_name='db2-binary.165903', master_log_pos='8529563' and new position at relay_log_file='./db1-relay.064772', relay_log_pos='8558451', master_log_name='db2-binary.165903', master_log_pos='8558151' 2024-07-01 5:10:55 11 [ERROR] mariadbd: Can't find record in 'activesessions' 2024-07-01 5:10:55 11 [ERROR] Slave SQL: Could not execute Delete_rows_v1 event on table aaadb.activesessions; Can't find record in 'activesessions', Error_code: 1032; handler error HA_ERR_KEY_NOT_FOUND; the event's master log db2-binary.165903, end_log_pos 8806991, Gtid 0-2-18666143600, Internal MariaDB error code: 1032 2024-07-01 5:10:55 11 [Warning] Slave: Can't find record in 'activesessions' Error_code: 1032 2024-07-01 5:10:55 11 [ERROR] Error running query, slave SQL thread aborted. Fix the problem, and restart the slave SQL thread with "SLAVE START". We stopped at log 'db2-binary.165903' position 8806304 2024-07-01 5:10:55 14 [ERROR] Slave (additional info): Commit failed due to failure of an earlier commit on which this one depends Error_code: 1964 2024-07-01 5:10:55 14 [Warning] Slave: Commit failed due to failure of an earlier commit on which this one depends Error_code: 1964 2024-07-01 5:10:55 14 [ERROR] Error running query, slave SQL thread aborted. Fix the problem, and restart the slave SQL thread with "SLAVE START". We stopped at log 'db2-binary.165903' position 8806304 2024-07-01 5:10:55 10 [ERROR] Slave (additional info): Commit failed due to failure of an earlier commit on which this one depends Error_code: 1964 2024-07-01 5:10:55 10 [Warning] Slave: Commit failed due to failure of an earlier commit on which this one depends Error_code: 1964 2024-07-01 5:10:55 10 [ERROR] Error running query, slave SQL thread aborted. Fix the problem, and restart the slave SQL thread with "SLAVE START". We stopped at log 'db2-binary.165903' position 8806304 2024-07-01 5:10:55 15 [ERROR] Slave (additional info): Commit failed due to failure of an earlier commit on which this one depends Error_code: 1964 2024-07-01 5:10:55 15 [Warning] Slave: Commit failed due to failure of an earlier commit on which this one depends Error_code: 1964 2024-07-01 5:10:55 15 [ERROR] Error running query, slave SQL thread aborted. Fix the problem, and restart the slave SQL thread with "SLAVE START". We stopped at log 'db2-binary.165903' position 8806304 2024-07-01 5:10:55 6 [ERROR] Slave (additional info): Commit failed due to failure of an earlier commit on which this one depends Error_code: 1964 2024-07-01 5:10:55 6 [Warning] Slave: Commit failed due to failure of an earlier commit on which this one depends Error_code: 1964 2024-07-01 5:10:55 6 [ERROR] Error running query, slave SQL thread aborted. Fix the problem, and restart the slave SQL thread with "SLAVE START". We stopped at log 'db2-binary.165903' position 8806304 2024-07-01 5:10:55 7 [ERROR] Slave (additional info): Commit failed due to failure of an earlier commit on which this one depends Error_code: 1964 2024-07-01 5:10:55 7 [Warning] Slave: Commit failed due to failure of an earlier commit on which this one depends Error_code: 1964 2024-07-01 5:10:55 7 [ERROR] Error running query, slave SQL thread aborted. Fix the problem, and restart the slave SQL thread with "SLAVE START". We stopped at log 'db2-binary.165903' position 8806304 2024-07-01 5:10:55 17 [ERROR] Slave (additional info): Commit failed due to failure of an earlier commit on which this one depends Error_code: 1964 2024-07-01 5:10:55 17 [Warning] Slave: Commit failed due to failure of an earlier commit on which this one depends Error_code: 1964 2024-07-01 5:10:55 17 [ERROR] Error running query, slave SQL thread aborted. Fix the problem, and restart the slave SQL thread with "SLAVE START". We stopped at log 'db2-binary.165903' position 8806304 2024-07-01 5:10:55 8 [ERROR] Slave (additional info): Commit failed due to failure of an earlier commit on which this one depends Error_code: 1964 2024-07-01 5:10:55 8 [Warning] Slave: Commit failed due to failure of an earlier commit on which this one depends Error_code: 1964 2024-07-01 5:10:55 8 [ERROR] Error running query, slave SQL thread aborted. Fix the problem, and restart the slave SQL thread with "SLAVE START". We stopped at log 'db2-binary.165903' position 8806304 2024-07-01 5:10:55 9 [ERROR] Slave (additional info): Commit failed due to failure of an earlier commit on which this one depends Error_code: 1964 2024-07-01 5:10:55 9 [Warning] Slave: Commit failed due to failure of an earlier commit on which this one depends Error_code: 1964 2024-07-01 5:10:55 9 [ERROR] Error running query, slave SQL thread aborted. Fix the problem, and restart the slave SQL thread with "SLAVE START". We stopped at log 'db2-binary.165903' position 8806304 2024-07-01 5:10:55 12 [ERROR] Slave (additional info): Commit failed due to failure of an earlier commit on which this one depends Error_code: 1964 2024-07-01 5:10:55 12 [Warning] Slave: Commit failed due to failure of an earlier commit on which this one depends Error_code: 1964 2024-07-01 5:10:55 12 [ERROR] Error running query, slave SQL thread aborted. Fix the problem, and restart the slave SQL thread with "SLAVE START". We stopped at log 'db2-binary.165903' position 8806304 2024-07-01 5:10:55 16 [ERROR] Slave (additional info): Commit failed due to failure of an earlier commit on which this one depends Error_code: 1964 2024-07-01 5:10:55 16 [Warning] Slave: Commit failed due to failure of an earlier commit on which this one depends Error_code: 1964 2024-07-01 5:10:55 16 [ERROR] Error running query, slave SQL thread aborted. Fix the problem, and restart the slave SQL thread with "SLAVE START". We stopped at log 'db2-binary.165903' position 8806304 2024-07-01 5:10:55 13 [ERROR] Slave (additional info): Commit failed due to failure of an earlier commit on which this one depends Error_code: 1964 2024-07-01 5:10:55 13 [Warning] Slave: Commit failed due to failure of an earlier commit on which this one depends Error_code: 1964 2024-07-01 5:10:55 13 [ERROR] Error running query, slave SQL thread aborted. Fix the problem, and restart the slave SQL thread with "SLAVE START". We stopped at log 'db2-binary.165903' position 8806304 2024-07-01 5:10:55 131337 [Note] Slave SQL thread exiting, replication stopped in log 'db2-binary.165903' at position 8806304, master: 10.76.24.77:3306 2024-07-01 5:12:07 131336 [Note] Slave I/O thread exiting, read up to log 'db2-binary.165905', position 201282764, master 10.76.24.77:3306 2024-07-01 5:12:07 131394 [Note] Slave I/O thread: Start asynchronous replication to master 'gtid@10.76.24.77:3306' in log 'db2-binary.165905' at position 201282764 2024-07-01 5:12:07 131395 [Note] Slave SQL thread initialized, starting replication in log 'db2-binary.165903' at position 8806304, relay log './db1-relay.064772' position: 8806604 2024-07-01 5:12:07 131394 [Note] Slave I/O thread: connected to master 'gtid@10.76.24.77:3306',replication started in log 'db2-binary.165905' at position 201282764 2024-07-01 5:12:07 131395 [Note] 'SQL_SLAVE_SKIP_COUNTER=100' executed at relay_log_file='./db1-relay.064772', relay_log_pos='8806604', master_log_name='db2-binary.165903', master_log_pos='8806304' and new position at relay_log_file='./db1-relay.064772', relay_log_pos='8826726', master_log_name='db2-binary.165903', master_log_pos='8826426' 2024-07-01 5:12:07 9 [ERROR] mariadbd: Can't find record in 'activesessions' 2024-07-01 5:12:07 9 [ERROR] Slave SQL: Could not execute Delete_rows_v1 event on table aaadb.activesessions; Can't find record in 'activesessions', Error_code: 1032; handler error HA_ERR_KEY_NOT_FOUND; the event's master log db2-binary.165903, end_log_pos 8879092, Gtid 0-2-18666143664, Internal MariaDB error code: 1032 2024-07-01 5:12:07 9 [Warning] Slave: Can't find record in 'activesessions' Error_code: 1032 2024-07-01 5:12:07 9 [ERROR] Error running query, slave SQL thread aborted. Fix the problem, and restart the slave SQL thread with "SLAVE START". We stopped at log 'db2-binary.165903' position 8878399 2024-07-01 5:12:07 8 [ERROR] Slave (additional info): Commit failed due to failure of an earlier commit on which this one depends Error_code: 1964 2024-07-01 5:12:07 8 [Warning] Slave: Record has changed since last read in table 'activesessions' Error_code: 1020 2024-07-01 5:12:07 8 [Warning] Slave: Deadlock found when trying to get lock; try restarting transaction Error_code: 1213 2024-07-01 5:12:07 8 [Warning] Slave: Commit failed due to failure of an earlier commit on which this one depends Error_code: 1964 2024-07-01 5:12:07 8 [ERROR] Error running query, slave SQL thread aborted. Fix the problem, and restart the slave SQL thread with "SLAVE START". We stopped at log 'db2-binary.165903' position 8878399 2024-07-01 5:12:07 17 [ERROR] Slave (additional info): Commit failed due to failure of an earlier commit on which this one depends Error_code: 1964 2024-07-01 5:12:07 17 [Warning] Slave: Commit failed due to failure of an earlier commit on which this one depends Error_code: 1964 2024-07-01 5:12:07 17 [ERROR] Error running query, slave SQL thread aborted. Fix the problem, and restart the slave SQL thread with "SLAVE START". We stopped at log 'db2-binary.165903' position 8878399 2024-07-01 5:12:07 7 [ERROR] Slave (additional info): Commit failed due to failure of an earlier commit on which this one depends Error_code: 1964 2024-07-01 5:12:07 7 [Warning] Slave: Commit failed due to failure of an earlier commit on which this one depends Error_code: 1964 2024-07-01 5:12:07 7 [ERROR] Error running query, slave SQL thread aborted. Fix the problem, and restart the slave SQL thread with "SLAVE START". We stopped at log 'db2-binary.165903' position 8878399 2024-07-01 5:12:07 6 [ERROR] Slave (additional info): Commit failed due to failure of an earlier commit on which this one depends Error_code: 1964 2024-07-01 5:12:07 6 [Warning] Slave: Record has changed since last read in table 'activesessions' Error_code: 1020 2024-07-01 5:12:07 6 [Warning] Slave: Deadlock found when trying to get lock; try restarting transaction Error_code: 1213 2024-07-01 5:12:07 6 [Warning] Slave: Commit failed due to failure of an earlier commit on which this one depends Error_code: 1964 2024-07-01 5:12:07 6 [ERROR] Error running query, slave SQL thread aborted. Fix the problem, and restart the slave SQL thread with "SLAVE START". We stopped at log 'db2-binary.165903' position 8878399 2024-07-01 5:12:07 15 [ERROR] Slave (additional info): Commit failed due to failure of an earlier commit on which this one depends Error_code: 1964 2024-07-01 5:12:07 15 [Warning] Slave: Commit failed due to failure of an earlier commit on which this one depends Error_code: 1964 2024-07-01 5:12:07 15 [ERROR] Error running query, slave SQL thread aborted. Fix the problem, and restart the slave SQL thread with "SLAVE START". We stopped at log 'db2-binary.165903' position 8878399 2024-07-01 5:12:07 10 [ERROR] Slave (additional info): Commit failed due to failure of an earlier commit on which this one depends Error_code: 1964 2024-07-01 5:12:07 10 [Warning] Slave: Commit failed due to failure of an earlier commit on which this one depends Error_code: 1964 2024-07-01 5:12:07 10 [ERROR] Error running query, slave SQL thread aborted. Fix the problem, and restart the slave SQL thread with "SLAVE START". We stopped at log 'db2-binary.165903' position 8878399 2024-07-01 5:12:07 14 [ERROR] Slave (additional info): Commit failed due to failure of an earlier commit on which this one depends Error_code: 1964 2024-07-01 5:12:07 14 [Warning] Slave: Commit failed due to failure of an earlier commit on which this one depends Error_code: 1964 2024-07-01 5:12:07 14 [ERROR] Error running query, slave SQL thread aborted. Fix the problem, and restart the slave SQL thread with "SLAVE START". We stopped at log 'db2-binary.165903' position 8878399 2024-07-01 5:12:07 11 [ERROR] Slave (additional info): Commit failed due to failure of an earlier commit on which this one depends Error_code: 1964 2024-07-01 5:12:07 11 [Warning] Slave: Commit failed due to failure of an earlier commit on which this one depends Error_code: 1964 2024-07-01 5:12:07 11 [ERROR] Error running query, slave SQL thread aborted. Fix the problem, and restart the slave SQL thread with "SLAVE START". We stopped at log 'db2-binary.165903' position 8878399 2024-07-01 5:12:07 13 [ERROR] Slave (additional info): Commit failed due to failure of an earlier commit on which this one depends Error_code: 1964 2024-07-01 5:12:07 13 [Warning] Slave: Commit failed due to failure of an earlier commit on which this one depends Error_code: 1964 2024-07-01 5:12:07 13 [ERROR] Error running query, slave SQL thread aborted. Fix the problem, and restart the slave SQL thread with "SLAVE START". We stopped at log 'db2-binary.165903' position 8878399 2024-07-01 5:12:07 16 [ERROR] Slave (additional info): Commit failed due to failure of an earlier commit on which this one depends Error_code: 1964 2024-07-01 5:12:07 16 [Warning] Slave: Commit failed due to failure of an earlier commit on which this one depends Error_code: 1964 2024-07-01 5:12:07 16 [ERROR] Error running query, slave SQL thread aborted. Fix the problem, and restart the slave SQL thread with "SLAVE START". We stopped at log 'db2-binary.165903' position 8878399 2024-07-01 5:12:07 12 [ERROR] Slave (additional info): Commit failed due to failure of an earlier commit on which this one depends Error_code: 1964 2024-07-01 5:12:07 12 [Warning] Slave: Commit failed due to failure of an earlier commit on which this one depends Error_code: 1964 2024-07-01 5:12:07 12 [ERROR] Error running query, slave SQL thread aborted. Fix the problem, and restart the slave SQL thread with "SLAVE START". We stopped at log 'db2-binary.165903' position 8878399 2024-07-01 5:12:07 131395 [Note] Slave SQL thread exiting, replication stopped in log 'db2-binary.165903' at position 8878399, master: 10.76.24.77:3306 2024-07-01 5:12:15 131394 [Note] Slave I/O thread exiting, read up to log 'db2-binary.165906', position 2883862, master 10.76.24.77:3306 2024-07-01 5:12:15 131402 [Note] Slave I/O thread: Start asynchronous replication to master 'gtid@10.76.24.77:3306' in log 'db2-binary.165906' at position 2883862 2024-07-01 5:12:15 131403 [Note] Slave SQL thread initialized, starting replication in log 'db2-binary.165903' at position 8878399, relay log './db1-relay.064772' position: 8878699 2024-07-01 5:12:15 131402 [Note] Slave I/O thread: connected to master 'gtid@10.76.24.77:3306',replication started in log 'db2-binary.165906' at position 2883862 2024-07-01 5:12:15 131403 [Note] 'SQL_SLAVE_SKIP_COUNTER=100' executed at relay_log_file='./db1-relay.064772', relay_log_pos='8878699', master_log_name='db2-binary.165903', master_log_pos='8878399' and new position at relay_log_file='./db1-relay.064772', relay_log_pos='8895786', master_log_name='db2-binary.165903', master_log_pos='8895486' 2024-07-01 5:12:15 6 [ERROR] mariadbd: Can't find record in 'activesessions' 2024-07-01 5:12:15 6 [ERROR] Slave SQL: Could not execute Delete_rows_v1 event on table aaadb.activesessions; Can't find record in 'activesessions', Error_code: 1032; handler error HA_ERR_KEY_NOT_FOUND; the event's master log db2-binary.165903, end_log_pos 8898447, Gtid 0-2-18666143687, Internal MariaDB error code: 1032 2024-07-01 5:12:15 6 [Warning] Slave: Can't find record in 'activesessions' Error_code: 1032 2024-07-01 5:12:15 6 [ERROR] Error running query, slave SQL thread aborted. Fix the problem, and restart the slave SQL thread with "SLAVE START". We stopped at log 'db2-binary.165903' position 8897705 2024-07-01 5:12:15 7 [ERROR] Slave (additional info): Commit failed due to failure of an earlier commit on which this one depends Error_code: 1964 2024-07-01 5:12:15 7 [Warning] Slave: Commit failed due to failure of an earlier commit on which this one depends Error_code: 1964 2024-07-01 5:12:15 7 [ERROR] Error running query, slave SQL thread aborted. Fix the problem, and restart the slave SQL thread with "SLAVE START". We stopped at log 'db2-binary.165903' position 8897705 2024-07-01 5:12:15 17 [ERROR] Slave (additional info): Commit failed due to failure of an earlier commit on which this one depends Error_code: 1964 2024-07-01 5:12:15 17 [Warning] Slave: Commit failed due to failure of an earlier commit on which this one depends Error_code: 1964 2024-07-01 5:12:15 17 [ERROR] Error running query, slave SQL thread aborted. Fix the problem, and restart the slave SQL thread with "SLAVE START". We stopped at log 'db2-binary.165903' position 8897705 2024-07-01 5:12:15 8 [ERROR] Slave (additional info): Commit failed due to failure of an earlier commit on which this one depends Error_code: 1964 2024-07-01 5:12:15 8 [Warning] Slave: Commit failed due to failure of an earlier commit on which this one depends Error_code: 1964 2024-07-01 5:12:15 8 [ERROR] Error running query, slave SQL thread aborted. Fix the problem, and restart the slave SQL thread with "SLAVE START". We stopped at log 'db2-binary.165903' position 8897705 2024-07-01 5:12:15 9 [ERROR] Slave (additional info): Commit failed due to failure of an earlier commit on which this one depends Error_code: 1964 2024-07-01 5:12:15 9 [Warning] Slave: Commit failed due to failure of an earlier commit on which this one depends Error_code: 1964 2024-07-01 5:12:15 9 [ERROR] Error running query, slave SQL thread aborted. Fix the problem, and restart the slave SQL thread with "SLAVE START". We stopped at log 'db2-binary.165903' position 8897705 2024-07-01 5:12:15 12 [ERROR] Slave (additional info): Commit failed due to failure of an earlier commit on which this one depends Error_code: 1964 2024-07-01 5:12:15 12 [Warning] Slave: Commit failed due to failure of an earlier commit on which this one depends Error_code: 1964 2024-07-01 5:12:15 12 [ERROR] Error running query, slave SQL thread aborted. Fix the problem, and restart the slave SQL thread with "SLAVE START". We stopped at log 'db2-binary.165903' position 8897705 2024-07-01 5:12:15 16 [ERROR] Slave (additional info): Commit failed due to failure of an earlier commit on which this one depends Error_code: 1964 2024-07-01 5:12:15 16 [Warning] Slave: Commit failed due to failure of an earlier commit on which this one depends Error_code: 1964 2024-07-01 5:12:15 16 [ERROR] Error running query, slave SQL thread aborted. Fix the problem, and restart the slave SQL thread with "SLAVE START". We stopped at log 'db2-binary.165903' position 8897705 2024-07-01 5:12:15 13 [ERROR] Slave (additional info): Commit failed due to failure of an earlier commit on which this one depends Error_code: 1964 2024-07-01 5:12:15 13 [Warning] Slave: Commit failed due to failure of an earlier commit on which this one depends Error_code: 1964 2024-07-01 5:12:15 13 [ERROR] Error running query, slave SQL thread aborted. Fix the problem, and restart the slave SQL thread with "SLAVE START". We stopped at log 'db2-binary.165903' position 8897705 2024-07-01 5:12:15 11 [ERROR] Slave (additional info): Commit failed due to failure of an earlier commit on which this one depends Error_code: 1964 2024-07-01 5:12:15 11 [Warning] Slave: Commit failed due to failure of an earlier commit on which this one depends Error_code: 1964 2024-07-01 5:12:15 11 [ERROR] Error running query, slave SQL thread aborted. Fix the problem, and restart the slave SQL thread with "SLAVE START". We stopped at log 'db2-binary.165903' position 8897705 2024-07-01 5:12:15 14 [ERROR] Slave (additional info): Commit failed due to failure of an earlier commit on which this one depends Error_code: 1964 2024-07-01 5:12:15 14 [Warning] Slave: Commit failed due to failure of an earlier commit on which this one depends Error_code: 1964 2024-07-01 5:12:15 14 [ERROR] Error running query, slave SQL thread aborted. Fix the problem, and restart the slave SQL thread with "SLAVE START". We stopped at log 'db2-binary.165903' position 8897705 2024-07-01 5:12:15 10 [ERROR] Slave (additional info): Commit failed due to failure of an earlier commit on which this one depends Error_code: 1964 2024-07-01 5:12:15 10 [Warning] Slave: Commit failed due to failure of an earlier commit on which this one depends Error_code: 1964 2024-07-01 5:12:15 10 [ERROR] Error running query, slave SQL thread aborted. Fix the problem, and restart the slave SQL thread with "SLAVE START". We stopped at log 'db2-binary.165903' position 8897705 2024-07-01 5:12:15 15 [ERROR] Slave (additional info): Commit failed due to failure of an earlier commit on which this one depends Error_code: 1964 2024-07-01 5:12:15 15 [Warning] Slave: Commit failed due to failure of an earlier commit on which this one depends Error_code: 1964 2024-07-01 5:12:15 15 [ERROR] Error running query, slave SQL thread aborted. Fix the problem, and restart the slave SQL thread with "SLAVE START". We stopped at log 'db2-binary.165903' position 8897705 2024-07-01 5:12:15 131403 [Note] Slave SQL thread exiting, replication stopped in log 'db2-binary.165903' at position 8897705, master: 10.76.24.77:3306 2024-07-01 5:12:31 131402 [Note] Slave I/O thread exiting, read up to log 'db2-binary.165906', position 27741300, master 10.76.24.77:3306 2024-07-01 5:12:31 131417 [Note] Slave I/O thread: Start asynchronous replication to master 'gtid@10.76.24.77:3306' in log 'db2-binary.165906' at position 27741300 2024-07-01 5:12:31 131418 [Note] Slave SQL thread initialized, starting replication in log 'db2-binary.165903' at position 8897705, relay log './db1-relay.064772' position: 8898005 2024-07-01 5:12:31 131417 [Note] Slave I/O thread: connected to master 'gtid@10.76.24.77:3306',replication started in log 'db2-binary.165906' at position 27741300 2024-07-01 5:12:31 131418 [Note] 'SQL_SLAVE_SKIP_COUNTER=100' executed at relay_log_file='./db1-relay.064772', relay_log_pos='8898005', master_log_name='db2-binary.165903', master_log_pos='8897705' and new position at relay_log_file='./db1-relay.064772', relay_log_pos='8916277', master_log_name='db2-binary.165903', master_log_pos='8915977' 2024-07-01 5:12:31 16 [ERROR] mariadbd: Can't find record in 'activesessions' 2024-07-01 5:12:31 16 [ERROR] Slave SQL: Could not execute Delete_rows_v1 event on table aaadb.activesessions; Can't find record in 'activesessions', Error_code: 1032; handler error HA_ERR_KEY_NOT_FOUND; the event's master log db2-binary.165903, end_log_pos 8930123, Gtid 0-2-18666143722, Internal MariaDB error code: 1032 2024-07-01 5:12:31 16 [Warning] Slave: Can't find record in 'activesessions' Error_code: 1032 2024-07-01 5:12:31 16 [ERROR] Error running query, slave SQL thread aborted. Fix the problem, and restart the slave SQL thread with "SLAVE START". We stopped at log 'db2-binary.165903' position 8929398 2024-07-01 5:12:31 12 [ERROR] Slave (additional info): Commit failed due to failure of an earlier commit on which this one depends Error_code: 1964 2024-07-01 5:12:31 12 [Warning] Slave: Commit failed due to failure of an earlier commit on which this one depends Error_code: 1964 2024-07-01 5:12:31 12 [ERROR] Error running query, slave SQL thread aborted. Fix the problem, and restart the slave SQL thread with "SLAVE START". We stopped at log 'db2-binary.165903' position 8929398 2024-07-01 5:12:31 9 [ERROR] Slave (additional info): Commit failed due to failure of an earlier commit on which this one depends Error_code: 1964 2024-07-01 5:12:31 9 [Warning] Slave: Commit failed due to failure of an earlier commit on which this one depends Error_code: 1964 2024-07-01 5:12:31 9 [ERROR] Error running query, slave SQL thread aborted. Fix the problem, and restart the slave SQL thread with "SLAVE START". We stopped at log 'db2-binary.165903' position 8929398 2024-07-01 5:12:31 8 [ERROR] Slave (additional info): Commit failed due to failure of an earlier commit on which this one depends Error_code: 1964 2024-07-01 5:12:31 8 [Warning] Slave: Commit failed due to failure of an earlier commit on which this one depends Error_code: 1964 2024-07-01 5:12:31 8 [ERROR] Error running query, slave SQL thread aborted. Fix the problem, and restart the slave SQL thread with "SLAVE START". We stopped at log 'db2-binary.165903' position 8929398 2024-07-01 5:12:31 17 [ERROR] Slave (additional info): Commit failed due to failure of an earlier commit on which this one depends Error_code: 1964 2024-07-01 5:12:31 17 [Warning] Slave: Commit failed due to failure of an earlier commit on which this one depends Error_code: 1964 2024-07-01 5:12:31 17 [ERROR] Error running query, slave SQL thread aborted. Fix the problem, and restart the slave SQL thread with "SLAVE START". We stopped at log 'db2-binary.165903' position 8929398 2024-07-01 5:12:31 7 [ERROR] Slave (additional info): Commit failed due to failure of an earlier commit on which this one depends Error_code: 1964 2024-07-01 5:12:31 7 [Warning] Slave: Commit failed due to failure of an earlier commit on which this one depends Error_code: 1964 2024-07-01 5:12:31 7 [ERROR] Error running query, slave SQL thread aborted. Fix the problem, and restart the slave SQL thread with "SLAVE START". We stopped at log 'db2-binary.165903' position 8929398 2024-07-01 5:12:31 6 [ERROR] Slave (additional info): Commit failed due to failure of an earlier commit on which this one depends Error_code: 1964 2024-07-01 5:12:31 6 [Warning] Slave: Commit failed due to failure of an earlier commit on which this one depends Error_code: 1964 2024-07-01 5:12:31 6 [ERROR] Error running query, slave SQL thread aborted. Fix the problem, and restart the slave SQL thread with "SLAVE START". We stopped at log 'db2-binary.165903' position 8929398 2024-07-01 5:12:31 15 [ERROR] Slave (additional info): Commit failed due to failure of an earlier commit on which this one depends Error_code: 1964 2024-07-01 5:12:31 15 [Warning] Slave: Commit failed due to failure of an earlier commit on which this one depends Error_code: 1964 2024-07-01 5:12:31 15 [ERROR] Error running query, slave SQL thread aborted. Fix the problem, and restart the slave SQL thread with "SLAVE START". We stopped at log 'db2-binary.165903' position 8929398 2024-07-01 5:12:31 10 [ERROR] Slave (additional info): Commit failed due to failure of an earlier commit on which this one depends Error_code: 1964 2024-07-01 5:12:31 10 [Warning] Slave: Commit failed due to failure of an earlier commit on which this one depends Error_code: 1964 2024-07-01 5:12:31 10 [ERROR] Error running query, slave SQL thread aborted. Fix the problem, and restart the slave SQL thread with "SLAVE START". We stopped at log 'db2-binary.165903' position 8929398 2024-07-01 5:12:31 14 [ERROR] Slave (additional info): Commit failed due to failure of an earlier commit on which this one depends Error_code: 1964 2024-07-01 5:12:31 14 [Warning] Slave: Commit failed due to failure of an earlier commit on which this one depends Error_code: 1964 2024-07-01 5:12:31 14 [ERROR] Error running query, slave SQL thread aborted. Fix the problem, and restart the slave SQL thread with "SLAVE START". We stopped at log 'db2-binary.165903' position 8929398 2024-07-01 5:12:31 11 [ERROR] Slave (additional info): Commit failed due to failure of an earlier commit on which this one depends Error_code: 1964 2024-07-01 5:12:31 11 [Warning] Slave: Commit failed due to failure of an earlier commit on which this one depends Error_code: 1964 2024-07-01 5:12:31 11 [ERROR] Error running query, slave SQL thread aborted. Fix the problem, and restart the slave SQL thread with "SLAVE START". We stopped at log 'db2-binary.165903' position 8929398 2024-07-01 5:12:31 13 [ERROR] Slave (additional info): Commit failed due to failure of an earlier commit on which this one depends Error_code: 1964 2024-07-01 5:12:31 13 [Warning] Slave: Commit failed due to failure of an earlier commit on which this one depends Error_code: 1964 2024-07-01 5:12:31 13 [ERROR] Error running query, slave SQL thread aborted. Fix the problem, and restart the slave SQL thread with "SLAVE START". We stopped at log 'db2-binary.165903' position 8929398 2024-07-01 5:12:31 131418 [Note] Slave SQL thread exiting, replication stopped in log 'db2-binary.165903' at position 8929398, master: 10.76.24.77:3306 2024-07-01 5:12:57 131417 [Note] Slave I/O thread exiting, read up to log 'db2-binary.165906', position 67350380, master 10.76.24.77:3306 2024-07-01 5:12:57 131437 [Note] Slave I/O thread: Start asynchronous replication to master 'gtid@10.76.24.77:3306' in log 'db2-binary.165906' at position 67350380 2024-07-01 5:12:57 131438 [Note] Slave SQL thread initialized, starting replication in log 'db2-binary.165903' at position 8929398, relay log './db1-relay.064772' position: 8929698 2024-07-01 5:12:57 131437 [Note] Slave I/O thread: connected to master 'gtid@10.76.24.77:3306',replication started in log 'db2-binary.165906' at position 67350380 2024-07-01 5:12:57 131438 [Note] 'SQL_SLAVE_SKIP_COUNTER=100' executed at relay_log_file='./db1-relay.064772', relay_log_pos='8929698', master_log_name='db2-binary.165903', master_log_pos='8929398' and new position at relay_log_file='./db1-relay.064772', relay_log_pos='8959852', master_log_name='db2-binary.165903', master_log_pos='8959552' 2024-07-01 5:12:57 17 [ERROR] mariadbd: Can't find record in 'activesessions' 2024-07-01 5:12:57 17 [Warning] Slave SQL: Could not execute Delete_rows_v1 event on table aaadb.activesessions; Can't find record in 'activesessions', Error_code: 1032; handler error HA_ERR_KEY_NOT_FOUND; the event's master log db2-binary.165903, end_log_pos 8960307, Gtid 0-2-18666143742, Internal MariaDB error code: 1032 2024-07-01 9:56:14 586303 [Warning] Aborted connection 586303 to db: 'unconnected' user: 'root' host: 'localhost' (Got an error reading communication packets) 2024-07-01 10:02:32 131438 [Note] Error reading relay log event: slave SQL thread was killed 2024-07-01 10:02:32 131438 [Note] Slave SQL thread exiting, replication stopped in log 'db2-binary.166042' at position 73517646, master: 10.76.24.77:3306 2024-07-01 10:02:32 131437 [Note] Slave I/O thread exiting, read up to log 'db2-binary.166042', position 73517646, master 10.76.24.77:3306 2024-07-01 10:02:43 610761 [Note] Master connection name: '' Master_info_file: 'master.info' Relay_info_file: 'relay-log.info' 2024-07-01 10:02:43 610761 [Note] 'CHANGE MASTER TO executed'. Previous state master_host='10.76.24.77', master_port='3306', master_log_file='db2-binary.166042', master_log_pos='73517646'. New state master_host='10.76.24.77', master_port='3306', master_log_file='db2-binary.166042', master_log_pos='73517646'. 2024-07-01 10:02:47 627336 [Note] Slave I/O thread: Start asynchronous replication to master 'gtid@10.76.24.77:3306' in log 'db2-binary.166042' at position 73517646 2024-07-01 10:02:47 627337 [Note] Slave SQL thread initialized, starting replication in log 'db2-binary.166042' at position 73517646, relay log './db1-relay.063685' position: 4 2024-07-01 10:02:47 627336 [Note] Slave I/O thread: connected to master 'gtid@10.76.24.77:3306',replication started in log 'db2-binary.166042' at position 73517646 2024-07-02 7:44:30 627336 [ERROR] Error reading packet from server: Lost connection to server during query (server_errno=2013) 2024-07-02 7:44:30 627336 [Note] Slave I/O thread: Failed reading log event, reconnecting to retry, log 'db2-binary.166681' at position 26398943 2024-07-02 7:44:30 627336 [ERROR] Slave I/O: error reconnecting to master 'gtid@10.76.24.77:3306' - retry-time: 60 maximum-retries: 100000 message: Can't connect to server on '10.76.24.77' (111 "Connection refused"), Internal MariaDB error code: 2003 2024-07-02 7:44:33 100275 [Warning] Aborted connection 100275 to db: 'unconnected' user: 'gtid' host: '10.76.24.77' (Got an error writing communication packets) 2024-07-02 7:45:01 2914152 [Note] Start binlog_dump to slave_server(2), pos(db1-binary.165919, 134384110), using_gtid(0), gtid('') 2024-07-02 7:45:30 627336 [Note] Slave: connected to master 'gtid@10.76.24.77:3306',replication resumed in log 'db2-binary.166681' at position 26398943 2024-07-02 9:11:28 2914152 [Warning] Aborted connection 2914152 to db: 'unconnected' user: 'gtid' host: '10.76.24.77' (Got an error writing communication packets) 2024-07-02 9:11:28 2986552 [Note] Start binlog_dump to slave_server(2), pos(db1-binary.165961, 130356238), using_gtid(0), gtid('') 2024-07-02 9:19:54 2986552 [Warning] Aborted connection 2986552 to db: 'unconnected' user: 'gtid' host: '10.76.24.77' (Got an error writing communication packets) 2024-07-02 9:19:54 2993784 [Note] Start binlog_dump to slave_server(2), pos(db1-binary.165965, 174460872), using_gtid(0), gtid('') 2024-07-02 9:20:26 2993784 [Warning] Aborted connection 2993784 to db: 'unconnected' user: 'gtid' host: '10.76.24.77' (Got an error writing communication packets) 2024-07-02 9:20:26 2994348 [Note] Start binlog_dump to slave_server(2), pos(db1-binary.165966, 19690790), using_gtid(0), gtid('') 2024-07-02 9:20:35 2994348 [Warning] Aborted connection 2994348 to db: 'unconnected' user: 'gtid' host: '10.76.24.77' (Got an error writing communication packets) 2024-07-02 9:20:35 2994477 [Note] Start binlog_dump to slave_server(2), pos(db1-binary.165966, 35824285), using_gtid(0), gtid('') 2024-07-02 9:20:48 2994477 [Warning] Aborted connection 2994477 to db: 'unconnected' user: 'gtid' host: '10.76.24.77' (Got an error writing communication packets) 2024-07-02 9:20:48 2994657 [Note] Start binlog_dump to slave_server(2), pos(db1-binary.165966, 57508761), using_gtid(0), gtid('') 2024-07-02 9:21:05 2994657 [Warning] Aborted connection 2994657 to db: 'unconnected' user: 'gtid' host: '10.76.24.77' (Got an error writing communication packets) 2024-07-02 9:21:05 2994907 [Note] Start binlog_dump to slave_server(2), pos(db1-binary.165966, 87239218), using_gtid(0), gtid('') 2024-07-02 9:21:22 2994907 [Warning] Aborted connection 2994907 to db: 'unconnected' user: 'gtid' host: '10.76.24.77' (Got an error writing communication packets) 2024-07-02 9:21:22 2995144 [Note] Start binlog_dump to slave_server(2), pos(db1-binary.165966, 114945604), using_gtid(0), gtid('') 2024-07-02 9:22:04 2995144 [Warning] Aborted connection 2995144 to db: 'unconnected' user: 'gtid' host: '10.76.24.77' (Got an error writing communication packets) 2024-07-02 9:22:04 2995763 [Note] Start binlog_dump to slave_server(2), pos(db1-binary.165966, 189184273), using_gtid(0), gtid('') 2024-07-02 9:22:28 2995763 [Warning] Aborted connection 2995763 to db: 'unconnected' user: 'gtid' host: '10.76.24.77' (Got an error writing communication packets) 2024-07-02 9:22:28 2996103 [Note] Start binlog_dump to slave_server(2), pos(db1-binary.165967, 19304757), using_gtid(0), gtid('') 2024-07-02 9:22:52 2996103 [Warning] Aborted connection 2996103 to db: 'unconnected' user: 'gtid' host: '10.76.24.77' (Got an error writing communication packets) 2024-07-02 9:22:52 2996449 [Note] Start binlog_dump to slave_server(2), pos(db1-binary.165967, 61246253), using_gtid(0), gtid('') 2024-07-02 9:23:00 2996449 [Warning] Aborted connection 2996449 to db: 'unconnected' user: 'gtid' host: '10.76.24.77' (Got an error writing communication packets) 2024-07-02 9:23:00 2996566 [Note] Start binlog_dump to slave_server(2), pos(db1-binary.165967, 75200733), using_gtid(0), gtid('') 2024-07-02 9:24:39 2996566 [Warning] Aborted connection 2996566 to db: 'unconnected' user: 'gtid' host: '10.76.24.77' (Got an error writing communication packets) 2024-07-02 9:24:39 2997956 [Note] Start binlog_dump to slave_server(2), pos(db1-binary.165968, 32790560), using_gtid(0), gtid('') 2024-07-02 9:26:42 2997956 [Warning] Aborted connection 2997956 to db: 'unconnected' user: 'gtid' host: '10.76.24.77' (Got an error writing communication packets) 2024-07-02 9:26:42 2999697 [Note] Start binlog_dump to slave_server(2), pos(db1-binary.165969, 31686117), using_gtid(0), gtid('') 2024-07-02 9:27:08 2999697 [Warning] Aborted connection 2999697 to db: 'unconnected' user: 'gtid' host: '10.76.24.77' (Got an error writing communication packets) 2024-07-02 9:27:08 3000056 [Note] Start binlog_dump to slave_server(2), pos(db1-binary.165969, 74261672), using_gtid(0), gtid('') 2024-07-02 9:27:33 3000056 [Warning] Aborted connection 3000056 to db: 'unconnected' user: 'gtid' host: '10.76.24.77' (Got an error writing communication packets) 2024-07-02 9:27:33 3000404 [Note] Start binlog_dump to slave_server(2), pos(db1-binary.165969, 115586511), using_gtid(0), gtid('') 2024-07-02 9:28:17 3000404 [Warning] Aborted connection 3000404 to db: 'unconnected' user: 'gtid' host: '10.76.24.77' (Got an error writing communication packets) 2024-07-02 9:28:17 3001026 [Note] Start binlog_dump to slave_server(2), pos(db1-binary.165969, 188966676), using_gtid(0), gtid('') 2024-07-02 9:29:00 3001026 [Warning] Aborted connection 3001026 to db: 'unconnected' user: 'gtid' host: '10.76.24.77' (Got an error writing communication packets) 2024-07-02 9:29:00 3001627 [Note] Start binlog_dump to slave_server(2), pos(db1-binary.165970, 50714159), using_gtid(0), gtid('') 2024-07-02 9:29:37 3001627 [Warning] Aborted connection 3001627 to db: 'unconnected' user: 'gtid' host: '10.76.24.77' (Got an error writing communication packets) 2024-07-02 9:29:37 3002186 [Note] Start binlog_dump to slave_server(2), pos(db1-binary.165970, 117478674), using_gtid(0), gtid('') 2024-07-02 9:31:03 3002186 [Warning] Aborted connection 3002186 to db: 'unconnected' user: 'gtid' host: '10.76.24.77' (Got an error writing communication packets) 2024-07-02 9:31:03 3003345 [Note] Start binlog_dump to slave_server(2), pos(db1-binary.165971, 55842692), using_gtid(0), gtid('') 2024-07-02 9:34:09 3003345 [Warning] Aborted connection 3003345 to db: 'unconnected' user: 'gtid' host: '10.76.24.77' (Got an error writing communication packets) 2024-07-02 9:34:09 3006188 [Note] Start binlog_dump to slave_server(2), pos(db1-binary.165972, 198794508), using_gtid(0), gtid('') 2024-07-02 9:34:34 3006188 [Warning] Aborted connection 3006188 to db: 'unconnected' user: 'gtid' host: '10.76.24.77' (Got an error writing communication packets) 2024-07-02 9:34:34 3006558 [Note] Start binlog_dump to slave_server(2), pos(db1-binary.165973, 37473697), using_gtid(0), gtid('') 2024-07-02 9:38:15 3006558 [Warning] Aborted connection 3006558 to db: 'unconnected' user: 'gtid' host: '10.76.24.77' (Got an error writing communication packets) 2024-07-02 9:38:15 3009732 [Note] Start binlog_dump to slave_server(2), pos(db1-binary.165975, 7146775), using_gtid(0), gtid('') 2024-07-02 9:40:10 3009732 [Warning] Aborted connection 3009732 to db: 'unconnected' user: 'gtid' host: '10.76.24.77' (Got an error writing communication packets) 2024-07-02 9:40:10 3011362 [Note] Start binlog_dump to slave_server(2), pos(db1-binary.165975, 201968007), using_gtid(0), gtid('') 2024-07-02 9:46:04 3011362 [Warning] Aborted connection 3011362 to db: 'unconnected' user: 'gtid' host: '10.76.24.77' (Got an error writing communication packets) 2024-07-02 9:46:04 3016382 [Note] Start binlog_dump to slave_server(2), pos(db1-binary.165978, 179109366), using_gtid(0), gtid('') 2024-07-02 9:47:43 3016382 [Warning] Aborted connection 3016382 to db: 'unconnected' user: 'gtid' host: '10.76.24.77' (Got an error writing communication packets) 2024-07-02 9:47:43 3017898 [Note] Start binlog_dump to slave_server(2), pos(db1-binary.165979, 150173495), using_gtid(0), gtid('') 2024-07-02 9:48:13 3017898 [Warning] Aborted connection 3017898 to db: 'unconnected' user: 'gtid' host: '10.76.24.77' (Got an error writing communication packets) 2024-07-02 9:48:13 3018331 [Note] Start binlog_dump to slave_server(2), pos(db1-binary.165979, 203069441), using_gtid(0), gtid('') 2024-07-02 9:48:58 3018331 [Warning] Aborted connection 3018331 to db: 'unconnected' user: 'gtid' host: '10.76.24.77' (Got an error writing communication packets) 2024-07-02 9:48:58 3018973 [Note] Start binlog_dump to slave_server(2), pos(db1-binary.165980, 72870595), using_gtid(0), gtid('') 2024-07-02 9:49:23 3018973 [Warning] Aborted connection 3018973 to db: 'unconnected' user: 'gtid' host: '10.76.24.77' (Got an error writing communication packets) 2024-07-02 9:49:23 3019346 [Note] Start binlog_dump to slave_server(2), pos(db1-binary.165980, 118171649), using_gtid(0), gtid('') 2024-07-02 9:59:51 3019346 [Warning] Aborted connection 3019346 to db: 'unconnected' user: 'gtid' host: '10.76.24.77' (Got an error writing communication packets) 2024-07-02 9:59:51 3028371 [Note] Start binlog_dump to slave_server(2), pos(db1-binary.165985, 158527763), using_gtid(0), gtid('') 2024-07-02 10:01:31 3028371 [Warning] Aborted connection 3028371 to db: 'unconnected' user: 'gtid' host: '10.76.24.77' (Got an error writing communication packets) 2024-07-02 10:01:31 3029886 [Note] Start binlog_dump to slave_server(2), pos(db1-binary.165986, 133186553), using_gtid(0), gtid('') 2024-07-02 10:05:37 3029886 [Warning] Aborted connection 3029886 to db: 'unconnected' user: 'gtid' host: '10.76.24.77' (Got an error writing communication packets) 2024-07-02 10:05:37 3033818 [Note] Start binlog_dump to slave_server(2), pos(db1-binary.165988, 207281890), using_gtid(0), gtid('') 2024-07-02 10:05:48 3033818 [Warning] Aborted connection 3033818 to db: 'unconnected' user: 'gtid' host: '10.76.24.77' (Got an error writing communication packets) 2024-07-02 10:05:48 3033979 [Note] Start binlog_dump to slave_server(2), pos(db1-binary.165989, 18051386), using_gtid(0), gtid('') 2024-07-02 10:06:09 3033979 [Warning] Aborted connection 3033979 to db: 'unconnected' user: 'gtid' host: '10.76.24.77' (Got an error writing communication packets) 2024-07-02 10:06:09 3034305 [Note] Start binlog_dump to slave_server(2), pos(db1-binary.165989, 58371143), using_gtid(0), gtid('') 2024-07-02 10:09:20 3034305 [Warning] Aborted connection 3034305 to db: 'unconnected' user: 'gtid' host: '10.76.24.77' (Got an error writing communication packets) 2024-07-02 10:09:20 3037081 [Note] Start binlog_dump to slave_server(2), pos(db1-binary.165990, 186463987), using_gtid(0), gtid('') 2024-07-02 10:09:33 3037081 [Warning] Aborted connection 3037081 to db: 'unconnected' user: 'gtid' host: '10.76.24.77' (Got an error writing communication packets) 2024-07-02 10:09:33 3037261 [Note] Start binlog_dump to slave_server(2), pos(db1-binary.165990, 208150745), using_gtid(0), gtid('') 2024-07-02 10:10:01 3037261 [Warning] Aborted connection 3037261 to db: 'unconnected' user: 'gtid' host: '10.76.24.77' (Got an error writing communication packets) 2024-07-02 10:10:01 3037678 [Note] Start binlog_dump to slave_server(2), pos(db1-binary.165991, 49036688), using_gtid(0), gtid('') 2024-07-02 10:10:45 3037678 [Warning] Aborted connection 3037678 to db: 'unconnected' user: 'gtid' host: '10.76.24.77' (Got an error writing communication packets) 2024-07-02 10:10:45 3038295 [Note] Start binlog_dump to slave_server(2), pos(db1-binary.165991, 125119929), using_gtid(0), gtid('') 2024-07-02 10:13:52 3038295 [Warning] Aborted connection 3038295 to db: 'unconnected' user: 'gtid' host: '10.76.24.77' (Got an error writing communication packets) 2024-07-02 10:13:52 3041036 [Note] Start binlog_dump to slave_server(2), pos(db1-binary.165993, 35909399), using_gtid(0), gtid('') 2024-07-02 10:16:20 3041036 [Warning] Aborted connection 3041036 to db: 'unconnected' user: 'gtid' host: '10.76.24.77' (Got an error writing communication packets) 2024-07-02 10:16:20 3043165 [Note] Start binlog_dump to slave_server(2), pos(db1-binary.165994, 82445106), using_gtid(0), gtid('') 2024-07-02 10:16:36 3043165 [Warning] Aborted connection 3043165 to db: 'unconnected' user: 'gtid' host: '10.76.24.77' (Got an error writing communication packets) 2024-07-02 10:16:36 3043387 [Note] Start binlog_dump to slave_server(2), pos(db1-binary.165994, 110247235), using_gtid(0), gtid('') 2024-07-02 10:17:12 3043387 [Warning] Aborted connection 3043387 to db: 'unconnected' user: 'gtid' host: '10.76.24.77' (Got an error writing communication packets) 2024-07-02 10:17:12 3043928 [Note] Start binlog_dump to slave_server(2), pos(db1-binary.165994, 174991259), using_gtid(0), gtid('') 2024-07-02 10:17:30 3043928 [Warning] Aborted connection 3043928 to db: 'unconnected' user: 'gtid' host: '10.76.24.77' (Got an error writing communication packets) 2024-07-02 10:17:30 3044206 [Note] Start binlog_dump to slave_server(2), pos(db1-binary.165994, 208865907), using_gtid(0), gtid('') 2024-07-02 10:31:44 3044206 [Warning] Aborted connection 3044206 to db: 'unconnected' user: 'gtid' host: '10.76.24.77' (Got an error writing communication packets) 2024-07-02 10:31:44 3056411 [Note] Start binlog_dump to slave_server(2), pos(db1-binary.166002, 33315410), using_gtid(0), gtid('') 2024-07-02 10:36:19 3056411 [Warning] Aborted connection 3056411 to db: 'unconnected' user: 'gtid' host: '10.76.24.77' (Got an error writing communication packets) 2024-07-02 10:36:19 3060795 [Note] Start binlog_dump to slave_server(2), pos(db1-binary.166004, 168562866), using_gtid(0), gtid('') 2024-07-02 10:36:26 3060795 [Warning] Aborted connection 3060795 to db: 'unconnected' user: 'gtid' host: '10.76.24.77' (Got an error writing communication packets) 2024-07-02 10:36:26 3060897 [Note] Start binlog_dump to slave_server(2), pos(db1-binary.166004, 180579867), using_gtid(0), gtid('') 2024-07-02 11:46:12 3060897 [Warning] Aborted connection 3060897 to db: 'unconnected' user: 'gtid' host: '10.76.24.77' (Got an error writing communication packets) 2024-07-02 11:47:00 5 [Note] Master 's-db3': Error reading relay log event: slave SQL thread was killed 2024-07-02 11:47:00 5 [Note] Master 's-db3': Slave SQL thread exiting, replication stopped in log 'FIRST' at position 0, master: :3306 2024-07-02 11:47:00 627337 [Note] Error reading relay log event: slave SQL thread was killed 2024-07-02 11:47:00 627337 [Note] Slave SQL thread exiting, replication stopped in log 'db2-binary.166682' at position 87352961, master: 10.76.24.77:3306 2024-07-02 11:47:00 627336 [Note] Slave I/O thread exiting, read up to log 'db2-binary.166682', position 87352961, master 10.76.24.77:3306 2024-07-02 11:47:00 21 [Note] Master 's-db2': Error reading relay log event: slave SQL thread was killed 2024-07-02 11:47:00 21 [Note] Master 's-db2': Slave SQL thread exiting, replication stopped in log 'FIRST' at position 0, master: :3306 2024-07-02 11:47:00 19 [Note] Master 's-db4': Slave SQL thread exiting, replication stopped in log 'db4-binary.143365' at position 87729946, master: 10.76.25.11:3306 2024-07-02 11:47:00 18 [Note] Master 's-db4': Slave I/O thread exiting, read up to log 'db4-binary.143365', position 87730406, master 10.76.25.11:3306 2024-07-02 11:47:00 23 [Note] Master 's-db5': Error reading relay log event: slave SQL thread was killed 2024-07-02 11:47:00 23 [Note] Master 's-db5': Slave SQL thread exiting, replication stopped in log 'FIRST' at position 0, master: :3306 2024-07-02 11:47:49 62 [Warning] Aborted connection 62 to db: 'unconnected' user: 'gtid' host: '10.76.25.11' (Got an error writing communication packets) 2024-07-02 12:48:04 3126250 [Note] Start binlog_dump to slave_server(2), pos(db1-binary.166033, 14358879), using_gtid(0), gtid('') 2024-07-02 13:03:58 3122966 [Note] Master connection name: '' Master_info_file: 'master.info' Relay_info_file: 'relay-log.info' 2024-07-02 13:03:58 3122966 [Note] 'CHANGE MASTER TO executed'. Previous state master_host='10.76.24.77', master_port='3306', master_log_file='db2-binary.166682', master_log_pos='87352961'. New state master_host='10.76.24.77', master_port='3306', master_log_file='db2-binary.167205', master_log_pos='77065552'. 2024-07-02 13:04:39 3122966 [Note] Master connection name: '' Master_info_file: 'master.info' Relay_info_file: 'relay-log.info' 2024-07-02 13:04:39 3122966 [Note] 'CHANGE MASTER TO executed'. Previous state master_host='10.76.24.77', master_port='3306', master_log_file='db2-binary.167205', master_log_pos='77065552'. New state master_host='10.76.24.77', master_port='3306', master_log_file='db2-binary.167205', master_log_pos='77065552'. 2024-07-02 13:04:55 3122966 [Note] Master connection name: 's-db4' Master_info_file: 'master-s@002ddb4.info' Relay_info_file: 'relay-log-s@002ddb4.info' 2024-07-02 13:04:55 3122966 [Note] 'CHANGE MASTER TO executed'. Previous state master_host='10.76.25.11', master_port='3306', master_log_file='db4-binary.143365', master_log_pos='87730406'. New state master_host='10.76.25.11', master_port='3306', master_log_file='db4-binary.143365', master_log_pos='87729946'. 2024-07-02 13:05:05 3127474 [Note] Slave I/O thread: Start asynchronous replication to master 'gtid@10.76.24.77:3306' in log 'db2-binary.167205' at position 77065552 2024-07-02 13:05:05 3127474 [Note] Slave I/O thread: connected to master 'gtid@10.76.24.77:3306',replication started in log 'db2-binary.167205' at position 77065552 2024-07-02 13:05:05 3127475 [Note] Slave SQL thread initialized, starting replication in log 'db2-binary.167205' at position 77065552, relay log './db1-relay.063685' position: 4 2024-07-02 13:05:34 3128143 [Note] Master 's-db4': Slave I/O thread: Start asynchronous replication to master 'gtid@10.76.25.11:3306' in log 'db4-binary.143365' at position 87729946 2024-07-02 13:05:34 3128144 [Note] Master 's-db4': Slave SQL thread initialized, starting replication in log 'db4-binary.143365' at position 87729946, relay log './db1-relay-s@002ddb4.000001' position: 4 2024-07-02 13:05:34 3128143 [Note] Master 's-db4': Slave I/O thread: connected to master 'gtid@10.76.25.11:3306',replication started in log 'db4-binary.143365' at position 87729946 2024-07-02 13:08:38 3130671 [Note] Start binlog_dump to slave_server(4), pos(db1-binary.166041, 178879097), using_gtid(0), gtid('') 2024-07-03 9:39:17 2913991 [Warning] Aborted connection 2913991 to db: 'aaadb' user: 'alepoaaa' host: '10.76.24.87' (Got an error reading communication packets) 2024-07-03 9:39:17 2913990 [Warning] Aborted connection 2913990 to db: 'aaadb' user: 'alepoaaa' host: '10.76.24.87' (Got an error reading communication packets) 2024-07-03 9:39:17 2913989 [Warning] Aborted connection 2913989 to db: 'aaadb' user: 'alepoaaa' host: '10.76.24.87' (Got an error reading communication packets) 2024-07-03 9:39:17 2913988 [Warning] Aborted connection 2913988 to db: 'aaadb' user: 'alepoaaa' host: '10.76.24.87' (Got an error reading communication packets) 2024-07-03 9:39:17 2913985 [Warning] Aborted connection 2913985 to db: 'aaadb' user: 'alepoaaa' host: '10.76.24.87' (Got an error reading communication packets) 2024-07-03 9:39:17 2913987 [Warning] Aborted connection 2913987 to db: 'aaadb' user: 'alepoaaa' host: '10.76.24.87' (Got an error reading communication packets) 2024-07-03 9:39:17 2913986 [Warning] Aborted connection 2913986 to db: 'aaadb' user: 'alepoaaa' host: '10.76.24.87' (Got an error reading communication packets) 2024-07-03 9:39:17 2913982 [Warning] Aborted connection 2913982 to db: 'aaadb' user: 'alepoaaa' host: '10.76.24.87' (Got an error reading communication packets) 2024-07-03 9:39:17 2913983 [Warning] Aborted connection 2913983 to db: 'aaadb' user: 'alepoaaa' host: '10.76.24.87' (Got an error reading communication packets) 2024-07-03 9:39:17 2913984 [Warning] Aborted connection 2913984 to db: 'aaadb' user: 'alepoaaa' host: '10.76.24.87' (Got an error reading communication packets) 2024-07-03 9:39:17 2913981 [Warning] Aborted connection 2913981 to db: 'aaadb' user: 'alepoaaa' host: '10.76.24.87' (Got an error reading communication packets) 2024-07-03 9:39:17 2913980 [Warning] Aborted connection 2913980 to db: 'aaadb' user: 'alepoaaa' host: '10.76.24.87' (Got an error reading communication packets) 2024-07-03 9:39:17 2913978 [Warning] Aborted connection 2913978 to db: 'aaadb' user: 'alepoaaa' host: '10.76.24.87' (Got an error reading communication packets) 2024-07-03 9:39:17 2913977 [Warning] Aborted connection 2913977 to db: 'aaadb' user: 'alepoaaa' host: '10.76.24.87' (Got an error reading communication packets) 2024-07-03 9:39:17 2913979 [Warning] Aborted connection 2913979 to db: 'aaadb' user: 'alepoaaa' host: '10.76.24.87' (Got an error reading communication packets) 2024-07-03 9:39:17 2913976 [Warning] Aborted connection 2913976 to db: 'aaadb' user: 'alepoaaa' host: '10.76.24.87' (Got an error reading communication packets) 2024-07-03 9:39:17 2913975 [Warning] Aborted connection 2913975 to db: 'aaadb' user: 'alepoaaa' host: '10.76.24.87' (Got an error reading communication packets) 2024-07-03 9:39:17 2913974 [Warning] Aborted connection 2913974 to db: 'aaadb' user: 'alepoaaa' host: '10.76.24.87' (Got an error reading communication packets) 2024-07-03 9:39:17 2913973 [Warning] Aborted connection 2913973 to db: 'aaadb' user: 'alepoaaa' host: '10.76.24.87' (Got an error reading communication packets) 2024-07-03 9:39:17 2913972 [Warning] Aborted connection 2913972 to db: 'aaadb' user: 'alepoaaa' host: '10.76.24.87' (Got an error reading communication packets) 2024-07-03 9:39:17 2913970 [Warning] Aborted connection 2913970 to db: 'aaadb' user: 'alepoaaa' host: '10.76.24.87' (Got an error reading communication packets) 2024-07-03 9:39:17 2913971 [Warning] Aborted connection 2913971 to db: 'aaadb' user: 'alepoaaa' host: '10.76.24.87' (Got an error reading communication packets) 2024-07-03 9:39:17 2913968 [Warning] Aborted connection 2913968 to db: 'aaadb' user: 'alepoaaa' host: '10.76.24.87' (Got an error reading communication packets) 2024-07-03 9:39:17 2913969 [Warning] Aborted connection 2913969 to db: 'aaadb' user: 'alepoaaa' host: '10.76.24.87' (Got an error reading communication packets) 2024-07-03 9:39:17 2913967 [Warning] Aborted connection 2913967 to db: 'aaadb' user: 'alepoaaa' host: '10.76.24.87' (Got an error reading communication packets) 2024-07-03 9:39:17 2913966 [Warning] Aborted connection 2913966 to db: 'aaadb' user: 'alepoaaa' host: '10.76.24.87' (Got an error reading communication packets) 2024-07-03 9:39:17 2913965 [Warning] Aborted connection 2913965 to db: 'aaadb' user: 'alepoaaa' host: '10.76.24.87' (Got an error reading communication packets) 2024-07-03 9:39:17 2913964 [Warning] Aborted connection 2913964 to db: 'aaadb' user: 'alepoaaa' host: '10.76.24.87' (Got an error reading communication packets) 2024-07-03 9:39:17 2913963 [Warning] Aborted connection 2913963 to db: 'aaadb' user: 'alepoaaa' host: '10.76.24.87' (Got an error reading communication packets) 2024-07-03 9:39:17 2913962 [Warning] Aborted connection 2913962 to db: 'aaadb' user: 'alepoaaa' host: '10.76.24.87' (Got an error reading communication packets) 2024-07-03 9:39:17 2913961 [Warning] Aborted connection 2913961 to db: 'aaadb' user: 'alepoaaa' host: '10.76.24.87' (Got an error reading communication packets) 2024-07-03 9:39:17 2913960 [Warning] Aborted connection 2913960 to db: 'aaadb' user: 'alepoaaa' host: '10.76.24.87' (Got an error reading communication packets) 2024-07-03 9:39:17 2913959 [Warning] Aborted connection 2913959 to db: 'aaadb' user: 'alepoaaa' host: '10.76.24.87' (Got an error reading communication packets) 2024-07-03 9:39:17 2913955 [Warning] Aborted connection 2913955 to db: 'aaadb' user: 'alepoaaa' host: '10.76.24.87' (Got an error reading communication packets) 2024-07-03 9:39:17 2913957 [Warning] Aborted connection 2913957 to db: 'aaadb' user: 'alepoaaa' host: '10.76.24.87' (Got an error reading communication packets) 2024-07-03 9:39:17 2913953 [Warning] Aborted connection 2913953 to db: 'aaadb' user: 'alepoaaa' host: '10.76.24.87' (Got an error reading communication packets) 2024-07-03 9:39:17 2913951 [Warning] Aborted connection 2913951 to db: 'aaadb' user: 'alepoaaa' host: '10.76.24.87' (Got an error reading communication packets) 2024-07-03 9:39:17 2913950 [Warning] Aborted connection 2913950 to db: 'aaadb' user: 'alepoaaa' host: '10.76.24.87' (Got an error reading communication packets) 2024-07-03 9:39:17 2913948 [Warning] Aborted connection 2913948 to db: 'aaadb' user: 'alepoaaa' host: '10.76.24.87' (Got an error reading communication packets) 2024-07-03 9:39:17 2913946 [Warning] Aborted connection 2913946 to db: 'aaadb' user: 'alepoaaa' host: '10.76.24.87' (Got an error reading communication packets) 2024-07-03 9:39:17 2913944 [Warning] Aborted connection 2913944 to db: 'aaadb' user: 'alepoaaa' host: '10.76.24.87' (Got an error reading communication packets) 2024-07-03 9:39:17 2913942 [Warning] Aborted connection 2913942 to db: 'aaadb' user: 'alepoaaa' host: '10.76.24.87' (Got an error reading communication packets) 2024-07-03 9:39:17 2913940 [Warning] Aborted connection 2913940 to db: 'aaadb' user: 'alepoaaa' host: '10.76.24.87' (Got an error reading communication packets) 2024-07-03 9:39:17 2913938 [Warning] Aborted connection 2913938 to db: 'aaadb' user: 'alepoaaa' host: '10.76.24.87' (Got an error reading communication packets) 2024-07-03 9:39:17 2913936 [Warning] Aborted connection 2913936 to db: 'aaadb' user: 'alepoaaa' host: '10.76.24.87' (Got an error reading communication packets) 2024-07-03 9:39:17 2913934 [Warning] Aborted connection 2913934 to db: 'aaadb' user: 'alepoaaa' host: '10.76.24.87' (Got an error reading communication packets) 2024-07-03 9:39:17 2913932 [Warning] Aborted connection 2913932 to db: 'aaadb' user: 'alepoaaa' host: '10.76.24.87' (Got an error reading communication packets) 2024-07-03 9:39:17 2913930 [Warning] Aborted connection 2913930 to db: 'aaadb' user: 'alepoaaa' host: '10.76.24.87' (Got an error reading communication packets) 2024-07-03 9:39:17 2913929 [Warning] Aborted connection 2913929 to db: 'aaadb' user: 'alepoaaa' host: '10.76.24.87' (Got an error reading communication packets) 2024-07-03 9:39:17 2913927 [Warning] Aborted connection 2913927 to db: 'aaadb' user: 'alepoaaa' host: '10.76.24.87' (Got an error reading communication packets) 2024-07-03 9:39:17 2913925 [Warning] Aborted connection 2913925 to db: 'aaadb' user: 'alepoaaa' host: '10.76.24.87' (Got an error reading communication packets) 2024-07-03 9:39:17 2913923 [Warning] Aborted connection 2913923 to db: 'aaadb' user: 'alepoaaa' host: '10.76.24.87' (Got an error reading communication packets) 2024-07-03 9:39:17 2913921 [Warning] Aborted connection 2913921 to db: 'aaadb' user: 'alepoaaa' host: '10.76.24.87' (Got an error reading communication packets) 2024-07-03 9:39:17 2913919 [Warning] Aborted connection 2913919 to db: 'aaadb' user: 'alepoaaa' host: '10.76.24.87' (Got an error reading communication packets) 2024-07-03 9:39:17 2913913 [Warning] Aborted connection 2913913 to db: 'aaadb' user: 'alepoaaa' host: '10.76.24.87' (Got an error reading communication packets) 2024-07-03 9:39:17 2913911 [Warning] Aborted connection 2913911 to db: 'aaadb' user: 'alepoaaa' host: '10.76.24.87' (Got an error reading communication packets) 2024-07-03 9:39:17 2913917 [Warning] Aborted connection 2913917 to db: 'aaadb' user: 'alepoaaa' host: '10.76.24.87' (Got an error reading communication packets) 2024-07-03 9:39:17 2913909 [Warning] Aborted connection 2913909 to db: 'aaadb' user: 'alepoaaa' host: '10.76.24.87' (Got an error reading communication packets) 2024-07-03 9:39:17 2913907 [Warning] Aborted connection 2913907 to db: 'aaadb' user: 'alepoaaa' host: '10.76.24.87' (Got an error reading communication packets) 2024-07-03 9:39:17 2913906 [Warning] Aborted connection 2913906 to db: 'aaadb' user: 'alepoaaa' host: '10.76.24.87' (Got an error reading communication packets) 2024-07-03 9:39:17 2913904 [Warning] Aborted connection 2913904 to db: 'aaadb' user: 'alepoaaa' host: '10.76.24.87' (Got an error reading communication packets) 2024-07-03 9:39:17 2913902 [Warning] Aborted connection 2913902 to db: 'aaadb' user: 'alepoaaa' host: '10.76.24.87' (Got an error reading communication packets) 2024-07-03 9:39:17 2913915 [Warning] Aborted connection 2913915 to db: 'aaadb' user: 'alepoaaa' host: '10.76.24.87' (Got an error reading communication packets) 2024-07-03 9:39:17 2913900 [Warning] Aborted connection 2913900 to db: 'aaadb' user: 'alepoaaa' host: '10.76.24.87' (Got an error reading communication packets) 2024-07-03 9:39:17 2913898 [Warning] Aborted connection 2913898 to db: 'aaadb' user: 'alepoaaa' host: '10.76.24.87' (Got an error reading communication packets) 2024-07-03 9:39:17 2913897 [Warning] Aborted connection 2913897 to db: 'aaadb' user: 'alepoaaa' host: '10.76.24.87' (Got an error reading communication packets) 2024-07-03 9:39:17 2913895 [Warning] Aborted connection 2913895 to db: 'aaadb' user: 'alepoaaa' host: '10.76.24.87' (Got an error reading communication packets) 2024-07-03 9:39:17 2913893 [Warning] Aborted connection 2913893 to db: 'aaadb' user: 'alepoaaa' host: '10.76.24.87' (Got an error reading communication packets) 2024-07-03 9:39:17 2913891 [Warning] Aborted connection 2913891 to db: 'aaadb' user: 'alepoaaa' host: '10.76.24.87' (Got an error reading communication packets) 2024-07-04 0:35:40 2914220 [Warning] Aborted connection 2914220 to db: 'aaadb' user: 'alepoaaa' host: '10.76.24.89' (Got an error reading communication packets) 2024-07-04 0:35:40 2914219 [Warning] Aborted connection 2914219 to db: 'aaadb' user: 'alepoaaa' host: '10.76.24.89' (Got an error reading communication packets) 2024-07-04 0:35:40 2914218 [Warning] Aborted connection 2914218 to db: 'aaadb' user: 'alepoaaa' host: '10.76.24.89' (Got an error reading communication packets) 2024-07-04 0:35:40 2914217 [Warning] Aborted connection 2914217 to db: 'aaadb' user: 'alepoaaa' host: '10.76.24.89' (Got an error reading communication packets) 2024-07-04 0:35:40 2914216 [Warning] Aborted connection 2914216 to db: 'aaadb' user: 'alepoaaa' host: '10.76.24.89' (Got an error reading communication packets) 2024-07-04 0:35:40 2914215 [Warning] Aborted connection 2914215 to db: 'aaadb' user: 'alepoaaa' host: '10.76.24.89' (Got an error reading communication packets) 2024-07-04 0:35:40 2914213 [Warning] Aborted connection 2914213 to db: 'aaadb' user: 'alepoaaa' host: '10.76.24.89' (Got an error reading communication packets) 2024-07-04 0:35:40 2914214 [Warning] Aborted connection 2914214 to db: 'aaadb' user: 'alepoaaa' host: '10.76.24.89' (Got an error reading communication packets) 2024-07-04 0:35:40 2914212 [Warning] Aborted connection 2914212 to db: 'aaadb' user: 'alepoaaa' host: '10.76.24.89' (Got an error reading communication packets) 2024-07-04 0:35:40 2914210 [Warning] Aborted connection 2914210 to db: 'aaadb' user: 'alepoaaa' host: '10.76.24.89' (Got an error reading communication packets) 2024-07-04 0:35:40 2914211 [Warning] Aborted connection 2914211 to db: 'aaadb' user: 'alepoaaa' host: '10.76.24.89' (Got an error reading communication packets) 2024-07-04 0:35:40 2914209 [Warning] Aborted connection 2914209 to db: 'aaadb' user: 'alepoaaa' host: '10.76.24.89' (Got an error reading communication packets) 2024-07-04 0:35:40 2914207 [Warning] Aborted connection 2914207 to db: 'aaadb' user: 'alepoaaa' host: '10.76.24.89' (Got an error reading communication packets) 2024-07-04 0:35:40 2914208 [Warning] Aborted connection 2914208 to db: 'aaadb' user: 'alepoaaa' host: '10.76.24.89' (Got an error reading communication packets) 2024-07-04 0:35:40 2914206 [Warning] Aborted connection 2914206 to db: 'aaadb' user: 'alepoaaa' host: '10.76.24.89' (Got an error reading communication packets) 2024-07-04 0:35:40 2914204 [Warning] Aborted connection 2914204 to db: 'aaadb' user: 'alepoaaa' host: '10.76.24.89' (Got an error reading communication packets) 2024-07-04 0:35:40 2914205 [Warning] Aborted connection 2914205 to db: 'aaadb' user: 'alepoaaa' host: '10.76.24.89' (Got an error reading communication packets) 2024-07-04 0:35:40 2914203 [Warning] Aborted connection 2914203 to db: 'aaadb' user: 'alepoaaa' host: '10.76.24.89' (Got an error reading communication packets) 2024-07-04 0:35:40 2914202 [Warning] Aborted connection 2914202 to db: 'aaadb' user: 'alepoaaa' host: '10.76.24.89' (Got an error reading communication packets) 2024-07-04 0:35:40 2914199 [Warning] Aborted connection 2914199 to db: 'aaadb' user: 'alepoaaa' host: '10.76.24.89' (Got an error reading communication packets) 2024-07-04 0:35:40 2914201 [Warning] Aborted connection 2914201 to db: 'aaadb' user: 'alepoaaa' host: '10.76.24.89' (Got an error reading communication packets) 2024-07-04 0:35:40 2914198 [Warning] Aborted connection 2914198 to db: 'aaadb' user: 'alepoaaa' host: '10.76.24.89' (Got an error reading communication packets) 2024-07-04 0:35:40 2914197 [Warning] Aborted connection 2914197 to db: 'aaadb' user: 'alepoaaa' host: '10.76.24.89' (Got an error reading communication packets) 2024-07-04 0:35:40 2914196 [Warning] Aborted connection 2914196 to db: 'aaadb' user: 'alepoaaa' host: '10.76.24.89' (Got an error reading communication packets) 2024-07-04 0:35:40 2914194 [Warning] Aborted connection 2914194 to db: 'aaadb' user: 'alepoaaa' host: '10.76.24.89' (Got an error reading communication packets) 2024-07-04 0:35:40 2914193 [Warning] Aborted connection 2914193 to db: 'aaadb' user: 'alepoaaa' host: '10.76.24.89' (Got an error reading communication packets) 2024-07-04 0:35:40 2914195 [Warning] Aborted connection 2914195 to db: 'aaadb' user: 'alepoaaa' host: '10.76.24.89' (Got an error reading communication packets) 2024-07-04 0:35:40 2914192 [Warning] Aborted connection 2914192 to db: 'aaadb' user: 'alepoaaa' host: '10.76.24.89' (Got an error reading communication packets) 2024-07-04 0:35:40 2914191 [Warning] Aborted connection 2914191 to db: 'aaadb' user: 'alepoaaa' host: '10.76.24.89' (Got an error reading communication packets) 2024-07-04 0:35:40 2914190 [Warning] Aborted connection 2914190 to db: 'aaadb' user: 'alepoaaa' host: '10.76.24.89' (Got an error reading communication packets) 2024-07-04 0:35:40 2914189 [Warning] Aborted connection 2914189 to db: 'aaadb' user: 'alepoaaa' host: '10.76.24.89' (Got an error reading communication packets) 2024-07-04 0:35:40 2914188 [Warning] Aborted connection 2914188 to db: 'aaadb' user: 'alepoaaa' host: '10.76.24.89' (Got an error reading communication packets) 2024-07-04 0:35:40 2914187 [Warning] Aborted connection 2914187 to db: 'aaadb' user: 'alepoaaa' host: '10.76.24.89' (Got an error reading communication packets) 2024-07-04 0:35:40 2914186 [Warning] Aborted connection 2914186 to db: 'aaadb' user: 'alepoaaa' host: '10.76.24.89' (Got an error reading communication packets) 2024-07-04 0:35:40 2914185 [Warning] Aborted connection 2914185 to db: 'aaadb' user: 'alepoaaa' host: '10.76.24.89' (Got an error reading communication packets) 2024-07-04 0:35:40 2914184 [Warning] Aborted connection 2914184 to db: 'aaadb' user: 'alepoaaa' host: '10.76.24.89' (Got an error reading communication packets) 2024-07-04 0:35:40 2914183 [Warning] Aborted connection 2914183 to db: 'aaadb' user: 'alepoaaa' host: '10.76.24.89' (Got an error reading communication packets) 2024-07-04 0:35:40 2914182 [Warning] Aborted connection 2914182 to db: 'aaadb' user: 'alepoaaa' host: '10.76.24.89' (Got an error reading communication packets) 2024-07-04 0:35:40 2914180 [Warning] Aborted connection 2914180 to db: 'aaadb' user: 'alepoaaa' host: '10.76.24.89' (Got an error reading communication packets) 2024-07-04 0:35:40 2914181 [Warning] Aborted connection 2914181 to db: 'aaadb' user: 'alepoaaa' host: '10.76.24.89' (Got an error reading communication packets) 2024-07-04 0:35:40 2914179 [Warning] Aborted connection 2914179 to db: 'aaadb' user: 'alepoaaa' host: '10.76.24.89' (Got an error reading communication packets) 2024-07-04 0:35:40 2914178 [Warning] Aborted connection 2914178 to db: 'aaadb' user: 'alepoaaa' host: '10.76.24.89' (Got an error reading communication packets) 2024-07-04 0:35:40 2914177 [Warning] Aborted connection 2914177 to db: 'aaadb' user: 'alepoaaa' host: '10.76.24.89' (Got an error reading communication packets) 2024-07-04 0:35:40 2914176 [Warning] Aborted connection 2914176 to db: 'aaadb' user: 'alepoaaa' host: '10.76.24.89' (Got an error reading communication packets) 2024-07-04 0:35:40 2914175 [Warning] Aborted connection 2914175 to db: 'aaadb' user: 'alepoaaa' host: '10.76.24.89' (Got an error reading communication packets) 2024-07-04 0:35:40 2914173 [Warning] Aborted connection 2914173 to db: 'aaadb' user: 'alepoaaa' host: '10.76.24.89' (Got an error reading communication packets) 2024-07-04 0:35:40 2914200 [Warning] Aborted connection 2914200 to db: 'aaadb' user: 'alepoaaa' host: '10.76.24.89' (Got an error reading communication packets) 2024-07-04 0:35:40 2914174 [Warning] Aborted connection 2914174 to db: 'aaadb' user: 'alepoaaa' host: '10.76.24.89' (Got an error reading communication packets) 2024-07-04 0:35:40 2914171 [Warning] Aborted connection 2914171 to db: 'aaadb' user: 'alepoaaa' host: '10.76.24.89' (Got an error reading communication packets) 2024-07-04 0:35:40 2914170 [Warning] Aborted connection 2914170 to db: 'aaadb' user: 'alepoaaa' host: '10.76.24.89' (Got an error reading communication packets) 2024-07-04 0:35:40 2914168 [Warning] Aborted connection 2914168 to db: 'aaadb' user: 'alepoaaa' host: '10.76.24.89' (Got an error reading communication packets) 2024-07-04 0:35:40 2914169 [Warning] Aborted connection 2914169 to db: 'aaadb' user: 'alepoaaa' host: '10.76.24.89' (Got an error reading communication packets) 2024-07-04 0:35:40 2914166 [Warning] Aborted connection 2914166 to db: 'aaadb' user: 'alepoaaa' host: '10.76.24.89' (Got an error reading communication packets) 2024-07-04 0:35:40 2914167 [Warning] Aborted connection 2914167 to db: 'aaadb' user: 'alepoaaa' host: '10.76.24.89' (Got an error reading communication packets) 2024-07-04 0:35:40 2914164 [Warning] Aborted connection 2914164 to db: 'aaadb' user: 'alepoaaa' host: '10.76.24.89' (Got an error reading communication packets) 2024-07-04 0:35:40 2914165 [Warning] Aborted connection 2914165 to db: 'aaadb' user: 'alepoaaa' host: '10.76.24.89' (Got an error reading communication packets) 2024-07-04 0:35:40 2914162 [Warning] Aborted connection 2914162 to db: 'aaadb' user: 'alepoaaa' host: '10.76.24.89' (Got an error reading communication packets) 2024-07-04 0:35:40 2914163 [Warning] Aborted connection 2914163 to db: 'aaadb' user: 'alepoaaa' host: '10.76.24.89' (Got an error reading communication packets) 2024-07-04 0:35:40 2914161 [Warning] Aborted connection 2914161 to db: 'aaadb' user: 'alepoaaa' host: '10.76.24.89' (Got an error reading communication packets) 2024-07-04 0:35:40 2914160 [Warning] Aborted connection 2914160 to db: 'aaadb' user: 'alepoaaa' host: '10.76.24.89' (Got an error reading communication packets) 2024-07-04 0:35:40 2913822 [Warning] Aborted connection 2913822 to db: 'aaadb' user: 'alepoaaa' host: '10.76.24.89' (Got an error reading communication packets) 2024-07-04 0:35:40 2913821 [Warning] Aborted connection 2913821 to db: 'aaadb' user: 'alepoaaa' host: '10.76.24.89' (Got an error reading communication packets) 2024-07-04 0:35:40 2913819 [Warning] Aborted connection 2913819 to db: 'aaadb' user: 'alepoaaa' host: '10.76.24.89' (Got an error reading communication packets) 2024-07-04 0:35:40 2913820 [Warning] Aborted connection 2913820 to db: 'aaadb' user: 'alepoaaa' host: '10.76.24.89' (Got an error reading communication packets) 2024-07-04 0:35:40 2913817 [Warning] Aborted connection 2913817 to db: 'aaadb' user: 'alepoaaa' host: '10.76.24.89' (Got an error reading communication packets) 2024-07-04 0:35:40 2914172 [Warning] Aborted connection 2914172 to db: 'aaadb' user: 'alepoaaa' host: '10.76.24.89' (Got an error reading communication packets) 2024-07-04 0:35:40 2913818 [Warning] Aborted connection 2913818 to db: 'aaadb' user: 'alepoaaa' host: '10.76.24.89' (Got an error reading communication packets) 2024-07-04 0:35:40 2913816 [Warning] Aborted connection 2913816 to db: 'aaadb' user: 'alepoaaa' host: '10.76.24.89' (Got an error reading communication packets) 2024-07-04 0:35:40 2913814 [Warning] Aborted connection 2913814 to db: 'aaadb' user: 'alepoaaa' host: '10.76.24.89' (Got an error reading communication packets) 2024-07-04 0:35:40 2913813 [Warning] Aborted connection 2913813 to db: 'aaadb' user: 'alepoaaa' host: '10.76.24.89' (Got an error reading communication packets) 2024-07-04 0:35:40 2913815 [Warning] Aborted connection 2913815 to db: 'aaadb' user: 'alepoaaa' host: '10.76.24.89' (Got an error reading communication packets) 2024-07-04 0:35:40 2918081 [Warning] Aborted connection 2918081 to db: 'aaadb' user: 'alepoaaa' host: '10.76.24.89' (Got an error reading communication packets) 2024-07-04 0:45:31 6375105 [Warning] Aborted connection 6375105 to db: 'aaadb' user: 'alepoaaaems' host: '10.76.24.67' (Got an error reading communication packets) 2024-07-04 0:45:31 6374819 [Warning] Aborted connection 6374819 to db: 'aaadb' user: 'alepoaaaems' host: '10.76.24.67' (Got an error reading communication packets) 2024-07-04 0:45:31 6375102 [Warning] Aborted connection 6375102 to db: 'aaadb' user: 'alepoaaaems' host: '10.76.24.67' (Got an error reading communication packets) 2024-07-04 0:45:31 6375101 [Warning] Aborted connection 6375101 to db: 'aaadb' user: 'alepoaaaems' host: '10.76.24.67' (Got an error reading communication packets) 2024-07-04 0:45:31 6375103 [Warning] Aborted connection 6375103 to db: 'aaadb' user: 'alepoaaaems' host: '10.76.24.67' (Got an error reading communication packets) 2024-07-04 0:45:31 6369564 [Warning] Aborted connection 6369564 to db: 'aaadb' user: 'alepoaaaems' host: '10.76.24.67' (Got an error reading communication packets) 2024-07-04 0:48:52 6398424 [Warning] Aborted connection 6398424 to db: 'aaadb' user: 'alepoaaaems' host: '10.76.24.74' (Got an error reading communication packets) 2024-07-04 0:48:52 6401471 [Warning] Aborted connection 6401471 to db: 'aaadb' user: 'alepoaaaems' host: '10.76.24.74' (Got an error reading communication packets) 2024-07-04 0:48:52 6363333 [Warning] Aborted connection 6363333 to db: 'aaadb' user: 'alepoaaaems' host: '10.76.24.74' (Got an error reading communication packets) 2024-07-04 0:48:52 6362357 [Warning] Aborted connection 6362357 to db: 'aaadb' user: 'alepoaaaems' host: '10.76.24.74' (Got an error reading communication packets) 2024-07-04 1:16:14 6398836 [Warning] Aborted connection 6398836 to db: 'aaadb' user: 'alepoaaaems' host: '10.76.24.67' (Got timeout reading communication packets) 2024-07-04 1:19:40 6403975 [Warning] Aborted connection 6403975 to db: 'aaadb' user: 'alepoaaaems' host: '10.76.24.74' (Got timeout reading communication packets) 2024-07-08 16:08:06 16378889 [Warning] Access denied for user 'root'@'10.76.24.83' (using password: NO) 2024-07-08 16:08:11 16379031 [Warning] Access denied for user 'gtid'@'10.76.24.83' (using password: NO) 2024-07-08 16:08:29 16379510 [Warning] Access denied for user 'gtid'@'10.76.24.83' (using password: NO) 2024-07-08 16:08:36 16379675 [Warning] Access denied for user 'root'@'10.76.24.83' (using password: NO) 2024-07-08 16:08:44 16379912 [Warning] Access denied for user 'root'@'10.76.24.83' (using password: NO) 2024-07-08 16:09:48 16381552 [Warning] Access denied for user 'alepo'@'10.76.24.83' (using password: NO) 2024-07-08 16:10:00 16381876 [Warning] Access denied for user 'replication'@'10.76.24.83' (using password: YES) 2024-07-08 16:10:50 16383168 [Warning] Access denied for user '-pP1cl#2023'@'10.76.24.83' (using password: NO) 240711 11:40:41 [ERROR] mysqld got signal 11 ; 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.11.5-MariaDB-log source revision: 7875294b6b74b53dd3aaa723e6cc103d2bb47b2c key_buffer_size=67108864 read_buffer_size=131072 max_used_connections=455 max_threads=802 thread_count=471 It is possible that mysqld could use up to key_buffer_size + (read_buffer_size + sort_buffer_size)*max_threads = 1831964 K bytes of memory Hope that's ok; if not, decrease some variables in the equation. Thread pointer: 0x7f82f511f4a8 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 = 0x7fd59e3cbb98 thread_stack 0x49000 /usr/sbin/mariadbd(my_print_stacktrace+0x2e)[0x55e3d9f0912e] mysys/stacktrace.c:216(my_print_stacktrace)[0x55e3d9a025b5] /lib64/libpthread.so.0(+0x12cf0)[0x7fd5b3700cf0] sql/sql_lex.cc:1962(Lex_input_stream::lex_token(YYSTYPE*, THD*))[0x55e3d9795dcd] sql/yy_mariadb.cc:28707(MYSQLparse(THD*))[0x55e3d9986f76] sql/sql_parse.cc:10394(parse_sql(THD*, Parser_state*, Object_creation_ctx*, bool))[0x55e3d97b881a] sql/sql_parse.cc:7988(mysql_parse(THD*, char*, unsigned int, Parser_state*))[0x55e3d97b4a1a] sql/sql_parse.cc:1896(dispatch_command(enum_server_command, THD*, char*, unsigned int, bool))[0x55e3d97be6e6] sql/sql_parse.cc:1407(do_command(THD*, bool))[0x55e3d97bfdab] sql/sql_connect.cc:1416(do_handle_one_connection(CONNECT*, bool))[0x55e3d98d3977] sql/sql_connect.cc:1318(handle_one_connection)[0x55e3d98d3cbd] perfschema/pfs.cc:2204(MyCTX_nopad::finish(unsigned char*, unsigned int*))[0x55e3d9c09c9d] /lib64/libpthread.so.0(+0x81ca)[0x7fd5b36f61ca] /lib64/libc.so.6(clone+0x43)[0x7fd5b2a46e73] Trying to get some variables. Some pointers may be invalid and cause the dump to abort. Query (0x7f82f50e55d0): Select UserIndex, NASIP, NASPort, GroupIndex ,NetworkServiceName From ActiveSessions Where UserIndex=40521671 And MainGroupIndex=402 Connection ID (thread ID): 6383771 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,hash_join_cardinality=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 unlimited unlimited bytes Max resident set unlimited unlimited bytes Max processes 2061710 2061710 processes Max open files 32768 32768 files Max locked memory 65536 65536 bytes Max address space unlimited unlimited bytes Max file locks unlimited unlimited locks Max pending signals 2061710 2061710 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: /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 2024-07-11 11:41:28 0 [Note] Starting MariaDB 10.11.5-MariaDB-log source revision 7875294b6b74b53dd3aaa723e6cc103d2bb47b2c as process 679579 2024-07-11 11:41:28 0 [Note] InnoDB: Compressed tables use zlib 1.2.11 2024-07-11 11:41:28 0 [Note] InnoDB: Number of transaction pools: 1 2024-07-11 11:41:28 0 [Note] InnoDB: Using crc32 + pclmulqdq instructions 2024-07-11 11:41:28 0 [Note] InnoDB: Using Linux native AIO 2024-07-11 11:41:28 0 [Note] InnoDB: Initializing buffer pool, total size = 300.000GiB, chunk size = 4.688GiB 2024-07-11 11:41:28 0 [Note] InnoDB: Completed initialization of buffer pool 2024-07-11 11:41:29 0 [Note] InnoDB: File system buffers for log disabled (block size=512 bytes) 2024-07-11 11:41:31 0 [Warning] InnoDB: 2674240512 bytes should have been read at 1620726784 from (unknown file), but got only 2147479552. Retrying. 2024-07-11 11:41:32 0 [Note] InnoDB: Starting crash recovery from checkpoint LSN=37847124692938 2024-07-11 11:41:36 0 [Warning] InnoDB: 4294955008 bytes should have been read at 12288 from (unknown file), but got only 2147479552. Retrying. 2024-07-11 11:41:43 0 [Note] InnoDB: Parsed redo log up to LSN=37847854263346; to recover: 151742 pages 2024-07-11 11:41:54 0 [Note] InnoDB: End of log at LSN=37848996745211 2024-07-11 11:41:55 0 [Note] InnoDB: Transaction 118505726599 was in the XA prepared state. 2024-07-11 11:41:55 0 [Note] InnoDB: Transaction 118505726600 was in the XA prepared state. 2024-07-11 11:41:55 0 [Note] InnoDB: Transaction 118505726604 was in the XA prepared state. 2024-07-11 11:41:55 0 [Note] InnoDB: Transaction 118505726605 was in the XA prepared state. 2024-07-11 11:41:55 0 [Note] InnoDB: 4 transaction(s) which must be rolled back or cleaned up in total 0 row operations to undo 2024-07-11 11:41:55 0 [Note] InnoDB: Trx id counter is 118505726610 2024-07-11 11:41:56 0 [Note] InnoDB: To recover: 168687 pages 2024-07-11 11:42:11 0 [Note] InnoDB: To recover: 168687 pages 2024-07-11 11:42:16 0 [Note] InnoDB: Last binlog file './db1-binary.172404', position 184064918 2024-07-11 11:42:16 0 [Note] InnoDB: 128 rollback segments are active. 2024-07-11 11:42:17 0 [Note] InnoDB: Starting in background the rollback of recovered transactions 2024-07-11 11:42:17 0 [Note] InnoDB: Rollback of non-prepared transactions completed 2024-07-11 11:42:17 0 [Note] InnoDB: Removed temporary tablespace data file: "./ibtmp1" 2024-07-11 11:42:17 0 [Note] InnoDB: Setting file './ibtmp1' size to 12.000MiB. Physically writing the file full; Please wait ... 2024-07-11 11:42:17 0 [Note] InnoDB: File './ibtmp1' size is now 12.000MiB. 2024-07-11 11:42:17 0 [Note] InnoDB: log sequence number 37848996745211; transaction id 118505726611 2024-07-11 11:42:17 0 [Note] InnoDB: Loading buffer pool(s) from /var/lib/mysql/ib_buffer_pool 2024-07-11 11:42:17 0 [Note] Plugin 'FEEDBACK' is disabled. 2024-07-11 11:42:17 0 [Warning] 'thread-concurrency' was removed. It does nothing now and exists only for compatibility with old my.cnf files. 2024-07-11 11:42:17 0 [Warning] 'innodb-thread-concurrency' was removed. It does nothing now and exists only for compatibility with old my.cnf files. 2024-07-11 11:42:17 0 [Warning] 'innodb-log-files-in-group' was removed. It does nothing now and exists only for compatibility with old my.cnf files. 2024-07-11 11:42:17 0 [Note] Recovering after a crash using db1-binary 2024-07-11 11:42:17 0 [Note] Starting table crash recovery... 2024-07-11 11:42:17 0 [Note] InnoDB: Starting recovery for XA transactions... 2024-07-11 11:42:17 0 [Note] InnoDB: Transaction 118505726600 in prepared state after recovery 2024-07-11 11:42:17 0 [Note] InnoDB: Transaction contains changes to 1 rows 2024-07-11 11:42:17 0 [Note] InnoDB: Transaction 118505726605 in prepared state after recovery 2024-07-11 11:42:17 0 [Note] InnoDB: Transaction contains changes to 1 rows 2024-07-11 11:42:17 0 [Note] InnoDB: Transaction 118505726604 in prepared state after recovery 2024-07-11 11:42:17 0 [Note] InnoDB: Transaction contains changes to 1 rows 2024-07-11 11:42:17 0 [Note] InnoDB: Transaction 118505726599 in prepared state after recovery 2024-07-11 11:42:17 0 [Note] InnoDB: Transaction contains changes to 1 rows 2024-07-11 11:42:17 0 [Note] InnoDB: 4 transactions in prepared state after recovery 2024-07-11 11:42:17 0 [Note] Found 4 prepared transaction(s) in InnoDB 2024-07-11 11:42:17 0 [Note] Crash table recovery finished. 2024-07-11 11:42:17 0 [Note] Server socket created on IP: '0.0.0.0'. 2024-07-11 11:42:17 0 [Note] Server socket created on IP: '::'. 2024-07-11 11:42:17 0 [Warning] 'user' entry '@alepo-db2-ilb' ignored in --skip-name-resolve mode. 2024-07-11 11:42:17 0 [Warning] 'user' entry 'root@localhost.localdomain' ignored in --skip-name-resolve mode. 2024-07-11 11:42:17 0 [Warning] 'proxies_priv' entry '@% root@alepo-db2-ilb' ignored in --skip-name-resolve mode. 2024-07-11 11:42:17 3 [Note] Reading Master_info: 'master-s@002ddb3.info' Relay_info:'relay-log-s@002ddb3.info' 2024-07-11 11:42:17 3 [Note] Initialized Master_info from 'master-s@002ddb3.info' 2024-07-11 11:42:17 4 [Note] Master 's-db3': Slave I/O thread: Start asynchronous replication to master '@:3306' in log '' at position 4 2024-07-11 11:42:17 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 2024-07-11 11:42:17 4 [Note] Master 's-db3': Slave I/O thread killed while connecting to master 2024-07-11 11:42:17 4 [Note] Master 's-db3': Slave I/O thread exiting, read up to log 'FIRST', position 4, master :3306 2024-07-11 11:42:17 3 [Note] Started replication for 's-db3' 2024-07-11 11:42:17 5 [Note] Master 's-db3': Slave SQL thread initialized, starting replication in log 'FIRST' at position 0, relay log './db1-relay-s@002ddb3.000019' position: 4 2024-07-11 11:42:17 3 [Note] Reading Master_info: 'master-s@002ddb4.info' Relay_info:'relay-log-s@002ddb4.info' 2024-07-11 11:42:17 3 [Note] Initialized Master_info from 'master-s@002ddb4.info' 2024-07-11 11:42:17 18 [Note] Master 's-db4': Slave I/O thread: Start asynchronous replication to master 'gtid@10.76.25.11:3306' in log 'db4-binary.149730' at position 206155030 2024-07-11 11:42:17 3 [Note] Started replication for 's-db4' 2024-07-11 11:42:17 3 [Note] Reading Master_info: 'master-s@002ddb2.info' Relay_info:'relay-log-s@002ddb2.info' 2024-07-11 11:42:17 19 [Note] Master 's-db4': Slave SQL thread initialized, starting replication in log 'db4-binary.149730' at position 206155030, relay log './db1-relay-s@002ddb4.012732' position: 783 2024-07-11 11:42:17 18 [Note] Master 's-db4': Slave I/O thread: connected to master 'gtid@10.76.25.11:3306',replication started in log 'db4-binary.149730' at position 206155030 2024-07-11 11:42:17 3 [Note] Initialized Master_info from 'master-s@002ddb2.info' 2024-07-11 11:42:17 20 [Note] Master 's-db2': Slave I/O thread: Start asynchronous replication to master '@:3306' in log '' at position 4 2024-07-11 11:42:17 20 [ERROR] Master 's-db2': Slave I/O: Fatal error: Invalid (empty) username when attempting to connect to the master server. Connection attempt terminated. Internal MariaDB error code: 1593 2024-07-11 11:42:17 20 [Note] Master 's-db2': Slave I/O thread killed while connecting to master 2024-07-11 11:42:17 20 [Note] Master 's-db2': Slave I/O thread exiting, read up to log 'FIRST', position 4, master :3306 2024-07-11 11:42:17 3 [Note] Started replication for 's-db2' 2024-07-11 11:42:17 21 [Note] Master 's-db2': Slave SQL thread initialized, starting replication in log 'FIRST' at position 0, relay log './db1-relay-s@002ddb2.000018' position: 4 2024-07-11 11:42:17 3 [Note] Reading Master_info: 'master-s@002ddb5.info' Relay_info:'relay-log-s@002ddb5.info' 2024-07-11 11:42:17 3 [Note] Initialized Master_info from 'master-s@002ddb5.info' 2024-07-11 11:42:17 22 [Note] Master 's-db5': Slave I/O thread: Start asynchronous replication to master '@:3306' in log '' at position 4 2024-07-11 11:42:17 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 2024-07-11 11:42:17 22 [Note] Master 's-db5': Slave I/O thread killed while connecting to master 2024-07-11 11:42:17 22 [Note] Master 's-db5': Slave I/O thread exiting, read up to log 'FIRST', position 4, master :3306 2024-07-11 11:42:17 3 [Note] Started replication for 's-db5' 2024-07-11 11:42:17 23 [Note] Master 's-db5': Slave SQL thread initialized, starting replication in log 'FIRST' at position 0, relay log './db1-relay-s@002ddb5.000010' position: 4 2024-07-11 11:42:18 25 [Note] Slave I/O thread: Start asynchronous replication to master 'gtid@10.76.24.77:3306' in log 'db2-binary.173532' at position 150835655 2024-07-11 11:42:18 0 [Note] /usr/sbin/mariadbd: ready for connections. Version: '10.11.5-MariaDB-log' socket: '/var/lib/mysql/mysql.sock' port: 3306 MariaDB Server 2024-07-11 11:42:18 26 [Note] Slave SQL thread initialized, starting replication in log 'db2-binary.173532' at position 150835655, relay log './db1-relay.076340' position: 767 2024-07-11 11:42:18 25 [Note] Slave I/O thread: connected to master 'gtid@10.76.24.77:3306',replication started in log 'db2-binary.173532' at position 150835655 2024-07-11 11:42:18 13 [Note] Detected table cache mutex contention at instance 1: 82% waits. Additional table cache instance activated. Number of instances after activation: 2. 2024-07-11 11:42:18 0 [Note] InnoDB: Buffer pool(s) load completed at 240711 11:42:18 2024-07-11 11:42:19 10 [Note] Detected table cache mutex contention at instance 1: 21% waits. Additional table cache instance activated. Number of instances after activation: 3. 2024-07-11 11:43:12 2270 [Note] Start binlog_dump to slave_server(3), pos(db1-binary.172404, 184068409), using_gtid(0), gtid('') 2024-07-11 11:43:12 2271 [Note] Start binlog_dump to slave_server(2), pos(db1-binary.172404, 184068409), using_gtid(0), gtid('') 2024-07-11 11:43:12 2274 [Note] Start binlog_dump to slave_server(4), pos(db1-binary.172404, 184068409), using_gtid(0), gtid('')