Bug #118414 [MY-013129] [MY-011809] [MY-011153]
Submitted: 11 Jun 11:30 Modified: 11 Jun 16:13
Reporter: xiaomoloving xiaomo Email Updates:
Status: Duplicate Impact on me:
None 
Category:MySQL Server Severity:S3 (Non-critical)
Version:8.0 OS:Any
Assigned to: MySQL Verification Team CPU Architecture:Any
Tags: Replicaiton, Slave crash;

[11 Jun 11:30] xiaomoloving xiaomo
Description:
2025-05-03T11:07:42.955275+08:00 0 [ERROR] [MY-013129] [Server] A message intended for a client cannot be sent there as no client-session is attached. Therefore, we're sending the information to the error-log 
instead: MY-001158 - Got an error reading communication packets
2025-05-03T11:07:43.472763+08:00 148 [ERROR] [MY-011161] [Repl] Semi-sync source failed on net_flush() before waiting for replica reply.
2025-05-03T11:07:44.357729+08:00 3780081 [Warning] [MY-011153] [Repl] Timeout waiting for reply of binlog (file: mysql-bin.021718, pos: 980193251), semi-sync up to file mysql-bin.021718, position 980193251), 
2025-05-03T11:24:52.932128+08:00 3782120 [Warning] [MY-011809] [Server] Cannot replicate to server with server_uuid='b10ca143-23fg-14f0-bcf1-0052314886f1' because the present server has purged required binary 
logs. The connecting server needs to replicate the missing transactions from elsewhere.

How to repeat:
2025-05-03T11:07:42.955275+08:00 0 [ERROR] [MY-013129] [Server] A message intended for a client cannot be sent there as no client-session is attached. Therefore, we're sending the information to the error-log 
instead: MY-001158 - Got an error reading communication packets
2025-05-03T11:07:43.472763+08:00 148 [ERROR] [MY-011161] [Repl] Semi-sync source failed on net_flush() before waiting for replica reply.
2025-05-03T11:07:44.357729+08:00 3780081 [Warning] [MY-011153] [Repl] Timeout waiting for reply of binlog (file: mysql-bin.021718, pos: 980193251), semi-sync up to file mysql-bin.021718, position 980193251), 
2025-05-03T11:24:52.932128+08:00 3782120 [Warning] [MY-011809] [Server] Cannot replicate to server with server_uuid='b10ca143-23fg-14f0-bcf1-0052314886f1' because the present server has purged required binary 
logs. The connecting server needs to replicate the missing transactions from elsewhere.
[11 Jun 16:13] MySQL Verification Team
Duplicate of Bug #118415