The slave cann't be working because of the binlog_format=statement

03-19-2014, 04:23 AM

In the master node, it reported
Unsafe statement written to the binary log using statement format since BINLOG_FORMAT = STATEMENT. The statement is unsafe because it uses a LIMIT clause.
I reset this variables binlog_format=mixed to reslove this problem.
But in the slave node, the slave thread couldn't be started, it reported
[ERROR] Slave SQL: The incident LOST_EVENTS occured on the master. Message: error writing to the binary log, Error_code: 1590
[ERROR] Error running query, slave SQL thread aborted. Fix the problem, and restart the slave SQL thread with "SLAVE START". We stopped at log 'mysql-bin.000036' position 371197684

is it possible for you to stop slave, "FLUSH LOGS" on master and start slave with new master file and position details?
I hope it will keep consistent your master and slave servers. so after that I would suggest to run pt-table-checksum utility for database consistency.