One server power outage, resulting in a InnoDB engine table (log table) corruption solution

1. mysql Log error

InnoDB Engine Tip database does not shut down properly, reported InnoDB error

180112  0:49:28  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  Doublewriteinnodb: buffer ... innodb: doing recovery: scanned up to log sequence number  2580576839180112  0:49:28  innodb: error: page 1 log sequence  number 2580582651innodb: is in the future! current system log  sequence number 2580576839.InnoDB: Your database may be corrupt  or you may have copied the innodbinnodb: tablespace but not  The innodb log files. seeinnodb: http://dev.mysql.com/doc/refman/5.5/en/forcing-innodb-recovery.htmlinnodb: for more information.180112   0:49:28  innodb: error: page 5 log sequence number  2580579963innodb: is in the future! current system log sequence  Number 2580576839.innodb: your database may be corrupt or you may  have copied the innodbinnodb: tablespace but not the innodb  log files. seeinnodb: http://dev.mysql.com/doc/refman/5.5/en/ forcing-innodb-recovery.htmlinnodb: for more information.180112  0:49:29   Innodb: error: page 65565 log sequence number 2580577006innodb: is  in the future! current system log sequence number 2580576839. innodb: your database may be corrupt  or you may have copied the innodbinnodb: tablespace but not  the innodb log files. seeinnodb: http://dev.mysql.com/doc/refman/5.5/en/ forcing-innodb-recovery.htmlinnodb: for more information.180112  0:49:29   Innodb: error: page 65566 log sequence number 2580577176innodb: is  in the future! current system log sequence number 2580576839. Innodb: your database may be corrupt or you may have copied  the InnoDBInnoDB: tablespace but not the InnoDB log files.  Seeinnodb: http://dev.mysql.com/doc/refman/5.5/en/forcing-innodb-recovery.htmlinnodb: for more  information.180112  0:49:29  innodb: starting an apply batch  of log records To the database ... innodb: progress in percents: 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 180112   0:49:29  innodb: assertion failure in thread 140330795001600 in  File rem0rec.c line 569innodb: 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, eveninnodb: immediately after the mysqld startup, there may beinnodb:  corruption in the innodb tablespace. please refer toinnodb: http:// dev.mysql.com/doc/refman/5.5/en/forcing-innodb-recovery.htmlinnodb: about forcing recovery.16 :49:29 utc - mysqld got signal 6 ; this could be because you hit a bug. it is also  possible that this binaryor 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 helpdiagnose the problem, but since we have already crashed, something is definitely wrong and this may  Fail.

2, check the status of the MySQL service, that MySQL is not running, but the lock file exists

error! MySQL is not running,but lock file (/var/lock/subsys/mysql) exists

3. Restart MySQL service, prompt error

[Email protected] subsys]#/etc/init.d/umail_mysqld restart error! MySQL server PID file could not being found! Starting MySQL. error! The server quit without updating PID file (/usr/local/u-mail/data/mysql/default.pid).

The following error is reported in the journal:

180112 9:12:44 Innodb:cannot Initialize created log files because180112 9:12:44 innodb:data files are corrupt, or new Data files were180112 9:12:44 innodb:created When the database is started previous180112 9:12:44 Innodb:time but the Database is not shut down180112 9:12:44 innodb:normally after that.180112 9:12:44 [ERROR] Plugin ' InnoDB ' init functio N Returned error.180112 9:12:44 [ERROR] Plugin ' InnoDB ' registration as a STORAGE ENGINE failed.

Move the database under the Ib_logfile file (since the first time you look at the log, you are prompted innodb:tablespace but not the InnoDB log files. See), you can restart the MySQL service.

4, thought to restart MySQL success can be, but did not expect the InnoDB engine table has been damaged.

Log prompt:

180112 9:37:40 [ERROR] cannot find or open table Umail/core_auth_log fromthe internal data Dictionary of InnoDB though th E. frm file for thetable exists. Maybe you has deleted and recreated InnoDB Datafiles but has forgotten to delete the corresponding. frm filesof InnoDB t Ables, or you are moved. frm files to another database?or, the table contains indexes the this version of the Enginedoes N ' t support. See http://dev.mysql.com/doc/refman/5.5/en/innodb-troubleshooting.htmlhow You can resolve the problem

(1) Use phpMyAdmin to see the hint is in use, repair tips unknown storage engine ' InnoDB ' error.

(2) MySQL command console input show engines; view, nor InnoDB engine.

5. Solutions

(1) Use the drop tables table name;, delete the InnoDB table

(2) Stop services related to MySQL service

(3) Use show processlist; command to see if there is a lock
(4) Place the SQL file that created these tables under one path
(5) to MySQL command console input source/usr/local/kx-mail/data/mysql/default/base_table.sql import
(6) Restart MySQL service

One server power outage, resulting in a InnoDB engine table (log table) corruption solution