Bug #61980 InnoDB: Assertion failure in btr0pcur.c line 236
Submitted: 26 Jul 2011 8:09 Modified: 26 Jul 2011 11:21
Reporter: Walter Heukels Email Updates:
Status: Duplicate Impact on me:
None 
Category:MySQL Server: InnoDB storage engine Severity:S1 (Critical)
Version:5.5.14 OS:Linux (CentOS 5.6)
Assigned to: CPU Architecture:Any

[26 Jul 2011 8:09] Walter Heukels
Description:
mysqld crashed with the following message:

len 232; hex b8bc3808000000007d40e313ab2a00000088fb12ab2a0000c843a138ab2a0000000000000000000000000000000000000300000000000000010000000000000002000000000000000000000000000000000000000000000000000000000000003339614a0000000000000000030000000c0f01213f001000ffffffffffffffff0200000000000000010000000000000083445107000000000de15a3aab2a0000020000000000000001000000000000000088fb12ab2a0000c10100000000000060e11177000000000200000000000000000000000000000008e15a3aab2a00001000000000000000; asc   8     }@   *       *   C 8 *                                                                  39aJ               !?                            DQ       Z: *                       *          `  w                      Z: *          ;
110725 17:41:49  InnoDB: Assertion failure in thread 1092294976 in file btr0pcur.c line 236

Thread pointer: 0x2aab313df870
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 = 0x411b10e0 thread_stack 0x40000
/usr/sbin/mysqld(my_print_stacktrace+0x39)[0x7ccc79]
/usr/sbin/mysqld(handle_segfault+0x379)[0x4fe7b9]
/lib64/libpthread.so.0[0x3a6be0eb10]
/lib64/libc.so.6(gsignal+0x35)[0x3a6b630265]
/lib64/libc.so.6(abort+0x110)[0x3a6b631d10]
/usr/sbin/mysqld[0x89d670]
/usr/sbin/mysqld[0x84fab6]
/usr/sbin/mysqld[0x853cae]
/usr/sbin/mysqld[0x8307cc]
/usr/sbin/mysqld(_ZN26QUICK_GROUP_MIN_MAX_SELECT11next_prefixEv+0x12c)[0x758cec]
/usr/sbin/mysqld(_ZN26QUICK_GROUP_MIN_MAX_SELECT8get_nextEv+0x30)[0x759730]
/usr/sbin/mysqld[0x76bd24]
/usr/sbin/mysqld(_Z10sub_selectP4JOINP13st_join_tableb+0x70)[0x5a6070]
/usr/sbin/mysqld[0x5a7810]
/usr/sbin/mysqld(_ZN4JOIN4execEv+0x12a8)[0x5b5828]
/usr/sbin/mysqld(_Z12mysql_selectP3THDPPP4ItemP10TABLE_LISTjR4ListIS1_ES2_jP8st_orderSB_S2_SB_yP13select_resultP18st_select_lex_unitP13st_select_lex+0x1a9)[0x5b6c89]
/usr/sbin/mysqld(_Z13handle_selectP3THDP3LEXP13select_resultm+0x16d)[0x5b756d]
/usr/sbin/mysqld[0x575415]
/usr/sbin/mysqld(_Z21mysql_execute_commandP3THD+0x32c8)[0x578c08]
/usr/sbin/mysqld(_Z11mysql_parseP3THDPcjP12Parser_state+0x10b)[0x57bb2b]
/usr/sbin/mysqld(_Z16dispatch_command19enum_server_commandP3THDPcj+0x14fd)[0x57d08d]
/usr/sbin/mysqld(_Z10do_commandP3THD+0xc4)[0x57d404]
/usr/sbin/mysqld(_Z24do_handle_one_connectionP3THD+0xef)[0x615d5f]
/usr/sbin/mysqld(handle_one_connection+0x54)[0x615e54]
/lib64/libpthread.so.0[0x3a6be0673d]
/lib64/libc.so.6(clone+0x6d)[0x3a6b6d44bd]

Trying to get some variables.
Some pointers may be invalid and cause the dump to abort.
Query (0x2aab3a4d14b0): is an invalid pointer
Connection ID (thread ID): 2571770
Status: NOT_KILLED

How to repeat:
Unknown.  This is a multiuser system with about 3,500 databases.  So far the problem has only occured once during one week of operation.
[26 Jul 2011 11:21] Valeriy Kravchuk
This is a duplicate of bug #61101 (that bug is private).