After power failures, our MySQL slaves sometimes stop replicating. The error is:<\/p>\n
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.<\/p><\/blockquote>\n
In the past, I would restore replication from another slave<\/a>, but this method seems much better<\/a> in that it’s faster and easier.<\/p>\n
Get the Relay_Master_Log_File and Exec_Master_Log_Pos from \u201cshow slave status\\G\u201d;<\/p>\n
reset slave to that point, and let it recover by itself as follows:
\nBe careful, using Relay_Master_Log_File value from \u201cshow slave status\\G\u201d for master_log_file, not Master_Log_File value. They\u2019re the same in this case.<\/p>\nmysql> slave stop;
\nQuery OK, 0 rows affected (0.00 sec)<\/p>\nmysql> change master to master_log_file=’LBMS-bin.000012′,master_log_pos=221245113;
\nQuery OK, 0 rows affected (0.04 sec)<\/p>\nmysql> start slave;
\nQuery OK, 0 rows affected (0.00 sec)<\/p><\/blockquote>\n","protected":false},"excerpt":{"rendered":"After power failures, our MySQL slaves sometimes stop replicating. The error is: 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), … Continue reading