Go Mysql:starting MySQL ..... error! The server quit without updating PID file

Transferred from: http://icesquare.com/wordpress/mysql-starting-mysql-error-the-server-quit-without-updating-pid-file/

He is also updating the system after the problem, I was the update after the problem, so according to his ideas to delete the configuration file can be started, as to why this problem occurs, back to time to carefully study.

This step-by-step-mainly for FreeBSD, however-the idea was the same for Linux. Every once a while, when I update my FreeBSD box, the system likes to shutdown my MySQL server. Therefore, I need to start it again after the update was done. Unfortunately, the upgrade process is not smooth every time. Sometimes it would throw me some error.

Oh Well, I got the following error messages:

Sometimes, the message would tell you the exact location of which PID file:

There is several solutions to troubleshoot these problems. I'll go through each of the one by one.

Solution 1:reboot the computer

Although it sounds simple, but it really works. During The system upgrade, the OS may disable some of your daemons. Instead of troubleshooting each one by one, the easiest-on-is-to-start everything over. For example, I experienced this problem today after upgrading theApache and Ruby (Yes, MySQL was not part of the U pdate), and I got this error message afterward. After rebooting the computer, the error message is gone.

Solution 2:remove Your MySQL Config File

If you had modified your MySQL configuration file, MySQL may not be like it few versions after (MySQL isn't backward compat Ibility friendly). It can be the problem of using a unsupported variable, or something similar. The easiest-is-to-remove your configuration file, and try to start the MySQL server again:

Backup your MySQL configuration first.

and restart the MySQL server again:

Hopefully you'll see the following message:

Solution 3:upgrade Your Database File

Sometimes, the newer MySQL doesn ' t like the database created in earlier version. I discovered this if I upgrade to MySQL 5.5.7:

Since MySQL tells me which PID file causes the problem, I open the file and take a look at what's going on:

And I saw something interesting: tables:table ' mysql.proxies_priv ' doesn ' t exist:

101112 10:49:16  innodb:initializing buffer pool, size = 128.0M 101112 10:49:16 innodb:completed  initialization o F Buffer pool 101112 10:49:16  innodb:highest supported file format is Barracuda. 101112 10:49:17  

The reason is very simple. MySQL could not open a table created in the earlier version (< 5.7.7) because it isn't compatible with the current ver Sion. So, we can try-to-start the MySQL in Safe mode through RC.D. First, you can edit the /etc/rc.conf and put the following into the file:

Restart MySQL through RC.D:

If You do it right, you should see something like the following:

Now, MySQL is already running the Safe-mode. We want to perform a MySQL upgrade on all tables:

You should see something like this:

Looking for ' MySQL ' as:mysql looking for ' mysqlcheck ' As:mysqlcheck Running ' mysqlcheck ' with connection arguments: '--p ort=3306 '--socket=/tmp/mysql.sock ' Running ' mysqlcheck ' with connection arguments: '--port=3306 '--socket=/tmp/ Mysql.sock ' Mysql.columns_priv ok mysql.db ok my Sql.event OK mysql.func OK mysql.general_lo                                 G OK mysql.help_category OK mysql.help_keyword                                   Ok mysql.help_relation OK mysql.help_topic Ok mysql.host ok mysql.ndb_binlog_index ok mysq                                  L.plugin OK mysql.proc OK mysql.procs_priv Ok mysql.servers ok mysql.slow_log ok mysql.tabl Es_priv OK mysql.time_zone OK mysql.time_zone_leap_sec                         Ond ok mysql.time_zone_name ok mysql.time_zone_transition Ok mysql.time_zone_transition_type OK mysql.user O K Running ' mysql_fix_privilege_tables ' ...  Ok

Now, we want-to-switch the MySQL back-to-normal mode by commenting the extra options in/etc/rc.conf:

and restart MySQL THROUGH/ETC/RC.D:

Now the MySQL was up and running again!

Happy mysqling.

–derrick

Go Mysql:starting MySQL ..... error! The server quit without updating PID file