Mysql - innoDb - is in the future! Current system log sequence number
Posted
by
Ward Loockx
on Server Fault
See other posts from Server Fault
or by Ward Loockx
Published on 2012-09-01T12:48:44Z
Indexed on
2012/09/01
15:39 UTC
Read the original article
Hit count: 328
I have this error in my syslog. I restored an older dump to solve this problem, after some reading. Now The errors in syslog are far less than before.
But still a few times an hour I get
Sep 1 14:23:29 homer mysqld: 120901 14:23:29 InnoDB: Error: page 96637 log sequence number 7 1223357717
Sep 1 14:23:29 homer mysqld: InnoDB: is in the future! Current system log sequence number 6 647303887.
Sep 1 14:23:29 homer mysqld: InnoDB: Your database may be corrupt or you may have copied the InnoDB
Sep 1 14:23:29 homer mysqld: InnoDB: tablespace but not the InnoDB log files. See
Sep 1 14:23:29 homer mysqld: InnoDB: http://dev.mysql.com/doc/refman/5.1/en/forcing-recovery.html
Sep 1 14:23:29 homer mysqld: InnoDB: for more information.
Sep 1 14:23:29 homer mysqld: 120901 14:23:29 InnoDB: Error: page 96638 log sequence number 8 150027924
Sep 1 14:23:29 homer mysqld: InnoDB: is in the future! Current system log sequence number 6 647303887.
Sep 1 14:23:29 homer mysqld: InnoDB: Your database may be corrupt or you may have copied the InnoDB
Sep 1 14:23:29 homer mysqld: InnoDB: tablespace but not the InnoDB log files. See
Sep 1 14:23:29 homer mysqld: InnoDB: http://dev.mysql.com/doc/refman/5.1/en/forcing-recovery.html
Sep 1 14:23:29 homer mysqld: InnoDB: for more information.
Sep 1 14:23:29 homer mysqld: 120901 14:23:29 InnoDB: Error: page 96639 log sequence number 7 4208567151
Sep 1 14:23:29 homer mysqld: InnoDB: is in the future! Current system log sequence number 6 647303887.
Sep 1 14:23:29 homer mysqld: InnoDB: Your database may be corrupt or you may have copied the InnoDB
Sep 1 14:23:29 homer mysqld: InnoDB: tablespace but not the InnoDB log files. See
Sep 1 14:23:29 homer mysqld: InnoDB: http://dev.mysql.com/doc/refman/5.1/en/forcing-recovery.html
Sep 1 14:23:29 homer mysqld: InnoDB: for more information.
Anybody that knows how I can track what database is causing this issue? And how to fix?
© Server Fault or respective owner