Bug #76845 Got Fatal Error: 1236, SLAVE_IO_STATE <empty>
Submitted: 27 Apr 2015 6:38 Modified: 27 Apr 2015 7:12
Reporter: Debdas Ghosh Email Updates:
Status: Unsupported Impact on me:
None 
Category:MySQL Server: Replication Severity:S2 (Serious)
Version:5.1.37 OS:Any
Assigned to: CPU Architecture:Any

[27 Apr 2015 6:38] Debdas Ghosh
Description:
I want to make Master to Master replication through two servers (10.33.4.58 and 10.33.4.73). At 10.33.4.73 server I got this error while doing "SHOW SLAVE STATUS":

mysql> show slave status\G;
*************************** 1. row ***************************
               Slave_IO_State:
                  Master_Host: 10.33.4.58
                  Master_User: slave_user
                  Master_Port: 3306
                Connect_Retry: 60
              Master_Log_File: log-bin.000007
          Read_Master_Log_Pos: 529
               Relay_Log_File: mysql-relay-bin.000002
                Relay_Log_Pos: 4
        Relay_Master_Log_File: log-bin.000007
             Slave_IO_Running: No
            Slave_SQL_Running: Yes
              Replicate_Do_DB: testy
          Replicate_Ignore_DB:
           Replicate_Do_Table:
       Replicate_Ignore_Table:
      Replicate_Wild_Do_Table:
  Replicate_Wild_Ignore_Table:
                   Last_Errno: 0
                   Last_Error:
                 Skip_Counter: 0
          Exec_Master_Log_Pos: 529
              Relay_Log_Space: 106
              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
Master_SSL_Verify_Server_Cert: No
                Last_IO_Errno: 0
                Last_IO_Error:
               Last_SQL_Errno: 0
               Last_SQL_Error:
1 row in set (0.00 sec)

Also got this error at mysql.err file:

150427 11:55:48 [Note] Error reading relay log event: slave SQL thread was killed
150427 11:55:48 [Note] Slave SQL thread initialized, starting replication in log 'log-bin.000007' at position 529, relay log '.\mysql-relay-bin.000002' position: 4
150427 11:55:49 [Note] Slave I/O thread: connected to master 'slave_user@10.33.4.58:3306',replication started in log 'log-bin.000007' at position 529
150427 11:55:49 [ERROR] Error reading packet from server: Could not find first log file name in binary log index file ( server_errno=1236)
150427 11:55:49 [ERROR] Got fatal error 1236: 'Could not find first log file name in binary log index file' from master when reading data from binary log
150427 11:55:49 [Note] Slave I/O thread exiting, read up to log 'log-bin.000007', position 529

So I am unable to do replication from 10.33.4.58 to 10.33.4.73.
I understand there must be some issue related to log files (either master log file or relay log file). But don't know how to fix it. Kindly help.

But I am able to do replication from 10.33.4.73 to 10.33.4.58.

How to repeat:
To repeat this error:
STOP SLAVE;
START SLAVE;
[27 Apr 2015 7:12] MySQL Verification Team
Thank you for taking the time to report a problem.  Unfortunately you are not using a current version of the product you reported a problem with -- the problem might already be fixed. Please download a new version from http://www.mysql.com/downloads/

If you are able to reproduce the bug with one of the latest versions, please change the version on this bug report to the version you tested and change the status back to "Open".  Again, thank you for your continued support of MySQL.

Since EOL of version 5.1 is 2013-12-31, I'll close this report as "Unsupported". Please upgrade to 5.5/5.6.