Pointing Longview to Correct MySQL sock location
I get the following error:
Unable to connect to the database: Can't connect to local MySQL server through socket '/var/run/mysqld/mysqld.sock' (2)
That is the default location for mysqld.sock for my installation.
In my.cnf, I've changed that to /tmp/mysql.sock
So, the problem is that I have mysql running with /tmp/mysql.sock whereas Longview seems to think it should be at /var/run/mysqld/mysqld.sock
Where is Longview getting that location?
Thanks.
4 Replies
Mine died today, victim of oom killer, and your error message is exactly what I saw when trying to use mysql command line client.
BTW: You should not really need to change location of lock file. The default value should work.
@sanvila:
Is the MySQL daemon running at all? (Try "service mysql restart")
Mine died today, victim of oom killer, and your error message is exactly what I saw when trying to use mysql command line client.
BTW: You should not really need to change location of lock file. The default value should work.
A sincere thank you for trying. I appreciate it.
Since a bunch of other services I have rely on it being set to /tmp/mysql.sock (yes yes, I could change them but this is almost now a matter of principle) I prefer to have it set to that.
Yes, mysql is running. It's serving my sites and services well. Alive and kicking with some 40 queries per second so mysql in itself is not the problem.
Perhaps I need to add a new [longview] section in my.cnf with the socket path set (already tried that very thing and no go).
Any other ideas? Thanks.
