Bug #40491 Replication is creating event id 100 errors in windows 2003
Submitted: 4 Nov 2008 10:50 Modified: 15 Feb 2009 12:49
Reporter: Intro IT Security Support Email Updates:
Status: No Feedback Impact on me:
None 
Category:MySQL Server: Replication Severity:S2 (Serious)
Version:5.1.29 OS:Windows (windows 2003 standard SP2)
Assigned to: CPU Architecture:Any
Tags: 5.1.29, Event ID: 100, replication

[4 Nov 2008 10:50] Intro IT Security Support
Description:
hello,

Been looking into this for some time now. I found a couple of bug reports that are similar to what we are experiencing, however none of these supply answers. 

These are: Bug #27595, Bug #5588, Bug #28608

We have setup 2 identical windows 2003 Standard SP2 machines(named IDG-Prim and IDG-Back), both with version 5.1.11 of MySQL. They are setup to replicate Master <-> Master. Below you will find the settings for replication in both my.ini's. The event logs of both machines are flooded with errors regarding mysql replication. I have included some of these messages below. These errors occur periodically every 15 minutes or so. Replication however never fails, both db's are in sync.

We are also getting a error about mysql.exe, again this never influences operation of the DB and replication of that DB. You will also find this error message below.

Hope you can be of assistance.

How to repeat:
setup Master <-> replication between 2 Windows 2003 standard SP2 machines, using Mysql V5.1.11. And the settings supplied in the attached .txt file.
[4 Nov 2008 12:34] MySQL Verification Team
Thank you for the bug report. Your server version is quite older could you please test with latest released version and comment the results, also verify the timeouts settings. Thanks in advance.
[4 Nov 2008 12:45] Intro IT Security Support
I assume you mean that i should update to v.5.1.29 as v.6 is still in alpha status. The timeout settings are all left to default.
[4 Nov 2008 12:49] MySQL Verification Team
Thank you for the feedback. Right version 5.1.29. Thanks.
[5 Nov 2008 9:46] Intro IT Security Support
setting connect_timeout = 10 in my.ini fixed our problem.
[6 Nov 2008 12:00] Intro IT Security Support
Sadly setting the time_out to 10 only fixed our problem on one of the 2 servers. Any other ideas?
[11 Nov 2008 15:42] Susanne Ebrecht
10 isn't very high.

Just try newer version (5.1.29) and set the value higher.
[18 Nov 2008 8:22] Intro IT Security Support
We updated mysql to version 5.1.29. upgrading was a pain in the ass, so we decided to do a fresh install (db was empty so that was no problem).

We however are still experiencing the same problems.
[18 Nov 2008 8:39] Intro IT Security Support
Updated the version numbers in bug report.
[20 Nov 2008 13:48] Susanne Ebrecht
Please check with:
show variables like '%time%'
the time out variable settings.

10 seconds is not much. Please increase the values to a higher value and test again.
[20 Nov 2008 14:50] Intro IT Security Support
We tried different settings, from 10 to a ridiculously high value. This however has no effect on the problem. It does not even change the interval in which the problem occurs.
[21 Nov 2008 10:42] Sveta Smirnova
Thank you for the feedback.

Please provide output of show variables like '%time%' as Susanne requested.

Also, please, try to increase slave_net_timeout
[21 Nov 2008 10:50] Intro IT Security Support
output of variables

Attachment: variables.txt (text/plain), 1.43 KiB.

[21 Nov 2008 10:52] Intro IT Security Support
Added the requested files.
[15 Jan 2009 12:49] Susanne Ebrecht
We are fishing in the dark here ....

Sveta suggested that you try to increase the value of slave_net_timeout.

Please try it.

My question is: Does your computers have different time settings? Are the clocks of the computers are synchron? Is one computer using another timezone then the other?

Please check the time of your computers.
[16 Feb 2009 0:00] Bugs System
No feedback was provided for this bug for over a month, so it is
being suspended automatically. If you are able to provide the
information that was originally requested, please do so and change
the status of the bug back to "Open".
[12 Dec 2009 0:18] Meiji KIMURA
For the cause and workaround, See Bug #48042.