rpl.rpl_binlog_max_cache_size [ERROR] Slave SQL: The incident LOST_EVENTS occured on the master. Message: error writing to the binary log, Error_code: 1590 rpl.rpl_row_basic_11bugs [Warning] Slave SQL: Could not execute Update_rows event on table test.t1; Can't find record in 't1', Error_code: 1032; handler error HA_ERR_KEY_NOT_FOUND; the event's master log master-bin.000001, end_log_pos 605, Error_code: 1032 [ERROR] Slave SQL: Error 'Unknown table 't1'' on query. Default database: 'test'. Query: 'DROP TABLE t1', Error_code: 1051 rpl.rpl_timezone [ERROR] Slave SQL: Error 'Unknown table 't1'' on query. Default database: 'test'. Query: 'DROP TABLE t1', Error_code: 1051 binlog.binlog_base64_flag [ERROR] Slave SQL: According to the master's version ('5.1.25-rc-debug-log'), it is probable that master suffers from this bug: http://bugs.mysql.com/bug.php?id=37426 and thus replicating the current binary log event may make the slave's data become different from the master's data. To take no risk, slave refuses to replicate this event and stops. We recommend that all updates be stopped on the master and slave, that the data of both be manually synchronized, that master's binary logs be deleted, that master be upgraded to a version at least equal to '5.1.26'. Then replication can be restarted. Error_code: 1105 [ERROR] Slave SQL: Table definition on master and slave does not match: Column 1 size mismatch - master has size 128, test.char128_utf8 on slave has size 385. Master's column size should be <= the slave's column size. Error_code: 1535 rpl.rpl_auto_increment_11932 [ERROR] Slave SQL: Error 'Can't drop database 'test1'; database doesn't exist' on query. Default database: ''. Query: 'drop database test1', Error_code: 1008 rpl.rpl_ignore_table [Warning] Slave SQL: Could not execute Delete_rows event on table mysql.user; Can't find record in 'user', Error_code: 1032; handler error HA_ERR_KEY_NOT_FOUND; the event's master log master-bin.000001, end_log_pos 3942, Error_code: 1032 ..... rpl.rpl_row_basic_2myisam [Warning] Slave SQL: Could not execute Delete_rows event on table test.t1; Can't find record in 't1', Error_code: 1032; handler error HA_ERR_KEY_NOT_FOUND; the event's master log master-bin.000001, end_log_pos 491, Error_code: 1032 rpl.rpl_loaddata [ERROR] Slave SQL: Query caused different errors on master and slave. Error on master: 'Duplicate entry '%-.192s' for key %d' (1062), Error on slave: 'no error' (0). Default database: 'test'. Query: 'LOAD DATA INFILE '../../tmp/SQL_LOAD-2-1-7.data' INTO TABLE `t2` FIELDS TERMINATED BY ',' OPTIONALLY ENCLOSED BY '%' ESCAPED BY '@' LINES TERMINATED BY '\n##\n' STARTING BY '>' IGNORE 1 LINES (`day`, `id`, `category`, `name`)', Error_code: 0 rpl.rpl_row_basic_3innodb [Warning] Slave SQL: Could not execute Delete_rows event on table test.t1; Can't find record in 't1', Error_code: 1032; handler error HA_ERR_KEY_NOT_FOUND; the event's master log master-bin.000001, end_log_pos 449, Error_code: 1032 rpl.rpl_loaddata_concurrent [ERROR] Slave SQL: Query caused different errors on master and slave. Error on master: 'Duplicate entry '%-.192s' for key %d' (1062), Error on slave: 'no error' (0). Default database: 'test'. Query: 'LOAD DATA CONCURRENT INFILE '../../tmp/SQL_LOAD-2-1-9.data' INTO TABLE `t2` FIELDS TERMINATED BY ',' OPTIONALLY ENCLOSED BY '%' ESCAPED BY '@' LINES TERMINATED BY '\n##\n' STARTING BY '>' IGNORE 1 LINES (`day`, `id`, `category`, `name`)', Error_code: 0