MySQL database startup failure 1067 unexpected Process Termination solution Summary

This article summarizes the solutions to the unexpected termination of MySQL database startup failure 1067 process. If you need it, please refer to this article.

This article summarizes the solutions to the unexpected termination of MySQL database startup failure 1067 process. If you need it, please refer to this article.

Symptom:

The day before yesterday, the MYSQL database was migrated. The version of MYSQL on machine B (new machine) is different from that on machine A. To facilitate the installation of MYSQL on machine B, the DATA directory on machine A is directly copied.

Start MYSQL, "unexpected termination of MYSQL 1067 process" error. I have encountered this error before and tried to solve it with inertia. The problem still persists, So google, searching for a long time... Fruitless

Finally, check the system application log: Find the latest MYSQL error, all in E:

Error message file 'd: \ system \ MySQL Server 5.0 \ share \ english \ errmsg. sys 'had only 480 error messages,
But it shoshould contain at least 481 error messages.
Check that the above file is the right version for this program

Probably a version issue

Solution:

Keep the database migrated from machine B, re-execute the repair operation of the MYSQL installation program on machine B, complete the installation, restart MYSQL, OK!

My Mysql encountered a 1067 error.
Error message: A system error has occurred. System error 1067 has occurred. The process terminated unexpectedly.

The solution on my machine is:

Modify % windir % \ my. ini, add [mysqld] # Set basedir to the mysql installation path basedir = D: \ Program \ Tools \ mysql datadir = D: \ Program \ Tools \ mysql \ data

Unable to start MYSQL service error 1067 process unexpectedly terminated

After the MYSQL service is started, the system prompts: the MYSQL service cannot be started on the local computer. Error 1067: the process was unexpectedly terminated.
This service is started -- set -- control panel -- Management Tools -- in the service
Solution 1: copy the my-***. inf file in the mysql directory to the windows directory of the system. Change the file name to my. inf.

Then add similar code in the [mysqld] Code area:

The Code is as follows:
# Set basedir to installation path, e.g., c:/mysql # Set it to the MYSQL installation directory Basedir = D:/Program Files/mysql-5.0.45-win32 # Set datadir to location of data directory, # E.g., c:/mysql/data or d:/mydata/data # Set it to the MYSQL DATA DIRECTORY Datadir = D:/Program Files/mysql-5.0.45-win32/data

Solution 2: mysql 1067

The error is as follows:

1. Run winmysqladmin to generate the my. ini file.
2. Start mysql service with mysqld-install
3. net start mysql startup mysql service display normal
When the mysql-u root-p connection is used, an error indicating that the server has not been started is reported. Check the server service. It is true that the mysql service has not been started. If the mysql service is manually started, a 1067 error is generated and the mysql service has been re-installed several times, the error persists. Check that all configurations are correct.

My system environment is win2003 mysql 4.0.12.
Solution: Copy my. ini generated by winmysqladmin to c: windows and start mysql.
This has not been tried: in fact, you do not need to reconfigure as long as you click mysql.exe in the/bin directory in turn

Mysqld.exe

Mysqld-nt.exe

Winmysqladmin.exe

The prompt box appears, and then the cancle is dropped.

Then click winmysqladmin.exe and select start service on the small icon in the lower right corner.

In this way, the ini file is automatically restored.

Solution 3

1. Cause of error: modified the mysql configuration file my. ini.

2. Check error:

Some code of the my. ini configuration file:

The Code is as follows:
[Mysqld] Port = 3306 Basedir = "D:/MySQL /" Datadir = "C:/Documents and Settings/All Users/Application Data/MySQL Server 5.1/Data /"

3. solution:

When we find the cause of the error, it is easier to understand the error. We only need to double-click mysqlbinmysqlintanceconfig.exe and reconfigure it to solve the problem.