141001 17:53:20 [Note] Plugin 'FEDERATED' is disabled. 
  141001 17:53:20 InnoDB: The InnoDB memory heap is disabled 
  141001 17:53:20 InnoDB: Mutexes and rw_locks use GCC atomic builtins 
  141001 17:53:20 InnoDB: Compressed tables use zlib 1.2.8 
  141001 17:53:20 InnoDB: Using Linux native AIO 
  141001 17:53:21 InnoDB: Initializing buffer pool, size = 128.0M 
  141001 17:53:21 InnoDB: Completed initialization of buffer pool 
  141001 17:53:21 InnoDB: highest supported file format is Barracuda. 
  InnoDB: Log scan progressed past the checkpoint lsn 966165818791 
  141001 17:53:21  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 966169358054 
  InnoDB: 1 transaction(s) which must be rolled back or cleaned up 
  InnoDB: in total 7935 row operations to undo 
  InnoDB: Trx id counter is 617A800 
  141001 17:53:24  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 141001 17:53:33  InnoDB: Error: page 384527 log sequence number 966169367520 
  InnoDB: is in the future! Current system log sequence number 966169358476. 
  InnoDB: Your database may be corrupt or you may have copied the InnoDB 
  InnoDB: tablespace but not the InnoDB log files. See 
  InnoDB:http://dev.mysql.com/doc/refman/5.5/en/forcing-innodb-recovery.html 
  InnoDB: for more information. 
  27 28 29 30 31 32 33 34 35 36 37 38 39 40 14:53:36 UTC - mysqld got signal 11 ; 
  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 = 346685 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 
  /usr/sbin/mysqld(my_print_stacktrace+0x20)[0x7fc859ef6480] 
  /usr/sbin/mysqld(handle_fatal_signal+0x3d5)[0x7fc859de1575] 
  /lib/x86_64-linux-gnu/libpthread.so.0(+0xfbb0)[0x7fc858b76bb0] 
  /usr/sbin/mysqld(+0x6391fb)[0x7fc85a0441fb] 
  /usr/sbin/mysqld(+0x63a5bc)[0x7fc85a0455bc] 
  /usr/sbin/mysqld(+0x627cc0)[0x7fc85a032cc0] 
  /usr/sbin/mysqld(+0x6295c4)[0x7fc85a0345c4] 
  /usr/sbin/mysqld(+0x5cbe6a)[0x7fc859fd6e6a] 
  /usr/sbin/mysqld(+0x5f88e9)[0x7fc85a0038e9] 
  /usr/sbin/mysqld(+0x5896c8)[0x7fc859f946c8] 
  /lib/x86_64-linux-gnu/libpthread.so.0(+0x7f6e)[0x7fc858b6ef6e] 
  /lib/x86_64-linux-gnu/libc.so.6(clone+0x6d)[0x7fc8582919cd] 
  The manual page athttp://dev.mysql.com/doc/mysql/en/crashing.html contains 
  information that should help you find out what is causing the crash. 
  141001 17:53:36 [Note] Plugin 'FEDERATED' is disabled. 
  141001 17:53:36 InnoDB: The InnoDB memory heap is disabled 
  141001 17:53:36 InnoDB: Mutexes and rw_locks use GCC atomic builtins 
  141001 17:53:36 InnoDB: Compressed tables use zlib 1.2.8 
  141001 17:53:36 InnoDB: Using Linux native AIO 
  141001 17:53:36 InnoDB: Initializing buffer pool, size = 128.0M 
  141001 17:53:36 InnoDB: Completed initialization of buffer pool 
  141001 17:53:36 InnoDB: highest supported file format is Barracuda. 
  InnoDB: Log scan progressed past the checkpoint lsn 966165818791 
  141001 17:53:36  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 966169358054 
  InnoDB: 1 transaction(s) which must be rolled back or cleaned up 
  InnoDB: in total 7935 row operations to undo 
  InnoDB: Trx id counter is 617A800 
  141001 17:53:37  InnoDB: Starting an apply batch of log records to the database... 
  InnoDB: Progress in percents: 0 1 2 3 4 5 14:53:39 UTC - mysqld got signal 11 ; 
  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 = 346685 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 
  /usr/sbin/mysqld(my_print_stacktrace+0x20)[0x7fcdd87be480] 
  /usr/sbin/mysqld(handle_fatal_signal+0x3d5)[0x7fcdd86a9575] 
  /lib/x86_64-linux-gnu/libpthread.so.0(+0xfbb0)[0x7fcdd743ebb0] 
  /usr/sbin/mysqld(+0x6391fb)[0x7fcdd890c1fb] 
  /usr/sbin/mysqld(+0x63a5bc)[0x7fcdd890d5bc] 
  /usr/sbin/mysqld(+0x627cc0)[0x7fcdd88facc0] 
  /usr/sbin/mysqld(+0x6295c4)[0x7fcdd88fc5c4] 
  /usr/sbin/mysqld(+0x5cbe6a)[0x7fcdd889ee6a] 
  /usr/sbin/mysqld(+0x5f88e9)[0x7fcdd88cb8e9] 
  /usr/sbin/mysqld(+0x5896c8)[0x7fcdd885c6c8] 
  /lib/x86_64-linux-gnu/libpthread.so.0(+0x7f6e)[0x7fcdd7436f6e] 
  /lib/x86_64-linux-gnu/libc.so.6(clone+0x6d)[0x7fcdd6b599cd] 
  The manual page athttp://dev.mysql.com/doc/mysql/en/crashing.html contains 
  information that should help you find out what is causing the crash. 
  141001 17:53:39 [Note] Plugin 'FEDERATED' is disabled. 
  141001 17:53:39 InnoDB: The InnoDB memory heap is disabled 
  141001 17:53:39 InnoDB: Mutexes and rw_locks use GCC atomic builtins 
  141001 17:53:39 InnoDB: Compressed tables use zlib 1.2.8 
  141001 17:53:39 InnoDB: Using Linux native AIO 
  141001 17:53:39 InnoDB: Initializing buffer pool, size = 128.0M 
  141001 17:53:39 InnoDB: Completed initialization of buffer pool 
  141001 17:53:39 InnoDB: highest supported file format is Barracuda. 
  InnoDB: Log scan progressed past the checkpoint lsn 966165818791 
  141001 17:53:39  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 966169358054 
  InnoDB: 1 transaction(s) which must be rolled back or cleaned up 
  InnoDB: in total 7935 row operations to undo 
  InnoDB: Trx id counter is 617A800 
  141001 17:53:40  InnoDB: Starting an apply batch of log records to the database... 
  InnoDB: Progress in percents: 0 1 2 3 4 5 14:53:40 UTC - mysqld got signal 11 ; 
  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 = 346685 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 
  /usr/sbin/mysqld(my_print_stacktrace+0x20)[0x7fbe83b42480] 
  /usr/sbin/mysqld(handle_fatal_signal+0x3d5)[0x7fbe83a2d575] 
  /lib/x86_64-linux-gnu/libpthread.so.0(+0xfbb0)[0x7fbe827c2bb0] 
  /usr/sbin/mysqld(+0x6391fb)[0x7fbe83c901fb] 
  /usr/sbin/mysqld(+0x63a5bc)[0x7fbe83c915bc] 
  /usr/sbin/mysqld(+0x627cc0)[0x7fbe83c7ecc0] 
  /usr/sbin/mysqld(+0x6295c4)[0x7fbe83c805c4] 
  /usr/sbin/mysqld(+0x5cbe6a)[0x7fbe83c22e6a] 
  /usr/sbin/mysqld(+0x5f88e9)[0x7fbe83c4f8e9] 
  /usr/sbin/mysqld(+0x5896c8)[0x7fbe83be06c8] 
  /lib/x86_64-linux-gnu/libpthread.so.0(+0x7f6e)[0x7fbe827baf6e] 
  /lib/x86_64-linux-gnu/libc.so.6(clone+0x6d)[0x7fbe81edd9cd] 
  The manual page athttp://dev.mysql.com/doc/mysql/en/crashing.html contains 
  information that should help you find out what is causing the crash.