{"id":12620,"date":"2024-07-01T13:33:58","date_gmt":"2024-07-01T08:03:58","guid":{"rendered":"https:\/\/www.skynats.com\/?p=12620"},"modified":"2025-01-08T20:35:53","modified_gmt":"2025-01-08T15:05:53","slug":"how-to-fix-mysql-replication-error-1594-relay-log-read-failure","status":"publish","type":"post","link":"https:\/\/www.skynats.com\/blog\/how-to-fix-mysql-replication-error-1594-relay-log-read-failure\/","title":{"rendered":"How to Fix MySQL Replication Error 1594: “Relay Log Read Failure”"},"content":{"rendered":"\n
\"MySQL<\/figure>\n\n\n\n

Occasionally, MySQL replication fails because of corrupted relay binlogs, and just running the ‘start slave’ command will not solve the issue. Here’s a step-by-step method for resolving this issue.<\/p>\n\n\n\n

MySQL replication<\/a> on the slave has stopped. When checked the slave status, it showed Yes for Slave_IO_Running but No for Slave_SQL_Running.\u00a0 It seems that the current slave’s relay log was corrupted.<\/p>\n\n\n\n

Following is the full output from the display slave status command on a slave server.<\/p>\n\n\n\n

mysql> SHOW SLAVE STATUS\\G\n***********************1. row ***********************\nSlave_IO_State: Waiting for master to send event\nMaster_Host: *.*.*.*\nMaster_User: replicant\nMaster_Port: 3306\nConnect_Retry: 60\nMaster_Log_File: mysql-bin.013184\nRead_Master_Log_Pos: 319962954\nRelay_Log_File: db1-relay-bin.007401\nRelay_Log_Pos: 992575394\nRelay_Master_Log_File: mysql-bin.012684\nSlave_IO_Running: Yes\nSlave_SQL_Running: No\nReplicate_Do_DB:\nReplicate_Ignore_DB:\nReplicate_Do_Table:\nReplicate_Ignore_Table:\nReplicate_Wild_Do_Table:\nReplicate_Wild_Ignore_Table:\nLast_Errno: 1594\nLast_Error: 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.\nSkip_Counter: 0\nExec_Master_Log_Pos: 992575181\nRelay_Log_Space: 537058497755\nUntil_Condition: None\nUntil_Log_File:\nUntil_Log_Pos: 0\nMaster_SSL_Allowed: No\nMaster_SSL_CA_File:\nMaster_SSL_CA_Path:\nMaster_SSL_Cert:\nMaster_SSL_Cipher:\nMaster_SSL_Key:\nSeconds_Behind_Master: NULL\nMaster_SSL_Verify_Server_Cert: No\nLast_IO_Errno: 0\nLast_IO_Error:\nLast_SQL_Errno: 1594\nLast_SQL_Error: 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.\nReplicate_Ignore_Server_Ids:\nMaster_Server_Id: 2\nMaster_Info_File: \/var\/lib\/mysql\/master.info\nSQL_Delay: 0\nSQL_Remaining_Delay: NULL\nSlave_SQL_Running_State:\nMaster_Retry_Count: 86400\nMaster_Bind:\nLast_IO_Error_Timestamp:\nLast_SQL_Error_Timestamp: 240627 13:09:22\nMaster_SSL_Crl:\nMaster_SSL_Crlpath:\nRetrieved_Gtid_Set:\nExecuted_Gtid_Set:\nAuto_Position: 0\nReplicate_Rewrite_DB:\nChannel_Name:\nMaster_TLS_Version:\n1 row in set (0.00 sec)<\/code><\/pre>\n\n\n\n
To resolve this error, erase the current binlog files on the slave and set a new position. Before proceeding, keep a note of the values for Relay_Master_Log_File and Exec_Master_Log_Pos.<\/p>\n\n\n\n
Relay_Master_Log_File: mysql-bin.012684\nExec_Master_Log_Pos: 992575181<\/code><\/pre>\n\n\n\n
To relaunch replication, use the following commands.<\/p>\n\n\n\n
1. First stop the slave using<\/p>\n\n\n\n
mysql> stop slave;<\/code><\/pre>\n\n\n\n
2. Then reset the slave’s replication position in the master binary log.<\/p>\n\n\n\n
mysql> reset slave;<\/code><\/pre>\n\n\n\n
3. Configure the slave to resume reading from its previous stop position.<\/p>\n\n\n\n
mysql> change master to master_log_file='mysql-bin.012684', master_log_pos=992575181;<\/code><\/pre>\n\n\n\n
Replace the values noted before.<\/p>\n\n\n\n
4. Finally start the slave<\/p>\n\n\n\n
mysql> start slave;<\/code><\/pre>\n\n\n\n
After following the above commands, check the slave status using the command<\/p>\n\n\n\n
mysql> SHOW SLAVE STATUS\\G<\/code><\/pre>\n\n\n\n
When the Seconds_Behind_Master value equals 0, the Master and Slave servers will be synced. Note that “reset slave” will erase master.info, relay-log.info, and all relay log files, reducing the need to manually clean up the \/var\/lib\/mysql directory.<\/a> Once all commands have been executed, the slave will reconnect with the master and start to read SQL statements.\u00a0<\/p>\n\n\n\n
If you’re facing the MySQL replication error 1594: “Relay Log Read Failure,”. Our team of experts can provide comprehensive support and swift solutions to resolve this issue and ensure your database runs smoothly. Contact Skynats<\/a> for professional assistance and minimize downtime with our reliable support services.<\/p>\n","protected":false},"excerpt":{"rendered":"
Occasionally, MySQL replication fails because of corrupted relay binlogs, and just running the ‘start slave’ command will not solve the issue. Here’s a step-by-step method for resolving this issue. MySQL replication on the slave has stopped. When checked the slave status, it showed Yes for Slave_IO_Running but No for Slave_SQL_Running.\u00a0 It seems that the current […]<\/p>\n","protected":false},"author":14,"featured_media":0,"comment_status":"closed","ping_status":"open","sticky":false,"template":"","format":"standard","meta":{"footnotes":""},"categories":[257,5],"tags":[881,882,105],"class_list":["post-12620","post","type-post","status-publish","format-standard","hentry","category-mysql","category-blog","tag-data-replication","tag-mysql-troubleshooting","tag-server-administration"],"_links":{"self":[{"href":"https:\/\/www.skynats.com\/blog\/wp-json\/wp\/v2\/posts\/12620","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/www.skynats.com\/blog\/wp-json\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/www.skynats.com\/blog\/wp-json\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"https:\/\/www.skynats.com\/blog\/wp-json\/wp\/v2\/users\/14"}],"replies":[{"embeddable":true,"href":"https:\/\/www.skynats.com\/blog\/wp-json\/wp\/v2\/comments?post=12620"}],"version-history":[{"count":0,"href":"https:\/\/www.skynats.com\/blog\/wp-json\/wp\/v2\/posts\/12620\/revisions"}],"wp:attachment":[{"href":"https:\/\/www.skynats.com\/blog\/wp-json\/wp\/v2\/media?parent=12620"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/www.skynats.com\/blog\/wp-json\/wp\/v2\/categories?post=12620"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/www.skynats.com\/blog\/wp-json\/wp\/v2\/tags?post=12620"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}