mysqld crashed with signal 11

Bug #1273567 reported by jinxuanhou
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
Percona XtraDB Cluster moved to https://jira.percona.com/projects/PXC
New
Undecided
Unassigned

Bug Description

an online server crashed suddenlly,follow is the error log:

21:01:42 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=268435456
read_buffer_size=8388608
max_used_connections=356
max_threads=1502
thread_count=140
connection_count=140
It is possible that mysqld could use up to
key_buffer_size + (read_buffer_size + sort_buffer_size)*max_threads = 61803307 K bytes of memory
Hope that's ok; if not, decrease some variables in the equation.

Thread pointer: 0x88bed5a0
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 = 7fa50d8cad58 thread_stack 0x30000
/usr/sbin/mysqld(my_print_stacktrace+0x35)[0x7dc685]
/usr/sbin/mysqld(handle_fatal_signal+0x4b4)[0x6b4924]
/lib64/libpthread.so.0[0x376200f500]
/usr/sbin/mysqld[0x88735c]
/usr/sbin/mysqld[0x87e377]
/usr/sbin/mysqld[0x8311ec]
/usr/sbin/mysqld[0x800a54]
/usr/sbin/mysqld[0x5c3651]
/usr/sbin/mysqld(_Z10sub_selectP4JOINP13st_join_tableb+0x79)[0x5c69a9]
/usr/sbin/mysqld[0x5c7377]
/usr/sbin/mysqld(_ZN4JOIN4execEv+0xc43)[0x5dcc43]
/usr/sbinmysqld(_Z12mysql_selectP3THDPPP4ItemP10TABLE_LISTjR4ListIS1_ES2_jP8st_orderSB_S2_SB_yP13select_resultP18st_select_lex_unitP13st_select_lex+0x12c)[0x5de3bc]
/usr/sbin/mysqld(_Z13handle_selectP3THDP3LEXP13select_resultm+0x1cd)[0x5dee6d]
/usr/sbin/mysqld[0x5970c2]
/usr/sbin/mysqld(_Z21mysql_execute_commandP3THD+0x3807)[0x59e117]
/usr/sbin/mysqld(_Z11mysql_parseP3THDPcjP12Parser_state+0x33b)[0x5a051b]
/usr/sbin/mysqld[0x5a0672]
/usr/sbin/mysqld(_Z16dispatch_command19enum_server_commandP3THDPcj+0x25d6)[0x5a3b76]
/usr/sbin/mysqld(_Z10do_commandP3THD+0x167)[0x5a4597]
/usr/sbin/mysqld(_Z24do_handle_one_connectionP3THD+0x14f)[0x64113f]
/usr/sbin/mysqld(handle_one_connection+0x51)[0x641321]
/usr/sbin/mysqld(pfs_spawn_thread+0x59)[0x7f5c99]
/lib64/libpthread.so.0[0x3762007851]
/lib64/libc.so.6(clone+0x6d)[0x37618e890d]

Trying to get some variables.
Some pointers may be invalid and cause the dump to abort.
Query (7fa1086246a0): is an invalid pointer
Connection ID (thread ID): 2171233
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.
140127 05:01:43 mysqld_safe Number of processes running now: 0
140127 05:01:43 mysqld_safe WSREP: not restarting wsrep node automatically
140127 05:01:43 mysqld_safe mysqld from pid file /DATA/mysql//ph-10-10-59-204.cp.no.sohu.com.pid ended

server version is:
Percona-XtraDB-Cluster-client-55-5.5.34-25.9.607.rhel6.x86_64
Percona-XtraDB-Cluster-devel-55-5.5.34-25.9.607.rhel6.x86_64
Percona-XtraDB-Cluster-shared-55-5.5.34-25.9.607.rhel6.x86_64
Percona-XtraDB-Cluster-galera-2-2.8-1.157.rhel6.x86_64
Percona-XtraDB-Cluster-server-55-5.5.34-25.9.607.rhel6.x86_64

jinxuanhou (hjxhjh2010)
description: updated
Revision history for this message
Shahriyar Rzayev (rzayev-sehriyar) wrote :

Percona now uses JIRA for bug reports so this bug report is migrated to: https://jira.percona.com/browse/PXC-1598

To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.