Bug #34436 | Binlog corruption on inserts with utf8 | ||
---|---|---|---|
Submitted: | 8 Feb 2008 23:31 | Modified: | 16 Mar 2008 6:12 |
Reporter: | Patrick Galbraith | Email Updates: | |
Status: | No Feedback | Impact on me: | |
Category: | MySQL Server: Replication | Severity: | S2 (Serious) |
Version: | 5.0.45 | OS: | Linux (Ubuntu Edgy) |
Assigned to: | CPU Architecture: | Any | |
Tags: | 5.0.45-log |
[8 Feb 2008 23:31]
Patrick Galbraith
[10 Feb 2008 18:25]
Valeriy Kravchuk
Thank you for a problem report. Please, upload compressed binary log to our FTP site and inform about file name and size/MD5 checksum. Try to repeat with a newer version, 5.0.51a, also.
[11 Feb 2008 13:51]
Patrick Galbraith
Valeriy, Thank you very much for the response. I have uploaded bin.000564.save and bin.000564.save.md5 (d01d6abf7faacb2e6117e37a3e9ea53d) to ftp.mysql.com/pub/mysql/upload . I'd be very interested to know what might have caused this error. I am upgrading mysql to 5.0.51 and will run the same type of test that exposed this issue and will let you know if I encounter it again.
[16 Feb 2008 6:12]
Sveta Smirnova
Thank you for the report. Did you increase max_allowed_packet on slave? If yes and you still get errors please provide output of SHOW SLAVE STATUS \G
[17 Mar 2008 0:00]
Bugs System
No feedback was provided for this bug for over a month, so it is being suspended automatically. If you are able to provide the information that was originally requested, please do so and change the status of the bug back to "Open".