Today 2 of 3 nodes crashed with similar backtrace:
16:40:13 UTC - mysqld got signal 11 ;
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=33554432
read_buffer_size=131072
max_used_connections=296
max_threads=1000
thread_count=91
connection_count=91
It is possible that mysqld could use up to
key_buffer_size + (read_buffer_size + sort_buffer_size)*max_threads = 1197416 K bytes of memory
Hope that's ok; if not, decrease some variables in the equation.
Thread pointer: 0x588a2c00
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...
121121 10:40:15 [Note] WSREP: (0cb18548-322e-11e2-0800-bf8bb6ded1ca, 'tcp://0.0.0.0:4567') reconnecting to b2aaa747-32f1-11e2-
0800-9dbb5a52fe4a (tcp://10.0.1.11:4567), attempt 0
stack_bottom = 7fe9da186e48 thread_stack 0x40000
/usr/sbin/mysqld(my_print_stacktrace+0x35)[0x7c83f5]
/usr/sbin/mysqld(handle_fatal_signal+0x4a4)[0x6a1e04]
/lib64/libpthread.so.0(+0xf500)[0x7ff77cf01500]
/usr/sbin/mysqld(wsrep_append_foreign_key+0xa2)[0x83baf2]
/usr/sbin/mysqld[0x874ab0]
/usr/sbin/mysqld[0x877e3e]
/usr/sbin/mysqld[0x878fba]
/usr/sbin/mysqld[0x862831]
/usr/sbin/mysqld[0x840daf]
/usr/sbin/mysqld(_ZN7handler13ha_delete_rowEPKh+0x5e)[0x6a68ee]
/usr/sbin/mysqld(_Z12mysql_deleteP3THDP10TABLE_LISTP4ItemP10SQL_I_ListI8st_orderEyy+0xafd)[0x78653d]
/usr/sbin/mysqld(_Z21mysql_execute_commandP3THD+0x2833)[0x595f93]
/usr/sbin/mysqld(_Z11mysql_parseP3THDPcjP12Parser_state+0x333)[0x598de3]
/usr/sbin/mysqld[0x5997a0]
/usr/sbin/mysqld(_Z16dispatch_command19enum_server_commandP3THDPcj+0x1a82)[0x59c072]
/usr/sbin/mysqld(_Z10do_commandP3THD+0x169)[0x59c499]
/usr/sbin/mysqld(_Z24do_handle_one_connectionP3THD+0x15f)[0x63710f]
/usr/sbin/mysqld(handle_one_connection+0x51)[0x6372d1]
/lib64/libpthread.so.0(+0x7851)[0x7ff77cef9851]
/lib64/libc.so.6(clone+0x6d)[0x7ff77c17f11d]
Trying to get some variables.
Some pointers may be invalid and cause the dump to abort.
Query (7fe91833f960): is an invalid pointer
Connection ID (thread ID): 98095
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.
121121 10:40:17 mysqld_safe Number of processes running now: 0
121121 10:40:17 mysqld_safe WSREP: not restarting wsrep node automatically
------------------------------------------------------------------
I tried to start mysql again but it crashed with same backtrace.
After downgrade to 5.5.24-23.6 it started successfully.
Percona- XtraDB- Cluster- server- 5.5.28- 23.7.369. rhel6.x86_ 64
Today 2 of 3 nodes crashed with similar backtrace:
16:40:13 UTC - mysqld got signal 11 ; bugs.percona. com/
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://
key_buffer_ size=33554432 size=131072 connections= 296 size)*max_ threads = 1197416 K bytes of memory
read_buffer_
max_used_
max_threads=1000
thread_count=91
connection_count=91
It is possible that mysqld could use up to
key_buffer_size + (read_buffer_size + sort_buffer_
Hope that's ok; if not, decrease some variables in the equation.
Thread pointer: 0x588a2c00 322e-11e2- 0800-bf8bb6ded1 ca, 'tcp:// 0.0.0.0: 4567') reconnecting to b2aaa747-32f1-11e2- 10.0.1. 11:4567) , attempt 0 mysqld( my_print_ stacktrace+ 0x35)[0x7c83f5] mysqld( handle_ fatal_signal+ 0x4a4)[ 0x6a1e04] libpthread. so.0(+0xf500) [0x7ff77cf01500 ] mysqld( wsrep_append_ foreign_ key+0xa2) [0x83baf2] mysqld[ 0x874ab0] mysqld[ 0x877e3e] mysqld[ 0x878fba] mysqld[ 0x862831] mysqld[ 0x840daf] mysqld( _ZN7handler13ha _delete_ rowEPKh+ 0x5e)[0x6a68ee] mysqld( _Z12mysql_ deleteP3THDP10T ABLE_LISTP4Item P10SQL_ I_ListI8st_ orderEyy+ 0xafd)[ 0x78653d] mysqld( _Z21mysql_ execute_ commandP3THD+ 0x2833) [0x595f93] mysqld( _Z11mysql_ parseP3THDPcjP1 2Parser_ state+0x333) [0x598de3] mysqld[ 0x5997a0] mysqld( _Z16dispatch_ command19enum_ server_ commandP3THDPcj +0x1a82) [0x59c072] mysqld( _Z10do_ commandP3THD+ 0x169)[ 0x59c499] mysqld( _Z24do_ handle_ one_connectionP 3THD+0x15f) [0x63710f] mysqld( handle_ one_connection+ 0x51)[0x6372d1] libpthread. so.0(+0x7851) [0x7ff77cef9851 ] libc.so. 6(clone+ 0x6d)[0x7ff77c1 7f11d]
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...
121121 10:40:15 [Note] WSREP: (0cb18548-
0800-9dbb5a52fe4a (tcp://
stack_bottom = 7fe9da186e48 thread_stack 0x40000
/usr/sbin/
/usr/sbin/
/lib64/
/usr/sbin/
/usr/sbin/
/usr/sbin/
/usr/sbin/
/usr/sbin/
/usr/sbin/
/usr/sbin/
/usr/sbin/
/usr/sbin/
/usr/sbin/
/usr/sbin/
/usr/sbin/
/usr/sbin/
/usr/sbin/
/usr/sbin/
/lib64/
/lib64/
Trying to get some variables.
Some pointers may be invalid and cause the dump to abort.
Query (7fe91833f960): is an invalid pointer
Connection ID (thread ID): 98095
Status: NOT_KILLED
You may download the Percona Server operations manual by visiting www.percona. com/software/ percona- server/. You may find information ------- ------- ------- ------- ------- ------- ------- ------- ---
http://
in the manual which will help you identify the cause of the crash.
121121 10:40:17 mysqld_safe Number of processes running now: 0
121121 10:40:17 mysqld_safe WSREP: not restarting wsrep node automatically
-------
I tried to start mysql again but it crashed with same backtrace.
After downgrade to 5.5.24-23.6 it started successfully.