Bug #78365 | InnoDB: Assertion failure in thread ... in file trx0trx.cc line 292 | ||
---|---|---|---|
Submitted: | 8 Sep 2015 11:49 | Modified: | 23 Nov 2018 9:28 |
Reporter: | Van Stokes | Email Updates: | |
Status: | Can't repeat | Impact on me: | |
Category: | MySQL Server: InnoDB storage engine | Severity: | S1 (Critical) |
Version: | 5.6.26-log | OS: | Ubuntu (14.04.03 x64) |
Assigned to: | CPU Architecture: | Any | |
Tags: | assertion, innodb, MySQL, server |
[8 Sep 2015 11:49]
Van Stokes
[8 Sep 2015 11:49]
Van Stokes
Error log showing assertion information
Attachment: 21050908.error.mysql01.log (text/x-log), 5.12 KiB.
[8 Sep 2015 11:49]
Van Stokes
The servers my.cnf file.
Attachment: mysql01.my.cnf (application/octet-stream, text), 8.62 KiB.
[8 Sep 2015 12:44]
Van Stokes
Following: http://dev.mysql.com/doc/refman/5.6/en/forcing-innodb-recovery.html Had to do "innodb-force-recovery = 4" to get the server to start. According to the documentation: "Values of 4 or greater can permanently corrupt data files." Therefore, we are considering the server as lost and we will rebuild from another master (we are using GTID).
[23 Nov 2018 9:28]
MySQL Verification Team
Thank you for the report, I'm not able to reproduce this issue at my end on any of the 5.5,5.6,5.7 and 8.0 latest GA build. If you can provide more information, feel free to add it to this bug and change the status back to 'Open'. Thank you for your interest in MySQL.