MySQL Bugs: #39250: Replication stops

Bug #39250	Replication stops
Submitted:	4 Sep 2008 15:44	Modified:	9 Oct 2008 15:52
Reporter:	Sören Rose	Email Updates:
Status:	No Feedback	Impact on me:	None
Category:	MySQL Server: Replication	Severity:	S2 (Serious)
Version:	5.0.22	OS:	Windows (2003 Server)
Assigned to:		CPU Architecture:	Any

Description:
The replication suddendly stops. The logfile says, there is a problem with the master.info file.
There should be a retry in accessing the master.info. 

080829  4:51:14 [ERROR] Failed to flush master info file
080829  4:51:14 [ERROR] Error reading relay log event: slave SQL thread aborted because of I/O error
080829  4:51:14 [Note] Slave I/O thread exiting, read up to log 'mysql-bin.000014', position 296138505
080829  4:51:14 [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
080829  4:51:14 [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.000014' position 296138363

after restarting the server, everything is fine.

How to repeat:
May be open the master.info exclusive

Suggested fix:
retry accessing master.info

Thank you for the report.

Error log contains information while error happened:

080829  4:51:14 [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
080829  4:51:14 [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.000014'
position 296138363

So it is probably not MySQL bug. Please follow instructions from error log and check your environment.

Also version 5.0.22 is old and at least one important bug #26489 about similar problem was fixed since.

Please upgrade both master and slave to current version 5.0.67, try with it and inform us if problem still exists and you haven't found problems in your environment.

We did all the things that are proposed in the log. The check on the binlog returned no errors. Everything seems ok. But the only thing to start the replication again was to restart the server.

Thank you for the feedback. So the issue was fixed?. Thanks in advance.

No feedback was provided for this bug for over a month, so it is
being suspended automatically. If you are able to provide the
information that was originally requested, please do so and change
the status of the bug back to "Open".