You are here

Confusing MySQL Replication Error Message

MySQL Performance Blog - Thu, 05/06/2008 - 3:00am

I already wrote about some MySQL Error Messages which are confusing, here is one more:

PLAIN TEXT SQL:
  1. 080603 20:53:10 [Note] Slave: connected TO master 'repl@host.com:3306',replication resumed IN log 'master-bin.003676' at position 444286437
  2. 080603 20:53:10 [Note] Slave: received end packet FROM server, apparent master shutdown:
  3. 080603 20:53:10 [Note] Slave I/O thread: Failed reading log event, reconnecting TO retry, log 'master-bin.003676' position 444292333
  4. 080603 20:53:10 [Note] Slave: connected TO master 'repl@host.com:3306',replication resumed IN log 'master-bin.003676' at position 444292333
  5. 080603 20:53:10 [Note] Slave: received end packet FROM server, apparent master shutdown:
  6. 080603 20:53:10 [Note] Slave I/O thread: Failed reading log event, reconnecting TO retry, log 'master-bin.003676' position 444294573
  7. 080603 20:53:10 [Note] Slave: connected TO master 'repl@host.com:3306',replication resumed IN log 'master-bin.003676' at position 444294573
  8. 080603 20:53:10 [Note] Slave: received end packet FROM server, apparent master shutdown:
  9. 080603 20:53:10 [Note] Slave I/O thread: Failed reading log event, reconnecting TO retry, log 'master-bin.003676' position 444298239
  10. 080603 20:53:10 [Note] Slave: connected TO master 'repl@host.com:3306',replication resumed IN log 'master-bin.003676' at position 444298239

After setting up new slave Server I'm getting error log file flooded with messages like this and there is no hint in the message what would explain what is wrong.

In fact the issue in this case is (because of configuration error) two slave servers got the same server-id.

Seriously in this case Master clearly sees the problem in this case as there are 2 servers with same server-id connected and replicating so it should report it to the slave instead of sending end packet.

At very least it would be nice to include possible reason for this error message which MySQL already does in many other cases.

I've now filed it as a bug.

Entry posted by peter | No comment

Add to: delicious | digg | reddit | netscape | Google Bookmarks