Server crash after select * from INNODB_BUFFER_PAGE; when using skip-innodb
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
Percona Server moved to https://jira.percona.com/projects/PS |
Invalid
|
Undecided
|
Unassigned | ||
5.1 |
Won't Fix
|
Medium
|
Unassigned | ||
5.5 |
New
|
Undecided
|
Unassigned | ||
5.6 |
Invalid
|
Undecided
|
Unassigned |
Bug Description
I am currently running Percona Server 5.1.68-
Whenever trying a select like this, the server crashes:
mysql> select * from information_
ERROR 2013 (HY000): Lost connection to MySQL server during query
130408 09:15:18 mysqld_safe Starting mysqld daemon with databases from /opt/data/
130408 9:15:18 [Warning] '--skip-locking' is deprecated and will be removed in a future release. Please use '--skip-
130408 9:15:18 [Note] Plugin 'FEDERATED' is disabled.
130408 9:15:18 [Note] Plugin 'InnoDB' is disabled.
130408 9:15:18 [Note] Event Scheduler: Loaded 0 events
130408 9:15:18 [Note] /usr/sbin/mysqld: ready for connections.
Version: '5.1.68-rel14.5' socket: '/var/run/
09:18:19 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_
read_buffer_
max_used_
max_threads=110
thread_count=1
connection_count=1
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: 0x1d979a0
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 = 7f03c9908ea8 thread_stack 0x30000
/usr/sbin/
/usr/sbin/
/lib/libpthread
/usr/sbin/
/usr/sbin/
/usr/sbin/
/usr/sbin/
/usr/sbin/
/usr/sbin/
/usr/sbin/
/usr/sbin/
/usr/sbin/
/usr/sbin/
/usr/sbin/
/lib/libpthread
/lib/libc.
Trying to get some variables.
Some pointers may be invalid and cause the dump to abort.
Query (1df1bf0): select * from INNODB_BUFFER_PAGE
Connection ID (thread ID): 8
Status: NOT_KILLED
Changed in percona-server: | |
status: | New → Confirmed |
no longer affects: | percona-server |
Same with older 5.1.67-rel14.4:
Version: '5.1.67-rel14.4' socket: '/var/lib/ mysql/mysql. sock' port: 3306 Percona Server (GPL), 14.4, Revision 511 bugs.percona. com/
14:48:28 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=8384512 size=131072 connections= 1 size)*max_ threads = 338436 K bytes of memory
read_buffer_
max_used_
max_threads=151
thread_count=1
connection_count=1
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: 0x224a550 mysqld( my_print_ stacktrace+ 0x35)[0x8ad405] mysqld( handle_ fatal_signal+ 0x40b)[ 0x6a8acb] libpthread. so.0(+0xf500) [0x7f5181462500 ] mysqld[ 0x74a7b2] mysqld( _Z24get_ schema_ tables_ resultP4JOIN23e num_schema_ table_state+ 0x209)[ 0x6bfe19] mysqld( _ZN4JOIN4execEv +0x4cd) [0x6369fd] mysqld( _Z12mysql_ selectP3THDPPP4 ItemP10TABLE_ LISTjR4ListIS1_ ES2_jP8st_ orderSB_ S2_SB_yP13selec t_resultP18st_ select_ lex_unitP13st_ select_ lex+0x12e) [0x632f0e] mysqld( _Z13handle_ selectP3THDP6st _lexP13select_ resultm+ 0x1bd)[ 0x63885d] mysqld[ 0x5cd76f] mysqld( _Z21mysql_ execute_ commandP3THD+ 0x4a3)[ 0x5ce803] mysqld( _Z11mysql_ parseP3THDPcjPP Kc+0x4fb) [0x5d3f4b] mysqld( _Z16dispatch_ command19enum_ server_ commandP3THDPcj +0xde5) [0x5d6155] mysqld( _Z10do_ commandP3THD+ 0x126)[ 0x5d6b66] mysqld( handle_ one_connection+ 0x325)[ 0x5c9b35] libpthread. so.0(+0x7851) [0x7f518145a851 ] libc.so. 6(clone+ 0x6d)[0x7f51806 c811d]
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 = 7f517eecde78 thread_stack 0x40000
/usr/sbin/
/usr/sbin/
/lib64/
/usr/sbin/
/usr/sbin/
/usr/sbin/
/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 (7f51700049e0): is an invalid pointer
Connection ID (thread ID): 1
Status: NOT_KILLED