MySQL 5.0.27 from RPM, on Redhat EL4. One master, two slaves, one database. Slaves have been up for 5 days.
This afternoon, both slaves stopped at the same place, with the same error: 070718 17:28:00 [Note] Slave SQL thread initialized, starting replication in log 'hlgbinlog-oil.000015' at position 138655868, relay log '/data/mysql/logs/soda-relay.000025' position: 138656009 070718 17:28:00 [Note] Slave I/O thread: connected to master '[EMAIL PROTECTED]:3306', replication started in log 'hlgbinlog-oil.000015' at position 139702230 070718 17:28:00 [ERROR] Error reading packet from server: error reading log entry ( server_errno=1236) 070718 17:28:00 [ERROR] Got fatal error 1236: 'error reading log entry' from master when reading data from binary log 070718 17:28:00 [Note] Slave I/O thread exiting, read up to log 'hlgbinlog-oil.000015', position 139702230 If I try to stop and restart the slave threads, or restart mysql, it just logs the same error again. The relay log ends there. The last query in the relay log, which matches the query in the master's binlog at position 139702230, is large insert statement. I tried grep'ing the query out of the master's binlog with mysqlbinlog, copying it to one of the slaves, and running it there (mysql -ufoo -p < query.sql) and it worked, so the query seems fine, though perhaps its large size is related to the problem. Any suggestions on how to re-start replication, and how to avoid this? -- Cos -- MySQL General Mailing List For list archives: http://lists.mysql.com/mysql To unsubscribe: http://lists.mysql.com/[EMAIL PROTECTED]
