Bug #58186 | binlogs are broken | ||
---|---|---|---|
Submitted: | 14 Nov 2010 19:20 | Modified: | 15 Nov 2010 20:54 |
Reporter: | Kiryl Hakhovich | Email Updates: | |
Status: | Not a Bug | Impact on me: | |
Category: | MySQL Server: General | Severity: | S2 (Serious) |
Version: | 5.1.32 | OS: | Linux (Fedora Core 13 x86_64) |
Assigned to: | CPU Architecture: | Any | |
Tags: | binlog, mysqlbinlog, replication |
[14 Nov 2010 19:20]
Kiryl Hakhovich
[14 Nov 2010 19:23]
Kiryl Hakhovich
zipped small bin log file that can't be parsed by mysqlbinlog tool on the box
Attachment: mysql-bin-102.000001.gz (application/x-gzip, text), 49.72 KiB.
[15 Nov 2010 6:47]
MySQL Verification Team
Hi Kiryl, 5.1.32 is ancient. There are numerous binlog corruption bugs fixed since then. You should consider testing a modern version, such as 5.1.52. Also, check master mysql error logs to be sure mysqld isn't crashing, thereby causing a corrupted binlog.
[15 Nov 2010 15:28]
Kiryl Hakhovich
thanks for response. mysql does not crash according to mysqld.log. when upgrading to this minor revision, should i also do table_upgrade step or can that be omitted in this case? thanks.
[15 Nov 2010 16:33]
Kiryl Hakhovich
okay. i have compiled 5.1.52 on this box, running the mtr --suite=binlog fail with following: binlog.binlog_auto_increment_bug33029 'row' [ fail ] Test ended at 2010-11-15 11:28:52 CURRENT_TEST: binlog.binlog_auto_increment_bug33029 mysqltest: At line 26: command "copy_file" failed with error 1 The result from queries just before the failure was: SET @old_relay_log_purge= @@global.relay_log_purge; - saving '/opt/mysql/mysql-test/var/log/binlog.binlog_auto_increment_bug33029-row/' to '/opt/mysql/mysql-test/var/log/binlog.binlog_auto_increment_bug33029-row/' Only 72 of 122 completed. mysql-test-run: *** ERROR: Not all tests completed (previos version 5.1.32 was failing at a different test of mtr) please advice. thank you
[15 Nov 2010 20:54]
Kiryl Hakhovich
to confirm: for version 5.1.52 compile with following options solves the issue CC='gcc' CFLAGS=' -g -O2 -DUNIV_LINUX -DUNIV_LINUX' CXX='g++' CXXFLAGS='-O3 -fno-implicit-templates -fno-exceptions -fno-rtti' LDFLAGS=' -rdynamic ' ASFLAGS='' ./configure '--with-plugins=innobase' 'prefix=/usr' '--with-ssl' '--with-big-tables' '--with-pthread' '--enable-profiling' '--enable-assembler' same options compile for 5.1.32 still breaks in mtr test for binlogsuite. hope this help to anyone.
[26 Apr 2012 10:42]
Mannoj S
Hi I use the later version than 5.1.52. But why is that I'm getting the same error when I use RBL on Linux version too? +-------------------------+------------------------------+ | Variable_name | Value | +-------------------------+------------------------------+ | protocol_version | 10 | | version | 5.1.61-log | | version_comment | MySQL Community Server (GPL) | | version_compile_machine | i686 | | version_compile_os | pc-linux-gnu | +-------------------------+------------------------------+ Below is the err msg. -bash-3.2$ mysqlbinlog /usr/local/mysql1_base/snapshot/mysql1_masterbin.000001 > rast.sql ERROR: Error in Log_event::read_log_event(): 'Found invalid event in binary log', data_len: 80, event_type: 19 Could not read entry at offset 1133:Error in log format or read error Regards, Mannoj
[26 Apr 2012 10:54]
Mannoj S
Ignore the above one. I kinda fixed it. Forgotten that it was fixed.., and posted the same.. sorry for the trouble !!