Bug #61241 In Master - Master replication slave I/O showing NO after some days
Submitted: 20 May 2011 5:55 Modified: 21 Jul 2011 23:39
Reporter: Venky P Email Updates:
Status: No Feedback Impact on me:
None 
Category:MySQL Server: Replication Severity:S1 (Critical)
Version:5.1.39 OS:Linux (Fedora 9 ver 2.6.25-14.fc9-x86_64 )
Assigned to: CPU Architecture:Any
Tags: I/) error in replication

[20 May 2011 5:55] Venky P
Description:
we are configured Master - Master configuration between two Fedora9 64 bit systems.
Replication working fine between two systems.
But after some days showing slave2 I/O showning NO.

In log Messages showing in Master1

110518 15:28:13 [Note] Plugin 'FEDERATED' is disabled.
110518 15:28:13 [Note] Plugin 'ndbcluster' is disabled.
110518 15:28:13  InnoDB: Started; log sequence number 0 27462945
110518 15:28:13 [Note] Event Scheduler: Loaded 0 events
110518 15:28:13 [Note] /usr/local/libexec/mysqld: ready for connections.
Version: '5.1.39-log'  socket: '/tmp/mysql.sock'  port: 3306  Source distribution
110518 15:29:06 [Note] Slave SQL thread initialized, starting replication in log 'imag-bin.000003' at position 2135667, relay log '/var/lib/mysql/relay.000023' position: 250
110518 15:29:06 [Note] Slave I/O thread: connected to master 'sqluser@192.168.70.154:3306',replication started in log 'imag-bin.000003' at position 2135667
110518 15:29:06 [ERROR] Error reading packet from server: Client requested master to start replication from impossible position ( server_errno=1236)
110518 15:29:06 [ERROR] Got fatal error 1236: 'Client requested master to start replication from impossible position' from master when reading data from binary log
110518 15:29:06 [Note] Slave I/O thread exiting, read up to log 'imag-bin.000003', position 2135667

In log Messages showing in Master2

Version: '5.1.39-log'  socket: '/tmp/mysql.sock'  port: 3306  Source distribution
110518 14:57:59 [Note] Slave SQL thread initialized, starting replication in log 'imag-bin.000003' at position 1215906, relay log '/var/lib/mysql/relay.000023' position: 118768
110518 14:57:59 [Note] Slave I/O thread: connected to master 'sqluser@192.168.70.155:3306',replication started in log 'imag-bin.000003' at position 1216232
110518 14:57:59 [ERROR] Slave SQL: Could not execute Write_rows event on table int500.ssoservicelogininfo; Duplicate entry '272' for key 'PRIMARY', Error_code: 1062; handler error HA_ERR_FOUND_DUPP_KEY; the event's master log imag-bin.000003, end_log_pos 1216205, Error_code: 1062
110518 14:57:59 [Warning] Slave: Duplicate entry '272' for key 'PRIMARY' Error_code: 1062
110518 14:57:59 [ERROR] Error running query, slave SQL thread aborted. Fix the problem, and restart the slave SQL thread with "SLAVE START". We stopped at log 'imag-bin.000003' position 1215906
110518 15:26:28 [Note] Slave I/O thread killed while reading event
110518 15:26:28 [Note] Slave I/O thread exiting, read up to log 'imag-bin.000003', position 1565852
110518 15:26:28 [Note] Slave SQL thread initialized, starting replication in log 'imag-bin.000003' at position 1215906, relay log '/var/lib/mysql/relay.000023' position: 118768
110518 15:26:28 [Note] Slave I/O thread: connected to master 'sqluser@192.168.70.155:3306',replication started in log 'imag-bin.000003' at position 1565852
110518 15:28:08 [Note] Slave: received end packet from server, apparent master shutdown:
110518 15:28:08 [Note] Slave I/O thread: Failed reading log event, reconnecting to retry, log 'imag-bin.000003' at postion 1566176
110518 15:28:08 [ERROR] Slave I/O: error reconnecting to master 'sqluser@192.168.70.155:3306' - retry-time: 60  retries: 86400, Error_code: 2013
110518 15:29:08 [Note] Slave: connected to master 'sqluser@192.168.70.155:3306',replication resumed in log 'imag-bin.000003' at position 1566176

How to repeat:
1. Master - Master replication was configured between two Fedora 9 64 bit machines.

2. After some days checked in Master1 "SHOW SLAVE STATUS" showing slave I/O : NO.

Suggested fix:
1. Long period this error message showing.

2. Some times tables contents also missing.
[20 May 2011 15:58] Valeriy Kravchuk
Please, check if the following problem still happens with recent version, 5.1.57.
[23 May 2011 4:56] Venky P
Could u give any fix on 5.1.39? Error to reproduce on 5.1.57 take long time.

--VenkiP
[21 Jun 2011 23:39] MySQL Verification Team
Could you please re-open this bug report if you find the same behavior with latest released version (there isn't fix for older version). Thanks.
[22 Jul 2011 23: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".