mysql.err

2014-07-12 22:27:43 7f1af54dc780 InnoDB: Warning: Using innodb_additional_mem_pool_size is DEPRECATED. This option may be removed in future releases, together with the option innodb_use_sys_malloc and with the InnoDB's internal memory allocator.
140712 22:27:43 [Note] InnoDB: Using mutexes to ref count buffer pool pages
140712 22:27:43 [Note] InnoDB: The InnoDB memory heap is disabled
140712 22:27:43 [Note] InnoDB: Mutexes and rw_locks use GCC atomic builtins
140712 22:27:43 [Note] InnoDB: Compressed tables use zlib 1.2.8
140712 22:27:43 [Note] InnoDB: Using Linux native AIO
140712 22:27:43 [Note] InnoDB: Not using CPU crc32 instructions
140712 22:27:43 [Note] InnoDB: Initializing buffer pool, size = 80.0M
140712 22:27:43 [Note] InnoDB: Completed initialization of buffer pool
140712 22:27:43 [Note] InnoDB: Highest supported file format is Barracuda.
140712 22:27:43 [Note] InnoDB: Log scan progressed past the checkpoint lsn 564334399
140712 22:27:43 [Note] InnoDB: Database was not shutdown normally!
140712 22:27:43 [Note] InnoDB: Starting crash recovery.
140712 22:27:43 [Note] InnoDB: Reading tablespace information from the .ibd files...
140712 22:27:43 [Note] InnoDB: Restoring possible half-written data pages
140712 22:27:43 [Note] InnoDB: from the doublewrite buffer...
InnoDB: Doing recovery: scanned up to log sequence number 564335336
2014-07-12 22:27:43 7f1af54dc780 InnoDB: Error: page 11 log sequence number 644260397
InnoDB: is in the future! Current system log sequence number 564335336.
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.6/en/forcing-innodb-recovery.html
InnoDB: for more information.
140712 22:27:43 [Note] InnoDB: Starting an apply batch of log records to the database...
InnoDB: Progress in percent: 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
2014-07-12 22:27:43 7f1af54dc780 InnoDB: Error: page 8 log sequence number 644260442
InnoDB: is in the future! Current system log sequence number 564335336.
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.6/en/forcing-innodb-recovery.html
InnoDB: for more information.
140712 22:27:43 [ERROR] 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.

To report this bug, see http://kb.askmonty.org/en/reporting-bugs

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.

Server version: 10.0.12-MariaDB
key_buffer_size=16384
read_buffer_size=131072
max_used_connections=0
max_threads=258
thread_count=0
It is possible that mysqld could use up to
key_buffer_size + (read_buffer_size + sort_buffer_size)*max_threads = 566740 K  bytes of memory
Hope that's ok; if not, decrease some variables in the equation.

Thread pointer: 0x0x0
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 = 0x0 thread_stack 0x48000
/usr/bin/mysqld(my_print_stacktrace+0x3d)[0xb9cc5d]
/usr/bin/mysqld(handle_fatal_signal+0x345)[0x70cc25]
/usr/lib/libpthread.so.0(+0xf4b0)[0x7f1af48334b0]
/usr/bin/mysqld[0x9d3a59]
/usr/bin/mysqld[0x9d5c63]
/usr/bin/mysqld[0x9354d5]
/usr/bin/mysqld[0x86edab]
/usr/bin/mysqld(_Z24ha_initialize_handlertonP13st_plugin_int+0x64)[0x70edd4]
/usr/bin/mysqld[0x5c3bf3]
/usr/bin/mysqld(_Z11plugin_initPiPPci+0x558)[0x5c4a08]
/usr/bin/mysqld[0x529ba0]
/usr/bin/mysqld(_Z11mysqld_mainiPPc+0x5ad)[0x52dcad]
/usr/lib/libc.so.6(__libc_start_main+0xf0)[0x7f1af3600000]
/usr/bin/mysqld[0x5225b1]
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.