Bug #72437 | Error reading GTIDs from binary log: -1 | ||
---|---|---|---|
Submitted: | 24 Apr 2014 12:50 | Modified: | 24 Aug 2018 19:02 |
Reporter: | Shahriyar Rzayev | Email Updates: | |
Status: | No Feedback | Impact on me: | |
Category: | MySQL Server: InnoDB storage engine | Severity: | S1 (Critical) |
Version: | 5.6.17, 5.6.19 | OS: | Linux (CentOS 6.5) |
Assigned to: | CPU Architecture: | Any |
[24 Apr 2014 12:50]
Shahriyar Rzayev
[24 Apr 2014 12:54]
Shahriyar Rzayev
Full Slave Error Log File
Attachment: slavesrv1.err (application/octet-stream, text), 106.63 KiB.
[28 Apr 2014 15:58]
Shahriyar Rzayev
Dear all, this failed slave server was a production one and due to Linux hard drive partition problem we have to re-install Linux. sadly i will not be able to provide you any further information. But from previous BUG reports i know that in investigation ibdata* files will be helpful. So at least now i can provide you with ibdata file. Thank you.
[28 Apr 2014 16:17]
Shahriyar Rzayev
Added mysql-bug-ibdata1-72437.zip file to sftp.oracle.com:/support/incoming
[22 Jul 2014 6:23]
Shahriyar Rzayev
Could reproduce same error with single MySQL instance version 5.6.19 (with GTID enabled): 2014-07-21 09:55:42 3064 [ERROR] Error in Log_event::read_log_event(): 'read error', data_len: 8105, event_type: 30 2014-07-21 09:55:42 3064 [Warning] Error reading GTIDs from binary log: -1
[24 Jul 2018 19:02]
MySQL Verification Team
Sorry for the delay. Please check with latest release. Thanks.
[25 Aug 2018 1: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".