08:49:21 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=8388608
read_buffer_size=131072
max_used_connections=1263
max_threads=4002
thread_count=35
connection_count=2
It is possible that mysqld could use up to
key_buffer_size + (read_buffer_size + sort_buffer_size)*max_threads = 1602318 K bytes of memory
Hope that's ok; if not, decrease some variables in the equation.
Thread pointer: 0x3a6f0770
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 = 7fc69734cd38 thread_stack 0x40000
/usr/sbin/mysqld(my_print_stacktrace+0x35)[0x900aa5]
/usr/sbin/mysqld(handle_fatal_signal+0x4b4)[0x667e04]
/lib64/libpthread.so.0(+0xf790)[0x7fd379669790]
/usr/sbin/mysqld(_ZN10MDL_ticket7destroyEPS_+0xc)[0x6574bc]
/usr/sbin/mysqld(_Z17mysql_ull_cleanupP3THD+0x49)[0x5fd779]
/usr/sbin/mysqld(_ZN3THD7cleanupEv+0xd0)[0x6b8420]
/usr/sbin/mysqld(_ZN3THD17release_resourcesEv+0x298)[0x6b8ff8]
/usr/sbin/mysqld(_Z29one_thread_per_connection_endP3THDb+0x2e)[0x58551e]
/usr/sbin/mysqld(_Z24do_handle_one_connectionP3THD+0x101)[0x6bf011]
/usr/sbin/mysqld(handle_one_connection+0x47)[0x6bf277]
/usr/sbin/mysqld(pfs_spawn_thread+0x12a)[0xafd66a]
/lib64/libpthread.so.0(+0x7a51)[0x7fd379661a51]
/lib64/libc.so.6(clone+0x6d)[0x7fd377b6593d]
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): 153707045
Status: KILL_CONNECTION
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.
160225 12:49:21 mysqld_safe Number of processes running now: 0
160225 12:49:21 mysqld_safe WSREP: not restarting wsrep node automatically
160225 12:49:21 mysqld_safe mysqld from pid file /var/lib/mysql/pxc-02.pid ended
160225 13:06:46 mysqld_safe Starting mysqld daemon with databases from /var/lib/mysql
160225 13:06:46 mysqld_safe WSREP: Running position recovery with --log_error='/var/lib/mysql/wsrep_recovery.W41Rgz' --pid-file='/var/lib/mysql/pxc-02-recover.pid'
2016-02-25 13:06:47 0 [Warning] TIMESTAMP with implicit DEFAULT value is deprecated. Please use --explicit_defaults_for_timestamp server option (see documentation for more details).
2016-02-25 13:06:47 0 [Note] /usr/sbin/mysqld (mysqld 5.6.26-74.0-56-log) starting as process 66423 ...
160225 13:06:55 mysqld_safe WSREP: Recovered position 8a89896c-a304-11e5-bed2-1e4a9bc0b937:16497980
Log of wsrep recovery (--wsrep-recover):
This time there was no error segfault in dmesg/message log.
In addition to the log excerpt, I've attached the MySQL configuration file.
Couple of days ago, a different node crashed:
08:49:21 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=8388608 size=131072 connections= 1263 size)*max_ threads = 1602318 K bytes of memory
read_buffer_
max_used_
max_threads=4002
thread_count=35
connection_count=2
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: 0x3a6f0770 mysqld( my_print_ stacktrace+ 0x35)[0x900aa5] mysqld( handle_ fatal_signal+ 0x4b4)[ 0x667e04] libpthread. so.0(+0xf790) [0x7fd379669790 ] mysqld( _ZN10MDL_ ticket7destroyE PS_+0xc) [0x6574bc] mysqld( _Z17mysql_ ull_cleanupP3TH D+0x49) [0x5fd779] mysqld( _ZN3THD7cleanup Ev+0xd0) [0x6b8420] mysqld( _ZN3THD17releas e_resourcesEv+ 0x298)[ 0x6b8ff8] mysqld( _Z29one_ thread_ per_connection_ endP3THDb+ 0x2e)[0x58551e] mysqld( _Z24do_ handle_ one_connectionP 3THD+0x101) [0x6bf011] mysqld( handle_ one_connection+ 0x47)[0x6bf277] mysqld( pfs_spawn_ thread+ 0x12a)[ 0xafd66a] libpthread. so.0(+0x7a51) [0x7fd379661a51 ] libc.so. 6(clone+ 0x6d)[0x7fd377b 6593d]
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 = 7fc69734cd38 thread_stack 0x40000
/usr/sbin/
/usr/sbin/
/lib64/
/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 (0): is an invalid pointer
Connection ID (thread ID): 153707045
Status: KILL_CONNECTION
You may download the Percona XtraDB Cluster operations manual by visiting www.percona. com/software/ percona- xtradb- cluster/. You may find information mysql/pxc- 02.pid ended '/var/lib/ mysql/wsrep_ recovery. W41Rgz' --pid-file= '/var/lib/ mysql/pxc- 02-recover. pid' defaults_ for_timestamp server option (see documentation for more details). a304-11e5- bed2-1e4a9bc0b9 37:16497980
http://
in the manual which will help you identify the cause of the crash.
160225 12:49:21 mysqld_safe Number of processes running now: 0
160225 12:49:21 mysqld_safe WSREP: not restarting wsrep node automatically
160225 12:49:21 mysqld_safe mysqld from pid file /var/lib/
160225 13:06:46 mysqld_safe Starting mysqld daemon with databases from /var/lib/mysql
160225 13:06:46 mysqld_safe WSREP: Running position recovery with --log_error=
2016-02-25 13:06:47 0 [Warning] TIMESTAMP with implicit DEFAULT value is deprecated. Please use --explicit_
2016-02-25 13:06:47 0 [Note] /usr/sbin/mysqld (mysqld 5.6.26-74.0-56-log) starting as process 66423 ...
160225 13:06:55 mysqld_safe WSREP: Recovered position 8a89896c-
Log of wsrep recovery (--wsrep-recover):
This time there was no error segfault in dmesg/message log.
In addition to the log excerpt, I've attached the MySQL configuration file.