Changes between Version 21 and Version 22 of Replication_Issues

Timestamp:

Aug 1, 2011, 3:07:26 PM (15 years ago)

Author:

Serge CHASTEL

Comment:

--

Replication_Issues

@@ -3 +3 @@
 
 [[PageOutline]]
+
+= 20110801/1505 =
+
+ippdb03 crashed often during the last weekend. SHOW SLAVE STATUS\G showed this error message:
+{{{
+*************************** 1. row ***************************
+             Slave_IO_State: Waiting for master to send event
+                Master_Host: ippdb01.ifa.hawaii.edu
+                Master_User: repl_gpc1
+                Master_Port: 3306
+              Connect_Retry: 60
+            Master_Log_File: mysqld-bin.020270
+        Read_Master_Log_Pos: 962746384
+             Relay_Log_File: mysqld-relay-bin.000005
+              Relay_Log_Pos: 24123883
+      Relay_Master_Log_File: mysqld-bin.020269
+           Slave_IO_Running: Yes
+          Slave_SQL_Running: No
+            Replicate_Do_DB: gpc1,czardb,ippadmin,isp
+        Replicate_Ignore_DB: 
+         Replicate_Do_Table: 
+     Replicate_Ignore_Table: 
+    Replicate_Wild_Do_Table: 
+Replicate_Wild_Ignore_Table: 
+                 Last_Errno: 0
+                 Last_Error: 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.
+               Skip_Counter: 1
+        Exec_Master_Log_Pos: 24123745
+            Relay_Log_Space: 2036505138
+            Until_Condition: None
+             Until_Log_File: 
+              Until_Log_Pos: 0
+         Master_SSL_Allowed: No
+         Master_SSL_CA_File: 
+         Master_SSL_CA_Path: 
+            Master_SSL_Cert: 
+          Master_SSL_Cipher: 
+             Master_SSL_Key: 
+      Seconds_Behind_Master: NULL
+}}}
+
+I googled a bit and found that whic fixed the problem: http://www.mysqlperformanceblog.com/2008/08/02/troubleshooting-relay-log-corruption-in-mysql/
+
+Precisely I did: {{{change master to master_log_file='mysqld-bin.020269',master_log_pos=24123745;}}}
+
+The problem seems to have been fixed
+
 = 20110727/1410: ippdb03 Replication Error =
 ippdb03 crashed. SHOW SLAVE STATUS messages was like: 'Duplicate entry ...'