分析從庫(kù)1062問(wèn)題，解析從庫(kù)binlog日志，報(bào)錯(cuò)如下

[root@xxxdb0402 tmp]# mysqlbinlog mysql-bin.004271 > 4.log
ERROR: Error in Log_event::read_log_event(): 'read error', data_len: 438, event_type: 2
[root@xxxdb0402 tmp]# grep  'rding' 4.log > rd4.log
[root@xxxdb0402 tmp]# ll rd4.log
-rw-r--r-- 1 root root 0 Sep  3 17:50 rd4.log
空的，第四個(gè)日志沒(méi)有錄入操作


奇怪報(bào)錯(cuò)了，google之，3種方案

1 寫(xiě)全路徑

[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
[root@xxxdb0402 tmp]# whereis  mysqlbinlog
mysqlbinlog: /usr/bin/mysqlbinlog
[root@xxxdb0402 tmp]# /usr/bin/mysqlbinlog mysql-bin.004271 > 4.log
/usr/bin/mysqlbinlog: Character set '#45' is not a compiled character set and is not specified in the '/usr/share/mysql/charsets/Index.xml' file
ERROR: Error in Log_event::read_log_event(): 'read error', data_len: 438, event_type: 2


2 加-f強(qiáng)制解析

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


3 這個(gè)copy過(guò)來(lái)的日志的時(shí)候，db正往日志里面寫(xiě)數(shù)據(jù)呢，從新copy下binlog到/tmp下。

那就重新copy一次binlog，再解析
[root@xxxdb0402 tmp]# cp /mysqldata/data/mysql-bin.004271 /tmp/
cp: overwrite `/tmp/mysql-bin.004271'? 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

3種方案都報(bào)一樣的錯(cuò)誤。Mysql版本5.5.25a。linux環(huán)境centos6.0

這個(gè)問(wèn)題如何搞定，比較詭異？

朋友建議直接在mysql的數(shù)據(jù)目錄之下用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

結(jié)果還是一樣的報(bào)錯(cuò)。