mysql报错：Ignoring the redo log due to missing MLOG_CHECKPOINT between the checkpoint 63593957 and the end 63593472.

mysql版本：5.7.19

系统版本：centos7.3

由于公司断电，跑在vmware虚拟机上的mysql挂掉，无法重启

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 mode.
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 cache. 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 the 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 the 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 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 be 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 are not created/initialized properly. Check for additional messages above. You will not be able to start replication on 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 = 5M
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 man 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 checkpoint 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

丢失数据
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 be corrupt or you may have copied the InnoDB tablespace but not the InnoDB log files. Please 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 be corrupt or you may have copied the InnoDB tablespace but not the InnoDB log files. Please 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 be corrupt or you may have copied the InnoDB tablespace but not the InnoDB log files. Please 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 be corrupt or you may have copied the InnoDB tablespace but not the InnoDB log files. Please 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 be corrupt or you may have copied the InnoDB tablespace but not the InnoDB log files. Please 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 be corrupt or you may have copied the InnoDB tablespace but not the InnoDB log files. Please 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 mode.
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 be corrupt or you may have copied the InnoDB tablespace but not the InnoDB log files. Please 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 be corrupt or you may have copied the InnoDB tablespace but not the InnoDB log files. Please 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 be corrupt or you may have copied the InnoDB tablespace but not the InnoDB log files. Please refer to http://dev.mysql.com/doc/refman/5.7/en/forcing-innodb-recovery.html for information about forcing recovery.

时间： 2024-08-30 10:46:51

mysql报错：Ignoring the redo log due to missing MLOG_CHECKPOINT between the checkpoint 63593957 and the end 63593472.的相关文章

springboot报错Unable to start EmbeddedWebApplicationContext due to missing EmbeddedServletContainerFactory bean

springboot项目在启动时需要把servlet容器编译进去,这时候如果你的maven依赖里面没有配置jetty或者tomcat相关依赖就会报错. 解决方法: jetty添加 <dependency> <groupId>org.springframework.boot</groupId> <artifactId>spring-boot-starter-jetty</artifactId> <scope>provided</s

MYSQL报错，Failed to open log

在清理MYSQL日志时,遇到奇怪的问题,Windows日志显示报错 Failed to open log (file 'F:\MySQL\Data\Hotwind-bin.000023', errno 2)For more information, see Help and Support Center at http://www.mysql.com. 处理方式:找到MYSQL文件夹下Data目录,删除所有包含*-bin.*文件,就能够正常启动MYSQL.

mysql报错问题解决Character set &#39;utf8mb4&#39; is not a compiled character set

mysql: Character set 'utf8mb4' is not a compiled character set and is not specified in the '/usr/share/mysql/charsets/Index.xml' file 报错的解决方法 1.由于日常程序使用了字符集utf8mb4,为了避免每次更新时,set names utf8mb4,就把配置文件改了,如下: 增加了mysql客户端的默认字符集设置 [[email protected]~]# vim

mysql报错：Access denied for user &#39;root&#39;@&#39;localhost&#39; 的一次解决办法

Centos6.5 X64,Mysql 5.6.20 X64 均是64位 顺便记录一下,方便后来人. 1.java.sql.SQLException: Access denied for user 'root'@'localhost' (using password: YES) 确认用户名.密码是正确的. select * from mysql.user;之后,发现 没有localhost用户 可以复制一行 127.0.0.1的记录,然后再次修改密码 mysql> UPDATE user SET

mysql报错：/usr/sbin/mysqld:unknown variable &#39;default-character-set=utf8&#39;

修改mysql的字符集时,为了将默认字符集设置为utf-8,便将/etc/my.cnf下[mysqld]加了一行 default-character-set=utf8, 但是在下次启动系统的时候,mysql登录不上,报错Can't connect to local MySQL serverthrough socket '/var/lib/mysql/mysql.sock'(2), 这时通过命令查找mysql.sock #find / -name mysql.sock , 没有查找到文件,mysq

Mysql报错 ：Unknown table engine &#39;InnoDB&#39; &nbsp;

问题: zabbix服务器重启后,进入zabbix的web发现登录不进去并且网页报mysql的错误,查看mysql的日之后,发现报错: [[email protected] ~]# tail -f /var/log/mysqld.log 140820 16:24:43 [Note] /usr/libexec/mysqld: ready for connections. Version: '5.1.73'  socket: '/var/lib/mysql/mysql.sock'  port: 33

Mysql报错Fatal error: Can&#39;t open and lock privilege tables: Table &#39;mysql.host&#39; doesn&#39;t exist

安装mysql后,启动时候没有启动成功,查看了下日志报错如下:--------------------------------------------- 1   可以:初始化mysql:mysql_install_db 2   目录权限问题chown -R mysql:mysql  /var/lib/mysql [[email protected] local]# less /var/log/mysqld.log1.查看报错信息如下:[ERROR] Fatal error: Can't open

mysql 报错&#39;./ivr/T_CDR&#39; is marked as crashed and should be repaired when doing LOCK TABLES

出现这种情况应该是在跑业务的时候,mysql数据库异常中断导致表异常,查看mysql日志报错如下 [[email protected] opt]# tail -n 5/var/log/mysqld.log 16082713:29:33[ERROR]/usr/libexec/mysqld:Table'./ivr/T_CDR' is marked as crashed and should be repaired 16082713:29:40[ERROR]/usr/libexec/mysqld:Ta

mysql报错Multi-statement transaction required more than &#39;max_binlog_cache_size&#39; bytes of storage

mysql报错Multi-statement transaction required more than 'max_binlog_cache_size' bytes of storage 在执行create table  xx  as  select xx的时候 或者在执行 tpcc-mysql的tpcc_load 的时候 都会遇到这个错误 1534, HY000, Writing one row to the row-based binary log failedRetrying ... 1