Bug #3401 Rare replication bug which leads to "Binlog has bad magic number" from slave
Submitted: 6 Apr 2004 16:12 Modified: 6 Apr 2004 16:16
Reporter: Guilhem Bichot Email Updates:
Status: Closed Impact on me:
Category:MySQL Server: Replication Severity:S3 (Non-critical)
Version:4.0 OS:Any (all)
Assigned to: CPU Architecture:Any

[6 Apr 2004 16:12] Guilhem Bichot
Hard to explain and repeat. The 4.1 source tree contains a test rpl_relayrotate which has the relevant synchronization options to trigger the crash.
The symptom is that the slave says its relay log has a "bad magic number".

How to repeat:

Suggested fix:
This is already fixed in 4.1, I am going to port back from the fix from 4.1 into 4.0
[6 Apr 2004 16:16] Guilhem Bichot
Thank you for your bug report. This issue has been committed to our
source repository of that product and will be incorporated into the
next release.

If necessary, you can access the source repository and build the latest
available version, including the bugfix, yourself. More information 
about accessing the source trees is available at

Additional info:

Fixed in ChangeSet@1.1771, 2004-04-07 01:14:11+02:00, guilhem@mysql.com