MySQL Forums
Forum List  »  InnoDB

Assertion Error - Another Database Crashing. - fts0que.cc
Posted by: Shamus J
Date: February 05, 2014 11:30AM

I get this "assertion failure" error many times in a day. Database crashes then restarts. Any help is appreciated.

##########################
2014-02-05 08:56:24 8c6b8f000 InnoDB: Assertion failure in thread 37693747200 in file fts0que.cc line 2616
InnoDB: Failing assertion: num_token < MAX_PROXIMITY_ITEM
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.6/en/forcing-innodb-recovery.html
InnoDB: about forcing recovery.
13:56:24 UTC - mysqld got signal 6 ;
This could be because you hit a bug. It is also possible that this binary
or one of the libraries it was linked against is corrupt, improperly built,
or misconfigured. This error can also be caused by malfunctioning hardware.
We will try our best to scrape up some info that will hopefully help
diagnose the problem, but since we have already crashed,
something is definitely wrong and this may fail.
################



Edited 1 time(s). Last edit at 02/05/2014 12:44PM by Shamus J.

Options: ReplyQuote


Subject
Views
Written By
Posted
Assertion Error - Another Database Crashing. - fts0que.cc
2191
February 05, 2014 11:30AM


Sorry, you can't reply to this topic. It has been closed.

Content reproduced on this site is the property of the respective copyright holders. It is not reviewed in advance by Oracle and does not necessarily represent the opinion of Oracle or any other party.