Results 1 to 3 of 3
  1. #1
    Join Date
    Jun 2002
    Posts
    1

    Unanswered: 020626 22:56:57 Slave: received 0 length packet from server, apparent master shutdow

    So, I have replication running and data is moving. However, on the slave this message keeps recurring over and over while the slave advances through the binary logs....

    Any ideas?

    020626 22:58:01 Error reading packet from server: Lost connection to MySQL server during query (server_errno=2013)
    020626 22:58:01 Slave: Failed reading log event, reconnecting to retry, log 'lax1edb1-bin.170' position 43587976
    020626 22:58:01 Slave: reconnected to master 'repl@lax1edb1.tm.tmcs:3306',replication resumed in log 'lax1edb1-bin.170' at position 43587976
    020626 22:58:01 Error reading packet from server: Lost connection to MySQL server during query (server_errno=2013)
    020626 22:58:01 Slave: Failed reading log event, reconnecting to retry, log 'lax1edb1-bin.170' position 43600814
    020626 22:58:01 Slave: reconnected to master 'repl@lax1edb1.tm.tmcs:3306',replication resumed in log 'lax1edb1-bin.170' at position 43600814
    020626 22:59:01 Slave: received 0 length packet from server, apparent master shutdown:
    020626 22:59:01 Slave: Failed reading log event, reconnecting to retry, log 'lax1edb1-bin.170' position 45651688
    020626 22:59:01 Slave: reconnected to master 'repl@lax1edb1.tm.tmcs:3306',replication resumed in log 'lax1edb1-bin.170' at position 45651688
    020626 22:59:03 Slave: received 0 length packet from server, apparent master shutdown:
    020626 23:00:03 Slave: Failed reading log event, reconnecting to retry, log 'lax1edb1-bin.170' position 45651688
    020626 23:00:08 Slave: reconnected to master 'repl@lax1edb1.tm.tmcs:3306',replication resumed in log 'lax1edb1-bin.170' at position 45651688
    020626 23:00:13 Error reading packet from server: Lost connection to MySQL server during query (server_errno=2013)
    020626 23:00:13 Slave: Failed reading log event, reconnecting to retry, log 'lax1edb1-bin.170' position 45810473
    020626 23:00:13 Slave: reconnected to master 'repl@lax1edb1.tm.tmcs:3306',replication resumed in log 'lax1edb1-bin.170' at position 45810473

  2. #2
    Join Date
    Jan 2003
    Location
    Olney, Maryland
    Posts
    1
    I am having very similar problem. I have one master and 20 slaves running. But only two slaves are giving me this message....
    although replication seems to be working.
    This message appears every minute...

    030113 11:58:37 Slave: received 0 length packet from server, apparent master shutdown:
    030113 11:58:37 Slave I/O thread: Failed reading log event, reconnecting to retry, log 'dv00-bin.001' position 368310767
    030113 11:58:37 Slave: received 0 length packet from server, apparent master shutdown:
    030113 11:58:37 Slave I/O thread: Failed reading log event, reconnecting to retry, log 'dv00-bin.001' position 368311694
    030113 11:58:37 Slave: received 0 length packet from server, apparent master shutdown:
    030113 11:58:37 Slave I/O thread: Failed reading log event, reconnecting to retry, log 'dv00-bin.001' position 368312930
    030113 11:58:37 Slave: received 0 length packet from server, apparent master shutdown:
    030113 11:58:37 Slave I/O thread: Failed reading log event, reconnecting to retry, log 'dv00-bin.001' position 368313548
    030113 11:58:37 Slave: received 0 length packet from server, apparent master shutdown:
    030113 11:58:37 Slave I/O thread: Failed reading log event, reconnecting to retry, log 'dv00-bin.001' position 368314475
    030113 11:58:37 Slave: received 0 length packet from server, apparent master shutdown:
    030113 11:58:37 Slave I/O thread: Failed reading log event, reconnecting to retry, log 'dv00-bin.001' position 368315093
    030113 11:58:37 Slave: received 0 length packet from server, apparent master shutdown:
    030113 11:58:37 Slave I/O thread: Failed reading log event, reconnecting to retry, log 'dv00-bin.001' position 368316329
    030113 11:58:40 Slave: received 0 length packet from server, apparent master shutdown:
    030113 11:58:40 Slave I/O thread: Failed reading log event, reconnecting to retry, log 'dv00-bin.001' position 368398832
    030113 11:58:40 Slave: received 0 length packet from server, apparent master shutdown:
    030113 11:58:40 Slave I/O thread: Failed reading log event, reconnecting to retry, log 'dv00-bin.001' position 368399141
    030113 11:58:40 Slave: received 0 length packet from server, apparent master shutdown:
    030113 11:58:40 Slave I/O thread: Failed reading log event, reconnecting to retry, log 'dv00-bin.001' position 368399450
    030113 11:58:40 Slave: received 0 length packet from server, apparent master shutdown:
    030113 11:58:40 Slave I/O thread: Failed reading log event, reconnecting to retry, log 'dv00-bin.001' position 368399759
    030113 11:58:40 Slave: received 0 length packet from server, apparent master shutdown:
    030113 11:58:40 Slave I/O thread: Failed reading log event, reconnecting to retry, log 'dv00-bin.001' position 368400068
    030113 11:58:40 Slave: received 0 length packet from server, apparent master shutdown:
    030113 11:58:40 Slave I/O thread: Failed reading log event, reconnecting to retry, log 'dv00-bin.001' position 368400377

  3. #3
    Join Date
    Dec 2003
    Posts
    1
    I ran into this as well and it was because two slaves were configured with the same server ID. One would connect but get knocked off when the other tried to connect. It will go on every minute or whatever master-connect-retry is set for.

    This became obvious when watching the process list on the master where on slave would connect, get updates, go idle, then get knocked off.

    This also wreaks havoc on the relay-log, making it grow out of control.

Posting Permissions

  • You may not post new threads
  • You may not post replies
  • You may not post attachments
  • You may not edit your posts
  •