30-Apr-2017-m1-2-mysql-crash

m1-2-prod-mysql-sigsegv.txt

16:00:23 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=524288000
read_buffer_size=131072
max_used_connections=693
max_threads=1002
thread_count=88
connection_count=70
It is possible that mysqld could use up to
key_buffer_size + (read_buffer_size + sort_buffer_size)*max_threads = 51957084 K  bytes of memory
Hope that's ok; if not, decrease some variables in the equation.


Thread pointer: 0x281e940
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 = 7fb8b406be00 thread_stack 0x30000
/usr/sbin/mysqld(my_print_stacktrace+0x2c)[0x9250cc]
/usr/sbin/mysqld(handle_fatal_signal+0x461)[0x69e3e1]
/lib/x86_64-linux-gnu/libpthread.so.0(+0x10330)[0x7fb9390ef330]
/usr/lib/x86_64-linux-gnu/libpython2.7.so.1.0(PyObject_Call+0x2a)[0x7fb772685d2a]
/usr/lib/x86_64-linux-gnu/libpython2.7.so.1.0(PyObject_CallFunction+0xbb)[0x7fb7726407eb]
/usr/lib/x86_64-linux-gnu/libpython2.7.so.1.0(PyErr_NewException+0x8c)[0x7fb7726272ac]
/lib/security/pam_python.so(+0x6b9c)[0x7fb72cabbb9c]
/lib/x86_64-linux-gnu/libpam.so.0(+0x2dff)[0x7fb8cc150dff]
/lib/x86_64-linux-gnu/libpam.so.0(pam_acct_mgmt+0x2c)[0x7fb8cc1505dc]
/usr/lib/mysql/plugin/auth_pam_compat.so(authenticate_user_with_pam_server+0x118)[0x7fb8b6bd7678]
/usr/sbin/mysqld[0x6afb5d]
/usr/sbin/mysqld(_Z16acl_authenticateP3THDj+0x1021)[0x6c53c1]
/usr/sbin/mysqld[0x6f3bc3]
/usr/sbin/mysqld(_Z16login_connectionP3THD+0x42)[0x6f5692]
/usr/sbin/mysqld(_Z22thd_prepare_connectionP3THD+0x24)[0x6f5eb4]
/usr/sbin/mysqld(_Z24do_handle_one_connectionP3THD+0x14b)[0x6f61fb]
/usr/sbin/mysqld(handle_one_connection+0x40)[0x6f6410]
/usr/sbin/mysqld(pfs_spawn_thread+0x143)[0xb969d3]
/lib/x86_64-linux-gnu/libpthread.so.0(+0x8184)[0x7fb9390e7184]
/lib/x86_64-linux-gnu/libc.so.6(clone+0x6d)[0x7fb9385f437d]

Trying to get some variables.
Some pointers may be invalid and cause the dump to abort.
Query (0): Connection ID (thread ID): 3646767
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.
170430 09:00:23 mysqld_safe Number of processes running now: 0
170430 09:00:23 mysqld_safe WSREP: not restarting wsrep node automatically
170430 09:00:23 mysqld_safe mysqld from pid file /var/run/mysqld/mysqld.pid ended
170430 09:37:39 mysqld_safe Starting mysqld daemon with databases from /db/mysql/