A vps will be accidentally restarted once in the last week or so. Sadly, this vps is built on the Mysql master database, after the machine is restarted, "Gotfatalerror1236frommasterwhenreadingdatafrombinarylog: Clientrequestedmastertostartreplicatio" appears during Database Synchronization from the database.
A vps will be accidentally restarted once in the last week or so. Sadly, this vps is built on the Mysql master database, after the machine is restarted, "Got fatal error 1236 from master when reading data from binary log: 'client requested master to start replicatio" may occur during Database Synchronization from the database.
A vps will be accidentally restarted once in the last week or so. Sadly, this vps is built on the Mysql master database, after the machine is restarted, the following error occurs during Database Synchronization from the slave Database: "Got fatal error 1236 from master when reading data from binary log: 'client requested master to start replication from impossible position' error.
At this time, the status is: Execute on the slave DatabaseSHOW SLAVE STATUS;
Will appearSlave_IO_Running: No
. And can find
Solution (applicable to lnmp 0.9 ):
- Log on to the master database server
- Run/usr/local/mysql/bin/mysqlbinlog/usr/local/mysql/var/mysql-bin.000023> test.txt
- Less test.txt
- Find the latest position id. For details, refer:
- Run stop slave on the SLAVE Database Server mysql;
- CHANGE MASTER TO MASTERHOST = 'master database ip', MASTERUSER = 'synchronize user', MASTERPASSWORD = 'synchronized password', MASTERLOGFILE = 'mysql-bin.000023', MASTERLOG_POS = 130216;
- Slave start;
- Now let's look at the show slave status; then we can see that the synchronization is normal.
Original article address: the slave Database Synchronization fails due to the restart of the Mysql master database server (Got fatal error 1236 from mas). Thank you for sharing it with me.