Re: Corrupted relay log
Paul Fierro wrote: One of my slaves stopped running due to a corrupted relay log. The error file shows: Error writing file 'dbs2.log' (errno: 28) Error in Log_event::read_log_event(): 'read error', data_len: 160, event_type: 2 $ perror 28 Error code 28: No space left on device You are out of disk space. -- MySQL General Mailing List For list archives: http://lists.mysql.com/mysql To unsubscribe:http://lists.mysql.com/[EMAIL PROTECTED]
Re: Corrupted relay log
On 10/28/2004 8:07 AM, gerald_clark [EMAIL PROTECTED] wrote: Paul Fierro wrote: One of my slaves stopped running due to a corrupted relay log. The error file shows: Error writing file 'dbs2.log' (errno: 28) Error in Log_event::read_log_event(): 'read error', data_len: 160, event_type: 2 $ perror 28 Error code 28: No space left on device You are out of disk space. At the time of the error this may have been the case, but I have plenty of disk space now. Is there a way to bypass/skip the corrupted relay log file? Paul -- MySQL General Mailing List For list archives: http://lists.mysql.com/mysql To unsubscribe:http://lists.mysql.com/[EMAIL PROTECTED]
Corrupted relay log
One of my slaves stopped running due to a corrupted relay log. The error file shows: Error writing file 'dbs2.log' (errno: 28) Error in Log_event::read_log_event(): 'read error', data_len: 160, event_type: 2 Error reading relay log event: slave SQL thread aborted because of I/O error Slave: Could not parse relay log event entry. The possible reasons are: the master's binary log is corrupted (you can check this by running 'mysqlbinlog' on the binary log), the slave's relay log is corrupted (you can check this by running 'mysqlbinlog' on the relay log), a network problem, or a bug in the master's or slave's MySQL code. If you want to check the master's binary log or slave's relay log, you will be able to know their names by issuing 'SHOW SLAVE STATUS' on this slave. Error_code: 0 Error running query, slave SQL thread aborted. Fix the problem, and restart the slave SQL thread with SLAVE START. We stopped at log 'dbm-bin.004' position 22254778 I ran mysqlbinlog on the relay log file as suggested in the error message, and when it stopped running it displayed: ERROR: Error in Log_event::read_log_event(): 'Event too big', data_len: 1696607332, event_type: 105 Could not read entry at offset 9068607:Error in log format or read error None of the other slaves had this problem, so I ruled out a corrupted master binary log. What are my options, if any? I tried SQL_SLAVE_SKIP_COUNTER but the slave still wouldn't start. Can I instruct the slave to skip this particular relay log file? Thanks, Paul -- MySQL General Mailing List For list archives: http://lists.mysql.com/mysql To unsubscribe:http://lists.mysql.com/[EMAIL PROTECTED]
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/[EMAIL PROTECTED]
RE: Corrupted relay log
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]
RE: Corrupted relay log
All you had to do what CHANGE MASTER TO MASTER_LOG_POS=Exec_master_log_pos, MASTER_HOST=Master_host, MASTER_USER=Master_user, MASTER_LOG_FILE=Relay_Master_Log_File This essentially forces mySQL to redownload the relay logs and stay in sync. Its call rewinding the replication thread. -- DVP -Original Message- From: Jeff McKeon [mailto:[EMAIL PROTECTED] Sent: Thursday, April 08, 2004 10:43 AM To: [EMAIL PROTECTED] Subject: RE: Corrupted relay log 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] -- MySQL General Mailing List For list archives: http://lists.mysql.com/mysql To unsubscribe:http://lists.mysql.com/[EMAIL PROTECTED]
