Data_Engine will not connect with MySQL server default mysql.sock location, it looks for mysql.sock in /tmp

book

Article ID: 34993

calendar_today

Updated On:

Products

DX Infrastructure Management NIMSOFT PROBES

Issue/Introduction

Symptoms


Data_Engine 8.00 Will not connect with MySQL server default mysql.sock location, it looks for mysql.sock in /tmp

Example data_engine errors:
Nov 20 10:38:56:075 [140499484841728] de: data_engine [main] [main] - Execute - Error: [main] thread_id: 0, error: Execute: Can't connect to local MySQL server through socket '/tmp/mysql.sock' (2) (errno:2002)
Nov 20 10:38:56:075 [140499484841728] de: VerifySettings - error: [[main] thread_id: 0, error: Execute: Can't connect to local MySQL server through socket '/tmp/mysql.sock' (2) (errno:2002)] sp: [ spn_bas_VerifyFeature





Solution


This is resolved by reconfiguring the mysql server to use /tmp/mysql.sock socket location - making a soft link to /tmp/MySQL.sock.

The default location for the Unix socket file that the server uses for communication with local clients is /tmp/mysql.sock. (For some distribution formats, the directory might be different, such as /var/lib/mysql for RPMs.)

On some versions of Unix, anyone can delete files in the /tmp directory or other similar directories used for temporary files. If the socket file is located in such a directory on your system, this might cause problems.

On most versions of Unix, you can protect your /tmp directory so that files can be deleted only by their owners or the superuser (root). To do this, set the sticky bit on the /tmp directory by logging in as root and using the following command:
shell> chmod +t /tmp

Environment

Release:
Component: UIMDEG