Description:
Hi,
we have MySQL master as
# cat /etc/redhat-release
Red Hat Enterprise Linux Server release 5.2 (Tikanga)
# mysql -V
mysql Ver 14.12 Distrib 5.0.45, for redhat-linux-gnu (x86_64) using readline 5.0
Slave MySQL is
$ mysql -V
mysql Ver 14.12 Distrib 5.0.22, for pc-linux-gnu (i686) using readline 5.0
$ cat /etc/redhat-release
Red Hat Enterprise Linux AS release 3 (Taroon Update 6)
Replication failed with
Last_Error: 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.
At the same time the Relay_Log_Space: show as 18446744071808678981 this is also wrong
this happned many time
How to repeat:
mysql> show slave status \G
*************************** 1. row ***************************
Slave_IO_State: Waiting for master to send event
Master_Host: Masterdb
Master_User: repl
Master_Port: 3306
Connect_Retry: 60
Master_Log_File: db5-bin.000041
Read_Master_Log_Pos: 23416589
Relay_Log_File: ympdbdw-relay-bin.000139
Relay_Log_Pos: 211420137
Relay_Master_Log_File: db5-bin.000040
Slave_IO_Running: Yes
Slave_SQL_Running: No
Replicate_Do_DB: bemusic,tmpfs,bemusic_archive,bemusic,tmpfs,bemusic_archive,bemusic,tmpfs,bemusic_archive
Replicate_Ignore_DB:
Replicate_Do_Table:
Replicate_Ignore_Table: bemusic.queue_item_archive,bemusic.queue_item_archive,bemusic.queue_item_archive
Replicate_Wild_Do_Table:
Replicate_Wild_Ignore_Table:
Last_Errno: 0
Last_Error: 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.
Skip_Counter: 0
Exec_Master_Log_Pos: 1061968117
Relay_Log_Space: 18446744071808678981
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: NULL
Suggested fix:
then I have stoped the slave "stop slave;"
then stoppend MySQL service
then deleted all log files then started the MySQL and slave service then it started without issue but it rebuild the DB from the begining( from the old binary log also it taking long time)
Description: Hi, we have MySQL master as # cat /etc/redhat-release Red Hat Enterprise Linux Server release 5.2 (Tikanga) # mysql -V mysql Ver 14.12 Distrib 5.0.45, for redhat-linux-gnu (x86_64) using readline 5.0 Slave MySQL is $ mysql -V mysql Ver 14.12 Distrib 5.0.22, for pc-linux-gnu (i686) using readline 5.0 $ cat /etc/redhat-release Red Hat Enterprise Linux AS release 3 (Taroon Update 6) Replication failed with Last_Error: 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. At the same time the Relay_Log_Space: show as 18446744071808678981 this is also wrong this happned many time How to repeat: mysql> show slave status \G *************************** 1. row *************************** Slave_IO_State: Waiting for master to send event Master_Host: Masterdb Master_User: repl Master_Port: 3306 Connect_Retry: 60 Master_Log_File: db5-bin.000041 Read_Master_Log_Pos: 23416589 Relay_Log_File: ympdbdw-relay-bin.000139 Relay_Log_Pos: 211420137 Relay_Master_Log_File: db5-bin.000040 Slave_IO_Running: Yes Slave_SQL_Running: No Replicate_Do_DB: bemusic,tmpfs,bemusic_archive,bemusic,tmpfs,bemusic_archive,bemusic,tmpfs,bemusic_archive Replicate_Ignore_DB: Replicate_Do_Table: Replicate_Ignore_Table: bemusic.queue_item_archive,bemusic.queue_item_archive,bemusic.queue_item_archive Replicate_Wild_Do_Table: Replicate_Wild_Ignore_Table: Last_Errno: 0 Last_Error: 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. Skip_Counter: 0 Exec_Master_Log_Pos: 1061968117 Relay_Log_Space: 18446744071808678981 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: NULL Suggested fix: then I have stoped the slave "stop slave;" then stoppend MySQL service then deleted all log files then started the MySQL and slave service then it started without issue but it rebuild the DB from the begining( from the old binary log also it taking long time)