Apache says MySQL daemon already running; if I stop the other daemon, Apache can't start its own

Question

What should happen:

./lampp start mysql -u root -p

--All is right and well with the world!--

What actually happens, and in this order:

./lampp start

mysql -u root -p

[Can't connect to local MySQL server through socket '/var/run/mysqld/mysqld.sock' (2)]

{at this point, phpmyinfo() shows mysql as activated}

sudo service mysql start

mysql -u root -p

[Can't connect to local MySQL server through socket '/var/run/mysqld/mysqld.sock' (2)]

{phpmyinfo() still shows mysql as activated}

./lampp stop

mysql -u root -p

(all is right and well with the world!)

./lampp start

Another MySQL daemon is already running...

{phpmyinfo() shows mysql as deactivated}

Basically, it seems there's some conflict going with mySQL. If I have apache running, I can't run mysql, but if I have mySQL running, I can't load it in Apache. The error remains the same. Both are trying to use the same socket, and it works if Apache isn't running. Any suggestions all would be extremely appreciated.

Answer 1

Tom,

check your my.cnf for the path to the socket file under the mysqld and client section.

[mysqld] socket=/path/to/socket [client] socket=/path/to/socket 

Edit:

If the [client] section doesn't exist then put it there so you don't have to manually specify the --socket=path when connecting from command line.