Can't start MySQL CentOS

Phenomenon :
[root@localhost ~]# service mysqld start
Another MySQL daemon already running with the same unix socket.
Starting mysqld: [failure]

But:
[root@localhost ~]# /etc/init.d/mysqld status
Mysqld has stopped

Clearly MySQL has stopped, starting when they reported the existing MySQL site to start, this is how to return a responsibility? For God to help us, thank you!

Started by Vicky at February 10, 2016 - 10:05 PM

ps -ef | Grep MySQL have a look whether there is a MySQL process

Posted by Curitis at February 14, 2016 - 10:09 PM

Looking for a foreign forum to try the next

[root@localhost mysql]# mv /var/lib/mysql/mysql.sock /var/lib/mysql/mysql.sock.bak

Then you can start.
[root@localhost mysql]# service mysqld start
Starting mysqld: [OK]

But do not know why this is, you know?

Posted by Vicky at March 01, 2016 - 10:42 PM

A process, but when kill -9 process, the results are as follows:

[root@localhost ~]# ps -ef | grep mysql
root 12988 2465 0 21:49 pts/0 00:00:00 grep mysql
[root@localhost ~]# kill -9 12988
-bash: kill: (12988) Without the process

Posted by Vicky at March 10, 2016 - 10:55 PM

You are mistaken. This process is a grep process, has pulled out of.
You should check is the PS -ef | grep mysqld
It seems there is no MySQL related processes..

Posted by Antoine at March 25, 2016 - 11:07 PM

Try service MySQL restart
Non mysqld

Posted by Joan at December 26, 2016 - 7:07 PM

The service script you have a problem?

Posted by Boyce at December 28, 2016 - 7:11 PM

[root@localhost mysql]# mv /var/lib/mysql/mysql.sock /var/lib/mysql/mysql.sock.bak

The implementation of the above command can, mysql.sock problem

Posted by Vicky at January 02, 2017 - 8:57 PM

If MySQL does not start, there was no mysql.sock this file, where the problem of?

Posted by Boyce at January 02, 2017 - 9:05 PM

Should be like this: MySQL did not stop, restart the machine after mysql.sock has always existed, but the machine after the restart MySQL actually to start, so it need to give the mysql.sock's name, then you can start.

Posted by Vicky at January 02, 2017 - 9:57 PM

Should be like this: MySQL did not stop, restart the machine after mysql.sock has always existed, but the machine after the restart MySQL actually did not start, so need to give the mysql.sock's name, then you can start.

Posted by Vicky at January 04, 2017 - 8:08 PM