Linux MySQL主从同步失败,报错1594的解决方法_MySQL
程序员文章站
2022-05-01 13:50:18
...
bitsCN.com
mysql 的主从同步挂了,从日志中报的错如下:120309 18:39:23 [Note] Slave SQL thread initialized, starting replication in log 'mysql-bin.000004' at position 2207467, relay log './mysqld-relay-bin.000011' position: 2207613 120309 18:39:23 [ERROR] Error in Log_event::read_log_event(): 'read error', data_len: 166, event_type: 2120309 18:39:23 [ERROR] Error reading relay log event: slave SQL thread aborted because of I/O error120309 18:39:23 [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 MySQL 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. Error_code: 1594120309 18:39:23 [ERROR] Error running query, slave SQL thread aborted. Fix the problem, and restart the slave SQL thread with "SLAVE START". We stopped at log 'mysql-bin.000004' position 2207467
分析主要原因是因为断电,所以引起读 binlog 出错,根据网上一些资料,修复的方法是: 1 stop slave; 2 change master to3 master_host='192.168.1.251', 4 master_user='repl', 5 master_password='password', 6 master_log_file='mysql-bin.000004', 7 master_log_pos=2207467; 8 start slave;这样就修复 OK 了.上面的同步文件和同步点 pos 是日志中报错上次记录的位置. 作者 php-oa bitsCN.com
mysql 的主从同步挂了,从日志中报的错如下:120309 18:39:23 [Note] Slave SQL thread initialized, starting replication in log 'mysql-bin.000004' at position 2207467, relay log './mysqld-relay-bin.000011' position: 2207613 120309 18:39:23 [ERROR] Error in Log_event::read_log_event(): 'read error', data_len: 166, event_type: 2120309 18:39:23 [ERROR] Error reading relay log event: slave SQL thread aborted because of I/O error120309 18:39:23 [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 MySQL 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. Error_code: 1594120309 18:39:23 [ERROR] Error running query, slave SQL thread aborted. Fix the problem, and restart the slave SQL thread with "SLAVE START". We stopped at log 'mysql-bin.000004' position 2207467
分析主要原因是因为断电,所以引起读 binlog 出错,根据网上一些资料,修复的方法是: 1 stop slave; 2 change master to3 master_host='192.168.1.251', 4 master_user='repl', 5 master_password='password', 6 master_log_file='mysql-bin.000004', 7 master_log_pos=2207467; 8 start slave;这样就修复 OK 了.上面的同步文件和同步点 pos 是日志中报错上次记录的位置. 作者 php-oa bitsCN.com
推荐阅读
-
Linux连接mysql报错:Access denied for user ‘root’@‘localhost’(using password: YES)的解决方法
-
linux配置mysql数据库远程连接失败的解决方法
-
MySQL5.6 GTID模式下同步复制报错不能跳过的解决方法
-
Linux连接mysql报错:Access denied for user ‘root’@‘localhost’(using password: YES)的解决方法
-
Linux下MySQL数据库的主从同步复制配置
-
linux下指定mysql数据库服务器主从同步的配置实例_MySQL
-
Linux环境中MySQL主从同步--添加新的从库
-
linux下指定mysql数据库服务器主从同步的配置实例
-
mysql主从同步不一致后的解决方法
-
Linux MySQL主从同步失败,报错1594的解决方法_MySQL