**************************...">

Mysql replication stops without errors

Mysql 5.1 Replication stops without error message

"SHOW SLAVE STATUS \ G"
> ***************************** 1. row ******************* ********
> Slave_IO_State: Waiting for master to send event
> Master_Host: xxx
> Master_User: repl
> Master_Port: 3306
> Connect_Retry: 60
> Master_Log_File: mysql-bin.000366
> Read_Master_Log_Pos: 6491726
> Relay_Log_File: mysql-relay-bin.000003
> Relay_Log_Pos: 75183691
> Relay_Master_Log_File: mysql-bin.000351
> Slave_IO_Running: Yes
> Slave_SQL_Running: Yes
> Replicate_Do_DB: xxx
> Replicate_Ignore_DB: 
> Replicate_Do_Table: 
> Replicate_Ignore_Table: 
> Replicate_Wild_Do_Table:    
> Replicate_Wild_Ignore_Table: 
> Last_Errno: 0
> Last_Error: 
> Skip_Counter: 0
> Exec_Master_Log_Pos: 75698643
> Relay_Log_Space: 1624786550
> Until_Condition: None
> Until_Log_File: 
> Until_Log_Pos: 0
> Master_SSL_Allowed: No
> Master_SSL_CA_File: 
> Master_SSL_CA_Path: 
> Master_SSL_Cert: 
> Master_SSL_Cipher: 
> Master_SSL_Key: 
> Seconds_Behind_Master: 6222 
> Master_SSL_Verify_Server_Cert: No
> Last_IO_Errno: 0
> Last_IO_Error: 
> Last_SQL_Errno: 0
> Last_SQL_Error:

The last binlog on master is mysql-bin.000365

What should I do and read to solve this problem?

+3
source share
1 answer

You need to reconfigure MySQL Slave because your subordinate shows Master_Log_File: mysql-bin.000366, however you say that your master is in mysql-bin.000365. That is why your slave cannot synchronize with the Master. To reconfigure Slave, make the following settings here

0
source

Source: https://habr.com/ru/post/1779964/


All Articles