- 论坛徽章:
- 0
|
- root@mysql1:/usr/local/mysql# bin/mysqlbinlog var/mysql-bin.000001
- /*!40019 SET @@session.max_insert_delayed_threads=0*/;
- /*!50003 SET @OLD_COMPLETION_TYPE=@@COMPLETION_TYPE,COMPLETION_TYPE=0*/;
- DELIMITER /*!*/;
- # at 4
- #111101 21:01:55 server id 128 end_log_pos 106 Start: binlog v 4, server v 5.1.37-log created 111101 21:01:55 at startup
- # Warning: this binlog is either in use or was not closed properly.
- ROLLBACK/*!*/;
- BINLOG '
- w+2vTg+AAAAAZgAAAGoAAAABAAQANS4xLjM3LWxvZwAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA
- AAAAAAAAAAAAAAAAAADD7a9OEzgNAAgAEgAEBAQEEgAAUwAEGggAAAAICAgC
- '/*!*/;
- ERROR: Error in Log_event::read_log_event(): 'Found invalid event in binary log', data_len: 78, event_type: 2
- DELIMITER ;
- # End of log file
- ROLLBACK /* added by mysqlbinlog */;
- /*!50003 SET COMPLETION_TYPE=@OLD_COMPLETION_TYPE*/;
复制代码 我在主库上创建了一个aaa的数据库,但是binlog确实这样,我刷过日志,也没用
主库的信息- mysql> show processlist;
- +----+------------+----------------------+------+-------------+------+----------------------------------------------------------------+------------------+
- | Id | User | Host | db | Command | Time | State | Info |
- +----+------------+----------------------+------+-------------+------+----------------------------------------------------------------+------------------+
- | 2 | mysqlrsync | 192.168.11.129:40801 | NULL | Binlog Dump | 417 | Has sent all binlog to slave; waiting for binlog to be updated | NULL |
- | 3 | root | localhost | NULL | Query | 0 | NULL | show processlist |
- +----+------------+----------------------+------+-------------+------+----------------------------------------------------------------+------------------+
- 2 rows in set (0.00 sec)
复制代码 slave 是信息- mysql> show slave status\G;
- *************************** 1. row ***************************
- Slave_IO_State: Waiting for master to send event
- Master_Host: 192.168.11.128
- Master_User: mysqlrsync
- Master_Port: 3306
- Connect_Retry: 60
- Master_Log_File: mysql-bin.000001
- Read_Master_Log_Pos: 184
- Relay_Log_File: mysql-relay-bin.000002
- Relay_Log_Pos: 251
- Relay_Master_Log_File: mysql-bin.000001
- Slave_IO_Running: Yes
- Slave_SQL_Running: No
- Replicate_Do_DB:
- Replicate_Ignore_DB:
- Replicate_Do_Table:
- Replicate_Ignore_Table:
- Replicate_Wild_Do_Table:
- Replicate_Wild_Ignore_Table:
- Last_Errno: 1594
- Last_Error: Relay log read failure: Could not parse relay log event entry. The possible reasons are: the master's binary log is corrupted (you can check this by running 'mysqlbinlog' on the binary log), the slave's relay log is corrupted (you can check this by running 'mysqlbinlog' on the relay log), a network problem, or a bug in the master's or slave's MySQL code. If you want to check the master's binary log or slave's relay log, you will be able to know their names by issuing 'SHOW SLAVE STATUS' on this slave.
- Skip_Counter: 0
- Exec_Master_Log_Pos: 106
- Relay_Log_Space: 484
- Until_Condition: None
- Until_Log_File:
- Until_Log_Pos: 0
- Master_SSL_Allowed: No
- Master_SSL_CA_File:
- Master_SSL_CA_Path:
- Master_SSL_Cert:
- Master_SSL_Cipher:
- Master_SSL_Key:
- Seconds_Behind_Master: NULL
- Master_SSL_Verify_Server_Cert: No
- Last_IO_Errno: 0
- Last_IO_Error:
- Last_SQL_Errno: 1594
- Last_SQL_Error: Relay log read failure: Could not parse relay log event entry. The possible reasons are: the master's binary log is corrupted (you can check this by running 'mysqlbinlog' on the binary log), the slave's relay log is corrupted (you can check this by running 'mysqlbinlog' on the relay log), a network problem, or a bug in the master's or slave's MySQL code. If you want to check the master's binary log or slave's relay log, you will be able to know their names by issuing 'SHOW SLAVE STATUS' on this slave.
- 1 row in set (0.00 sec)
- ERROR:
- No query specified
复制代码 |
|