84669 person learning
152542 person learning
20005 person learning
5487 person learning
7821 person learning
359900 person learning
3350 person learning
180660 person learning
48569 person learning
18603 person learning
40936 person learning
1549 person learning
1183 person learning
32909 person learning
1. It may be that the /usr/local/mysql/data/mysql.pid file does not have write permissionSolution: Give permission and execute "chown -R mysql:mysql /var/data" "chmod -R 755 /usr/ local/mysql/data” Then restart mysqld! 2. The mysql process may already exist in the processSolution: Use the command "ps -ef|grep mysqld" to check whether there is a mysqld process. If there is, use "kill -9 process ID" to kill it, and then restart mysqld! 3. It may be the second time I installed mysql on the machine, and there is residual data that affects the startup of the service. Solution: Go to the mysql data directory/data and take a look. If mysql-bin.index exists, delete it quickly. It is the culprit. I solved it using the third method! 4. When mysql does not specify a configuration file when starting, it will use the /etc/my.cnf configuration file. Please open this file to check whether the data directory (datadir) is specified under the [mysqld] section. Solution: Please set this line under [mysqld]: datadir = /usr/local/mysql/data5. Skip-federated field problemSolution: Check if there is any in the /etc/my.cnf file If there are any skip-federated fields that are commented out, comment them out immediately. 6. The error log directory does not existSolution: Use the "chown" "chmod" command to give mysql owner and permissions7. Selinux is the cause of trouble. If it is a centos system, selinux will be turned on by defaultSolution: Close For it, open /etc/selinux/config, change SELINUX=enforcing to SELINUX=disabled, save and exit, and try restarting the machine.
Baidu has a lot of solutions...
![[Web front-end] Node.js quick start](https://img.php.cn/upload/course/000/000/067/662b5d34ba7c0227.png)
1. It may be that the /usr/local/mysql/data/mysql.pid file does not have write permission
Solution: Give permission and execute "chown -R mysql:mysql /var/data" "chmod -R 755 /usr/ local/mysql/data” Then restart mysqld!
2. The mysql process may already exist in the process
Solution: Use the command "ps -ef|grep mysqld" to check whether there is a mysqld process. If there is, use "kill -9 process ID" to kill it, and then restart mysqld!
3. It may be the second time I installed mysql on the machine, and there is residual data that affects the startup of the service.
Solution: Go to the mysql data directory/data and take a look. If mysql-bin.index exists, delete it quickly. It is the culprit. I solved it using the third method!
4. When mysql does not specify a configuration file when starting, it will use the /etc/my.cnf configuration file. Please open this file to check whether the data directory (datadir) is specified under the [mysqld] section.
Solution: Please set this line under [mysqld]: datadir = /usr/local/mysql/data
5. Skip-federated field problem
Solution: Check if there is any in the /etc/my.cnf file If there are any skip-federated fields that are commented out, comment them out immediately.
6. The error log directory does not exist
Solution: Use the "chown" "chmod" command to give mysql owner and permissions
7. Selinux is the cause of trouble. If it is a centos system, selinux will be turned on by default
Solution: Close For it, open /etc/selinux/config, change SELINUX=enforcing to SELINUX=disabled, save and exit, and try restarting the machine.
Baidu has a lot of solutions...