Upgrade to 5.5.28 did not fix the issue, as server continues to crash every few days under load.
121223 8:30:11 InnoDB: Assertion failure in thread 140082639791872 in file ha_
innodb.cc line 4360
InnoDB: Failing assertion: share->idx_trans_tbl.index_count == mysql_num_index
InnoDB: We intentionally generate a memory trap.
InnoDB: Submit a detailed bug report to http://bugs.mysql.com.
InnoDB: If you get repeated assertion failures or crashes, even
InnoDB: immediately after the mysqld startup, there may be
InnoDB: corruption in the InnoDB tablespace. Please refer to
InnoDB: http://dev.mysql.com/doc/refman/5.5/en/forcing-innodb-recovery.html
InnoDB: about forcing recovery.
08:30:11 UTC - mysqld got signal 6 ;
I've tried emailing in for a price quote on getting this issue looked at, but haven't received a response back.
Upgrade to 5.5.28 did not fix the issue, as server continues to crash every few days under load.
121223 8:30:11 InnoDB: Assertion failure in thread 140082639791872 in file ha_ idx_trans_ tbl.index_ count == mysql_num_index bugs.mysql. com. dev.mysql. com/doc/ refman/ 5.5/en/ forcing- innodb- recovery. html
innodb.cc line 4360
InnoDB: Failing assertion: share->
InnoDB: We intentionally generate a memory trap.
InnoDB: Submit a detailed bug report to http://
InnoDB: If you get repeated assertion failures or crashes, even
InnoDB: immediately after the mysqld startup, there may be
InnoDB: corruption in the InnoDB tablespace. Please refer to
InnoDB: http://
InnoDB: about forcing recovery.
08:30:11 UTC - mysqld got signal 6 ;
I've tried emailing in for a price quote on getting this issue looked at, but haven't received a response back.