Getting error “Plugin 'InnoDB' registration as a STORAGE ENGINE failed” when starting MySQL

前端 未结 7 1550
失恋的感觉
失恋的感觉 2021-02-01 05:54

I found many similar question on Stackoverflow but didn\'t get the exact error solution. My issue is when starting MySQL service on one of the Dedicated Centos 6.5 machine, I am

相关标签:
7条回答
  • 2021-02-01 06:30

    Nothing was working with reinstalls, removes, and others (I had no data to keep, not a fix; more of a data destruction process, big caveat there):

    1005  mysql_install_db
    1007  /usr/bin/mysqld_safe --datadir='/var/lib/mysql
    1008  /usr/bin/mysqld_safe --datadir='/var/lib/mysql' (^z)
    1009  bg
    1010  mysql
    1011  mysql_secure_installation
    1012  mysql
    1013  mysql -p
    

    And viola; actually usable database.

    0 讨论(0)
  • 2021-02-01 06:31

    Although late but putting answer here so that solution that helped me can help someone. I took following steps:

    1. Added more RAM to sever
    2. Decrease the value of innodb-buffer-pool size
    3. Set innodb_log_file_size
    4. Restart mysql

    Example of addition to my.cnf:

    innodb_buffer_pool_size = 10M
    innodb_log_file_size = 1000M
    
    0 讨论(0)
  • 2021-02-01 06:32

    This is frequently occurred issue. Do following -

    1. delete/move out these "aria_log_contro, ib_logfile0, ib_logfile1, ib_data1" files from location "..\xampp\mysql\data" and also from "..\xampp\mysql\backup".
    2. stop and start apache server and mysql form xampp control panel

    This should fix the issue; actually it worked for me.

    0 讨论(0)
  • 2021-02-01 06:34

    I fixed this issue by following:

    • Login to server via SSH with root access.
    • Navigate to /var/lib/mysql.
    • If you see log files like, ib_logfile0 and ib_logfile1, rename or move them to some other folder.
    • Stop and start the MySQL service by running sudo service mysql stop and sudo service mysql start

    I hope this helps. Thanks

    0 讨论(0)
  • 2021-02-01 06:39

    Changing the values of innodb_buffer_pool_size and innodb_log_file_size didn't work for me.

    Moving ib_logfile0 and ib_logfile1 files didn't help either.

    What did help was:

    > service mysql stop
    

    Edit my.cfg and add innodb_force_recovery = 1

    > service mysql start
    > service mysql stop
    

    Comment the innodb_force_recovery = 1 line.

    > service mysql start
    

    And voilá. (I should note that I have no idea if this involves any data loss or not)

    0 讨论(0)
  • 2021-02-01 06:43

    I have the same problems, this my solution:

    1. Add more RAM to the server

    2. Decrease the value of innodb-buffer-pool size in the config file:

      sudo nano /etc/mysql/my.cnf

      innodb_buffer_pool_size = 10M
      

    After save /etc/mysql/my.cnf.

    Restart mysql service:

    sudo service mysql restart
    
    exit
    
    0 讨论(0)
提交回复
热议问题