Bug #49545 Replication playing up
Submitted: 8 Dec 2009 23:05 Modified: 8 Jan 2010 23:58
Reporter: Mohamad Charafeddine Email Updates:
Status: No Feedback Impact on me:
None 
Category:MySQL Server: Replication Severity:S2 (Serious)
Version:Ver 14.12 Distrib 5.0.22 OS:Linux (Linux 2.6.18-53.el5)
Assigned to: CPU Architecture:Any
Tags: corrupted, replication

[8 Dec 2009 23:05] Mohamad Charafeddine
Description:
Hi Guys,

The environment setup is 1 master and 3 slaves. Whenever the master is restarted, its binlogs are out of order. before doing a restart, i shutdown mysql. on shutdown its using file xbm1-bin.000007. after restarting the machine mysql opens binlog xbm1-bin.000009 but doesn't use it, then after that it opens binlog xbm1-bin.000008 and continues normally. i thought its supposed to be in order. but i cant find xbm1-bin.000008 in the bin index file and i cant see it when i do "show master logs" even though its using it.

on the other side the slaves get a communication error. here are some errors from one of the slaves (this is after restart):

091207 15:35:29 [Note] Slave I/O thread: Failed reading log event, reconnecting to retry, log 'xbm1-bin.000009' position 98
091207 15:35:29 [Note] Slave: connected to master 'synch@xbm1:3306',replication resumed in log 'xbm1-bin.000009' at position 98
091207 15:42:31 [ERROR] Error reading packet from server: Lost connection to MySQL server during query ( server_errno=2013)
091207 15:42:31 [Note] Slave I/O thread: Failed reading log event, reconnecting to retry, log 'xbm1-bZ^\K^C^A' position 4
091207 15:42:31 [Note] Slave: connected to master 'synch@xbm1:3306',replication resumed in log 'xbm1-bZ^\K^C^A' at position 4
091207 15:42:31 [ERROR] Error reading packet from server: Could not find first log file name in binary log index file ( server_errno=1236)

you can see the 4th line where the slave just gets confused and thinks the binlog name is "xbm1-bZ^\K^C^A" which stops the replication obviously.

How to repeat:
run 1 master, and 3 slaves connected to the master. shutdown MySQL on the master only then Restart the master server and you will see the bin log files.
[8 Dec 2009 23:58] Miguel Solorzano
Thank you for the bug report. Your version 5.0.22 is quite older please try current release 5.0.88. Thanks in advance.
[9 Jan 2010 0:00] Bugs System
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".