[EMAIL PROTECTED] wrote:
So this would imply that you cannot simply stop/start a slave server - instead, I would need to write a wrapper script that stops the slave using "STOP SLAVE", and at next startup, read the master.info file to find out where it left off, and then issue a "CHANGE MASTER TO..." statement to continue on ?
That can certainly be done, but it seems strange that there's no mention of such a big "gotcha" in the MySQL manual...
it's not mentioned because it's not the way things (are supposed to) work.
i use replication extensively and i've never had to do what you suggest. stopping and starting a slave server always resumes at the last-known position (as recorded in master.info).
[ this assumes a CLEAN shutdown of the slave. if you have to kill -9 it, all bets are off. ]
are you sure that the mysql server user has write permission on all the various replication files? maybe mysqld was started once as a different user and now it can't update the master.info or relay-log.info properly. that would cause what you describe.
-jsd-
-- MySQL General Mailing List For list archives: http://lists.mysql.com/mysql To unsubscribe: http://lists.mysql.com/[EMAIL PROTECTED]
