Happened also on PS 5.5.23 in exactly the same line/function:
140303 15:56:35 InnoDB: Assertion failure in thread 1263663424 in file btr0pcur.c line 455
InnoDB: Failing assertion: page_is_comp(next_page) == page_is_comp(page)
InnoDB: We intentionally generate a memory trap.
InnoDB: Submit a detailed bug report to http://bugs.mysql.com.
InnoDB: If you get repeated assertion failures or crashes, even
InnoDB: immediately after the mysqld startup, there may be
InnoDB: corruption in the InnoDB tablespace. Please refer to
InnoDB: http://dev.mysql.com/doc/refman/5.5/en/forcing-innodb-recovery.html
InnoDB: about forcing recovery.
15:56:35 UTC - mysqld got signal 6 ;
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.
key_buffer_size=8388608
read_buffer_size=131072
max_used_connections=6
max_threads=1350
thread_count=3
connection_count=3
It is possible that mysqld could use up to
key_buffer_size + (read_buffer_size + sort_buffer_size)*max_threads = 2962329 K bytes of memory
Hope that's ok; if not, decrease some variables in the equation.
Thread pointer: 0x15dd4960
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 = 4b51f0f8 thread_stack 0x80000
/usr/sbin/mysqld(my_print_stacktrace+0x35)[0x7a3b95]
/usr/sbin/mysqld(handle_fatal_signal+0x4a4)[0x67f474]
/lib64/libpthread.so.0[0x3b30a0eb10]
/lib64/libc.so.6(gsignal+0x35)[0x3b30630265]
/lib64/libc.so.6(abort+0x110)[0x3b30631d10]
/usr/sbin/mysqld[0x82c6c5]
/usr/sbin/mysqld[0x7db797]
/usr/sbin/mysqld[0x7dc22d]
/usr/sbin/mysqld[0x7b341d]
/usr/sbin/mysqld(_ZN7handler15read_range_nextEv+0x2d)[0x68061d]
/usr/sbin/mysqld(_ZN7handler21read_multi_range_nextEPP18st_key_multi_range+0x2d)[0x67fd9d]
/usr/sbin/mysqld(_ZN18QUICK_RANGE_SELECT8get_nextEv+0x41)[0x72f4d1]
/usr/sbin/mysqld[0x745e6b]
/usr/sbin/mysqld(_Z10sub_selectP4JOINP13st_join_tableb+0x79)[0x5a9569]
/usr/sbin/mysqld[0x5ae150]
/usr/sbin/mysqld(_ZN4JOIN4execEv+0xc7e)[0x5c38be]
/usr/sbin/mysqld(_Z12mysql_selectP3THDPPP4ItemP10TABLE_LISTjR4ListIS1_ES2_jP8st_orderSB_S2_SB_yP13select_resultP18st_select_lex_unitP13st_select_lex+0x12c)[0x5bf38c]
/usr/sbin/mysqld(_Z13handle_selectP3THDP3LEXP13select_resultm+0x1cd)[0x5c511d]
/usr/sbin/mysqld(_Z21mysql_execute_commandP3THD+0x3c6c)[0x588eac]
/usr/sbin/mysqld(_Z11mysql_parseP3THDPcjP12Parser_state+0x333)[0x589d53]
/usr/sbin/mysqld(_ZN15Query_log_event14do_apply_eventEPK14Relay_log_infoPKcj+0xcc8)[0x725468]
/usr/sbin/mysqld(_Z26apply_event_and_update_posP9Log_eventP3THDP14Relay_log_info+0x125)[0x528275]
/usr/sbin/mysqld[0x52cd39]
/usr/sbin/mysqld(handle_slave_sql+0x919)[0x52e109]
/lib64/libpthread.so.0[0x3b30a0673d]
/lib64/libc.so.6(clone+0x6d)[0x3b306d3d1d]
Trying to get some variables.
Some pointers may be invalid and cause the dump to abort.
Query (2aad5408b3ea): is an invalid pointer
Connection ID (thread ID): 805
Status: NOT_KILLED
Happened also on PS 5.5.23 in exactly the same line/function:
140303 15:56:35 InnoDB: Assertion failure in thread 1263663424 in file btr0pcur.c line 455 comp(next_ page) == page_is_comp(page) bugs.mysql. com. dev.mysql. com/doc/ refman/ 5.5/en/ forcing- innodb- recovery. html
InnoDB: Failing assertion: page_is_
InnoDB: We intentionally generate a memory trap.
InnoDB: Submit a detailed bug report to http://
InnoDB: If you get repeated assertion failures or crashes, even
InnoDB: immediately after the mysqld startup, there may be
InnoDB: corruption in the InnoDB tablespace. Please refer to
InnoDB: http://
InnoDB: about forcing recovery.
15:56:35 UTC - mysqld got signal 6 ;
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.
key_buffer_ size=8388608 size=131072 connections= 6 size)*max_ threads = 2962329 K bytes of memory
read_buffer_
max_used_
max_threads=1350
thread_count=3
connection_count=3
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: 0x15dd4960 mysqld( my_print_ stacktrace+ 0x35)[0x7a3b95] mysqld( handle_ fatal_signal+ 0x4a4)[ 0x67f474] libpthread. so.0[0x3b30a0eb 10] libc.so. 6(gsignal+ 0x35)[0x3b30630 265] libc.so. 6(abort+ 0x110)[ 0x3b30631d10] mysqld[ 0x82c6c5] mysqld[ 0x7db797] mysqld[ 0x7dc22d] mysqld[ 0x7b341d] mysqld( _ZN7handler15re ad_range_ nextEv+ 0x2d)[0x68061d] mysqld( _ZN7handler21re ad_multi_ range_nextEPP18 st_key_ multi_range+ 0x2d)[0x67fd9d] mysqld( _ZN18QUICK_ RANGE_SELECT8ge t_nextEv+ 0x41)[0x72f4d1] mysqld[ 0x745e6b] mysqld( _Z10sub_ selectP4JOINP13 st_join_ tableb+ 0x79)[0x5a9569] mysqld[ 0x5ae150] mysqld( _ZN4JOIN4execEv +0xc7e) [0x5c38be] mysqld( _Z12mysql_ selectP3THDPPP4 ItemP10TABLE_ LISTjR4ListIS1_ ES2_jP8st_ orderSB_ S2_SB_yP13selec t_resultP18st_ select_ lex_unitP13st_ select_ lex+0x12c) [0x5bf38c] mysqld( _Z13handle_ selectP3THDP3LE XP13select_ resultm+ 0x1cd)[ 0x5c511d] mysqld( _Z21mysql_ execute_ commandP3THD+ 0x3c6c) [0x588eac] mysqld( _Z11mysql_ parseP3THDPcjP1 2Parser_ state+0x333) [0x589d53] mysqld( _ZN15Query_ log_event14do_ apply_eventEPK1 4Relay_ log_infoPKcj+ 0xcc8)[ 0x725468] mysqld( _Z26apply_ event_and_ update_ posP9Log_ eventP3THDP14Re lay_log_ info+0x125) [0x528275] mysqld[ 0x52cd39] mysqld( handle_ slave_sql+ 0x919)[ 0x52e109] libpthread. so.0[0x3b30a067 3d] libc.so. 6(clone+ 0x6d)[0x3b306d3 d1d]
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 = 4b51f0f8 thread_stack 0x80000
/usr/sbin/
/usr/sbin/
/lib64/
/lib64/
/lib64/
/usr/sbin/
/usr/sbin/
/usr/sbin/
/usr/sbin/
/usr/sbin/
/usr/sbin/
/usr/sbin/
/usr/sbin/
/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 (2aad5408b3ea): is an invalid pointer
Connection ID (thread ID): 805
Status: NOT_KILLED