Bug #672 mysqlbinlog's remote binlog dump does not work
Submitted: 18 Jun 2003 6:38 Modified: 2 Jul 2003 7:16
Reporter: Guilhem Bichot Email Updates:
Status: Closed Impact on me:
None 
Category:MySQL Server: Replication Severity:S3 (Non-critical)
Version:4.0 OS:Any (all)
Assigned to: Bugs System

[18 Jun 2003 6:38] Guilhem Bichot
Description:
When invoked with --user, mysqlbinlog will not try to read a local binlog but ask the mysqld server to send it to him.
The results are wrong.
Monty in Warsaw about this problem: "if it does not work then remove the
option".
Btw this option seems a bit useless to me.

How to repeat:
Have an alive mysqld with --log-bin, say active binlog is gbichot2-bin.000012,

[guilhem@gbichot2 1]$ mysql1 -e "show master status"
+---------------------+----------+--------------+------------------+
| File                | Position | Binlog_do_db | Binlog_ignore_db |
+---------------------+----------+--------------+------------------+
| gbichot2-bin.000012 |     2004 |              |                  |
+---------------------+----------+--------------+------------------+

[guilhem@gbichot2 1]$ /m/mysql-4.1/client/mysqlbinlog -uroot gbichot2-bin.000012
#700101  1:00:00 server id 1  log_pos 0         Rotate to gbichot2-bin.000012  pos: 4
ERROR: Could not construct log event object

The most serious bug is the ERROR immediately after only one event (all my events are not printed: I had 2000 bytes of binlog).
This first event is garbage (see the date: 1970) but this is expected, it is a dummy event which does not hurt (except that it can surprise a user).

Suggested fix:
probably remove the option from mysqlbinlog.
[1 Jul 2003 1:51] Victor Vagin
functionality is restored
[2 Jul 2003 7:16] Victor Vagin
Thank you for your bug report. This issue has been fixed in the latest
development tree for that product. You can find more information about
accessing our development trees at 
    http://www.mysql.com/doc/en/Installing_source_tree.html

remote mode was fixed