ERROR: Error in Log_event::read_log_event(): 'read error', data_len: 438, event_type: 2

Analysis 1062 issues from the library, from the library binlog log parsing, given as
[@ xxxdb0402 the root tmp] # the mysqlbinlog MySQL-bin.004271> 4.log
ERROR: Error in log_event :: read_log_event (): 'Read error', data_len The: 438 , EVENT_TYPE: 2
[@ xxxdb0402 the root tmp] # grep 'rding' 4.log> rd4.log
[@ xxxdb0402 the root tmp] # LL rd4.log
-rw-R & lt - r-- the root the root. 1 0. 3 On Sep. 17: 50 rd4.log
empty, and the fourth did not log entry operations


strange being given, google, the three schemes
1 to write the whole path
[root @ xxxdb0402 tmp] # /opt/mysql/product/5.5.25a/bin/mysqlbinlog mysql -bin.004271> 4.log
eRROR: error in log_event :: read_log_event (): 'Read error', data_len The: 438, EVENT_TYPE: 2
[@ xxxdb0402 the root tmp] # the whereis the mysqlbinlog
the mysqlbinlog: / usr / bin / the mysqlbinlog
[the root @ xxxdb0402 tmp] # / usr / bin / mysqlbinlog mysql-bin.004271> 4.log
/ usr / bin / mysqlbinlog: the SET Character '# 45' IS A Compiled Character not not specified in the SET and IS at The '/usr/share/mysql/charsets/Index.xml' File
ERROR: Error in log_event :: read_log_event () : 'Read error', data_len The: 438, EVENT_TYPE: 2


2 -f force applied analytical
[@ xxxdb0402 the root tmp] # -f the mysqlbinlog MySQL-bin.004271> 4.log
eRROR: error in log_event :: read_log_event (): ' error the Read ', data_len: 438, event_type: 2


3 copy of this log over time, db being written to the log data inside it, under the new copy binlog to the next / tmp.
Then again copy once binlog, and then parse
[root @ xxxdb0402 tmp] # cp /mysqldata/data/mysql-bin.004271 / tmp /
cp: Overwrite `/tmp/mysql-bin.004271 'the y-?
[Root @ xxxdb0402 tmp ] # /opt/mysql/product/5.5.25a/bin/mysqlbinlog mysql-bin.004271> 4.log
ERROR: Error in Log_event::read_log_event(): 'read error', data_len: 438, event_type: 2

 

Three kinds of programs have reported the same mistake. Mysql version 5.5.25a. linux environment centos6.0

 

How to fix this problem, more strange?

 

A friend suggested direct mysql data directory under test with mysqlbinlog

[root@xxxdb0402 data]# /opt/mysql/product/5.5.25a/bin/mysqlbinlog -f mysql-bin.004271 > 4.log
ERROR: Error in Log_event::read_log_event(): 'read error', data_len: 438, event_type: 2

The result is still the same error.

 

 

Guess you like

Origin blog.csdn.net/csdnhsh/article/details/91784143