Description:
I get I following error in my error.log and I am not able to start my server anyome. Could someone help me ?
7:57:26 InnoDB: ERROR: the age of the last checkpoint is 9441571,
InnoDB: which exceeds the log group capacity 9433498.
InnoDB: If you are using big BLOB or TEXT rows, you must set the
InnoDB: combined size of log files at least 10 times bigger than the
InnoDB: largest such row.
13:06:25 InnoDB: Error: page 6596 log sequence number 2933047928118
InnoDB: is in the future! Current system log sequence number 2933047580828.
3:07:04 InnoDB: Error: page 16384 log sequence number 2933047809205
InnoDB: is in the future! Current system log sequence number 2933047581012.
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.
InnoDB: Dump of the tablespace extent descriptor: len 40; hex 00000000000237f1ffffffff00000000000025f600000004ffafaaaaeaffffffffffffffffffffff; asc 7 % ;
InnoDB: Serious error! InnoDB is trying to free page 16768
InnoDB: though it is already marked as free in the tablespace!
InnoDB: The tablespace free space info is corrupt.
InnoDB: You may need to dump your InnoDB tables and recreate the whole
InnoDB: database!
InnoDB: Please refer to
InnoDB: http://dev.mysql.com/doc/refman/5.5/en/forcing-innodb-recovery.html
InnoDB: about forcing recovery.
180301 13:07:04 InnoDB: Assertion failure in thread 139894455232256 in file fsp0fsp.c line 3309
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.
11:07:04 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 = 346701 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+0x33)[0x7f3bce1a2f43]
/usr/sbin/mysqld(handle_fatal_signal+0x3e4)[0x7f3bce08f634]
/lib/x86_64-linux-gnu/libpthread.so.0(+0xf890)[0x7f3bcd88a890]
/lib/x86_64-linux-gnu/libc.so.6(gsignal+0x37)[0x7f3bcc280067]
/lib/x86_64-linux-gnu/libc.so.6(abort+0x148)[0x7f3bcc281448]
/usr/sbin/mysqld(+0x5f3a70)[0x7f3bce2aea70]
/usr/sbin/mysqld(+0x5f9cec)[0x7f3bce2b4cec]
/usr/sbin/mysqld(+0x5acec3)[0x7f3bce267ec3]
/usr/sbin/mysqld(+0x64c80b)[0x7f3bce30780b]
/usr/sbin/mysqld(+0x64cf50)[0x7f3bce307f50]
/usr/sbin/mysqld(+0x642d18)[0x7f3bce2fdd18]
/usr/sbin/mysqld(+0x580c25)[0x7f3bce23bc25]
/usr/sbin/mysqld(+0x571b1c)[0x7f3bce22cb1c]
/usr/sbin/mysqld(+0x576313)[0x7f3bce231313]
/lib/x86_64-linux-gnu/libpthread.so.0(+0x8064)[0x7f3bcd883064]
/lib/x86_64-linux-gnu/libc.so.6(clone+0x6d)[0x7f3bcc33362d]
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.
180301 13:07:04 [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.
180301 13:07:04 [Note] Plugin 'FEDERATED' is disabled.
180301 13:07:04 InnoDB: The InnoDB memory heap is disabled
180301 13:07:04 InnoDB: Mutexes and rw_locks use GCC atomic builtins
180301 13:07:04 InnoDB: Compressed tables use zlib 1.2.8
180301 13:07:04 InnoDB: Using Linux native AIO
180301 13:07:04 InnoDB: Initializing buffer pool, size = 128.0M
180301 13:07:04 InnoDB: Completed initialization of buffer pool
180301 13:07:04 InnoDB: highest supported file format is Barracuda.
InnoDB: The log sequence number in ibdata files does not match
InnoDB: the log sequence number in the ib_logfiles!
180301 13:07:04 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...
180301 13:07:04 InnoDB: ERROR: We were only able to scan the log up to
InnoDB: 2933047580672, but a checkpoint was at 2933047581012.
InnoDB: It is possible that the database is now corrupt!
180301 13:07:04 InnoDB: Error: page 6 log sequence number 2933047610692
InnoDB: is in the future! Current system log sequence number 2933047581012.
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.
How to repeat:
I get I above error on my error.log and I am not able to start my server anyome.
Could someone help me ?
