Not the answer you need?
Register and ask your own question!

InnoDB: Assertion failure in thread 140061262591744 in file row0mysql.c line 1478

pathetpathet ContributorInactive User Role Beginner
Hello :-)

yesterday our PXC stopped. Two of three node died.
I think somebody tested something with MyISAM..
The error log is attached.

Whats happend here ?
  | Variable_name           | Value                                                                  |
  | innodb_version          | 5.5.37-35.0-35.0                                                       |
  | protocol_version        | 10                                                                     |
  | slave_type_conversions  |                                                                        |
  | version                 | 5.5.37-35.0                                                            |
  | version_comment         | Percona XtraDB Cluster (GPL), Release 35.0 (Ubuntu), wsrep_25.10.rXXXX |
  | version_compile_machine | x86_64                                                                 |
  | version_compile_os      | Linux                                                                  |
[code]140923 14:28:50  InnoDB: Assertion failure in thread 140061262591744 in file row0mysql.c line 1478
InnoDB: Failing assertion: node->pcur->rel_pos == BTR_PCUR_ON
InnoDB: We intentionally generate a memory trap.
InnoDB: Submit a detailed bug report to
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: about forcing recovery.
12:28:50 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.
Please help us make Percona XtraDB Cluster better by reporting any
bugs at

It is possible that mysqld could use up to 
key_buffer_size + (read_buffer_size + sort_buffer_size)*max_threads = 343074 K  bytes of memory
Hope that's ok; if not, decrease some variables in the equation.

Thread pointer: 0x7f625c000990
Attempting backtrace. You can use the following information to find out
where mysqld died. If you see no messages after this, something went
terribly wrong...
stack_bottom = 7f628dcdaa30 thread_stack 0x40000

Trying to get some variables.
Some pointers may be invalid and cause the dump to abort.
Query (0): is an invalid pointer
Connection ID (thread ID): 4

You may download the Percona XtraDB Cluster operations manual by visiting You may find information
in the manual which will help you identify the cause of the crash.
140923 14:28:50 mysqld_safe Number of processes running now: 0
140923 14:28:50 mysqld_safe WSREP: not restarting wsrep node automatically
140923 14:28:50 mysqld_safe mysqld from pid file /var/lib/mysql/ ended

Thanks in advanced..



  • niljoshiniljoshi MySQL Sage Inactive User Role Beginner

    As per the error logs, someone was trying to delete the records from the table.

    You issue seems similar to this bug.
    can you check if that is the case. Its happening with MyISAM + PXC
Sign In or Register to comment.

MySQL, InnoDB, MariaDB and MongoDB are trademarks of their respective owners.
Copyright ©2005 - 2020 Percona LLC. All rights reserved.