Hi Guys,
One of our production servers crashed and it generated the below trace. I am not an expert in reading the trace, and with my experience it seams to be some issue that got triggered with tmp table delete operation (not sure if I am correct on this). Can some one please help on how to proceed on find the root cause of the crash ?
Or is there a document which explains / gives an insight on reading MySQL crash traces ?
InnoDB: Assertion failure in thread 140533852047104 in file row0mysql.c line 3492
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.
10:13:26 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=16777216
read_buffer_size=131072
max_used_connections=391
max_threads=1200
thread_count=2
connection_count=2
It is possible that mysqld could use up to
key_buffer_size + (read_buffer_size + sort_buffer_size)*max_threads = 2641440 K bytes of memory
Hope that's ok; if not, decrease some variables in the equation.
Thread pointer: 0xc418c30
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 = 7fd096547e68 thread_stack 0x40000
/usr/sbin/mysqld(my_print_stacktrace+0x35)[0x7ae975]
/usr/sbin/mysqld(handle_fatal_signal+0x4a4)[0x686504]
/lib64/libpthread.so.0[0x372960f710]
/lib64/libc.so.6(gsignal+0x35)[0x3729232925]
/lib64/libc.so.6(abort+0x175)[0x3729234105]
/usr/sbin/mysqld[0x7df981]
/usr/sbin/mysqld[0x7c820a]
/usr/sbin/mysqld(_Z18rm_temporary_tableP10handlertonPKc+0x111)[0x54cc51]
/usr/sbin/mysqld(_Z15close_temporaryP5TABLEbb+0xaa)[0x54cd6a]
/usr/sbin/mysqld(_Z20drop_temporary_tableP3THDP10TABLE_LISTPb+0x79)[0x54fee9]
/usr/sbin/mysqld(_Z23mysql_rm_table_no_locksP3THDP10TABLE_LISTbbbb+0x29d)[0x5e8d3d]
/usr/sbin/mysqld(_Z14mysql_rm_tableP3THDP10TABLE_LISTcc+0x15d)[0x5e9acd]
/usr/sbin/mysqld(_Z21mysql_execute_commandP3THD+0x16e3)[0x5895f3]
/usr/sbin/mysqld(_ZN13sp_instr_stmt9exec_coreEP3THDPj+0x1e)[0x75554e]
/usr/sbin/mysqld(_ZN13sp_lex_keeper23reset_lex_and_exec_coreEP3THDPjbP8sp_instr+0x97)[0x7556d7]
/usr/sbin/mysqld(_ZN13sp_instr_stmt7executeEP3THDPj+0x134)[0x75a764]
/usr/sbin/mysqld(_ZN7sp_head7executeEP3THDb+0x6c1)[0x758541]
/usr/sbin/mysqld(_ZN7sp_head17execute_procedureEP3THDP4ListI4ItemE+0x6a7)[0x759417]
/usr/sbin/mysqld(_Z21mysql_execute_commandP3THD+0x191e)[0x58982e]
/usr/sbin/mysqld(_Z11mysql_parseP3THDPcjP12Parser_state+0x188)[0x58cb68]
/usr/sbin/mysqld(_Z16dispatch_command19enum_server_commandP3THDPcj+0x1ab7)[0x58ee77]
/usr/sbin/mysqld(_Z24do_handle_one_connectionP3THD+0xcf)[0x627fcf]
/usr/sbin/mysqld(handle_one_connection+0x51)[0x6280d1]
/lib64/libpthread.so.0[0x37296079d1]
/lib64/libc.so.6(clone+0x6d)[0x37292e8b6d]
Trying to get some variables.
Some pointers may be invalid and cause the dump to abort.
Query (7fcfea66e760): is an invalid pointer
Connection ID (thread ID): 235779
Status: NOT_KILLED
The manual page at
http://dev.mysql.com/doc/mysql/en/crashing.html contains
information that should help you find out what is causing the crash.
141106 04:13:26 mysqld_safe Number of processes running now: 0
141106 04:13:26 mysqld_safe mysqld restarted
141106 4:13:26 [Note] Plugin 'FEDERATED' is disabled.
141106 4:13:26 InnoDB: The InnoDB memory heap is disabled
141106 4:13:26 InnoDB: Mutexes and rw_locks use GCC atomic builtins
141106 4:13:26 InnoDB: Compressed tables use zlib 1.2.3
141106 4:13:26 InnoDB: Using Linux native AIO
141106 4:13:26 InnoDB: Initializing buffer pool, size = 4.7G
141106 4:13:27 InnoDB: Completed initialization of buffer pool
141106 4:13:27 InnoDB: highest supported file format is Barracuda.
InnoDB: Log scan progressed past the checkpoint lsn 409442754469
141106 4:13:27 InnoDB: Database was not shut down normally!
InnoDB: Starting crash recovery.
InnoDB: Reading tablespace information from the .ibd files...
InnoDB: Restoring possible half-written data pages from the doublewrite
InnoDB: buffer...
InnoDB: Doing recovery: scanned up to log sequence number 409447996928
InnoDB: Doing recovery: scanned up to log sequence number 409453239808
InnoDB: Doing recovery: scanned up to log sequence number 409455112930
141106 4:13:28 InnoDB: Starting an apply batch of log records to the database...
InnoDB: Progress in percents: 0 1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20 21 22 23 24 25 26 27 28 29 30 31 32 33 34 35 36 37 38 39 40 41 42 43 44 459 50 51 52 53 54 55 56 57 58 59 60 61 62 63 64 65 66 67 68 69 70 71 72 73 74 75 76 77 78 79 80 81 82 83 84 85 86 87 88 89 90 91 92 93 94 95 96 97 98 99
InnoDB: Apply batch completed
InnoDB: Last MySQL binlog file position 0 14319455, file name /mysql/logs/mysql-bin.001742
InnoDB: We removed now the InnoDB internal data dictionary entry
InnoDB: of table "tmp"."#sql43f7_39903_10".
InnoDB: We removed now the InnoDB internal data dictionary entry
InnoDB: of table "tmp"."#sql43f7_39903_d".
InnoDB: We removed now the InnoDB internal data dictionary entry
InnoDB: of table "tmp"."#sql43f7_39903_e".
141106 4:13:30 InnoDB: Assertion failure in thread 139979185108736 in file row0mysql.c line 3492
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.
10:13:30 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=16777216
read_buffer_size=131072
max_used_connections=0
max_threads=1200
thread_count=0
connection_count=0
It is possible that mysqld could use up to
key_buffer_size + (read_buffer_size + sort_buffer_size)*max_threads = 2641440 K bytes of memory
Hope that's ok; if not, decrease some variables in the equation.
Thread pointer: 0x0
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 = 0 thread_stack 0x40000
/usr/sbin/mysqld(my_print_stacktrace+0x35)[0x7ae975]
/usr/sbin/mysqld(handle_fatal_signal+0x4a4)[0x686504]
/lib64/libpthread.so.0[0x372960f710]
/lib64/libc.so.6(gsignal+0x35)[0x3729232925]
/lib64/libc.so.6(abort+0x175)[0x3729234105]
/usr/sbin/mysqld[0x7df981]
/usr/sbin/mysqld[0x7e08f8]
/usr/sbin/mysqld[0x89fd62]
/usr/sbin/mysqld[0x7fafa9]
/usr/sbin/mysqld[0x7c8f6e]
/usr/sbin/mysqld(_Z24ha_initialize_handlertonP13st_plugin_int+0x48)[0x688f18]
/usr/sbin/mysqld[0x593c6a]
/usr/sbin/mysqld(_Z11plugin_initPiPPci+0xa54)[0x598324]
/usr/sbin/mysqld[0x5168ba]
/usr/sbin/mysqld(_Z11mysqld_mainiPPc+0x46d)[0x51a11d]
/lib64/libc.so.6(__libc_start_main+0xfd)[0x372921ed1d]
/usr/sbin/mysqld[0x50f5d5]
The manual page at
http://dev.mysql.com/doc/mysql/en/crashing.html contains
information that should help you find out what is causing the crash.
141106 04:13:30 mysqld_safe mysqld from pid file /var/run/mysqld/mysqld.pid ended
Thanks
Raghupradeep