The background: We are doing replication. The file-system containing the SLAVE's relay-log got filled to capacity. Later on, I noticed replication has not been working for the last month or more.
My Action: I deleted the 2 oldest relay-log then attempted to restart SLAVE. Now, the SLAVE will not start. Replication will not start. The SLAVE continues to request for those logs. My Question: What instructions/command can I issue to the SLAVE so it can ignore relay-logs not found? See below for msg I have been getting from the SLAVE -- for all attempts to restart. 080809 2:09:23 [ERROR] Failed to open the relay log 'FIRST' (relay_log_pos 4) 080809 2:09:23 [ERROR] Could not open log file 080809 2:13:58 [ERROR] Error reading master configuration 080809 2:29:49 [ERROR] Error reading master configuration 080809 7:31:40 [ERROR] Error reading master configuration 080809 7:57:32 [ERROR] Failed to open log (file './naxbmisq02-relay-bin.000157', errno 2) 080809 7:57:32 [ERROR] Failed to open the relay log 'FIRST' (relay_log_pos 4) 080809 7:57:32 [ERROR] Could not open log file 080809 8:01:27 [ERROR] Error reading master configuration 080809 8:11:42 [ERROR] Error reading master configuration ******************************************** This message is intended only for the use of the Addressee and may contain information that is PRIVILEGED and CONFIDENTIAL. If you are not the intended recipient, you are hereby notified that any dissemination of this communication is strictly prohibited. If you have received this communication in error, please erase all copies of the message and its attachments and notify us immediately. Thank you. ******************************************** -- MySQL General Mailing List For list archives: http://lists.mysql.com/mysql To unsubscribe: http://lists.mysql.com/[EMAIL PROTECTED]
