holland-discuss team mailing list archive

[Tim Soderstrom <tim@xxxxxxxxxxxxxxxxxxxxx>]

Just to cover the simple case, you have confirmed you're not directly writing to the slave outside of replication? Just in case, do you have read_only set on the slave? I would say you best bet is to see what writes are occurring by looking at the binary log directly:

# mysqlbinlog -v -v -v --start-position=794214533 --stop-position=794214675 mysql-bin.000008

Tim S.

On Apr 11, 2013, at 5:39 AM, Brandon Metcalf wrote:

> I'm dumping mysql dbs on a server that is both a slave and a master and getting the following:
> 
> 2013-04-10 20:46:03,650 [WARNING] Sanity check on master status failed.  Previously recorded mysql-bin.000008:794214533 but currently found mysql-bin.000008:794214675
> 2013-04-10 20:46:03,650 [WARNING] ALERT! Binary log position changed during backup!
> 
> I'm stopping the slave which is indicated in the logs and my options looks like:
> 
> [mysqldump]
> file-per-database       = yes
> lock-method             = auto-detect
> databases               = "wiki", "wordpress_docs"
> dump-routines           = yes
> stop-slave              = yes
> flush-logs              = no
> bin-log-position        = yes
> 
> Indeed, the two DBs that I'm dumping have different binlog coordinates in the CHANGE MASTER statement in the dumps.
> 
> What's going on here?  Thanks.
> _______________________________________________
> Mailing list: https://launchpad.net/~holland-discuss
> Post to     : holland-discuss@xxxxxxxxxxxxxxxxxxx
> Unsubscribe : https://launchpad.net/~holland-discuss
> More help   : https://help.launchpad.net/ListHelp