Did you copy the relay-log.info and relay logs from the seed slave?
Relay_Master_Log_file is line 3 in the relay-log.info file. This file
is managed by the SQL thread and helps the slave keep track of what it
has execute in the relay logs.
On Mon, 14 Feb 2005 14:03:08 -0800 (PST), Atle Veka
> On Mon, 14 Feb 2005, Jeremy Cole wrote:
> > AFAIK, the log file name is not known by the slave unless it either
> > receives a rotate log event (go to next log) or you have started it
> > against a particular log file. If you start replication "from the
> > beginning" (not specifying a log file) against a master, the first
> > filename is not passed down.
> > In order to force a filename to be displayed you could either: FLUSH
> > LOGS on the master, or specify the log file name in the CHANGE MASTER on
> > the slave.
> Hi Jeremy,
> If that's the case it would have to mean that the SQL thread knew about it
> while the IO thread did not, correct? Here's a snip of the SHOW SLAVE
> STATUS from yesterday:
> Master_Log_File: db1-bin.248
> Read_Master_Log_Pos: 428653772
> Relay_Log_File: db9-relay-bin.002
> Relay_Log_Pos: 1186147
> The way the seeding was done was that the slave got a copy of the
> replicated DB + master.info from an existing slave.
> MySQL General Mailing List
> For list archives: http://lists.mysql.com/mysql
> To unsubscribe: http://lists.mysql.com/mysql?unsub=1