I think this was a bug that was fixed in later versions of mysql, but
I'm not totally sure if it actually has been fixed .
I did get past this error though:
Error initializing relay log position: Could not find target log during
relay log initialization
What I had to do was shutdown the whole sl
Does anyone know what this replication Slave_SQL error means?
Error initializing relay log position: Could not find target log during
relay log initialization
How do I specify the target log other than what I'm doing? See below for
details.
Daniel Gibby wrote:
The problem isn't that it can't
The problem isn't that it can't connect to the master. The IO is running
fine. It is just the SQL slave thread that won't restart. I have looked
in the server log and that just has a duplication of the message I get
when I try to CHANGE MASTER TO RELAY_LOG_FILE=...
Error initializing relay log
Did you look in the error log for the slave to find out the reason it can
not contact the master?
>> Original Message <<
On 3/15/04, 1:39:44 PM, Daniel Gibby <[EMAIL PROTECTED]> wrote
regarding hard boot killed replication execution:
> My master server was hard
