MySQL Forums :: Replication :: Could not parse relay log event entry


Advanced Search

Could not parse relay log event entry
Posted by: Sandarbh Shrivastava ()
Date: February 03, 2010 01:10AM

Hi,
My Slave database is not working it throws me below error message:

Slave: 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: 0

I have changed the master log position and started the slave again but now slave_IO_running shows NO.

Below are the logs which i am getting into mysql server logs:

100127 9:08:01 [ERROR] Slave: 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: 0
100127 9:08:01 [ERROR] Error running query, slave SQL thread aborted. Fix the problem, and restart the slave SQL thread with "SLAVE START". We stopped at log 'mysqldb1-bin.001059' position 421223116
100127 9:31:57 [ERROR] Error reading packet from server: Lost connection to MySQL server during query ( server_errno=2013)
100127 9:31:57 [Note] Slave I/O thread: Failed reading log event, reconnecting to retry, log 'mysqldb1-bin.001064' position 134628860
100127 9:31:57 [Note] Slave: connected to master 'user@xx.xxx.xx.xx:3306',replication resumed in log 'mysqldb1-bin.001064' at position 134628860
100127 12:55:58 [Note] Slave I/O thread killed while reading event
100127 12:55:58 [Note] Slave I/O thread exiting, read up to log 'mysqldb1-bin.001064', position 712393225
100127 12:56:03 [Note] Slave SQL thread initialized, starting replication in log 'mysqldb1-bin.001059' at position 421223116, relay log '/data/mysql/slave1-relay-bin.000633' position: 16243864
100127 12:56:03 [ERROR] Error in Log_event::read_log_event(): 'Event too big', data_len: 1029990688, event_type: 2
100127 12:56:03 [ERROR] Error reading relay log event: slave SQL thread aborted because of I/O error
100127 12:56:03 [ERROR] Slave: 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: 0
100127 12:56:03 [ERROR] Error running query, slave SQL thread aborted. Fix the problem, and restart the slave SQL thread with "SLAVE START". We stopped at log 'mysqldb1-bin.001059' position 421223116
100127 12:56:03 [Note] Slave I/O thread: connected to master 'user@xx.xxx.xx.xx:3306', replication started in log 'mysqldb1-bin.001064' at position 712393225

Sandarbh

Options: ReplyQuote


Subject Views Written By Posted
Could not parse relay log event entry 8616 Sandarbh Shrivastava 02/03/2010 01:10AM
Re: Could not parse relay log event entry 3509 Rick James 02/06/2010 03:50PM


Sorry, you can't reply to this topic. It has been closed.

Content reproduced on this site is the property of the respective copyright holders. It is not reviewed in advance by Oracle and does not necessarily represent the opinion of Oracle or any other party.