I just had an instance crash with a similar query.
select /*! SQL_NO_CACHE */ @a:='2013-01-14 14:57:00', @b:='(none)', @c:='10.20.36.131', @d:='3307', X.* from information_schema.INNODB_BUFFER_POOL_STATS as X
The instance is MyISAM only and I run it with skip-innodb.
Version: '5.1.66rel14.1' socket: '/san/mainolpanalytics/mainolpanalytics.sock' port: 3307 Percona Server with XtraDB (GPL), Release rel14.1, Revision 495
121230 9:23:43 [Note] Event Scheduler: scheduler thread started with id 1
22:57:35 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=1073741824
read_buffer_size=131072
max_used_connections=14
max_threads=50
thread_count=10
connection_count=9
It is possible that mysqld could use up to
key_buffer_size + (read_buffer_size + sort_buffer_size)*max_threads = 1157930 K bytes of memory
Hope that's ok; if not, decrease some variables in the equation.
Thread pointer: 0x7f568800f550
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 = 7f568ee8de98 thread_stack 0x40000
/usr/local/mainolpanalytics/libexec/mysqld(my_print_stacktrace+0x35)[0x8ab885]
/usr/local/mainolpanalytics/libexec/mysqld(handle_fatal_signal+0x378)[0x6ae2f8]
/lib/libpthread.so.0(+0xef60)[0x7f56d154df60]
/usr/local/mainolpanalytics/libexec/mysqld[0x800cb6]
/usr/local/mainolpanalytics/libexec/mysqld[0x74e365]
/usr/local/mainolpanalytics/libexec/mysqld(_Z24get_schema_tables_resultP4JOIN23enum_schema_table_state+0x1d1)[0x6c5271]
/usr/local/mainolpanalytics/libexec/mysqld(_ZN4JOIN4execEv+0x3ff)[0x63a7ff]
/usr/local/mainolpanalytics/libexec/mysqld(_Z12mysql_selectP3THDPPP4ItemP10TABLE_LISTjR4ListIS1_ES2_jP8st_orderSB_S2_SB_yP13select_resultP18st_select_lex_unitP13st_select_lex+0x199)[0x63c8d9]
/usr/local/mainolpanalytics/libexec/mysqld(_Z13handle_selectP3THDP6st_lexP13select_resultm+0x1c5)[0x63d225]
/usr/local/mainolpanalytics/libexec/mysqld[0x5c7ef1]
/usr/local/mainolpanalytics/libexec/mysqld(_Z21mysql_execute_commandP3THD+0x3b6)[0x5cad16]
/usr/local/mainolpanalytics/libexec/mysqld(_Z11mysql_parseP3THDPcjPPKc+0x51b)[0x5d0f8b]
/usr/local/mainolpanalytics/libexec/mysqld(_Z16dispatch_command19enum_server_commandP3THDPcj+0x46e)[0x5d13fe]
/usr/local/mainolpanalytics/libexec/mysqld(_Z10do_commandP3THD+0x129)[0x5d2699]
/usr/local/mainolpanalytics/libexec/mysqld(handle_one_connection+0x9cd)[0x5c45cd]
/lib/libpthread.so.0(+0x68ba)[0x7f56d15458ba]
/lib/libc.so.6(clone+0x6d)[0x7f56d05b902d]
Trying to get some variables.
Some pointers may be invalid and cause the dump to abort.
Query (29015d0): select /*! SQL_NO_CACHE */ @a:='2013-01-14 14:57:00', @b:='(none)', @c:='10.20.36.131', @d:='3307', X.* from information_schema.INNODB_BUFFER_POOL_STATS as X
Connection ID (thread ID): 447175
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.
130114 14:57:35 mysqld_safe Number of processes running now: 0
I just had an instance crash with a similar query.
select /*! SQL_NO_CACHE */ @a:='2013-01-14 14:57:00', @b:='(none)', @c:='10.20.36.131', @d:='3307', X.* from information_ schema. INNODB_ BUFFER_ POOL_STATS as X
The instance is MyISAM only and I run it with skip-innodb.
Version: '5.1.66rel14.1' socket: '/san/mainolpan alytics/ mainolpanalytic s.sock' port: 3307 Percona Server with XtraDB (GPL), Release rel14.1, Revision 495 bugs.percona. com/
121230 9:23:43 [Note] Event Scheduler: scheduler thread started with id 1
22:57:35 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://
key_buffer_ size=1073741824 size=131072 connections= 14 size)*max_ threads = 1157930 K bytes of memory
read_buffer_
max_used_
max_threads=50
thread_count=10
connection_count=9
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: 0x7f568800f550 mainolpanalytic s/libexec/ mysqld( my_print_ stacktrace+ 0x35)[0x8ab885] mainolpanalytic s/libexec/ mysqld( handle_ fatal_signal+ 0x378)[ 0x6ae2f8] .so.0(+ 0xef60) [0x7f56d154df60 ] mainolpanalytic s/libexec/ mysqld[ 0x800cb6] mainolpanalytic s/libexec/ mysqld[ 0x74e365] mainolpanalytic s/libexec/ mysqld( _Z24get_ schema_ tables_ resultP4JOIN23e num_schema_ table_state+ 0x1d1)[ 0x6c5271] mainolpanalytic s/libexec/ mysqld( _ZN4JOIN4execEv +0x3ff) [0x63a7ff] mainolpanalytic s/libexec/ mysqld( _Z12mysql_ selectP3THDPPP4 ItemP10TABLE_ LISTjR4ListIS1_ ES2_jP8st_ orderSB_ S2_SB_yP13selec t_resultP18st_ select_ lex_unitP13st_ select_ lex+0x199) [0x63c8d9] mainolpanalytic s/libexec/ mysqld( _Z13handle_ selectP3THDP6st _lexP13select_ resultm+ 0x1c5)[ 0x63d225] mainolpanalytic s/libexec/ mysqld[ 0x5c7ef1] mainolpanalytic s/libexec/ mysqld( _Z21mysql_ execute_ commandP3THD+ 0x3b6)[ 0x5cad16] mainolpanalytic s/libexec/ mysqld( _Z11mysql_ parseP3THDPcjPP Kc+0x51b) [0x5d0f8b] mainolpanalytic s/libexec/ mysqld( _Z16dispatch_ command19enum_ server_ commandP3THDPcj +0x46e) [0x5d13fe] mainolpanalytic s/libexec/ mysqld( _Z10do_ commandP3THD+ 0x129)[ 0x5d2699] mainolpanalytic s/libexec/ mysqld( handle_ one_connection+ 0x9cd)[ 0x5c45cd] .so.0(+ 0x68ba) [0x7f56d15458ba ] so.6(clone+ 0x6d)[0x7f56d05 b902d]
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 = 7f568ee8de98 thread_stack 0x40000
/usr/local/
/usr/local/
/lib/libpthread
/usr/local/
/usr/local/
/usr/local/
/usr/local/
/usr/local/
/usr/local/
/usr/local/
/usr/local/
/usr/local/
/usr/local/
/usr/local/
/usr/local/
/lib/libpthread
/lib/libc.
Trying to get some variables. schema. INNODB_ BUFFER_ POOL_STATS as X
Some pointers may be invalid and cause the dump to abort.
Query (29015d0): select /*! SQL_NO_CACHE */ @a:='2013-01-14 14:57:00', @b:='(none)', @c:='10.20.36.131', @d:='3307', X.* from information_
Connection ID (thread ID): 447175
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.
130114 14:57:35 mysqld_safe Number of processes running now: 0