分析从库1062问题，解析从库binlog日志，报错如下 [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 'rd
分析从库1062问题，解析从库binlog日志，报错如下[root@xxxdb0402 tmp]# mysqlbinlog mysql-bin.004271 > 4.logERROR: 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空的，第四个日志没有录入操作奇怪报错了，google之，3种方案1 写全路径[root@xxxdb0402 tmp]# /opt/mysql/product/5.5.25a/bin/mysqlbinlog mysql-bin.004271 > 4.logERROR: Error in Log_event::read_log_event(): 'read error', data_len: 438, event_type: 2[root@xxxdb0402 tmp]# whereis mysqlbinlogmysqlbinlog: /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' fileERROR: Error in Log_event::read_log_event(): 'read error', data_len: 438, event_type: 22 加-f强制解析[root@xxxdb0402 tmp]# mysqlbinlog -f mysql-bin.004271 > 4.logERROR: Error in Log_event::read_log_event(): 'read error', data_len: 438, event_type: 23 这个copy过来的日志的时候，db正往日志里面写数据呢，从新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.logERROR: Error in Log_event::read_log_event(): 'read error', data_len: 438, event_type: 2
3种方案都报一样的错误。Mysql版本5.5.25a。linux环境centos6.0
这个问题如何搞定，比较诡异？
朋友建议直接在mysql的数据目录之下用mysqlbinlog试下
[root@xxxdb0402 data]# /opt/mysql/product/5.5.25a/bin/mysqlbinlog -f mysql-bin.004271 > 4.logERROR: Error in Log_event::read_log_event(): 'read error', data_len: 438, event_type: 2
结果还是一样的报错。
