2018-09-25 22:39:07 432 [Warning] Using unique option prefix myisam-recover instead of myisam-recover-options is deprecated and will be removed in a future release. Please use the full name instead.
2018-09-25 22:39:07 432 [Note] Plugin 'FEDERATED' is disabled.
2018-09-25 22:39:07 432 [Note] InnoDB: Using atomics to ref count buffer pool pages
2018-09-25 22:39:07 432 [Note] InnoDB: The InnoDB memory heap is disabled
2018-09-25 22:39:07 432 [Note] InnoDB: Mutexes and rw_locks use GCC atomic builtins
2018-09-25 22:39:07 432 [Note] InnoDB: Memory barrier is not used
2018-09-25 22:39:07 432 [Note] InnoDB: Compressed tables use zlib 1.2.8
2018-09-25 22:39:07 432 [Note] InnoDB: Using Linux native AIO
2018-09-25 22:39:07 432 [Note] InnoDB: Using CPU crc32 instructions
2018-09-25 22:39:07 432 [Note] InnoDB: Initializing buffer pool, size = 128.0M
2018-09-25 22:39:07 432 [Note] InnoDB: Completed initialization of buffer pool
2018-09-25 22:39:08 432 [Note] InnoDB: Highest supported file format is Barracuda.
2018-09-25 22:39:08 432 [Note] InnoDB: The log sequence numbers 1595675 and 1595675 in ibdata files do not match the log sequence number 1595916 in the ib_logfiles!
2018-09-25 22:39:08 432 [Note] InnoDB: Database was not shutdown normally!
2018-09-25 22:39:08 432 [Note] InnoDB: Starting crash recovery.
2018-09-25 22:39:08 432 [Note] InnoDB: Reading tablespace information from the .ibd files...
2018-09-25 22:39:08 432 [Note] InnoDB: Restoring possible half-written data pages 
2018-09-25 22:39:08 432 [Note] InnoDB: from the doublewrite buffer...
2018-09-25 22:39:08 432 [Note] InnoDB: 128 rollback segment(s) are active.
2018-09-25 22:39:08 432 [Note] InnoDB: Creating tablespace and datafile system tables.
2018-09-25 22:39:08 7f87ddea4740 InnoDB: Error: Write to file ./ib_logfile0 failed at offset 2048.
InnoDB: 4608 bytes should have been written, only 2048 were written.
InnoDB: Operating system error number 2.
InnoDB: Check that your OS and file system support files of this size.
InnoDB: Check also that the disk is not full or a disk quota exceeded.
InnoDB: Error number 2 means 'No such file or directory'.
InnoDB: Some operating system error numbers are described at
InnoDB: http://dev.mysql.com/doc/refman/5.6/en/operating-system-error-codes.html
2018-09-25 22:39:08 7f87ddea4740  InnoDB: Assertion failure in thread 140221520430912 in file fil0fil.cc line 5764
InnoDB: Failing assertion: ret
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.
22:39:08 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=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 = 76300 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 0x30000
mysqld(my_print_stacktrace+0x2c)[0x8c317c]
mysqld(handle_fatal_signal+0x481)[0x661c61]
/lib/x86_64-linux-gnu/libpthread.so.0(+0xf890)[0x7f87dda85890]
/lib/x86_64-linux-gnu/libc.so.6(gsignal+0x37)[0x7f87dc47b067]
/lib/x86_64-linux-gnu/libc.so.6(abort+0x148)[0x7f87dc47c448]
mysqld[0xa8bc64]
mysqld[0x96178f]
mysqld[0x961c99]
mysqld[0x9fc351]
mysqld[0x9fc5b9]
mysqld[0x9fcacd]
mysqld[0xa5c708]
mysqld[0x9e27df]
mysqld[0x922b48]
mysqld(_Z24ha_initialize_handlertonP13st_plugin_int+0x48)[0x5ab438]
mysqld[0x6e31f1]
mysqld(_Z11plugin_initPiPPci+0x8f0)[0x6e9750]
mysqld(_Z11mysqld_mainiPPc+0x857)[0x5a46a7]
/lib/x86_64-linux-gnu/libc.so.6(__libc_start_main+0xf5)[0x7f87dc467b45]
mysqld[0x5984ed]
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.