Fix Linux under MySQL boot error starting mysql.manager of Pid-file quit without updating file. [FAILED]

Just finished loading MySQL, start the Times with the following error:

Starting mysql.manager of Pid-file quit without updating file. [FAILED]

Fix Linux under MySQL boot error starting mysql.manager of Pid-file quit without updating file. [FAILED]

650) this.width=650; "src=" Https://s3.51cto.com/wyfs02/M02/92/F4/wKioL1kF7WeC0GhGAABMNSdGy9E028.png "title=" QQ picture 20170430215741.png "alt=" Wkiol1kf7wec0ghgaabmnsdgy9e028.png "/>

In order to try the various methods found from Google, found that as long as the following MySQL initialization command can be resolved:

/usr/local/mysql/bin/mysql_install_db--user=mysql

650) this.width=650; "src=" Https://s4.51cto.com/wyfs02/M02/92/F4/wKioL1kF7TThTHjYAALSxdzGV60963.png "title=" QQ picture 20170430215526.png "alt=" Wkiol1kf7tththjyaalsxdzgv60963.png "/>

The following is a collection of methods found from Google to solve this problem, perhaps the cause of each person's problems will be different, for reference:

First, check the error log

Error log is our solution to the direction of the light, without the direction of light we have no direction.

I have this error in the log of times when I install the Times:

/usr/local/mysql/bin/mysqld:error while loading shared libraries:libstdc++.so.5:cannot open Sharedobject file:no such File or directory

It is obvious that the library file libstdc++.so.5 is missing, and we search for and LIBSTDC related packages to install.

Maybe it's the selinux that's causing the disaster.

If it is a CentOS system, the default is to turn on SELinux, this time you can close it, open the/etc/selinux/config, the selinux=enforcing changed to selinux=disabled after save to restart the machine to try.

Third, residual data

Also may be the second time to install MySQL on the machine, there are residual data affect the start of the service, go to MySQL data directory/data See, if there is mysql-bin.index, quickly delete it, it is the culprit.

Iv. Determining the permissions of the data Catalog

Data Catalog is generally <prefix>/data, check its attribution, if it is not the MySQL owner, the general installation of MySQL will create MySQL users and groups, this time to modify the users and groups:

Chown-r Mysql:mysql/var/data

Five. No data directory specified

MySQL will use the/ETC/MY.CNF configuration file when it is not specified at startup, please open this file to see if there is a specified data directory (DATADIR) under the [Mysqld] section. If not, set this line under [mysqld]:

DataDir =/usr/local/mysql/data

Six, and the MySQL process is running.

If this is the second time that you install MySQL on a machine, there is a high likelihood that the MySQL process will be running on the system. You can perform the following commands to view:

Ps-ef | grep MySQL

If there is more than one line of results, kill it quickly.

Seven, the Skip-federated field in the Mischief

You can check if there are any skip-federated fields in the/etc/my.cnf file that are not commented out, and if so, comment them out immediately.

Viii. error log directory does not exist

It's also possible that you don't yet know where MySQL's error logs are, right? You can then execute the command to view:

CD Mysql/bin./mysql_safe

At this point will be error, and the error in the display will be written in such a directory of such a file, here to check if this directory and file is in, in the words to be resolved by the log instructions, if not, you will create a directory and modify permissions and attribution. Generally it will be/var/lib/mysql/mysql.error, note that Mysql.error does not have to be created.

Cd/var/libmkdir mysqlchmod 777 Mysqlchown mysql:mysql MySQL

Then try it again. If still can't, leave a message let everybody help you look ...

Nine, may be data/mysql-bin.index in mischief

Before: Because the hard drive is full, MySQL can't start up. Log in to see a bit and find out why. Delete MySQL log file, restart MySQL discovery error: Starting mysql.manager of Pid-file quit without updating file. [FAILED]

There are many explanations for this reason on the Internet, but they are not what I want to say. The reason I want to say is actually very stupid: Data/mysql-bin.index did not delete, Data/mysql-bin.index is the log file index file, only delete the log file and not the log index file processing is obviously not working.

Delete the Data/mysql-bin.index file, and then service mysqld start will do.

This article from "Nicol Lock Silk Sorrow" blog, please make sure to keep this source http://smoke520.blog.51cto.com/9256117/1920892

Fix Linux under MySQL boot error starting mysql.manager of Pid-file quit without updating file. [FAILED]