Just to clarify - are you asking for suggestions regarding avoiding 
re-seeding the slave or regarding what is likely to have gone wrong?

Generally, a newer slave can cope with an older master, but not the other 
way around. If you updated the master while slave was out of date, you may 
be out of options.

For what it's worth, LOAD DATA FROM MASTER tends to be much faster and 
more reliable than copying tar balls across if you have to re-seed.

The error indicates that there's a problem with that version, though. Have 
you tried any versions between 32 and 42?

Gordan

On Tue, 12 Jun 2007, Ian P. Christian wrote:

> I upgraded my slave server a few weeks ago, and the slave failed, with
> an error similar to the one shown below.
> 
> I rolled back my upgrade, and it started working again, so I forgot
> about it.
> 
> Today, I upgraded the master (again, from 5.0.32 to 5.0.42) - and hte
> slave failed again.
> 
> I thought upgrading the slave to match the master might help, but still
> it failed.  Below is the error.
> 
> The hostname did *not* change.
> 
> 
> 070612 13:35:09 [Warning] No argument was provided to --log-bin, and
> --log-bin-index was not used; so replication may break when this MySQL
> server acts as a master and has his hostname changed!! Please use
> '--log-bin=/var/run/mysqld/mysqld-bin' to avoid this problem.
> 
> 070612 13:35:09  InnoDB: Started; log sequence number 40 824537593
> 070612 13:35:09 [Warning] Neither --relay-log nor --relay-log-index were
> used; so replication may break when this MySQL server acts as a slave
> and has his hostname changed!! Please use
> '--relay-log=/var/run/mysqld/mysqld-relay-bin' to avoid this problem.
> 070612 13:35:09 [ERROR] Failed to open the relay log
> './xian-relay-bin.000962' (relay_log_pos 284157529)
> 070612 13:35:09 [ERROR] Could not find target log during relay log
> initialization
> 070612 13:35:09 [ERROR] Failed to initialize the master info structure
> 070612 13:35:09 [Note] /usr/sbin/mysqld: ready for connections.
> Version: '5.0.42-log'  socket: '/var/run/mysqld/mysqld.sock'  port: 3306
>  Gentoo Linux mysql-5.0.42
> 
> Any ideas/suggestions welcome, reseeding the slave will literally take days.
> 
> 


-- 
MySQL General Mailing List
For list archives: http://lists.mysql.com/mysql
To unsubscribe:    http://lists.mysql.com/[EMAIL PROTECTED]

Reply via email to