mysqld got signal 6 ; This could be because you hit a bug.

[Vladimir Glazachev]

OS - Gentoo / CentOS
PXC - Percona-XtraDB-Cluster-5.5.31-23.7.5.438.Linux.x86_64

It happens very often.

21:48:28 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=558
max_threads=5002
thread_count=171
connection_count=171
It is possible that mysqld could use up to
key_buffer_size + (read_buffer_size + sort_buffer_size)*max_threads = 10955876 K bytes of memory
Hope that's ok; if not, decrease some variables in the equation.

Thread pointer: 0x4155cae0
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 = 7f47fb55ce78 thread_stack 0x40000
/usr/local/mysql/bin/mysqld(my_print_stacktrace+0x35)[0x7d2845]
/usr/local/mysql/bin/mysqld(handle_fatal_signal+0x4b4)[0x6aaf24]
/lib64/libpthread.so.0(+0x10450)[0x7f592b118450]
/lib64/libc.so.6(gsignal+0x35)[0x7f5929c2e735]
/lib64/libc.so.6(abort+0x180)[0x7f5929c2fb50]
/usr/local/mysql/lib/libgalera_smm.so(_ZN6galera3FSMINS_9TrxHandle5StateENS1_10TransitionENS_10EmptyGuardENS_11EmptyActionEE8shift_toES2
_+0x2d9)[0x7f5928d39e39]
/usr/local/mysql/lib/libgalera_smm.so(_ZN6galera13ReplicatorSMM11post_commitEPNS_9TrxHandleE+0xd9)[0x7f5928d57729]
/usr/local/mysql/lib/libgalera_smm.so(galera_post_commit+0x5e)[0x7f5928d6f16e]
/usr/local/mysql/bin/mysqld(_Z25wsrep_cleanup_transactionP3THD+0x97)[0x65f887]
/usr/local/mysql/bin/mysqld[0x6b0d46]
/usr/local/mysql/bin/mysqld(_Z15ha_commit_transP3THDb+0x4b9)[0x6b2239]
/usr/local/mysql/bin/mysqld(_Z12trans_commitP3THD+0x47)[0x64af37]
/usr/local/mysql/bin/mysqld(_Z21mysql_execute_commandP3THD+0x1580)[0x598ad0]
/usr/local/mysql/bin/mysqld(_Z11mysql_parseP3THDPcjP12Parser_state+0x33b)[0x59cd0b]
/usr/local/mysql/bin/mysqld[0x59dd92]
/usr/local/mysql/bin/mysqld(_Z16dispatch_command19enum_server_commandP3THDPcj+0x1af2)[0x59ff92]
/usr/local/mysql/bin/mysqld(_Z10do_commandP3THD+0x167)[0x5a0587]
/usr/local/mysql/bin/mysqld(_Z24do_handle_one_connectionP3THD+0x14f)[0x63c4bf]
/usr/local/mysql/bin/mysqld(handle_one_connection+0x51)[0x63c6a1]
/lib64/libpthread.so.0(+0x7c64)[0x7f592b10fc64]
/lib64/libc.so.6(clone+0x6d)[0x7f5929ce376d]

Trying to get some variables.
Some pointers may be invalid and cause the dump to abort.
Query (7f4208f754b0): COMMIT
Connection ID (thread ID): 3357573
Status: NOT_KILLED

[Vladimir Glazachev (studzvg)]

Suddenly one og three nodes in clusters crashes and it happens quite often.
PXC - Percona-XtraDB-Cluster-5.5.31-23.7.5.438.Linux.x86_64

[Vladimir Glazachev (studzvg)]

PXC - Percona-XtraDB-Cluster-5.5.31-23.7.5.438.Linux.x86_64

[Raghavendra D Prabhu (raghavendra-prabhu)]

@Vladimir,

Do you see this message - 130829 14:52:17 [ERROR] WSREP: FSM: no such a transition EXECUTING -> COMMITTED - in the logs? If yes, then it is similar to http://paste.wnohang.net/69af6a which is being debugged here https://bugs.launchpad.net/percona-xtradb-cluster/+bug/1123233

[Vladimir Glazachev (studzvg)]

Yes, I did, I see this message before the crash:
130829 17:48:28 [ERROR] WSREP: FSM: no such a transition EXECUTING -> COMMITTED

[Vladimir Glazachev (studzvg)]

I've checked that case, but I don't see solution for that. Is there some workaround ?

[Raghavendra D Prabhu (raghavendra-prabhu)]

Marking this a duplicate of lp:1123233 That issue has fixed this crash for most of the cases, you can test with latest PXC 5.5.33 and let us know.