Re: Restarting Slave After Master Crash

[Rafael Rodriguez Jr.]

i guess this thread seems dead but i ran into the same problem and this is how i fixed it. It seems that the MYSQL just needs the reference/starting point in the log so it can resume replication.

Try this

STOP SLAVE

FLUSH TABLES WITH READ LOCK;

SHOW MASTER STATUS (record these valuse it will state name of file and position)

UNLOCKTABLES;

CHANGE MASTER TO MASTER_LOG_FILE='recorded_log_file_name',
CHANGE MASTER TO MASTER_LOG_POS=recorded_log_position;

START SLAVE


you may still get an error message at first in the logs but replication should resume