mysqld crashes with SIG 11
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
Percona Server moved to https://jira.percona.com/projects/PS |
Expired
|
Undecided
|
Unassigned | ||
5.6 |
Expired
|
Undecided
|
Unassigned |
Bug Description
Hello,
Our master database crashed after receiving a signal 11. The dump is attached to this bug report.
Previous to this crash, both innodb_table_stats and innodb_index_stats were missing from the filesystem and from the output of a 'SHOW TABLES' command. This went buy unoticed for a very long time until mysqld crashed with this dump.
The messages in the log before the crash were:
2014-10-
2014-10-
Messages like these were left unoticed in the logfile for months, but they were there.
We are using the following percona version:
Server version: 5.6.14-rel62.0-log Percona Server with XtraDB (GPL), Release rel62.0, Revision 483
Thank you
Please, try to install clean Percona Server 5.6.22-71.0 (latest), load the same data (after making sure persisten statistcis tables are there) and check if the same crashing query:
SELECT DISTINCT COUNT(DISTINCT `messaging_ threads` .`id`) FROM `messaging_threads`
(or whatever it was) still leads to crash.
Please, upload also your my.cnf file content. For now this looks to me like a result of somewhat incorrect upgrade from pre-5.6 version.