Description:
Mysql server got crash unknowingly. we want to make sure why mysql got crash
Below is the error log
150118 20:45:56 [Note] /usr/local/mysql/bin/mysqld: ready for connections.
Version: '5.5.30' socket: '/tmp/mysql.sock' port: 3306 MySQL Community Server (GPL)
len 224; hex f8b5afceb67f0000b6341ceab77f0000003e58deb77f00000000000000000000000000000000000000000000000000000100000000000000020000000000000001000000000000000000000000000000000000000000000000000000000000000100000000000000000000000000000084b075e4bccdff490000000000000000010000000000000083445107000000008e6fa8acb67f000002000000000000000100000000000000003e58deb77f0000930200000000000060e11177000000000200000000000000489e51cfb67f0000886fa8acb67f00001800000000000000; asc 4 >X u I DQ o >X ` w H Q o ;
TRANSACTION 4DC8A7CB, ACTIVE 3 sec fetching rows
mysql tables in use 2, locked 0
MySQL thread id 13772342, OS thread handle 0x7fb734148700, query id 975317946 10.31.2.240 psmart preparing
SELECT FILENAME FROM STREAM_0050C2C68229 WHERE SESSID IN (select DISTINCT SESSID FROM SESSION_0050C2C68229 WHERE STREAM2MOS < STREAM1MOS AND STREAM2MOS > '1.0' and STREAM2MOS < '2.8' AND STARTTIME_EPOCH >= '1425196800' AND STARTTIME_EPOCH <= '1427871599')
150402 18:18:26 InnoDB: Assertion failure in thread 140424829503232 in file btr0pcur.c line 250
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.
01:18: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=4194304
read_buffer_size=131072
max_used_connections=348
max_threads=800
thread_count=35
connection_count=35
It is possible that mysqld could use up to
key_buffer_size + (read_buffer_size + sort_buffer_size)*max_threads = 141239 K bytes of memory
Hope that's ok; if not, decrease some variables in the equation.
Thread pointer: 0xd328040
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 = 7fb734147e68 thread_stack 0x40000
/usr/local/mysql/bin/mysqld(my_print_stacktrace+0x35)[0x79ffa5]
/usr/local/mysql/bin/mysqld(handle_fatal_signal+0x403)[0x66f5a3]
/lib64/libpthread.so.0[0x305f20f710]
/lib64/libc.so.6(gsignal+0x35)[0x305ee32925]
/lib64/libc.so.6(abort+0x175)[0x305ee34105]
/usr/local/mysql/bin/mysqld[0x883ccb]
/usr/local/mysql/bin/mysqld[0x838c36]
/usr/local/mysql/bin/mysqld[0x8392b9]
/usr/local/mysql/bin/mysqld[0x81340c]
/usr/local/mysql/bin/mysqld(_ZN30subselect_indexsubquery_engine4execEv+0x235)[0x6de9f5]
/usr/local/mysql/bin/mysqld(_ZN14Item_subselect4execEv+0x4d)[0x6dd84d]
/usr/local/mysql/bin/mysqld(_ZN17Item_in_subselect8val_boolEv+0x20)[0x6ddf20]
/usr/local/mysql/bin/mysqld(_ZN17Item_in_optimizer7val_intEv+0x152)[0x692532]
/usr/local/mysql/bin/mysqld[0x5957ad]
/usr/local/mysql/bin/mysqld(_Z10sub_selectP4JOINP13st_join_tableb+0x86)[0x59ad76]
/usr/local/mysql/bin/mysqld[0x5a0668]
/usr/local/mysql/bin/mysqld(_ZN4JOIN4execEv+0x8ea)[0x5b480a]
/usr/local/mysql/bin/mysqld(_Z12mysql_selectP3THDPPP4ItemP10TABLE_LISTjR4ListIS1_ES2_jP8st_orderSB_S2_SB_yP13select_resultP18st_select_lex_unitP13st_select_lex+0x1c3)[0x5b0593]
/usr/local/mysql/bin/mysqld(_Z13handle_selectP3THDP3LEXP13select_resultm+0x179)[0x5b6379]
/usr/local/mysql/bin/mysqld[0x574061]
/usr/local/mysql/bin/mysqld(_Z21mysql_execute_commandP3THD+0x250b)[0x5799ab]
/usr/local/mysql/bin/mysqld(_Z11mysql_parseP3THDPcjP12Parser_state+0x18a)[0x57bcea]
/usr/local/mysql/bin/mysqld(_Z16dispatch_command19enum_server_commandP3THDPcj+0x1331)[0x57d8a1]
/usr/local/mysql/bin/mysqld(_Z24do_handle_one_connectionP3THD+0x167)[0x6146e7]
/usr/local/mysql/bin/mysqld(handle_one_connection+0x54)[0x614754]
/lib64/libpthread.so.0[0x305f2079d1]
/lib64/libc.so.6(clone+0x6d)[0x305eee8b5d]
Trying to get some variables.
Some pointers may be invalid and cause the dump to abort.
Query (7fb6ae021cd0): is an invalid pointer
Connection ID (thread ID): 13772342
Status: KILL_QUERY
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.
150402 18:18:47 mysqld_safe Number of processes running now: 0
150402 18:18:47 mysqld_safe mysqld restarted
150402 18:18:47 [Note] Plugin 'FEDERATED' is disabled.
150402 18:18:47 InnoDB: The InnoDB memory heap is disabled
150402 18:18:47 InnoDB: Mutexes and rw_locks use GCC atomic builtins
150402 18:18:47 InnoDB: Compressed tables use zlib 1.2.3
150402 18:18:47 InnoDB: Using Linux native AIO
150402 18:18:47 InnoDB: Initializing buffer pool, size = 6.0G
150402 18:18:47 InnoDB: Completed initialization of buffer pool
150402 18:18:47 InnoDB: highest supported file format is Barracuda.
InnoDB: Log scan progressed past the checkpoint lsn 286756584814
150402 18:18:47 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 286760908900
150402 18:23:37 InnoDB: Starting an apply batch of log records to the database...
InnoDB: Progress in percents: 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 45 46 47 48 49 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
150402 18:23:42 InnoDB: Waiting for the background threads to start
150402 18:23:43 InnoDB: 5.5.30 started; log sequence number 286760908900
How to repeat:
We are not sure about how to repeat but we have only error message
