Operation not allowed when innodb_forced_recovery > 0

Graphemetech Services

• June 30, 2019 16:05

Hello Everyone Few days back my dedicated server has passed through a severe hard drive crash and my service provider unable to recover the data. They suggested me to go with a brand new server and create vps nodes there and migrate data one by one to the new vps nodes. (As bulk migration stops in the middle because of corrupted hard drive.) Now I have created all required VMs, installed WHM in them and start copying domain files one by one. In one VM installed with WHM, showing me this error whenever I am doing any database record edit or creating tables etc. "Operation not allowed when innodb_forced_recovery > 0". I read in other cpanel forum, edited /etc/my.cnf in the same VM node and modified the line innodb_forced_recovery=2 to innodb_forced_recovery=0. Saved and restarted mysql. Now Mysql not starting. Getting this error Waiting for "mysql" to restart "Unrecognized configuration options may have caused the MySQL startup errors. The system has attempted to auto-update your MySQL configuration file for your MySQL version. This should resolve any errors that stem from an outdated MySQL configuration file. "Unrecognized configuration options may have caused the MySQL startup errors. The system has attempted to auto-update your MySQL configuration file for your MySQL version. This should resolve any errors that stem from an outdated MySQL configuration file. "failed. Cpanel::Exception::Services::StartError Service Status mysqld (/usr/sbin/mysqld --daemonize --pid-file=/var/run/mysqld/mysqld.pid) is running as mysql with PID 27359 (systemd+/proc check method). Service Error (XID fajegw) The "mysql" service failed to start. Startup Log Jun 30 21:03:41 server systemd[1]: mysqld.service failed. Jun 30 21:03:41 server systemd[1]: mysqld.service holdoff time over, scheduling restart. Jun 30 21:03:41 server systemd[1]: Stopped MySQL Server. Jun 30 21:03:41 server systemd[1]: start request repeated too quickly for mysqld.service Jun 30 21:03:41 server systemd[1]: Failed to start MySQL Server. Jun 30 21:03:41 server systemd[1]: Unit mysqld.service entered failed state. Jun 30 21:03:41 server systemd[1]: mysqld.service failed. Jun 30 21:03:45 server systemd[1]: start request repeated too quickly for mysqld.service Jun 30 21:03:45 server systemd[1]: Failed to start MySQL Server. Jun 30 21:03:45 server systemd[1]: mysqld.service failed. mysql has failed. Contact your system administrator if the service does not automagically recover Please help me fix this

• 

  nixuser

  • July 01, 2019 13:59

  Tried commenting that line in my.cnf and restarting mysql?

  0
• 

  cPanelMichael

  • July 02, 2019 19:05

  Hello @Graphemetech Services, The innodb_forced_recovery option is only intended for use when InnoDB is corrupted. Since InnoDB should not be corrupted on the new cPanel & WHM servers, you should remove this line completely from the /etc/my.cnf file and then restart MySQL. Let me know if this helps. Thank you.

  0

Please sign in to leave a comment.