It MIGHT also be MySQL hitting max connection limit and refusing new connections.
Check the permissions on the mysqld.sock file and the path to the file, make sure whatever user you're running as can access that socket file. The my.cnf file is going to reference paths for the mysqld to create the .sock, and depending on the section you set that in, it might or might not affect clients (such as php) - most webserver configurations may require at least a reload, if not a restart to get the embedded PHP to see a my.cnf change.
Or, alternatively, use 127.0.0.1:3306 (assuming you're having MySQL listen on TCP at all).
On Wed, Mar 5, 2014 at 11:01 AM, Luis Quintana sla07@earthlink.net wrote:
I have been recently seeing this error pop up, whenever trying to login to my observium instance, and was wondering if anyone had experienced this before. This is an install I did back around October of 2013 and other then expanding the hdd, a month or so ago, I havent really messed with the settings (the first time i saw this was about a week and a half ago or so). After searching on google a little bit, it seems like the socket trying to be leveraged is at location '/var/run/mysqld/mysqld.sock' yet when i do a search for '-type s', i only see '/run/mysqld/mysqld.sock'.
The '/etc/mysql/my.cnf' file already lists "socket = /var/run/mysqld/mysqld.sock" though. Should I just modify the my.cnf file to include '/run/mysqld/mysqld.sock'?
This is the error I get:
MySQL Error: Can't connect to local MySQL server through socket '/var/run/mysqld/mysqld.sock' (111) _______________________________________________ observium mailing list observium@observium.org http://postman.memetic.org/cgi-bin/mailman/listinfo/observium