http://dev.nuclearrooster.com/2009/03/06/relay-log-issues-when-starting-mysql-replication-slave/ Tue, 07 Feb 2012 18:30:45 +0000 hourly 1 http://wordpress.org/?v=3.2.1 http://dev.nuclearrooster.com/2009/03/06/relay-log-issues-when-starting-mysql-replication-slave/comment-page-1/#comment-42274 Sam Tue, 07 Feb 2012 18:30:45 +0000 http://dev.nuclearrooster.com/?p=89#comment-42274 That worked great for me, after I searched several other places trying to figure out why my replication was no longer working. Thanks so much for posting it! That worked great for me, after I searched several other places trying to figure out why my replication was no longer working. Thanks so much for posting it!

]]> http://dev.nuclearrooster.com/2009/03/06/relay-log-issues-when-starting-mysql-replication-slave/comment-page-1/#comment-37254 DR.J Fri, 09 Sep 2011 12:22:25 +0000 http://dev.nuclearrooster.com/?p=89#comment-37254 Thanks you made my Friday. My instance pointed to the default relay log, even though I had defined a different one. Deleting them worked for me too. Thanks you made my Friday.
My instance pointed to the default relay log, even though I had defined a different one.
Deleting them worked for me too.

]]> http://dev.nuclearrooster.com/2009/03/06/relay-log-issues-when-starting-mysql-replication-slave/comment-page-1/#comment-32329 Akom Mon, 02 May 2011 20:33:57 +0000 http://dev.nuclearrooster.com/?p=89#comment-32329 That really helped - mine broke with a 5.0 to 5.1 upgrade on the slave (master is still 5.0). Deleted files, started, (it tried to play from beginning of relay logs, with duplicate errors), stop slave, change master to previously shown master position, start slave - and it's all good. Whew That really helped – mine broke with a 5.0 to 5.1 upgrade on the slave (master is still 5.0). Deleted files, started, (it tried to play from beginning of relay logs, with duplicate errors), stop slave, change master to previously shown master position, start slave – and it’s all good. Whew

]]>