Here's what I did to fix it... Excert from MySql Manual... When you back up your slave's data, you should back up these two small files as well, along with the relay log files. They are needed to resume replication after you restore the slave's data. If you lose the relay logs but still have the `relay-log.info' file, you can check it to determine how far the SQL thread has executed in the master binary logs. Then you can use CHANGE MASTER TO with the MASTER_RELAY_LOG and MASTER_RELAY_POS options to tell the slave to re-read the binary logs from that point. This requires that the binary logs still exist on the master server.
I performed these steps... Read info form relay-log.info file. Mysql:> Slave Stop; Mysql:> Change master to master_host = '192.168.1.10', Master_User = 'name', Master_Password = 'pass', Master_log_File = '<get this from relay-log.info>', Master_log_pos = <get this from relay-log.info>; Mysql:> Slave Start; Does anyone see a problem with this method? Thanks, Jeff > -----Original Message----- > From: Jeff McKeon > Sent: Thursday, April 08, 2004 8:54 AM > To: [EMAIL PROTECTED] > Subject: Corrupted relay log > > > Is there any way to fix a corrupted relay log on a slave? > > Jeff > > -- > MySQL General Mailing List > For list archives: http://lists.mysql.com/mysql > To unsubscribe: > http://lists.mysql.com/mysql?> [EMAIL PROTECTED] > > -- MySQL General Mailing List For list archives: http://lists.mysql.com/mysql To unsubscribe: http://lists.mysql.com/[EMAIL PROTECTED]
