On Tue, Aug 19, 2003 at 02:51:28PM -0400, [EMAIL PROTECTED] wrote: > > I am having another problem with replication in mysql 4.0.13. The > slave server crashed and upon re-starting there was a new relay-bin > log file created and the old relay-bin log file remained.
Right. It needs to finish with the old relay file before it can remove it and move on to the new one. > MySQL, however seemed to be stuck on the old one. The slave reported > to be running fine according to the command SHOW SLAVE STATUS, but > there is definitely an inconsistency in the data between the two > servers. Show SHOW SLAVE STATUS reported no errors? What about the error log? > Is there any way to tell MySQL to process the other relay-bin files? It should do so automatically. > I have tried using CHANGE MASTER TO to change the relay log, but > then I get the error that the position doesn't exist in the new > log. When I change the position to 0 it flushes the logs and deletes > all of the relay-bin files. Yeah, don't do that. Jeremy -- Jeremy D. Zawodny | Perl, Web, MySQL, Linux Magazine, Yahoo! <[EMAIL PROTECTED]> | http://jeremy.zawodny.com/ MySQL 4.0.13: up 18 days, processed 902,497,489 queries (578/sec. avg) -- MySQL General Mailing List For list archives: http://lists.mysql.com/mysql To unsubscribe: http://lists.mysql.com/[EMAIL PROTECTED]
