One of my servers crashed today with the Assertion Failure error. It is running Percona XtraDB Cluster 5.5.30-30.2 which appears to be the latest code available as I am writing this.
The following bugs seem like they could be related but I'm not really sure as I am not a programmer and don't understand all of the debugging/terminology involved. If they are related and the bug is fixed in 5.5.31 then I would like to know when that release will be available to download.
Output of the error.log immediately after the crash (some sensitive info in the query was replaced with x's).
len 224; hex b87403acc52b0000c12040b1ba2b000000e82d81b82b0000000000000000000000000000000000000000000000000000030000000000000002000000000000000100000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000001000000000000008344510700000000cd167824c52b00000200000000000000010000000000000000e82d81b82b0000010000000000000060e1117700000000020000000000000038947a24c52b0000c8167824c52b00001000000000000000; asc t + @ + - + DQ x$ + - + ` w 8 z$ + x$ + ;
TRANSACTION 1C2CB25FD, ACTIVE 0 sec fetching rows
mysql tables in use 3, locked 0
MySQL thread id 8421534, OS thread handle 0x2bb86a0c7700, query id 46018609 xx.xx.xx.xx xx_xx_xxxx Sending data
SELECT COUNT(1) as count FROM `xxxxxxxxxxxxx_xxx`.`xxxxxxx_xxx_xxxx_xx` WHERE `xxxxxxxxxxxxx_xxx`.`xxxxxxx_xxx_xxxx_xx`.`key` = 'xxxxxxxxxxxxxxxxxxxxxxxxxxxxxx' && `xxxxxxxxxxxxx_xxx`.`xxxxxxx_xxx_xxxx_xx`.`hour` = 'xx' && `xxxxxxxxxxxxx_xxx`.`xxxxxxx_xxx_xxxx_xx`.`xxx` = 'xx' /* xxxxxxx=xxx.xxxxxxxxxxxxx.xxx/xxx.xxx */
130524 14:30:47 InnoDB: Assertion failure in thread 48071053178624 in file btr0pcur.c line 254
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.
19:30:47 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.
Please help us make Percona Server better by reporting any
bugs at http://bugs.percona.com/
key_buffer_size=8388608
read_buffer_size=262144
max_used_connections=262
max_threads=1502
thread_count=74
connection_count=74
It is possible that mysqld could use up to
key_buffer_size + (read_buffer_size + sort_buffer_size)*max_threads = 796213 K bytes of memory
Hope that's ok; if not, decrease some variables in the equation.
Thread pointer: 0x55bb48a0
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 = 2bb86a0c6e70 thread_stack 0x40000
/usr/sbin/mysqld(my_print_stacktrace+0x2e)[0x7da13e]
/usr/sbin/mysqld(handle_fatal_signal+0x4a4)[0x6b0c74]
/lib/x86_64-linux-gnu/libpthread.so.0(+0xfcb0)[0x2ba852598cb0]
/lib/x86_64-linux-gnu/libc.so.6(gsignal+0x35)[0x2ba852e16425]
/lib/x86_64-linux-gnu/libc.so.6(abort+0x17b)[0x2ba852e19b8b]
/usr/sbin/mysqld[0x88184c]
/usr/sbin/mysqld[0x518caf]
/usr/sbin/mysqld[0x82f6e0]
/usr/sbin/mysqld[0x804a14]
/usr/sbin/mysqld(_ZN7handler21read_multi_range_nextEPP18st_key_multi_range+0x2d)[0x6b102d]
/usr/sbin/mysqld(_ZN18QUICK_RANGE_SELECT8get_nextEv+0x3f)[0x7634bf]
/usr/sbin/mysqld(_ZN26QUICK_ROR_INTERSECT_SELECT8get_nextEv+0xd2)[0x775262]
/usr/sbin/mysqld[0x77a0f9]
/usr/sbin/mysqld(_Z10sub_selectP4JOINP13st_join_tableb+0x64)[0x5d2b54]
/usr/sbin/mysqld[0x5dccfd]
/usr/sbin/mysqld(_ZN4JOIN4execEv+0x8e2)[0x5ec4a2]
/usr/sbin/mysqld(_Z12mysql_selectP3THDPPP4ItemP10TABLE_LISTjR4ListIS1_ES2_jP8st_orderSB_S2_SB_yP13select_resultP18st_select_lex_unitP13st_select_lex+0x133)[0x5edfb3]
/usr/sbin/mysqld(_Z13handle_selectP3THDP3LEXP13select_resultm+0x1d5)[0x5eea25]
/usr/sbin/mysqld[0x5a10fe]
/usr/sbin/mysqld(_Z21mysql_execute_commandP3THD+0x90b)[0x5a953b]
/usr/sbin/mysqld(_Z11mysql_parseP3THDPcjP12Parser_state+0x314)[0x5b08b4]
/usr/sbin/mysqld[0x5b11d8]
/usr/sbin/mysqld(_Z16dispatch_command19enum_server_commandP3THDPcj+0x1a80)[0x5b3270]
/usr/sbin/mysqld(_Z10do_commandP3THD+0x167)[0x5b36c7]
/usr/sbin/mysqld(_Z24do_handle_one_connectionP3THD+0x14f)[0x64ecff]
/usr/sbin/mysqld(handle_one_connection+0x51)[0x64eed1]
/lib/x86_64-linux-gnu/libpthread.so.0(+0x7e9a)[0x2ba852590e9a]
/lib/x86_64-linux-gnu/libc.so.6(clone+0x6d)[0x2ba852ed3ccd]
Trying to get some variables.
Some pointers may be invalid and cause the dump to abort.
Query (2bc5247a1bd0): is an invalid pointer
Connection ID (thread ID): 8421534
Status: KILL_QUERY
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.
One of my servers crashed today with the Assertion Failure error. It is running Percona XtraDB Cluster 5.5.30-30.2 which appears to be the latest code available as I am writing this.
The following bugs seem like they could be related but I'm not really sure as I am not a programmer and don't understand all of the debugging/ terminology involved. If they are related and the bug is fixed in 5.5.31 then I would like to know when that release will be available to download.
https:/ /bugs.launchpad .net/percona- server/ +bug/1177004 /bugs.launchpad .net/percona- server/ +bug/1134757
https:/
Output of the error.log immediately after the crash (some sensitive info in the query was replaced with x's).
len 224; hex b87403acc52b000 0c12040b1ba2b00 0000e82d81b82b0 000000000000000 000000000000000 000000000000000 000000030000000 000000002000000 000000000100000 000000000000000 000000000000000 000000000000000 000000000000000 000000000000000 000000000000000 000000000000000 000000000000000 001000000000000 008344510700000 000cd167824c52b 000002000000000 000000100000000 00000000e82d81b 82b000001000000 0000000060e1117 700000000020000 000000000038947 a24c52b0000c816 7824c52b0000100 0000000000000; asc t + @ + - + DQ x$ + - + ` w 8 z$ + x$ + ; xxx`.`xxxxxxx_ xxx_xxxx_ xx` WHERE `xxxxxxxxxxxxx_ xxx`.`xxxxxxx_ xxx_xxxx_ xx`.`key` = 'xxxxxxxxxxxxxx xxxxxxxxxxxxxxx x' && `xxxxxxxxxxxxx_ xxx`.`xxxxxxx_ xxx_xxxx_ xx`.`hour` = 'xx' && `xxxxxxxxxxxxx_ xxx`.`xxxxxxx_ xxx_xxxx_ xx`.`xxx` = 'xx' /* xxxxxxx= xxx.xxxxxxxxxxx xx.xxx/ xxx.xxx */ bugs.mysql. com. dev.mysql. com/doc/ refman/ 5.5/en/ forcing- innodb- recovery. html bugs.percona. com/
TRANSACTION 1C2CB25FD, ACTIVE 0 sec fetching rows
mysql tables in use 3, locked 0
MySQL thread id 8421534, OS thread handle 0x2bb86a0c7700, query id 46018609 xx.xx.xx.xx xx_xx_xxxx Sending data
SELECT COUNT(1) as count FROM `xxxxxxxxxxxxx_
130524 14:30:47 InnoDB: Assertion failure in thread 48071053178624 in file btr0pcur.c line 254
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.
19:30:47 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.
Please help us make Percona Server better by reporting any
bugs at http://
key_buffer_ size=8388608 size=262144 connections= 262 size)*max_ threads = 796213 K bytes of memory
read_buffer_
max_used_
max_threads=1502
thread_count=74
connection_count=74
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: 0x55bb48a0 mysqld( my_print_ stacktrace+ 0x2e)[0x7da13e] mysqld( handle_ fatal_signal+ 0x4a4)[ 0x6b0c74] 64-linux- gnu/libpthread. so.0(+0xfcb0) [0x2ba852598cb0 ] 64-linux- gnu/libc. so.6(gsignal+ 0x35)[0x2ba852e 16425] 64-linux- gnu/libc. so.6(abort+ 0x17b)[ 0x2ba852e19b8b] mysqld[ 0x88184c] mysqld[ 0x518caf] mysqld[ 0x82f6e0] mysqld[ 0x804a14] mysqld( _ZN7handler21re ad_multi_ range_nextEPP18 st_key_ multi_range+ 0x2d)[0x6b102d] mysqld( _ZN18QUICK_ RANGE_SELECT8ge t_nextEv+ 0x3f)[0x7634bf] mysqld( _ZN26QUICK_ ROR_INTERSECT_ SELECT8get_ nextEv+ 0xd2)[0x775262] mysqld[ 0x77a0f9] mysqld( _Z10sub_ selectP4JOINP13 st_join_ tableb+ 0x64)[0x5d2b54] mysqld[ 0x5dccfd] mysqld( _ZN4JOIN4execEv +0x8e2) [0x5ec4a2] mysqld( _Z12mysql_ selectP3THDPPP4 ItemP10TABLE_ LISTjR4ListIS1_ ES2_jP8st_ orderSB_ S2_SB_yP13selec t_resultP18st_ select_ lex_unitP13st_ select_ lex+0x133) [0x5edfb3] mysqld( _Z13handle_ selectP3THDP3LE XP13select_ resultm+ 0x1d5)[ 0x5eea25] mysqld[ 0x5a10fe] mysqld( _Z21mysql_ execute_ commandP3THD+ 0x90b)[ 0x5a953b] mysqld( _Z11mysql_ parseP3THDPcjP1 2Parser_ state+0x314) [0x5b08b4] mysqld[ 0x5b11d8] mysqld( _Z16dispatch_ command19enum_ server_ commandP3THDPcj +0x1a80) [0x5b3270] mysqld( _Z10do_ commandP3THD+ 0x167)[ 0x5b36c7] mysqld( _Z24do_ handle_ one_connectionP 3THD+0x14f) [0x64ecff] mysqld( handle_ one_connection+ 0x51)[0x64eed1] 64-linux- gnu/libpthread. so.0(+0x7e9a) [0x2ba852590e9a ] 64-linux- gnu/libc. so.6(clone+ 0x6d)[0x2ba852e d3ccd]
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 = 2bb86a0c6e70 thread_stack 0x40000
/usr/sbin/
/usr/sbin/
/lib/x86_
/lib/x86_
/lib/x86_
/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/
/usr/sbin/
/usr/sbin/
/lib/x86_
/lib/x86_
Trying to get some variables.
Some pointers may be invalid and cause the dump to abort.
Query (2bc5247a1bd0): is an invalid pointer
Connection ID (thread ID): 8421534
Status: KILL_QUERY
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.