16:01:05 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 XtraDB Cluster better by reporting any
bugs at https://bugs.launchpad.net/percona-xtradb-cluster
key_buffer_size=134217728
read_buffer_size=131072
max_used_connections=123
max_threads=502
thread_count=55
connection_count=53
It is possible that mysqld could use up to
key_buffer_size + (read_buffer_size + sort_buffer_size)*max_threads = 331448 K bytes of memory
Hope that's ok; if not, decrease some variables in the equation.
Thread pointer: 0x7f42dc2d0470
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 = 7f4316fe9e50 thread_stack 0x1000000
/usr/sbin/mysqld(my_print_stacktrace+0x2e)[0x8ccd9e]
/usr/sbin/mysqld(handle_fatal_signal+0x36c)[0x6828dc]
/lib/x86_64-linux-gnu/libpthread.so.0(+0xf0a0)[0x7f440256d0a0]
/lib/x86_64-linux-gnu/libc.so.6(+0x79429)[0x7f44007ee429]
/lib/x86_64-linux-gnu/libc.so.6(__libc_malloc+0x70)[0x7f44007efa70]
/usr/sbin/mysqld(my_malloc+0x32)[0x8c8bc2]
/usr/sbin/mysqld(reset_root_defaults+0x67)[0x8c4aa7]
/usr/sbin/mysqld(_ZN3THD16init_for_queriesEP14Relay_log_info+0x43)[0x6c7b93]
/usr/sbin/mysqld(_Z28prepare_new_connection_stateP3THD+0xe3)[0x6d0ad3]
/usr/sbin/mysqld(_Z22thd_prepare_connectionP3THD+0x1a0)[0x6d0eb0]
/usr/sbin/mysqld(_Z24do_handle_one_connectionP3THD+0x137)[0x6d1067]
/usr/sbin/mysqld(handle_one_connection+0x42)[0x6d1262]
/usr/sbin/mysqld(pfs_spawn_thread+0x140)[0xb195d0]
/lib/x86_64-linux-gnu/libpthread.so.0(+0x6b50)[0x7f4402564b50]
/lib/x86_64-linux-gnu/libc.so.6(clone+0x6d)[0x7f440085095d]
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): 1018029
Status: NOT_KILLED
You may download the Percona XtraDB Cluster operations manual by visiting http://www.percona.com/software/percona-xtradb-cluster/. You may find information
in the manual which will help you identify the cause of the crash.
150331 18:01:06 mysqld_safe Number of processes running now: 0
150331 18:01:06 mysqld_safe WSREP: not restarting wsrep node automatically
150331 18:01:06 mysqld_safe mysqld from pid file /var/run/mysqld/mysqld.pid ended
Another crash log ...
16:01:05 UTC - mysqld got signal 11 ; /bugs.launchpad .net/percona- xtradb- cluster
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 https:/
key_buffer_ size=134217728 size=131072 connections= 123 size)*max_ threads = 331448 K bytes of memory
read_buffer_
max_used_
max_threads=502
thread_count=55
connection_count=53
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: 0x7f42dc2d0470 mysqld( my_print_ stacktrace+ 0x2e)[0x8ccd9e] mysqld( handle_ fatal_signal+ 0x36c)[ 0x6828dc] 64-linux- gnu/libpthread. so.0(+0xf0a0) [0x7f440256d0a0 ] 64-linux- gnu/libc. so.6(+0x79429) [0x7f44007ee429 ] 64-linux- gnu/libc. so.6(__ libc_malloc+ 0x70)[0x7f44007 efa70] mysqld( my_malloc+ 0x32)[0x8c8bc2] mysqld( reset_root_ defaults+ 0x67)[0x8c4aa7] mysqld( _ZN3THD16init_ for_queriesEP14 Relay_log_ info+0x43) [0x6c7b93] mysqld( _Z28prepare_ new_connection_ stateP3THD+ 0xe3)[0x6d0ad3] mysqld( _Z22thd_ prepare_ connectionP3THD +0x1a0) [0x6d0eb0] mysqld( _Z24do_ handle_ one_connectionP 3THD+0x137) [0x6d1067] mysqld( handle_ one_connection+ 0x42)[0x6d1262] mysqld( pfs_spawn_ thread+ 0x140)[ 0xb195d0] 64-linux- gnu/libpthread. so.0(+0x6b50) [0x7f4402564b50 ] 64-linux- gnu/libc. so.6(clone+ 0x6d)[0x7f44008 5095d]
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 = 7f4316fe9e50 thread_stack 0x1000000
/usr/sbin/
/usr/sbin/
/lib/x86_
/lib/x86_
/lib/x86_
/usr/sbin/
/usr/sbin/
/usr/sbin/
/usr/sbin/
/usr/sbin/
/usr/sbin/
/usr/sbin/
/usr/sbin/
/lib/x86_
/lib/x86_
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): 1018029
Status: NOT_KILLED
You may download the Percona XtraDB Cluster operations manual by visiting www.percona. com/software/ percona- xtradb- cluster/. You may find information mysqld/ mysqld. pid ended
http://
in the manual which will help you identify the cause of the crash.
150331 18:01:06 mysqld_safe Number of processes running now: 0
150331 18:01:06 mysqld_safe WSREP: not restarting wsrep node automatically
150331 18:01:06 mysqld_safe mysqld from pid file /var/run/