Fix MySQL Server Issue: “Another MySQL daemon already running with the same unix socket.”

Fix MySQL Server Issue: “Another MySQL daemon already running with the same unix socket.” featured image
(Last Updated On: December 13, 2017)

Just the code you need for responding to this error.

The following message can sometime prevent MySQL from (re)starting:

Another MySQL daemon already running with the same unix socket.

Sometimes, this message displays when you KNOW there is not another MySQL daemon running on the same unix socket, because you just issued a “stop” command or performed a graceful reboot, or you just checked running services and there simply isn’t a MySQL daemon running (a clue is that MySQL went away or is otherwise not working!).

When you receive this error message in your terminal window, on CentOS servers, running the following command may well clear up these problems:

mv /var/lib/mysql/mysql.sock /var/lib/mysql/mysql.sock.bak
service mysqld start

The first line of code moves the mysql.sock file to a backup location, while the second instructs mysqld (the MySQL daemon) to start. This should get things back up and running…

Now to discover why things broke in the first place!

Leave a comment below if the above helped (or didn’t help) you to get a MySQL issue resolved.

1 thought on “Fix MySQL Server Issue: “Another MySQL daemon already running with the same unix socket.”

Leave a Reply

Your email address will not be published. Required fields are marked *

Silicon Dales