these are log view
2017-07-10 16:27:12 27528 [Note] Plugin 'FEDERATED' is disabled.
2017-07-10 16:27:12 27528 [Note] InnoDB: Using atomics to ref count buffer pool pages
2017-07-10 16:27:12 27528 [Note] InnoDB: The InnoDB memory heap is disabled
2017-07-10 16:27:12 27528 [Note] InnoDB: Mutexes and rw_locks use GCC atomic builtins
2017-07-10 16:27:12 27528 [Note] InnoDB: Memory barrier is not used
2017-07-10 16:27:12 27528 [Note] InnoDB: Compressed tables use zlib 1.2.3
2017-07-10 16:27:12 27528 [Note] InnoDB: Using Linux native AIO
2017-07-10 16:27:12 27528 [Note] InnoDB: Using CPU crc32 instructions
2017-07-10 16:27:12 27528 [Note] InnoDB: Initializing buffer pool, size = 128.0M
2017-07-10 16:27:12 27528 [Note] InnoDB: Completed initialization of buffer pool
2017-07-10 16:27:12 27528 [Note] InnoDB: Highest supported file format is Barracuda.
2017-07-10 16:27:12 27528 [Note] InnoDB: Log scan progressed past the checkpoint lsn 13025627845
2017-07-10 16:27:12 27528 [Note] InnoDB: Database was not shutdown normally!
2017-07-10 16:27:12 27528 [Note] InnoDB: Starting crash recovery.
2017-07-10 16:27:12 27528 [Note] InnoDB: Reading tablespace information from the .ibd files...
2017-07-10 16:27:12 27528 [Note] InnoDB: Restoring possible half-written data pages
2017-07-10 16:27:12 27528 [Note] InnoDB: from the doublewrite buffer...
InnoDB: Doing recovery: scanned up to log sequence number 13026386304
2017-07-10 16:27:12 27528 [Note] InnoDB: Starting an apply batch of log records to the database...
InnoDB: Progress in percent: 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
2017-07-10 16:27:12 27528 [Note] InnoDB: 128 rollback segment(s) are active.
2017-07-10 16:27:12 27528 [Note] InnoDB: Waiting for purge to start
2017-07-10 16:27:12 27528 [Note] InnoDB: 5.6.36 started; log sequence number 13026386304
2017-07-10 16:27:12 27528 [Note] Recovering after a crash using mysql-bin
2017-07-10 16:27:12 27528 [Note] Starting crash recovery...
2017-07-10 16:27:12 27528 [Note] Crash recovery finished.
2017-07-10 16:27:12 7f160bfff700 InnoDB: Assertion failure in thread 139732667332352 in file fsp0fsp.cc line 1868
InnoDB: Failing assertion: inode
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.6/en/forcing-innodb-recovery.html
InnoDB: about forcing recovery.
13:27:12 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=402653184
read_buffer_size=2097152
max_used_connections=0
max_threads=151
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 = 1013644 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)[0x922735]
/usr/sbin/mysqld(handle_fatal_signal+0x3d8)[0x679f58]
/lib64/libpthread.so.0(+0xf7e0)[0x7f164ac8f7e0]
/lib64/libc.so.6(gsignal+0x35)[0x7f164993a495]
/lib64/libc.so.6(abort+0x175)[0x7f164993bc75]
/usr/sbin/mysqld[0xad7df2]
/usr/sbin/mysqld[0xae0002]
/usr/sbin/mysqld[0xa3eae3]
/usr/sbin/mysqld[0xa40602]
/usr/sbin/mysqld[0xa2dddf]
/usr/sbin/mysqld[0xa31adb]
/lib64/libpthread.so.0(+0x7aa1)[0x7f164ac87aa1]
/lib64/libc.so.6(clone+0x6d)[0x7f16499f0bcd]
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.
2017-07-10 16:27:12 27528 [Note] Plugin 'FEDERATED' is disabled.
2017-07-10 16:27:12 27528 [Note] InnoDB: Using atomics to ref count buffer pool pages
2017-07-10 16:27:12 27528 [Note] InnoDB: The InnoDB memory heap is disabled
2017-07-10 16:27:12 27528 [Note] InnoDB: Mutexes and rw_locks use GCC atomic builtins
2017-07-10 16:27:12 27528 [Note] InnoDB: Memory barrier is not used
2017-07-10 16:27:12 27528 [Note] InnoDB: Compressed tables use zlib 1.2.3
2017-07-10 16:27:12 27528 [Note] InnoDB: Using Linux native AIO
2017-07-10 16:27:12 27528 [Note] InnoDB: Using CPU crc32 instructions
2017-07-10 16:27:12 27528 [Note] InnoDB: Initializing buffer pool, size = 128.0M
2017-07-10 16:27:12 27528 [Note] InnoDB: Completed initialization of buffer pool
2017-07-10 16:27:12 27528 [Note] InnoDB: Highest supported file format is Barracuda.
2017-07-10 16:27:12 27528 [Note] InnoDB: Log scan progressed past the checkpoint lsn 13025627845
2017-07-10 16:27:12 27528 [Note] InnoDB: Database was not shutdown normally!
2017-07-10 16:27:12 27528 [Note] InnoDB: Starting crash recovery.
2017-07-10 16:27:12 27528 [Note] InnoDB: Reading tablespace information from the .ibd files...
2017-07-10 16:27:12 27528 [Note] InnoDB: Restoring possible half-written data pages
2017-07-10 16:27:12 27528 [Note] InnoDB: from the doublewrite buffer...
InnoDB: Doing recovery: scanned up to log sequence number 13026386304
2017-07-10 16:27:12 27528 [Note] InnoDB: Starting an apply batch of log records to the database...
InnoDB: Progress in percent: 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
2017-07-10 16:27:12 27528 [Note] InnoDB: 128 rollback segment(s) are active.
2017-07-10 16:27:12 27528 [Note] InnoDB: Waiting for purge to start
2017-07-10 16:27:12 27528 [Note] InnoDB: 5.6.36 started; log sequence number 13026386304
2017-07-10 16:27:12 27528 [Note] Recovering after a crash using mysql-bin
2017-07-10 16:27:12 27528 [Note] Starting crash recovery...
2017-07-10 16:27:12 27528 [Note] Crash recovery finished.
2017-07-10 16:27:12 7f160bfff700 InnoDB: Assertion failure in thread 139732667332352 in file fsp0fsp.cc line 1868
InnoDB: Failing assertion: inode
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.6/en/forcing-innodb-recovery.html
InnoDB: about forcing recovery.
13:27:12 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=402653184
read_buffer_size=2097152
max_used_connections=0
max_threads=151
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 = 1013644 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)[0x922735]
/usr/sbin/mysqld(handle_fatal_signal+0x3d8)[0x679f58]
/lib64/libpthread.so.0(+0xf7e0)[0x7f164ac8f7e0]
/lib64/libc.so.6(gsignal+0x35)[0x7f164993a495]
/lib64/libc.so.6(abort+0x175)[0x7f164993bc75]
/usr/sbin/mysqld[0xad7df2]
/usr/sbin/mysqld[0xae0002]
/usr/sbin/mysqld[0xa3eae3]
/usr/sbin/mysqld[0xa40602]
/usr/sbin/mysqld[0xa2dddf]
/usr/sbin/mysqld[0xa31adb]
/lib64/libpthread.so.0(+0x7aa1)[0x7f164ac87aa1]
/lib64/libc.so.6(clone+0x6d)[0x7f16499f0bcd]
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.
