Bug #4507 mysqlbinlog --read-from-remote-server sometimes cannot accept 2 binlogs

• Submitted: 11 Jul 2004 11:17
• Modified: 30 Jul 2004 21:21
• Reporter: Guilhem Bichot
• Status: Closed
• Category: MySQL Server: Replication
• Severity: S3 (Non-critical)
• Version: 4.0
• OS: Any (all)
• Assigned to: Guilhem Bichot
• CPU Architecture: Any

[11 Jul 2004 11:17] Guilhem Bichot

Description:
Happens when mysqlbinlog -R binlog.001 binlog.002 .
As mysqlbinlog -R uses COM_BINLOG_DUMP, the mysqld server kills its client thread when it finishes dumping the binlog. So for the second binlog, the connection is broken.
If you do
mysqlbinlog -R binlog.001 binlog.002,
on Unix you may not notice it because it may use Unix sockets and so reconnects automatically when needed. If you use TCP/IP, you will get:
ERROR: Error checking master version: Lost connection to MySQL server during query
when mysqlbinlog processes the 2nd binlog.

How to repeat:
see above.

Suggested fix:
Fix will appear in our development version MySQL 4.1.4.

[30 Jul 2004 21:21] 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
    http://www.mysql.com/doc/en/Installing_source_tree.html

Additional info:

Fixed in 4.1:
ChangeSet@1.1856.175.1, 2004-07-29 23:25:58+02:00, [e-mail]