Unable to start MySQL service error 1067: Process aborted unexpectedly

This error encountered in the previous weeks, no solution, the direct rough unloading load, their own use is wampserver integrated environment, the consequences of the reinstall is MySQL inside some existing database there is no, a little tragedy, but fortunately are some test database, back directly to the small partner back to a copy , this time again met, can't stand, Google Baidu, took two clocks to solve the solution is in the MySQL My.ini file add a line:

The following document addresses the general process that MySQL cannot start under windows:

1, first check whether the port number of MySQL is taken up, Windows CMD under the use, useful words to the corresponding program to shut down

Query port occupancy under Windows: Netstat-ano | Findstr "3306" to get the process number that occupies the port

Process name according to process number PID name: tasklist |findstr 6432, resulting in process names

Windows kills the corresponding process, with Task Manager, or taskkill/pid 6432 or taskkill/im notepad.exe

2, if there is no port occupancy, right-click Computer---Management---services, find dozen mysql,wampserver is wampmysqld, such as, try to start, can start the best, not start, will prompt the corresponding error, according to different types of errors, Usually get the corresponding prompt or solution, if not, see next step:

3. Look at the application in the event manager, find the MySQL with the red exclamation point, see what the error log is, and the following are the problems I encountered this time:

InnoDB: attempted to open a previously opened Tablespace. Previous tablespace Ck_cookabuy/ck_brands uses space id:35 at filepath:. \ck_cookabuy\ck_brands.ibd. Cannot open tablespace cookabuy3/ck_users which uses space id:35 at filepath:. \cookabuy3\ck_users.ibd

Event Viewer

Based on the error, find this article under Goole:

is to add the My.ini in MySQL configuration file

Innodb_force_recovery = 1

After the restart is normal, after the finished can be removed.

And then I went back to the reason why this configuration option was wrong,

It turned out that my machine shut down when the database is not properly closed, because lazy, in their own machine development, generally directly shut down, resulting in the MySQL log file corruption, restart can not be normal recovery, more can not be normal external services.

and off

In the Innodb_force_recovery parameter, refer to this blog post "case" using Innodb_force_recovery to solve the MySQL server crash unable to restart the problem, only to know that he has 6 parameters

1. (srv_force_ignore_corrupt): Ignores the corrupt page that is checked.
2. (srv_force_no_background): Prevent the main thread from running, such as the main thread needs to perform full purge operation, will cause crash.
3. (Srv_force_no_trx_undo): The transaction rollback operation is not performed.
4. (srv_force_no_ibuf_merge): does not perform the insert buffer merge operation.
5. (Srv_force_no_undo_log_scan): Do not look for the log, InnoDB storage engine will not commit the transaction as committed.
6. (Srv_force_no_log_redo): Do not roll forward operations.

this will be able to understand the cause of the error and the solution, it seems to be shut down or to shut down the database properly.

See Baidu inside a lot of methods, toss a long time, and finally so a sentence configuration to solve the problem, is their own experience is not enough, only to do a record. Hopefully this article will help small partners with the same problems.

Unable to start MySQL service error 1067: Process aborted unexpectedly