Server crash after select * from INNODB_BUFFER_PAGE; when using skip-innodb

Bug #1166098 reported by Radu Epure
6
This bug affects 1 person
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-rel14.5-513.squeeze on Debian Squeeze with skip-innodb configured in my.cnf.

Whenever trying a select like this, the server crashes:
mysql> select * from information_schema.INNODB_BUFFER_PAGE;
ERROR 2013 (HY000): Lost connection to MySQL server during query

130408 09:15:18 mysqld_safe Starting mysqld daemon with databases from /opt/data/mysql/mysqld118
130408 9:15:18 [Warning] '--skip-locking' is deprecated and will be removed in a future release. Please use '--skip-external-locking' instead.
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/mysqld/mysqld118.sock' port: 3306 (Percona Server (GPL), 14.5, Revision 513)
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://bugs.percona.com/

key_buffer_size=268435456
read_buffer_size=2097152
max_used_connections=1
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_size)*max_threads = 713926 K bytes of memory
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/mysqld(my_print_stacktrace+0x35)[0x8cc6a5]
/usr/sbin/mysqld(handle_fatal_signal+0x40b)[0x6c460b]
/lib/libpthread.so.0(+0xef60)[0x7f03dbbdef60]
/usr/sbin/mysqld[0x7690b2]
/usr/sbin/mysqld(_Z24get_schema_tables_resultP4JOIN23enum_schema_table_state+0x209)[0x6dbd99]
/usr/sbin/mysqld(_ZN4JOIN4execEv+0x4cd)[0x64b16d]
/usr/sbin/mysqld(_Z12mysql_selectP3THDPPP4ItemP10TABLE_LISTjR4ListIS1_ES2_jP8st_orderSB_S2_SB_yP13select_resultP18st_select_lex_unitP13st_select_lex+0x12e)[0x6477de]
/usr/sbin/mysqld(_Z13handle_selectP3THDP6st_lexP13select_resultm+0x1bd)[0x64cfed]
/usr/sbin/mysqld[0x5e1bff]
/usr/sbin/mysqld(_Z21mysql_execute_commandP3THD+0x4a3)[0x5e3cc3]
/usr/sbin/mysqld(_Z11mysql_parseP3THDPcjPPKc+0x4fb)[0x5e938b]
/usr/sbin/mysqld(_Z16dispatch_command19enum_server_commandP3THDPcj+0xde5)[0x5ea5c5]
/usr/sbin/mysqld(_Z10do_commandP3THD+0x126)[0x5eafd6]
/usr/sbin/mysqld(handle_one_connection+0x325)[0x5dde05]
/lib/libpthread.so.0(+0x68ba)[0x7f03dbbd68ba]
/lib/libc.so.6(clone+0x6d)[0x7f03daa4102d]

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

Revision history for this message
Valerii Kravchuk (valerii-kravchuk) wrote :

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
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://bugs.percona.com/

key_buffer_size=8384512
read_buffer_size=131072
max_used_connections=1
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_size)*max_threads = 338436 K bytes of memory
Hope that's ok; if not, decrease some variables in the equation.

Thread pointer: 0x224a550
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/mysqld(my_print_stacktrace+0x35)[0x8ad405]
/usr/sbin/mysqld(handle_fatal_signal+0x40b)[0x6a8acb]
/lib64/libpthread.so.0(+0xf500)[0x7f5181462500]
/usr/sbin/mysqld[0x74a7b2]
/usr/sbin/mysqld(_Z24get_schema_tables_resultP4JOIN23enum_schema_table_state+0x209)[0x6bfe19]
/usr/sbin/mysqld(_ZN4JOIN4execEv+0x4cd)[0x6369fd]
/usr/sbin/mysqld(_Z12mysql_selectP3THDPPP4ItemP10TABLE_LISTjR4ListIS1_ES2_jP8st_orderSB_S2_SB_yP13select_resultP18st_select_lex_unitP13st_select_lex+0x12e)[0x632f0e]
/usr/sbin/mysqld(_Z13handle_selectP3THDP6st_lexP13select_resultm+0x1bd)[0x63885d]
/usr/sbin/mysqld[0x5cd76f]
/usr/sbin/mysqld(_Z21mysql_execute_commandP3THD+0x4a3)[0x5ce803]
/usr/sbin/mysqld(_Z11mysql_parseP3THDPcjPPKc+0x4fb)[0x5d3f4b]
/usr/sbin/mysqld(_Z16dispatch_command19enum_server_commandP3THDPcj+0xde5)[0x5d6155]
/usr/sbin/mysqld(_Z10do_commandP3THD+0x126)[0x5d6b66]
/usr/sbin/mysqld(handle_one_connection+0x325)[0x5c9b35]
/lib64/libpthread.so.0(+0x7851)[0x7f518145a851]
/lib64/libc.so.6(clone+0x6d)[0x7f51806c811d]

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

Changed in percona-server:
status: New → Confirmed
no longer affects: percona-server
Revision history for this message
Laurynas Biveinis (laurynas-biveinis) wrote :

The fill function for this I_S table does not have the RETURN_IF_INNODB_NOT_STARTED guard, that should be it.

tags: added: low-hanging-fruit xtradb
Revision history for this message
Radu Epure (radurazvan-epure) wrote :
Download full text (3.2 KiB)

Tested with 5.5.30-rel30.1-465.squeeze on Debian Squeeze with the same result:

mysql> select * from information_schema.INNODB_BUFFER_PAGE;
ERROR 2013 (HY000): Lost connection to MySQL server during query

07:18:02 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=268435456
read_buffer_size=2097152
max_used_connections=1
max_threads=112
thread_count=1
connection_count=1
It is possible that mysqld could use up to
key_buffer_size + (read_buffer_size + sort_buffer_size)*max_threads = 722257 K bytes of memory
Hope that's ok; if not, decrease some variables in the equation.

Thread pointer: 0x17d6b10
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 = 7f6236f0ae98 thread_stack 0x30000
/usr/sbin/mysqld(my_print_stacktrace+0x35)[0x7cc825]
/usr/sbin/mysqld(handle_fatal_signal+0x4b4)[0x69bf74]
/lib/libpthread.so.0(+0xef60)[0x7f6248fc1f60]
/usr/sbin/mysqld[0x807199]
/usr/sbin/mysqld(_Z24get_schema_tables_resultP4JOIN23enum_schema_table_state+0x25e)[0x5daf4e]
/usr/sbin/mysqld(_ZN4JOIN4execEv+0x4dd)[0x5d59bd]
/usr/sbin/mysqld(_Z12mysql_selectP3THDPPP4ItemP10TABLE_LISTjR4ListIS1_ES2_jP8st_orderSB_S2_SB_yP13select_resultP18st_select_lex_unitP13st_select_lex+0x12c)[0x5d790c]
/usr/sbin/mysqld(_Z13handle_selectP3THDP3LEXP13select_resultm+0x1cd)[0x5d83cd]
/usr/sbin/mysqld[0x595002]
/usr/sbin/mysqld(_Z21mysql_execute_commandP3THD+0x1543)[0x598e53]
/usr/sbin/mysqld(_Z11mysql_parseP3THDPcjP12Parser_state+0x333)[0x59c593]
/usr/sbin/mysqld(_Z16dispatch_command19enum_server_commandP3THDPcj+0x15cd)[0x59dc0d]
/usr/sbin/mysqld(_Z24do_handle_one_connectionP3THD+0xd7)[0x63aac7]
/usr/sbin/mysqld(handle_one_connection+0x51)[0x63ac01]
/lib/libpthread.so.0(+0x68ba)[0x7f6248fb98ba]
/lib/libc.so.6(clone+0x6d)[0x7f624825b02d]

Trying to get some variables.
Some pointers may be invalid and cause the dump to abort.
Query (1832580): select * from information_schema.INNODB_BUFFER_PAGE
Connection ID (thread ID): 9
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.
130409 07:18:02 mysqld_safe Number of processes running now: 0
130409 07:18:02 mysqld_safe mysqld restarted
130409 7:18:02 [Note] Plugin 'FEDERATED' is disabled.
130409 7:18:02 [Note] Plugin 'InnoDB' is disabled.
130409 7:18:02 [Warning] 'user' entry 'root@robocop' ignored in --skip-name-resolve mode.
130409 7:18:02 [Note] Event Scheduler: Loaded 0 events
130409 7:18:02 [Note] /usr/sbin/mysqld: ready for connections.
Version: '5.5.30-30.1' so...

Read more...

Revision history for this message
Raghavendra D Prabhu (raghavendra-prabhu) wrote :

Seems to be fixed in 5.5.31
https://dev.mysql.com/doc/relnotes/mysql/5.5/en/news-5-5-31.html

=======================

InnoDB: If the server was started with the skip-innodb option, or InnoDB otherwise failed to start, query any of these Information Schema tables would cause a severe error:

    INNODB_BUFFER_PAGE

    INNODB_BUFFER_PAGE_LRU

    INNODB_BUFFER_POOL_STATS

(Bug #14144290)

==============

Revision history for this message
Laurynas Biveinis (laurynas-biveinis) wrote :
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/PS-2932

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.