150908 16:08:07 [Warning] Using unique option prefix key_buffer instead of key_buffer_size is deprecated and will be removed in a future release. Please use the full name instead.
150908 16:08:07 [Warning] 'THREAD_CONCURRENCY' is deprecated and will be removed in a future release.
150908 16:08:07 [Note] mysqld (mysqld 5.5.43-0ubuntu0.14.04.1) starting as process 18603 ...
150908 16:08:07 [Note] Plugin 'FEDERATED' is disabled.
150908 16:08:07 InnoDB: Mutexes and rw_locks use GCC atomic builtins
150908 16:08:07 InnoDB: Compressed tables use zlib 1.2.8
150908 16:08:07 InnoDB: Using Linux native AIO
150908 16:08:07 InnoDB: Initializing buffer pool, size = 256.0M
150908 16:08:07 InnoDB: Completed initialization of buffer pool
150908 16:08:07 InnoDB: highest supported file format is Barracuda.
150908 16:08:07  InnoDB: ERROR: We were only able to scan the log up to
InnoDB: 1611264, but a checkpoint was at 1611737.
InnoDB: It is possible that the database is now corrupt!
150908 16:08:07  InnoDB: Assertion failure in thread 140397484521344 in file fsp0fsp.c line 2102
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.5/en/forcing-innodb-recovery.html
InnoDB: about forcing recovery.
16:08:07 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 = 1013452 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
mysqld(my_print_stacktrace+0x20)[0x7fb0d681ec80]
mysqld(handle_fatal_signal+0x3d5)[0x7fb0d6708f15]
/lib/x86_64-linux-gnu/libpthread.so.0(+0x10340)[0x7fb0d5499340]
/lib/x86_64-linux-gnu/libc.so.6(gsignal+0x39)[0x7fb0d4af0cc9]
/lib/x86_64-linux-gnu/libc.so.6(abort+0x148)[0x7fb0d4af40d8]
mysqld(+0x6028d0)[0x7fb0d69308d0]
mysqld(+0x607d16)[0x7fb0d6935d16]
mysqld(+0x616059)[0x7fb0d6944059]
mysqld(+0x5dfb93)[0x7fb0d690db93]
mysqld(+0x590aea)[0x7fb0d68beaea]
mysqld(+0x55fe38)[0x7fb0d688de38]
mysqld(_Z24ha_initialize_handlertonP13st_plugin_int+0x41)[0x7fb0d670af41]
mysqld(+0x302171)[0x7fb0d6630171]
mysqld(_Z11plugin_initPiPPci+0x92a)[0x7fb0d663416a]
mysqld(+0x28ac4b)[0x7fb0d65b8c4b]
mysqld(_Z11mysqld_mainiPPc+0x45b)[0x7fb0d65bd5cb]
/lib/x86_64-linux-gnu/libc.so.6(__libc_start_main+0xf5)[0x7fb0d4adbec5]
mysqld(+0x286b08)[0x7fb0d65b4b08]
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.