TIBCO LogLogic LMI - How to fix error "Unix socket lock file is empty /tmp/mysql.sock.lock"
Article ID: KB0072497
Updated On:
| Products | Versions |
|---|---|
| TIBCO LogLogic Enterprise Virtual Appliance | All versions |
Description
Sometimes engine_mysqld may crash or stop in a not cleanly manner. This may cause the mysql daemon to not properly clean up the connection including the socket file that is place under /tmp folder.
You may see below errors in log /var/log/sys.log file:
<27>Feb 23 09:17:41 rl-logs03 mysqld[27144]: Unix socket lock file is empty /tmp/mysql.sock.lock.
<27>Feb 23 09:17:41 rl-logs03 mysqld[27144]: Unable to setup unix socket lock file.
<27>Feb 23 09:17:41 rl-logs03 mysqld[27144]: Aborting
Environment
Linux RHEL
Resolution
The existing mysql socket file under /tmp is the root cause of this issue. The socket is locked therefore engine_mysqld wil fail to start properly. This - in turn - will cause other engines to fail to start as well. Since the purpose of this file (socket type) is to receive/record connections to the Database, Administrators can safely delete that file. Once the file is deleted engine_mysqld will create a new socket file at next 'mtask' start.
Issue/Introduction
engine_mysql may be unable to start
Feedback
Yes
No
Powered by
