I cannot say if it ever worked I have inherited the sorting out of our servers at the radio station due to it being run by volunteers and as in all volunteer organisations people come and go I did do some research on the internet and tried various commands in the terminal but kept on getting MySQL does not exist yet when I tried the locate MySQL I did get an output with various directories and sub directories I did come across the getenforce command and when I typed it the output came back with disabled

Date: Thu, 21 May 2015 17:07:29 -0400 From: m.roth@5-cent.us To: centos@centos.org Subject: Re: [CentOS] Centos 6.6 Can't connect to local MySQL server through socket /var/lib/MySQL/MySQL.sock (error 2002)‏

Graham Wilman wrote:

...

Hi

Total newby to centos I am currently assisting a community radio station set up in the Uk we are using a server based system for our playout software, unfortunately at the moment one of our client servers is experience the above error I came across the error on our main server a few weeks ago and found the solution just by reinstalling the MySQL db but I have tried to deploy the same fix on our client server otherwise known as studio-b client but unfortunately this has not solved the problem any assistance with this would be very much appreciated.

First question - did it ever work? If not, is selinux enforcing?

   mark "getenforce"

---

CentOS mailing list CentOS@centos.org http://lists.centos.org/mailman/listinfo/centos

On Thu, 2015-05-21 at 22:45 +0100, Graham Wilman wrote:

I cannot say if it ever worked I have inherited the sorting out of our servers at the radio station due to it being run by volunteers and as in all volunteer organisations people come and go I did do some research on the internet and tried various commands in the terminal but kept on getting MySQL does not exist yet when I tried the locate MySQL I did get an output with various directories and sub directories I did come across the getenforce command and when I typed it the output came back with disabled

<snip>

Regarding "locate", try running updatedb. It may be that after your predecessor got MySql set up updated was not run. That is what loads the strings into the DB for locate. The try locate again.

HTH, Bill

------------ Original Message ------------

Date: Friday, May 22, 2015 12:24:38 PM +0200 From: Leon Fauster leonfauster@googlemail.com

Am 21.05.2015 um 22:43 schrieb Graham Wilman gwillman@hotmail.co.uk:

...

Total newby to centos I am currently assisting a community radio station set up in the Uk we are using a server based system for our playout software, unfortunately at the moment one of our client servers is experience the above error I came across the error on our main server a few weeks ago and found the solution just by reinstalling the MySQL db but I have tried to deploy the same fix on our client server otherwise known as studio-b client but unfortunately this has not solved the problem any assistance with this would be very much appreciated.

# grep sock /etc/my.cnf socket=/var/lib/mysql/mysql.sock

-- LF

Check that mysqld is running. Assuming it is, confirm the location (including directory/file capitalization) of the socket file -- the default is as indicated above. If that's all there, then the issue is that your client is trying to find the socket file in a non-standard location of /var/lib/MySQL/MySQL.sock. I suspect that there is a client configuration file that controls this which can be adjusted.

[you can change where mysqld writes its socket file, but that could break other applications that use the default location, so I don't recommend that approach.]