Common errors and solutions of MySQL reading binlog logs

1. see binlog, Open is garbled mode , Can't see the execution sql sentence

Find out MySQL Library binlog The logs are all garbled , As shown below ：  BINLOG ’  IXZqVhNIAAAALQAAAGcBAAAAAHoAAAAAAAEABHRlc3QAAno0AAEDAABUOcnY 
IXZqVh5IAAAAKAAAAI8BAAAAAHoAAAAAAAEAAgAB//4BAAAAcu+UpA==, If you force -v They will not be implemented in detail sql sentence

The solution is ：

It can be used --base64-output=DECODE-ROWS -v Check it out sql sentence

for example ：

/usr/local/mysql/bin/mysqlbinlog--base64-output=DECODE-ROWS -v mysql-bin.000003

2. mysqlbinlog: [ERROR] unknown variable 'default-character-set=utf8mb4'

When we're in my.cnf Add default-character-set=utf8mb4 Options , So in mysqlbinlog see binlog It's a mistake .

resolvent ：mysqlbinlog Add later --no-defaults Option means that no settings in the configuration file are read

/usr/local/mysql/bin/mysqlbinlog--no-defaults mysql-bin.000003