RE: Replication Stopping at position before it started????

In normal situations, you never need to change the logfile name or position. The slave would notice that it is at the end of file, and move on to the start of the next file.

I'm assuming you shut down mysql (master) when you "re-booted"; an abrupt power failure can cause confusion in the binlog positions.

> -----Original Message-----
> From: Jesse [mailto:jlc@msdlg.com]
> Sent: Wednesday, October 10, 2007 5:23 AM
> To: Nicklas Westerlund
> Cc: replication@lists.mysql.com
> Subject: Re: Replication Stopping at position before it started????
>
> > Perhaps you set master_log_pos to 235 on mysql-bin.000002 ?
>
> Nope. When I re-set the slave last night, I executed the
> following command:
> CHANGE MASTER TO
> MASTER_LOG_FILE='mysql-bin.000003',
> MASTER_LOG_POS=235;
>
> I know for sure that I did this, because I had re-booted the
> master server
> (due to an update), and noticed that the log file name had
> changed, so I was
> sure to change it before I re-started the slave.
>
> Jesse
>
>
> --
> MySQL Replication Mailing List
> For list archives: http://lists.mysql.com/replication
> To unsubscribe:
> http://lists.mysql.com/replication?unsub=rjames@yahoo-inc.com
>
>

-- 
MySQL Replication Mailing List
For list archives: 
http://lists.mysql.com/replication
To unsubscribe:    
http://lists.mysql.com/replication?unsub=lists@pantek.com