Changes between Version 23 and Version 24 of Replication_Issues

Timestamp:

Aug 1, 2011, 3:22:04 PM (15 years ago)

Author:

Serge CHASTEL

Comment:

--

Replication_Issues

@@ -28 +28 @@
 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.
+                 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
@@ -42 +46 @@
              Master_SSL_Key: 
       Seconds_Behind_Master: NULL
+}}}
+
+The relay log was corrupted (I ran: 'mysqlbinlog mysqld-relay-bin.000005 > /dev/null' and saw an error message lloking like:
+{{{
+ERROR: Error in Log_event::read_log_event(): 'read error', data_len: 0, event_type: 0
+Could not read entry at offset <some value>:Error in log format or read error
 }}}