Bug #70549 nysql crash 5.5.24, just wondered why
Submitted: 8 Oct 2013 0:01 Modified: 8 Nov 2013 17:42
Reporter: Mark Nielsen Email Updates:
Status: No Feedback Impact on me:
None 
Category:MySQL Server Severity:S3 (Non-critical)
Version:5.5.24 OS:Linux
Assigned to: CPU Architecture:Any

[8 Oct 2013 0:01] Mark Nielsen
Description:
mysql crashed

I took out the hexcode after " len 16384; hex". I can post it if it is needed. 
It crashed, and then it couldn't start up until I did a 
innodb_force_recovery = 3
innodb_purge_threads=0

Systems logs didn't show anything bad. Apparently it is not hardware related. 

31004  8:50:45  InnoDB: Dump of the ibuf bitmap page:
131004  8:50:45  InnoDB: Page dump in ascii and hex (16384 bytes):
 len 16384; hex
InnoDB: End of page dump
131004  8:50:45  InnoDB: Page checksum 923160634 (32bit_calc: 3680802039), prior-to-4.0.14-form checksum 1893168166
InnoDB: stored checksum 541630198, prior-to-4.0.14-form stored checksum 1893168166
InnoDB: Page lsn 249 1778413392, low 4 bytes of lsn at page end 1778413392
InnoDB: Page number (if stored to page already) 1,
InnoDB: space id (if created with >= MySQL-4.1.1 and stored already) 786
InnoDB: Page may be an insert buffer bitmap page

InnoDB: Dump of the page:
131004  8:50:45  InnoDB: Page dump in ascii and hex (16384 bytes):
 len 16384; hex
InnoDB: End of page dump
131004  8:50:45  InnoDB: Page checksum 1575996416 (32bit_calc: 2253597184), prior-to-4.0.14-form checksum 1371122432
InnoDB: stored checksum 0, prior-to-4.0.14-form stored checksum 0
InnoDB: Page lsn 0 0, low 4 bytes of lsn at page end 0
InnoDB: Page number (if stored to page already) 0,
InnoDB: space id (if created with >= MySQL-4.1.1 and stored already) 0
InnoDB: Page may be a freshly allocated page
InnoDB: Error: corruption in the tablespace. Bitmap shows insert
InnoDB: buffer records to page n:o 10774 though the page
InnoDB: type is 0, which is not an index leaf page!
InnoDB: We try to resolve the problem by skipping the insert buffer
InnoDB: merge for this page. Please run CHECK TABLE on your tables
InnoDB: to determine if they are corrupt after this.

InnoDB: Please submit a detailed bug report to http://bugs.mysql.com

InnoDB: Discarding record
 PHYSICAL RECORD: n_fields 9; 1-byte offsets; info bits 0
 0: len 4; hex 00000312; asc     ;;
 1: len 1; hex 00; asc  ;;
 2: len 4; hex 00002a16; asc   * ;;
 3: len 30; hex 000000018609000380008609000380008609000380008609000380008608; asc                               ; (total 34 bytes);
 4: len 3; hex 020c96; asc    ;;
 5: len 3; hex 01e4fa; asc    ;;
 6: len 3; hex 000003; asc    ;;
 7: len 3; hex 32dc7f; asc 2  ;;
 8: len 8; hex 80000000001fba01; asc         ;;

InnoDB: from the insert buffer!

InnoDB: Page directory corruption: infimum not pointed to
131004  8:54:02  InnoDB: Page dump in ascii and hex (16384 bytes):
 len 16384; hex
InnoDB: End of page dump
131004  8:54:03  InnoDB: Page checksum 3082136618 (32bit_calc: 3759737386), prior-to-4.0.14-form checksum 116688470
InnoDB: stored checksum 3082136618, prior-to-4.0.14-form stored checksum 116688470
InnoDB: Page lsn 249 1794486294, low 4 bytes of lsn at page end 1794486294
InnoDB: Page number (if stored to page already) 0,
InnoDB: space id (if created with >= MySQL-4.1.1 and stored already) 0
InnoDB: Page may be a freshly allocated page
InnoDB: Page directory corruption: supremum not pointed to
131004  8:54:03  InnoDB: Page dump in ascii and hex (16384 bytes):
 len 16384; hex
InnoDB: End of page dump
131004  8:54:03  InnoDB: Page checksum 3082136618 (32bit_calc: 3759737386), prior-to-4.0.14-form checksum 116688470
InnoDB: stored checksum 3082136618, prior-to-4.0.14-form stored checksum 116688470
InnoDB: Page lsn 249 1794486294, low 4 bytes of lsn at page end 1794486294
InnoDB: Page number (if stored to page already) 0,
InnoDB: space id (if created with >= MySQL-4.1.1 and stored already) 0
InnoDB: Page may be a freshly allocated page
08:54:03 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.

key_buffer_size=67108864
read_buffer_size=131072
max_used_connections=16385
max_threads=16384
thread_count=476
connection_count=476
It is possible that mysqld could use up to
key_buffer_size + (read_buffer_size + sort_buffer_size)*max_threads = 35917824 K  bytes of memory
Hope that's ok; if not, decrease some variables in the equation.

Thread pointer: 0x421145c0
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 = 7f7d7644be80 thread_stack 0x30000
/usr/sbin/mysqld(my_print_stacktrace+0x2e)[0x7b187e]
/usr/sbin/mysqld(handle_fatal_signal+0x484)[0x68a7e4]
/lib/x86_64-linux-gnu/libpthread.so.0(+0xfcb0)[0x7f8ac60a2cb0]
/usr/sbin/mysqld[0x8ef081]
/usr/sbin/mysqld[0x841b92]
/usr/sbin/mysqld[0x905f20]
/usr/sbin/mysqld[0x90a1be]
/usr/sbin/mysqld[0x7edd08]
/usr/sbin/mysqld[0x7d7691]
/usr/sbin/mysqld(_ZN7handler12ha_write_rowEPh+0x57)[0x691d87]
/usr/sbin/mysqld(_Z12write_recordP3THDP5TABLEP12st_copy_info+0x72)[0x584932]
/usr/sbin/mysqld(_Z12mysql_insertP3THDP10TABLE_LISTR4ListI4ItemERS3_IS5_ES6_S6_15enum_duplicatesb+0x9f8)[0x587048]
/usr/sbin/mysqld(_Z21mysql_execute_commandP3THD+0x133c)[0x59952c]
/usr/sbin/mysqld(_ZN18Prepared_statement7executeEP6Stringb+0x3f9)[0x5ae939]
/usr/sbin/mysqld(_ZN18Prepared_statement12execute_loopEP6StringbPhS2_+0x7b)[0x5ae9cb]
/usr/sbin/mysqld(_Z22mysql_sql_stmt_executeP3THD+0xab)[0x5aed7b]
/usr/sbin/mysqld(_Z21mysql_execute_commandP3THD+0x1f23)[0x59a113]
/usr/sbin/mysqld(_ZN13sp_instr_stmt9exec_coreEP3THDPj+0x1e)[0x755d5e]
/usr/sbin/mysqld(_ZN13sp_lex_keeper23reset_lex_and_exec_coreEP3THDPjbP8sp_instr+0x97)[0x75bb57]
/usr/sbin/mysqld(_ZN13sp_instr_stmt7executeEP3THDPj+0x134)[0x75c004]
/usr/sbin/mysqld(_ZN7sp_head7executeEP3THDb+0x65c)[0x75882c]
/usr/sbin/mysqld(_ZN7sp_head17execute_procedureEP3THDP4ListI4ItemE+0x69f)[0x759f6f]
/usr/sbin/mysqld(_Z21mysql_execute_commandP3THD+0x17a7)[0x599997]
/usr/sbin/mysqld(_Z11mysql_parseP3THDPcjP12Parser_state+0x30c)[0x59f11c]
/usr/sbin/mysqld(_Z16dispatch_command19enum_server_commandP3THDPcj+0x1608)[0x5a07d8]
/usr/sbin/mysqld(_Z24do_handle_one_connectionP3THD+0x14f)[0x638a0f]
/usr/sbin/mysqld(handle_one_connection+0x51)[0x638ad1]
/lib/x86_64-linux-gnu/libpthread.so.0(+0x7e9a)[0x7f8ac609ae9a]
/lib/x86_64-linux-gnu/libc.so.6(clone+0x6d)[0x7f8ac5dc7cbd]

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

How to repeat:
Not sure how to repeat.
[8 Oct 2013 17:42] Sveta Smirnova
Thank you for the report.

Such a crash can happen if your InnoDB tablespace is corrupt. Corruption can happen if InnoDB tablespace was modified outside of MySQL, for example, if OS crashed, physical disk was corrupted, or because some buggy MySQL code.

But we can not say you hit a bug in MySQL unless you prove corruption happened if MySQL executed some buggy instructions. Please try to find out what lead to the corruption, send us this information and reopen the report. You can turn general query log and InnODB Monitors on and wait when next such a crash occurs.

Please check your operating system log files for indicators of OS crash or disk corruptions. Please also check your hard disks for corruptions.
[9 Nov 2013 1:00] Bugs System
No feedback was provided for this bug for over a month, so it is
being suspended automatically. If you are able to provide the
information that was originally requested, please do so and change
the status of the bug back to "Open".