Hello, i have tested this tutorial: Setting Up Master-Master Replication With MySQL 5 On Debian Etch. I build a local test environment for furter tests with my database. After my 12 day holiday I power on the machine, and nothing, the replication was crashed. Code: May 6 11:40:04 dev1.lan mysqld[7410]: 080506 11:40:04 [ERROR] Slave I/O thread: error connecting to master '[email protected]:3306': Error: 'Lost connection to MySQL server at 'reading initial communication packet', system error: 111' errno: 2013 retry-time: 60 retries: 86400 I think this is an error related the binlog age. Im right? Can anybody confirm that? Code: May 6 11:40:12 dev1.lan mysqld[7954]: 080506 11:40:12 [Note] Slave I/O thread: connected to master '[email protected]:3306', replication started in log 'mysql-bin.000035' at position 98 May 6 11:40:12 dev1.lan mysqld[7954]: 080506 11:40:12 [ERROR] Error reading packet from server: Could not find first log file name in binary log index file ( server_errno=1236) May 6 11:40:12 dev1.lan mysqld[7954]: 080506 11:40:12 [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 May 6 11:40:12 dev1.lan mysqld[7954]: 080506 11:40:12 [Note] Slave I/O thread exiting, read up to log 'mysql-bin.000035', position 98 But the BIG question is, can this occur when I use the replication on my productive systems? 127.0.0.1
