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
lt;<<<<
On 3/15/04, 1:39:44 PM, Daniel Gibby <[EMAIL PROTECTED]> wrote
regarding hard boot killed replication execution:
My master server was hard booted and now my slave can't execute the
replicated binary
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
My master server was hard booted and now my slave can't execute the
replicated binary sql logs.
mysql> show slave status\G
*** 1. row ***
Master_Host: post.somehost.com
Master_User: replicator
Master_Port: 3306
Conn
