Skip to:

  1. Skip to Jira Navigation
  2. Skip to Side Navigation
  3. Skip to Main Content

MySQL server fails to start with an error " 7fa1d9fff700 InnoDB: Assertion failure"

Description

We are using Percona MySQL server 5.6.46.

MySQL server fails to start with an error " 7fa1d9fff700 InnoDB: Assertion failure in thread 140333123892992 in file lock0lock.cc line 5251". 

Also we tried digging more into it by running mysqld with core-file parameter enabled and generated a core dump. 

Assertion failure happens when we are restarting MySQL services. Some of the times, it get starts but other times we face an assertion failure.

Ran GDB tool on core dump to extract more information about the error.

Attaching screenshot of the back trace we obtained.

Can you tell us what exactly is causing an assertion failure ? aslo how can we mitigate the above issue ?

Environment

None

Attachments

4
  • 03 Jan 2020, 05:12 AM
  • 02 Jan 2020, 07:08 AM
  • 02 Jan 2020, 07:07 AM
  • 31 Dec 2019, 01:17 PM

Smart Checklist

Activity

Show:

Lalit Choudhary March 17, 2020 at 6:48 AM

We cannot reproduce described behavior. Please upgrade to the latest version of Percona software and test with it. In case if you are still able to reproduce the issue, please, update the report with the repeatable test case.

Lalit Choudhary March 17, 2020 at 6:39 AM

With below settings also issue not reproduciable. Tested with PS 5.6.46

1. innodb_status_output_locks on, innodb_status_output on, innodb-status-file on
2. 1. innodb_status_output_locks on, innodb_status_output on, innodb-status-file off
3. 1. innodb_status_output_locks off, innodb_status_output on, innodb-status-file off
4. innodb_status_output_locks off, innodb_status_output on, innodb-status-file on

Lalit Choudhary January 13, 2020 at 3:56 PM

Hi Chaitanya,

No need to create another bug will try to get an on-demand reproduciable test case.

Chaitanya Tondlekar January 8, 2020 at 7:36 AM

Lalit, Thanks. This worked for us. We tried disabling the innodb-status-file parameter and it doesn't give assertion failures on restart. 

But what if we want innodb status file to be enabled for dumping innodb engine metrics into file ? If enabling the parameter,it gives assertion failure on latest available version of percona server 5.6. So we need to open the bug again for the resolutions. Still there are work around for getting stats of innodb metrics. 

Really your help is appreciated.

Lalit Choudhary January 6, 2020 at 11:55 AM

as described in the bug case issue occurred when the InnoDB monitor is enabled. As i can in your case it is enabled,

Disabling  InnoDB monitor may stop this issue occurring for now.

 

 

Cannot Reproduce

Details

Assignee

Reporter

Affects versions

Priority

Smart Checklist

Created December 31, 2019 at 1:17 PM
Updated March 6, 2024 at 11:26 AM
Resolved March 17, 2020 at 6:48 AM