mysqld quite with errcode 6

[Vladimir Sverzhinsky]

I have 3 node PXC setup on RHEL 6.
The problem is that PXC nodes started shutting down randomly with error code 6 after updating rpm's to version 5.5.29-23.7.2.389.

130217 2:07:20 InnoDB: Assertion failure in thread 140647299794688 in file fil0fil.c line 2415
InnoDB: Failing assertion: node->n_pending == 0
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.
22:07:20 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 Server better by reporting any
bugs at http://bugs.percona.com/

key_buffer_size=8388608
read_buffer_size=131072
max_used_connections=50
max_threads=400
thread_count=48
connection_count=48
It is possible that mysqld could use up to
key_buffer_size + (read_buffer_size + sort_buffer_size)*max_threads = 883651 K bytes of memory
Hope that's ok; if not, decrease some variables in the equation.

Thread pointer: 0x259e9b90
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 = 7feb0057be48 thread_stack 0x40000
/usr/sbin/mysqld(my_print_stacktrace+0x35)[0x7c9765]
/usr/sbin/mysqld(handle_fatal_signal+0x4a4)[0x6a2ce4]
/lib64/libpthread.so.0[0x3d7a80f500]
/lib64/libc.so.6(gsignal+0x35)[0x3d7a0328a5]
/lib64/libc.so.6(abort+0x175)[0x3d7a034085]
/usr/sbin/mysqld[0x8b4fb9]
/usr/sbin/mysqld[0x80b778]
/usr/sbin/mysqld[0x7ee0e9]
/usr/sbin/mysqld(_Z18rm_temporary_tableP10handlertonPc+0xf4)[0x556314]
/usr/sbin/mysqld(_Z15close_temporaryP5TABLEbb+0xba)[0x55642a]
/usr/sbin/mysqld(_Z21close_temporary_tableP3THDP5TABLEbb+0xf9)[0x55a8c9]
/usr/sbin/mysqld(_Z20drop_temporary_tableP3THDP10TABLE_LISTPb+0x79)[0x55a9c9]
/usr/sbin/mysqld(_Z23mysql_rm_table_no_locksP3THDP10TABLE_LISTbbbb+0x25a)[0x5f872a]
/usr/sbin/mysqld(_Z14mysql_rm_tableP3THDP10TABLE_LISTcc+0x15d)[0x5f940d]
/usr/sbin/mysqld(_Z21mysql_execute_commandP3THD+0xafd)[0x59479d]
/usr/sbin/mysqld(_ZN13sp_instr_stmt9exec_coreEP3THDPj+0x1e)[0x77190e]
/usr/sbin/mysqld(_ZN13sp_lex_keeper23reset_lex_and_exec_coreEP3THDPjbP8sp_instr+0x97)[0x771a97]
/usr/sbin/mysqld(_ZN13sp_instr_stmt7executeEP3THDPj+0x1bc)[0x7767ac]
/usr/sbin/mysqld(_ZN7sp_head7executeEP3THDb+0x63f)[0x77424f]
/usr/sbin/mysqld(_ZN7sp_head17execute_procedureEP3THDP4ListI4ItemE+0x687)[0x775537]
/usr/sbin/mysqld(_Z21mysql_execute_commandP3THD+0x1da8)[0x595a48]
/usr/sbin/mysqld(_Z11mysql_parseP3THDPcjP12Parser_state+0x333)[0x599323]
/usr/sbin/mysqld[0x599ce0]
/usr/sbin/mysqld(_Z16dispatch_command19enum_server_commandP3THDPcj+0x1a82)[0x59c5b2]
/usr/sbin/mysqld(_Z10do_commandP3THD+0x169)[0x59c9d9]
/usr/sbin/mysqld(_Z24do_handle_one_connectionP3THD+0x15f)[0x6379ef]
/usr/sbin/mysqld(handle_one_connection+0x51)[0x637bb1]
/lib64/libpthread.so.0[0x3d7a807851]
/lib64/libc.so.6(clone+0x6d)[0x3d7a0e811d]

Trying to get some variables.
Some pointers may be invalid and cause the dump to abort.
Query (7fe4d0169f60): is an invalid pointer
Connection ID (thread ID): 54715
Status: NOT_KILLED

You may download the Percona Server operations manual by visiting
http://www.percona.com/software/percona-server/. You may find information
in the manual which will help you identify the cause of the crash.
130217 02:07:20 mysqld_safe Number of processes running now: 0
130217 02:07:20 mysqld_safe WSREP: not restarting wsrep node automatically
130217 02:07:20 mysqld_safe mysqld from pid file /mnt/var-lib-mysql/tmp/my.pid ended

First, I thought that there was a regression in version and I downgraded RPM's to previous release 5.5.29-23.7.1.387.
But the problem is still there.

This issue seems to be very similar to - https://bugs.launchpad.net/percona-server/+bug/1128848, except that my PXC setup has barely any load.

The problem can be seen in attached error logs(sql1.g2.err and sql3.g2.err).

[Raghavendra D Prabhu (raghavendra-prabhu)]

There are existing Percona Server bugs relating to this, adding that project..