MySQL cannot be started

Recently encountered a problem, MySQL cannot be started, and after reinstalling it to StartService, it will fail to find my from the Internet. if the database engine in ini is changed to MyISAM, you can use the default-storage-engineINNODB and default-storage-engineMYISAM for personal testing. MySQL can be used, but it is not fundamentally solved.

Recently encountered a problem, MySQL cannot be started, after reinstalling it to the Start Service, it will fail to find my from the Internet. change the database engine in ini to MyISAM. You can use default-storage-engine = INNODB and default-storage-engine = MYISAM for personal testing. MySQL can indeed be used, but not fundamentally

A problem occurred recently. MySQL cannot be started. After being reinstalled, it fails to Start the Service.

You can change the database engine in my. ini to MyISAM from the Internet.

Before Modification

Default-storage-engine = INNODB

After modification

Default-storage-engine = MYISAM

In my personal test, MySQL can be used, but it does not fundamentally solve the problem that the Innodb engine cannot be started.

Check the log to find this error

Plugin 'innodb' registry as a storage engine failed

The reason is that the logfie file is locked due to a database exception. Even if MySQL is reinstalled, this logfie still exists.

Delete the id_logfile * in the MySQL database file. The problem is solved and the Innodb engine starts properly.