MySQL Master-Master or Master-Slave Replication Error Fix Rumi, January 18, 2013 Scenario Master – Master replication MasterA is a client facing server MasterB is a warm standby server (read only) MasterB restarted abruptly and when instances were braught back up MasterA (it’s slave) was showing the following error: MasterA has the following error in show slave status: Last_IO_Errno: 1236 Last_IO_Error: Got fatal error 1236 from master when reading data from binary log: ‘Could not find first log file name in binary log index file’ Solution: Slave: stop slave; Master: flush logs Master: show master status; — take note of the master log file and master log position Slave: CHANGE MASTER TO MASTER_LOG_FILE=’log-bin.00000X′, MASTER_LOG_POS=106; Slave: start slave; Read more: http://mysqlpreacher.com/wordpress/2010/12/could-not-find-first-log-file-name-in-binary-log-index-file/#ixzz2ILRnl4XI Src: http://mysqlpreacher.com/wordpress/2010/12/could-not-find-first-log-file-name-in-binary-log-index-file/ Administrations Configurations (Linux) MySQL MySQL