MySQL error: Ignoring the redo log due to missing mlog_checkpoint between the CHECKPOINT 63593957 and the end 63593472.

Source: Internet
Author: User
Tags mysql version system log

MySQL error: Ignoring the redo log due to missing mlog_checkpoint between the CHECKPOINT 63593957 and the end 63593472.

MySQL version: 5.7.19

System version: centos7.3

MySQL running on VMware virtual machine hangs and cannot be restarted due to company power outage

Innodb_force_recovery=6
2017-11-15t12:07:25.235397+08:00 0 [Warning] ' db ' entry ' sys [email protected] ' ignored in--skip-name-resolve mode.
2017-11-15t12:07:25.235408+08:00 0 [Warning] ' proxies_priv ' entry ' @ [email protected] ' ignored in--skip-name-resolve mo De.
2017-11-15t12:07:25.235540+08:00 0 [ERROR] innodb:failed to find tablespace for table ' MySQL '. ' Time_zone_leap_second ' in The cache. Attempting to load the tablespace with space ID 46
2017-11-15t12:07:25.256456+08:00 0 [ERROR] innodb:failed to find tablespace for table ' MySQL '. ' Time_zone_name ' in the CAC He. Attempting to load the tablespace with space ID 47
2017-11-15t12:07:25.258414+08:00 0 [ERROR] innodb:failed to find tablespace for table ' MySQL '. ' Time_zone ' in the cache. Attempting to load the tablespace with space ID 45
2017-11-15t12:07:25.263576+08:00 0 [ERROR] innodb:failed to find tablespace for table ' MySQL '. ' Time_zone_transition_ Type ' in the cache. Attempting to load the tablespace with space ID 49
2017-11-15t12:07:25.267569+08:00 0 [ERROR] innodb:failed to find tablespace for table ' MySQL '. ' Time_zone_transition ' in t He cache. Attempting to load the tablespace with space ID 48
2017-11-15t12:07:25.272648+08:00 0 [ERROR] innodb:failed to find tablespace for table ' MySQL '. ' Servers ' in the cache. Attempting to load the tablespace with space ID 41
2017-11-15t12:07:25.276466+08:00 0 [ERROR] innodb:failed to find tablespace for table ' MySQL '. ' Slave_master_info ' in the Cache. Attempting to load the tablespace with space ID 42
2017-11-15t12:07:25.280225+08:00 0 [ERROR] innodb:failed to find tablespace for table ' MySQL '. ' Slave_relay_log_info ' in t He cache. Attempting to load the tablespace with space ID 43
2017-11-15t12:07:25.286619+08:00 0 [ERROR] innodb:failed to find tablespace for table ' MySQL '. ' Slave_worker_info ' in the Cache. Attempting to load the tablespace with space ID 44
2017-11-15t12:07:25.292450+08:00 0 [ERROR] Error writing master configuration.
2017-11-15t12:07:25.292468+08:00 0 [ERROR] Error reading master configuration.
2017-11-15t12:07:25.294535+08:00 0 [Warning] Recovery from the master POS 1065 and file mysql-bin.000003 for channel '. Previous Relay log pos and relay log file had been set to 4,/data/mysql/mysql3306/logs/mysql-relay.000003 respectively.
2017-11-15t12:07:25.294643+08:00 0 [ERROR] Error writing relay log configuration.
2017-11-15t12:07:25.294656+08:00 0 [ERROR] Error reading relay log configuration.
2017-11-15t12:07:25.294983+08:00 0 [ERROR] slave:failed to initialize the master info structure for channel '; Its record may still is present in ' mysql.slave_master_info ' table, consider deleting it.
2017-11-15t12:07:25.294996+08:00 0 [ERROR] Failed to create or recover replication info repositories.
2017-11-15t12:07:25.295000+08:00 0 [Note] Some of the channels is not created/initialized properly. Check for additional messages above. You are not being able to start replication in those channels until the issue is resolved and the server restarted.

http://blog.csdn.net/weiwangsisoftstone/article/details/52954228

-15t11:44:46.406153+08:00 0 [Note] innodb:using CPU CRC32 Instructions
2017-11-15t11:44:46.453775+08:00 0 [Note] innodb:initializing buffer pool, total size = 5M, instances = 1, chunk size = 5 M
2017-11-15t11:44:46.454888+08:00 0 [Note] innodb:completed initialization of buffer pool
2017-11-15t11:44:46.456582+08:00 0 [Note] innodb:if the mysqld execution user is authorized, page cleaner thread priority can be changed. See the Mans page of SetPriority ().
2017-11-15t11:44:46.546548+08:00 0 [Note] innodb:opened 8 undo Tablespaces
2017-11-15t11:44:46.546575+08:00 0 [Note] innodb:8 undo Tablespaces made Active
2017-11-15t11:44:46.546960+08:00 0 [Note] innodb:highest supported file format is Barracuda.
2017-11-15t11:44:46.562061+08:00 0 [ERROR] innodb:ignoring the redo log due to missing mlog_checkpoint between the CHECKP Oint 63593957 and the end 63593472.
2017-11-15t11:44:46.562090+08:00 0 [ERROR] innodb:plugin initialization aborted with error Generic error
2017-11-15t11:44:47.062885+08:00 0 [ERROR] Plugin ' InnoDB ' init function returned ERROR.
2017-11-15t11:44:47.062936+08:00 0 [ERROR] Plugin ' InnoDB ' registration as a STORAGE ENGINE failed.
2017-11-15t11:44:47.062945+08:00 0 [ERROR] Failed to initialize plugins.
2017-11-15t11:44:47.062951+08:00 0 [ERROR] aborting

2017-11-15t11:44:47.062962+08:00 0 [Note] Binlog End
2017-11-15t11:44:47.063067+08:00 0 [Note] shutting down plugin ' MyISAM '
2017-11-15t11:44:47.063097+08:00 0 [Note] shutting down plugin ' CSV '
2017-11-15t11:44:47.063622+08:00 0 [Note]/usr/local/mysql/bin/mysqld:shutdown complete


Lost data
2017-11-15t11:54:17.694175+08:00 0 [Note] Server socket created on IP: ':: '.
2017-11-15t11:54:17.696000+08:00 0 [ERROR] innodb:page [page id:space=40, page number=3] log sequence number 3725922 is In the future! Current system log sequence number 2440232.
2017-11-15t11:54:17.696018+08:00 0 [ERROR] innodb:your database may corrupt or we may have copied the InnoDB Tablespa Ce but not the InnoDB log files. Refer to http://dev.mysql.com/doc/refman/5.7/en/forcing-innodb-recovery.html for information about forcing Recovery.
2017-11-15t11:54:17.696287+08:00 0 [ERROR] innodb:page [page id:space=40, page number=1] log sequence number 3720522 is In the future! Current system log sequence number 2440232.
2017-11-15t11:54:17.696300+08:00 0 [ERROR] innodb:your database may corrupt or we may have copied the InnoDB Tablespa Ce but not the InnoDB log files. Refer to http://dev.mysql.com/doc/refman/5.7/en/forcing-innodb-recovery.html for information about forcing Recovery.
2017-11-15t11:54:17.696535+08:00 0 [ERROR] innodb:page [page id:space=40, page number=2] log sequence number 3724576 is In the future! Current system log sequence number 2440232.
2017-11-15t11:54:17.696551+08:00 0 [ERROR] innodb:your database may corrupt or we may have copied the InnoDB Tablespa Ce but not the InnoDB log files. Refer to http://dev.mysql.com/doc/refman/5.7/en/forcing-innodb-recovery.html for information about forcing Recovery.
2017-11-15t11:54:17.697469+08:00 0 [ERROR] innodb:page [page id:space=32, page number=3] log sequence number 2483079 is In the future! Current system log sequence number 2440232.
2017-11-15t11:54:17.697485+08:00 0 [ERROR] innodb:your database may corrupt or we may have copied the InnoDB Tablespa Ce but not the InnoDB log files. Refer to http://dev.mysql.com/doc/refman/5.7/en/forcing-innodb-recovery.html for information about forcing Recovery.
2017-11-15t11:54:17.697809+08:00 0 [ERROR] innodb:page [page id:space=32, page number=1] log sequence number 2479069 is In the future! Current system log sequence number 2440232.
2017-11-15t11:54:17.697821+08:00 0 [ERROR] innodb:your database may corrupt or we may have copied the InnoDB Tablespa Ce but not the InnoDB log files. Refer to http://dev.mysql.com/doc/refman/5.7/en/forcing-innodb-recovery.html for information about forcing Recovery.
2017-11-15t11:54:17.698049+08:00 0 [ERROR] innodb:page [page id:space=32, page number=2] log sequence number 2482784 is In the future! Current system log sequence number 2440232.
2017-11-15t11:54:17.698061+08:00 0 [ERROR] innodb:your database may corrupt or we may have copied the InnoDB Tablespa Ce but not the InnoDB log files. Refer to http://dev.mysql.com/doc/refman/5.7/en/forcing-innodb-recovery.html for information about forcing Recovery.
2017-11-15t11:54:17.700092+08:00 0 [Warning] ' user ' entry ' [email protected] ' ignored in--skip-name-resolve mode.
2017-11-15t11:54:17.700140+08:00 0 [Warning] ' user ' entry ' [email protected] ' ignored in--skip-name-resolve mode.
2017-11-15t11:54:17.700153+08:00 0 [Warning] ' user ' entry ' [email protected] ' ignored in--skip-name-resolve mode.
2017-11-15t11:54:17.701714+08:00 0 [Warning] ' db ' entry ' Performance_schema [email protected] ' ignored in-- Skip-name-resolve mode.
2017-11-15t11:54:17.701727+08:00 0 [Warning] ' db ' entry ' sys [email protected] ' ignored in--skip-name-resolve mode.
2017-11-15t11:54:17.701881+08:00 0 [Warning] ' proxies_priv ' entry ' @ [email protected] ' ignored in--skip-name-resolve mo De.
2017-11-15t11:54:17.702485+08:00 0 [ERROR] innodb:page [page id:space=46, page number=3] log sequence number 3754946 is In the future! Current system log sequence number 2440232.
2017-11-15t11:54:17.702502+08:00 0 [ERROR] innodb:your database may corrupt or we may have copied the InnoDB Tablespa Ce but not the InnoDB log files. Refer to http://dev.mysql.com/doc/refman/5.7/en/forcing-innodb-recovery.html for information about forcing Recovery.
2017-11-15t11:54:17.702718+08:00 0 [ERROR] innodb:page [page id:space=46, page number=1] log sequence number 3751039 is In the future! Current system log sequence number 2440232.
2017-11-15t11:54:17.702741+08:00 0 [ERROR] innodb:your database may corrupt or we may have copied the InnoDB Tablespa Ce but not the InnoDB log files. Refer to http://dev.mysql.com/doc/refman/5.7/en/forcing-innodb-recovery.html for information about forcing Recovery.
2017-11-15t11:54:17.702962+08:00 0 [ERROR] innodb:page [page id:space=46, page number=2] log sequence number 3754946 is In the future! Current system log sequence number 2440232.
2017-11-15t11:54:17.702974+08:00 0 [ERROR] innodb:your database may corrupt or we may have copied the InnoDB Tablespa Ce but not the InnoDB log files. Refer to http://dev.mysql.com/doc/refman/5.7/en/forcing-innodb-recovery.html for information about forcing Recovery.

MySQL error: Ignoring the redo log due to missing mlog_checkpoint between the CHECKPOINT 63593957 and the end 63593472.

Contact Us

The content source of this page is from Internet, which doesn't represent Alibaba Cloud's opinion; products and services mentioned on that page don't have any relationship with Alibaba Cloud. If the content of the page makes you feel confusing, please write us an email, we will handle the problem within 5 days after receiving your email.

If you find any instances of plagiarism from the community, please send an email to: info-contact@alibabacloud.com and provide relevant evidence. A staff member will contact you within 5 working days.

A Free Trial That Lets You Build Big!

Start building with 50+ products and up to 12 months usage for Elastic Compute Service

  • Sales Support

    1 on 1 presale consultation

  • After-Sales Support

    24/7 Technical Support 6 Free Tickets per Quarter Faster Response

  • Alibaba Cloud offers highly flexible support services tailored to meet your exact needs.