Resolve MySQL Automatic stop service solution

Analysis reason one: MySQL's automatic backup function may cause the database to shut down the service before the backup, but when this starts the server does not respond,

Start-run-services.msc, open Windows service to find MySQL services and double-click, click the Recovery tab, the first failure: default is "No action", changed to "Restart service."
Adding "0" at the bottom of "Restart service: minutes" means that the service restarts immediately if it terminates unexpectedly. Click OK to make the settings effective. At this time you end the MYSQL-NT process in the Task Manager, will find that the end does not drop, but should pay attention, such mysql.exe is unable to stop, if want to stop must change just changed back.

Analysis reason two, may be the MySQL connection problem
To modify the maximum number of MySQL connections, use the memory variable modification method to modify the maximum number of MySQL connections
The steps are as follows (both Windows and Linux platforms apply):

A, client login MySQL, enter username and password ' B, set the new maximum number of connections at the MySQL command prompt for 500:mysql> set global max_connections=500
C, display the currently running query:mysql> show processlist
D, display the current mysql system parameter Status:mysql> show status# K;
E, exit client:mysql> exit '
Viewing the current maximum number of connections only needs to be seen by executing the following command in the Mysqladmin directory: Mysqladmin-username-password variables |find "Max_con". You can also use the MySQL parameter list in the PHP tutorial myadmin to view the maximum number of connections.
Disadvantage: Restart the computer or MySQL after the maximum number of connections will be reset to the original value, need to reset.
2, modify My.ini or My.cnf file method (need to restart MySQL), you can refer to the same directory under the MySQL configuration template (small memory, large memory, large memory). E Windows system to open the My.ini file to find set-variable =max_connections=100 this line, change to the need to set the maximum number of connections, and then restart it.
Under the Linux console:
1, open my.cnf file: vi/etc/my.cnf
2 Modify the Max_connections value to the set value under [Mysqld].
Attention:
You may have installed a different MySQL source and version (Windows Mysql+iis and php+apache+mysql Suite final installation results are almost not the same), the My.ini file path may be somewhat different, My.ini may also retain a copy of the C: Windows directory needs to be modified at the same time

This method was accidentally discovered by me and was tested to be feasible. Let's take it out and share it with you.

My Computer-> right-click-> Service-> find MySQL service double-click a new Window-> restore-> The first failure is set to restart the service

The following reset failure count is set to 0 restart service set to 0

In this way, it is easy to handle the problem of automatic MySQL shutdown.

Another kind of situation

100904 22:37:27 innodb:log file. Ib_logfile0 did not exist:new to be created
innodb:setting log file. Ib_logfile0 size to MB
Innodb:database physically writes the file full:wait ...
100904 22:37:28 innodb:log file. Ib_logfile1 did not exist:new to be created
innodb:setting log file. Ib_logfile1 size to MB
Innodb:database physically writes the file full:wait ...
Innodb:doublewrite Buffer not found:creating new
Innodb:doublewrite Buffer Created
Innodb:creating FOREIGN KEY constraint system tables
Innodb:foreign key constraint system tables created
100904 22:37:29 innodb:started; Log sequence number 0 0
100904 22:37:29 [ERROR] Do your already have another MYSQLD server running on port:3306?
100904 22:37:29 [ERROR] Aborting

100904 22:37:29 innodb:starting shutdown ...
100904 22:37:31 Innodb:shutdown completed; Log sequence number 0 43655
100904 22:37:31 [note] Wampmysqld:shutdown complete

100904 22:43:42 innodb:started; Log sequence number 0 43655
100904 22:43:42 [ERROR] Do your already have another MYSQLD server running on port:3306?
100904 22:43:42 [ERROR] Aborting

100904 22:43:42 innodb:starting shutdown ...
100904 22:43:45 Innodb:shutdown completed; Log sequence number 0 43655
100904 22:43:45 [note] Wampmysqld:shutdown complete

100904 22:43:49 innodb:started; Log sequence number 0 43655
100904 22:43:49 [ERROR] Do your already have another MYSQLD server running on port:3306?
100904 22:43:49 [ERROR] Aborting

100904 22:43:49 innodb:starting shutdown ...
100904 22:43:52 Innodb:shutdown completed; Log sequence number 0 43655
100904 22:43:52 [note] Wampmysqld:shutdown complete

100905 8:23:24 innodb:started; Log sequence number 0 43655
100905 8:23:24 [ERROR] Do your already have another MYSQLD server running on port:3306?
100905 8:23:24 [ERROR] Aborting

100905 8:23:24 innodb:starting shutdown ...
100905 8:23:27 Innodb:shutdown completed; Log sequence number 0 43655
100905 8:23:27 [note] Wampmysqld:shutdown complete

100905 8:23:28 innodb:started; Log sequence number 0 43655
100905 8:23:28 [ERROR] Do your already have another MYSQLD server running on port:3306?
100905 8:23:28 [ERROR] Aborting

100905 8:23:28 innodb:starting shutdown ...
100905 8:23:30 Innodb:shutdown completed; Log sequence number 0 43655
100905 8:23:30 [note] Wampmysqld:shutdown complete

100905 8:41:35 innodb:started; Log sequence number 0 43655
100905 8:41:35 [ERROR] Do your already have another MYSQLD server running on port:3306?
100905 8:41:35 [ERROR] Aborting

100905 8:41:35 innodb:starting shutdown ...
100905 8:41:37 Innodb:shutdown completed; Log sequence number 0 43655
100905 8:41:37 [note] Wampmysqld:shutdown complete

100905 8:41:42 innodb:started; Log sequence number 0 43655
100905 8:41:42 [ERROR] Do your already have another MYSQLD server running on port:3306?
100905 8:41:42 [ERROR] Aborting

100905 8:41:42 innodb:starting shutdown ...
100905 8:41:45 Innodb:shutdown completed; Log sequence number 0 43655
100905 8:41:45 [note] Wampmysqld:shutdown complete

100905 8:47:15 innodb:started; Log sequence number 0 43655
100905 8:47:15 [ERROR] Do your already have another MYSQLD server running on port:3306?
100905 8:47:15 [ERROR] Aborting

100905 8:47:15 innodb:starting shutdown ...
100905 8:47:17 Innodb:shutdown completed; Log sequence number 0 43655
100905 8:47:17 [note] Wampmysqld:shutdown complete

100905 8:54:20 innodb:started; Log sequence number 0 43655
100905 8:54:20 [ERROR] Do your already have another MYSQLD server running on port:3306?
100905 8:54:20 [ERROR] Aborting

100905 8:54:20 innodb:starting shutdown ...
100905 8:54:23 Innodb:shutdown completed; Log sequence number 0 43655
100905 8:54:23 [note] Wampmysqld:shutdown complete

100905 8:54:53 innodb:started; Log sequence number 0 43655
100905 8:54:53 [ERROR] Do your already have another MYSQLD server running on port:3306?
100905 8:54:53 [ERROR] Aborting

100905 8:54:53 innodb:starting shutdown ...
100905 8:54:55 Innodb:shutdown completed; Log sequence number 0 43655
100905 8:54:55 [note] Wampmysqld:shutdown complete

100905 8:58:20 innodb:started; Log sequence number 0 43655
100905 8:58:20 [ERROR] Do your already have another MYSQLD server running on port:3306?
100905 8:58:20 [ERROR] Aborting

100905 8:58:20 innodb:starting shutdown ...
100905 8:58:22 Innodb:shutdown completed; Log sequence number 0 43655
100905 8:58:22 [note] Wampmysqld:shutdown complete

100905 8:59:57 innodb:started; Log sequence number 0 43655
100905 8:59:57 [ERROR] Do your already have another MYSQLD server running on port:3306?
100905 8:59:57 [ERROR] Aborting

100905 8:59:57 innodb:starting shutdown ...
100905 9:00:00 Innodb:shutdown completed; Log sequence number 0 43655
100905 9:00:00 [note] Wampmysqld:shutdown complete

100905 9:02:21 innodb:started; Log sequence number 0 43655
100905 9:02:21 [ERROR] Do your already have another MYSQLD server running on port:3306?
100905 9:02:21 [ERROR] Aborting

100905 9:02:21 innodb:starting shutdown ...
100905 9:02:23 Innodb:shutdown completed; Log sequence number 0 43655
100905 9:02:23 [note] Wampmysqld:shutdown complete

100905 9:02:29 innodb:started; Log sequence number 0 43655
100905 9:02:29 [ERROR] Do your already have another MYSQLD server running on port:3306?
100905 9:02:29 [ERROR] Aborting

100905 9:02:29 innodb:starting shutdown ...
100905 9:02:31 Innodb:shutdown completed; Log sequence number 0 43655
100905 9:02:31 [note] Wampmysqld:shutdown complete

100905 9:08:16 innodb:started; Log sequence number 0 43655
100905 9:08:16 [ERROR] Do your already have another MYSQLD server running on port:3306?
100905 9:08:16 [ERROR] Aborting

100905 9:08:16 innodb:starting shutdown ...
100905 9:08:18 Innodb:shutdown completed; Log sequence number 0 43655
100905 9:08:18 [note] Wampmysqld:shutdown complete

100905 9:08:54 innodb:started; Log sequence number 0 43655
100905 9:08:54 [ERROR] Do your already have another MYSQLD server running on port:3306?
100905 9:08:54 [ERROR] Aborting

100905 9:08:54 innodb:starting shutdown ...
100905 9:08:56 Innodb:shutdown completed; Log sequence number 0 43655
100905 9:08:56 [note] Wampmysqld:shutdown complete

100905 9:35:05 innodb:started; Log sequence number 0 43655
100905 9:35:05 [ERROR] Do your already have another MYSQLD server running on port:3306?
100905 9:35:05 [ERROR] Aborting

100905 9:35:05 innodb:starting shutdown ...
100905 9:35:08 Innodb:shutdown completed; Log sequence number 0 43655
100905 9:35:08 [note] Wampmysqld:shutdown complete

100905 9:38:08 innodb:started; Log sequence number 0 43655
100905 9:38:08 [ERROR] Do your already have another MYSQLD server running on port:3306?
100905 9:38:08 [ERROR] Aborting

100905 9:38:08 innodb:starting shutdown ...
100905 9:38:10 Innodb:shutdown completed; Log sequence number 0 43655
100905 9:38:10 [note] Wampmysqld:shutdown complete

100905 16:18:51 innodb:started; Log sequence number 0 43655
100905 16:18:52 [ERROR] Do your already have another MYSQLD server running on port:3306?
100905 16:18:52 [ERROR] Aborting

100905 16:18:52 innodb:starting shutdown ...
100905 16:18:54 Innodb:shutdown completed; Log sequence number 0 43655
100905 16:18:54 [note] Wampmysqld:shutdown complete

After analysis is

3306 ports are occupied,
1. Previously installed MySQL did not uninstall clean
2. Other procedures (such as the Thunderbolt Random Access port number) occupies 3306 ports

This is good to do, as long as the MySQL configuration file to modify the port can be.