1067 error on attempt to start MySQL

Question

I\'ve installed MySQL on Windows 7. When I\'m trying to start MySQL service I\'m getting error 1067: The process terminated unexpectedly. Log message:

101111         


        

Answer 1

In my case, I had another MySQL version installed and running. I found this by going into the mysql_error.log file. I fix this by going to services and stopping the running MySQL version and setting up to a manual, and starting the mysql needed.

Answer 2

...an old one... anyway I had the same issue with MariaDB

In my case most pathes contain special characters like: # Wrapping pathes in my.ini in double quotes made the trick - e.g.

datadir="C:/#windata64/db/MariaDB/data"

Answer 3

My issue happened right after a power failure. I got the error 1067 The process terminated unexpectedly. MySQL needless to say did not start. The answer was simple

1. Open mysql path\data
2. Remove (delete) both ib_logfile0 and ib_logfile1.
3. Start the service

Answer 4

Check the file "C:\Program Files\MySQL\MySQL Server 5.1\my.ini"

The datadir line in my.ini should specify a path. Check the contents of that datadir path. Does it contain a folder named "mysql" and another folder named "test"?

If not, here are two choices:

1. Change the datadir line in my.ini to the correct location. This will probably be C:\ProgramData\MySQL\MySQL Server 5.1\data

2. Clean out the existing contents of your datadir path. Copy the contents of the C:\ProgramData\MySQL\MySQL Server 5.1\data to your datadir path. Restarting the mysql service should rebuild your empty database.

Answer 5

I had the same error and it was caused by non standard characters in the log files path. In order to fix that I found my.ini config file (in my case C:\ProgramData\MySQL\MySQL Server 5.6\my.ini) and modified keys slow_query_log_file and log-error. After that I managed to start MySQL service succesfully.

Answer 6

In my instance it had nothing to do with spaces in the file name. I used the MSI installer custom configuration and opted to exclude the default databases, assuming it was just something like Northwind/Adventureworks. Nope, it includes the core MySql system database... once I added that to the installation it worked.