| Bug #44152 | At the end of a large replication MySQL logs server_errorno=2013 | ||
|---|---|---|---|
| Submitted: | 8 Apr 2009 13:57 | Modified: | 20 Jul 2012 13:33 |
| Reporter: | Gary Glickman | Email Updates: | |
| Status: | Duplicate | Impact on me: | |
| Category: | MySQL Server: Replication | Severity: | S3 (Non-critical) |
| Version: | 5.0.77 | OS: | Windows (Win2003 SP2. 8GB RAM. 60GB HD (30 GB free space)) |
| Assigned to: | CPU Architecture: | Any | |
| Tags: | Lost connection, replication, Server Erorr 2013 | ||
[8 Apr 2009 13:57]
Gary Glickman
[8 Apr 2009 15:02]
Valeriy Kravchuk
Thank you for the problem report. Please, send my.ini files from master and problematic slave. Also, send the results of ping command from slave to master during the period when this problem happens.
[13 Apr 2009 20:09]
Sveta Smirnova
Thank you for the report. Please also provide master error log file.
[12 Jun 2009 8:51]
Susanne Ebrecht
Your master has lots of shutdowns. Starting/shutdown master during 2 minutes, 2 times and so on. Is it possible that you got the error messages from slave because somebody shutdown the master?
[12 Jun 2009 14:50]
Gary Glickman
Really? After over a month of silence that is the response? Did you look at the logs? So you suggest that we were able to stop and restart the server all within 1 second? Do you even compare the times of the shutdown against the error? Sorry, I know this is free support, but still. Anyway, if you are interested in making your product better, I am posting the .err files from the master and slave again. There are a couple of months of data in there now. You will see that over a month elapsed between restarts of the master and during that time the slave threw the error regularly.
[12 Jun 2009 14:51]
Gary Glickman
slave.err - 2+ months of data
Attachment: slave.err (text/plain), 111.69 KiB.
[21 Jun 2009 23:20]
Michael Riggs
Do your 2 slaves have the same server-id? From http://www.mysqlperformanceblog.com/2008/06/04/confusing-mysql-replication-error-message/ " 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. http://bugs.mysql.com/bug.php?id=37211 "
[22 Jun 2009 9:06]
Sveta Smirnova
Can be same as bug #44430
[22 Jun 2009 12:50]
Gary Glickman
No. They do not have the same name. Like the original post states, we replicate 45+k records successfuly. But during the replication with this one host only, the error appears one or twice. The other slave never throws an error. The difference is that the error free slave is next to the master and the slave with errors is 1,000 miles away from the master accross the wan through several hops. I have already posted the slave config settings. So please review those before suggesting tomeout settings. Thanks in advance.
[23 Jun 2009 7:05]
Sveta Smirnova
Thank you for the feedback. > The difference > is that the error free slave is next to the master and the slave with > errors is 1,000 miles away from the master accross the wan through > several hops. Please check your network in this case. Try to increase timeouts. Most likely not MySQL bug. > I have already posted the slave config settings. So please review those before suggesting tomeout settings. Yes, we reviewed. There is no magic timeout value, so I'd recommend to verify how your network works.
[13 Aug 2009 9:35]
Susanne Ebrecht
We are not able to repeat it. Also it really looks like a network problem and not a MySQL problem.
[20 Jul 2012 13:33]
Jon Stephens
Duplicate of BUG#53955.
