Bug #39323 | slave sql thread crashes when reading relay log | ||
---|---|---|---|
Submitted: | 8 Sep 2008 17:25 | Modified: | 11 Sep 2008 16:44 |
Reporter: | Jochen Wersdörfer | Email Updates: | |
Status: | Not a Bug | Impact on me: | |
Category: | MySQL Server: Replication | Severity: | S3 (Non-critical) |
Version: | 5.0.51a-12 | OS: | Linux (Debian GNU/Linux lenny/sid) |
Assigned to: | CPU Architecture: | Any |
[8 Sep 2008 17:25]
Jochen Wersdörfer
[9 Sep 2008 11:46]
Susanne Ebrecht
Many thanks for writing a bug report. Unfortunately there are some replication bugs at the packages made by Debian. So we have to figure out first, if this bug is related to us or to Debian. Therefor we need to know how you install MySQL. Did you download the source from our webpage and then compile it or did you use the Debian package and install by using apt-get or aptitude?
[9 Sep 2008 17:38]
Jochen Wersdörfer
I used the precompiled package from Debian. Just a minute ago i tried with a self-compiled version of 5.0.67 and now there's only a parse error instead of a crash: mysql> show slave status\G *************************** 1. row *************************** Slave_IO_State: Queueing master event to the relay log Master_Host: 172.16.100.16 Master_User: repl Master_Port: 3306 Connect_Retry: 60 Master_Log_File: mysqld-bin.000072 Read_Master_Log_Pos: 129561789 Relay_Log_File: mysqld-relay-bin.000096 Relay_Log_Pos: 112362 Relay_Master_Log_File: mysqld-bin.000020 Slave_IO_Running: Yes Slave_SQL_Running: No Replicate_Do_DB: foobar 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: 0 Exec_Master_Log_Pos: 12360857 Relay_Log_Space: 60868833367 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 So, it seems to be a debian-issue, tomorrow i'll try self-compiled mysql-versions on master and slaves, maybe this is enough to get rid of this replication-problems - thanks a lot.
[11 Sep 2008 16:44]
Jochen Wersdörfer
Ok, now i tested with self-compiled 5.0.67 on master and slave and now replication works without problems.
[1 Oct 2008 20:29]
MySQL Verification Team
i suspect this could have been due to bug #26489 caused by master sending wrong packets to the slave in the event of network failures..