【无标题】You can set innodb_force_recovery=1 in my.cnf to force InnoDB: a startup if you are trying to r

本文主要是介绍【无标题】You can set innodb_force_recovery=1 in my.cnf to force InnoDB: a startup if you are trying to r，希望对大家解决编程问题提供一定的参考价值，需要的开发者们随着小编来一起学习吧！

在配置主从之前，可以正常启动，添加复制参数后，无法启动。

注意参数：添加前和添加后不一至

innodb_data_file_path=ibdata1:200M;ibdata2:200M;ibdata3:200M;ibdata4:200M:autoextend:max:5G
innodb_temp_data_file_path =ibtmp1:200M;ibtmp2:200M;ibtmp3:200M:autoextend:max:20G

[root@mymha5 3306]# systemctl status mysqld
● mysqld.service - MySQL Server
Loaded: loaded (/usr/lib/systemd/system/mysqld.service; enabled; vendor preset: disabled)
Active: activating (start) since Fri 2022-04-01 22:06:49 CST; 2s ago
Docs: man:mysqld(8)
http://dev.mysql.com/doc/refman/en/using-systemd.html
Main PID: 4459; : 31590 (mysql.server)
Tasks: 6
CGroup: /system.slice/mysqld.service
├─ 304 /mysql/app/mysql/bin/mysqld --defaults-file=/mysql/data/3306/my.cnf --basedir=/mysql/app/...
├─ 329 sleep 1
├─31590 /bin/sh /mysql/app/mysql/support-files/mysql.server start
└─31603 /bin/sh /mysql/app/mysql/bin/mysqld_safe --defaults-file=/mysql/data/3306/my.cnf --datadi...

Apr 01 22:06:49 mymha5 systemd[1]: Starting MySQL Server...

#############################################################

[root@mymha5 3306]# journalctl -xe

-- Unit mysqld.service has begun starting up.
Apr 01 22:06:20 mymha5 mysql.server[25450]: Starting MySQL.......The server quit without updating PID file (/my
Apr 01 22:06:20 mymha5 systemd[1]: mysqld.service: control process exited, code=exited status=1
Apr 01 22:06:20 mymha5 systemd[1]: Failed to start MySQL Server.
-- Subject: Unit mysqld.service has failed
-- Defined-By: systemd
-- Support: http://lists.freedesktop.org/mailman/listinfo/systemd-devel
--
-- Unit mysqld.service has failed.

##################################################

[root@mymha5 ~]# tail -f 100 /mysql/log/3306/itpuxdb-error.err

2022-04-01T22:04:25.394130+08:00 0 [Note] InnoDB: Opened 3 undo tablespaces
2022-04-01T22:04:25.394152+08:00 0 [Note] InnoDB: 3 undo tablespaces made active
2022-04-01T22:04:25.394298+08:00 0 [Note] InnoDB: Highest supported file format is Barracuda.
2022-04-01T22:04:25.401758+08:00 0 [Note] InnoDB: Creating shared tablespace for temporary tables
2022-04-01T22:04:25.401781+08:00 0 [Note] InnoDB: Need to create a new innodb_temporary data file 'ibtmp3'.
2022-04-01T22:04:25.401856+08:00 0 [Note] InnoDB: Setting file './ibtmp1' size to 200 MB. Physically writing the file full; Please wait ...
2022-04-01T22:04:25.401919+08:00 0 [Note] InnoDB: Progress in MB:
100 200
2022-04-01T22:04:25.538903+08:00 0 [Note] InnoDB: File './ibtmp1' size is now 200 MB.
2022-04-01T22:04:25.539039+08:00 0 [Note] InnoDB: Setting file './ibtmp3' size to 200 MB. Physically writing the file full; Please wait ...
2022-04-01T22:04:25.539114+08:00 0 [Note] InnoDB: Progress in MB:
100 200
2022-04-01T22:04:25.675688+08:00 0 [Note] InnoDB: File './ibtmp3' size is now 200 MB.
2022-04-01T22:04:25.676380+08:00 0 [Note] InnoDB: 96 redo rollback segment(s) found. 96 redo rollback segment(s) are active.
2022-04-01T22:04:25.676390+08:00 0 [Note] InnoDB: 32 non-redo rollback segment(s) are active.
2022-04-01T22:04:25.676610+08:00 0 [Note] InnoDB: Waiting for purge to start
2022-04-01T22:04:25.727567+08:00 0 [ERROR] InnoDB: Tablespace size stored in header is 51200 pages, but the sum of data file sizes is only 38400 pages
2022-04-01T22:04:25.727645+08:00 0 [ERROR] InnoDB: Cannot start InnoDB. The tail of the system tablespace is missing. Have you edited innodb_data_file_path in my.cnf in an InnoDB: inappropriate way, removing ibdata files from there? You can set innodb_force_recovery=1 in my.cnf to force InnoDB: a startup if you are trying to recover a badly corrupt database.
2022-04-01T22:04:25.727664+08:00 0 [ERROR] InnoDB: Plugin initialization aborted with error Generic error