Shulou(Shulou.com)06/01 Report--

The following is to understand that there is no pid error solution to start the mysql failure report. I believe everyone will benefit a lot after reading it. The text is not much in the essence. I hope there is no pid error solution to start the mysql failure report. This short article is what you want.

Symptom: the following error is prompted when service mysql start:

[root@mysqldb data] # service mysql startStarting MySQL..The server quit without updating PID file ([failure] / data/3306/mysql.pid).

Cause analysis: the mysql.pid file is created when the mysql is reactivated. If the creation fails, the error will be prompted. It is found that there are many reasons for this error.

Such as permissions, port occupied, parameter file configuration error, and so on, the details are as follows:

Solution:

There are no pid files or are not authorized in the datadir data directory of mysql

(1) be sure to authorize such as / data/mysql

Chown-R mysql:mysql / data/mysql

(2) if the authorization does not work, you can create a pid named by the host name under / data/mysql, for example, my host name is centos-6.3

You can

Cd / data/mysql & & touch centos-6.3.pid

Write a pid number that is not in the process at will.

(3) if it still doesn't work, you need to look at the configuration in the configuration file / etc/my.cnf and remove the # before port, datadir, basedir and socket.

(4) the other treatment methods may be caused by the following reasons

1 > it may be the second time to install mysql on the machine, and there is residual data that affects the startup of the service.

Solution: go to mysql's data directory / data. If mysql-bin.index exists, delete it as soon as possible. It's the culprit.

2 > mysql will use the / etc/my.cnf configuration file when it starts without specifying a configuration file. Please open this file to see if there is a specified data directory (datadir) under the [mysqld] section.

Solution: please set this line under [mysqld]: datadir = / usr/local/mysql/data

3 > skip-federated field problem

Solution: check the / etc/my.cnf file to see if there are any skip-federated fields that have not been commented out, and if so, comment them out immediately.

4 > the disaster caused by selinux. If it is a centos system, selinux will be enabled by default.

Solution: close it, open / etc/selinux/config, change SELINUX=enforcing to SELINUX=disabled, then save and exit and restart the machine.

(5) since it is started by system command, check whether the configuration items in the mysql.server configuration file are correct. If you can't judge whether the parameters are correct, you can start with Mysqld_safe.

The reference command is as follows:

[root@mysqldb 3306] # lltotal 8drwxr-xr-x 5 mysql mysql 4096 Mar 15 19:16 data-rw-r--r-- 1 mysql mysql 3676 Mar 15 18:44 my.cnf

[root@mysqldb 3306] # vi mysql.start-create

/ mysql/app/mysql/bin/mysqld_safe-defaults-file=/mysql/data/3306/my.cnf-user=mysqld

[root@mysqldb 3306] # chmod-R 777 mysql.start-Authorization

[root@mysqldb 3306] # lltotal 12drwxr-xr-x 5 mysql mysql 4096 Mar 15 19:16 data-rw-r--r-- 1 mysql mysql 3676 Mar 15 18:44 my.cnf-rwxrwxrwx 1 root root 89 Mar 15 22:36 mysql.start [root@mysqldb 3306] #. / mysql.start [root@mysqldb 3306] # 2018-03-15T14:36:52.021705Z mysqld_safe Logging to'/ mysql/log/3306/mysqldb-error.err'.2018-03-15T14:36:52. 043126Z mysqld_safe Starting mysqld daemon with databases from / mysql/data/3306/data [root@mysqldb 3306] # ps-ef | grep mysqlroot 3627 10 22:36 pts/0 00:00:00 / bin/sh / mysql/app/mysql/bin/mysqld_safe-- defaults-file=/mysql/data/3306/my.cnf-- user=mysqldmysql 4764 3627 48 22:36 pts/0 00:00:11 / mysql/app/mysql/bin/mysqld-- defaults-file=/mysql/data/ 3306/my.cnf-- basedir=/mysql/app/mysql-- datadir = / mysql/data/3306/data-- plugin-dir=/mysql/app/mysql/lib/plugin-- user=mysqld-- log-error=/mysql/log/3306/mysqldb-error.err-- open-files-limit=65536-- pid-file=/mysql/data/3306/mysql.pid-- socket=/mysql/data/3306/mysql.sock-- port=3306root 4796 2174 22:37 pts/0 00:00:00 grep mysql

(6) whether the command is correct when Mysql is closed, point 6 is not consistent with the description of this article, but this incorrect closure will also lead to this phenomenon.

After reading the article that there is no pid error resolution in starting the mysql failure report, many readers will certainly want to know more about it. For more industry information, you can follow our industry information section.

Welcome to subscribe "Shulou Technology Information " to get latest news, interesting things and hot topics in the IT industry, and controls the hottest and latest Internet news, technology news and IT industry trends.