My Oracle Support Banner

MySQL Server Does Not Start: "Could not create unix socket lock file" Or "Can't start server : Bind on unix socket" (Doc ID 2093350.1)

Last updated on MARCH 08, 2017

Applies to:

MySQL Server - Version 5.6 and later
Information in this document applies to any platform.

Symptoms

When attempting to start MySQL, the following - or similar - error is reported in the error log:

2016-01-05T22:53:31.085694Z 0 [ERROR] Could not create unix socket lock file /var/lib/mysql/mysql.sock.lock.
2016-01-05T22:53:31.085729Z 0 [ERROR] Unable to setup unix socket lock file.
2016-01-05T22:53:31.085735Z 0 [ERROR] Aborting

 or

2016-01-06 09:55:43 28812 [ERROR] Can't start server : Bind on unix socket: No such file or directory
2016-01-06 09:55:43 28812 [ERROR] Do you already have another mysqld server running on socket: /var/lib/mysql/data/mysql.sock ?
2016-01-06 09:55:43 28812 [ERROR] Aborting

 or

2016-01-06 09:57:39 30061 [ERROR] Can't start server : Bind on unix socket: Permission denied
2016-01-06 09:57:39 30061 [ERROR] Do you already have another mysqld server running on socket: /var/lib/mysql/data/mysql.sock ?
2016-01-06 09:57:39 30061 [ERROR] Aborting

 

Changes

The issue may start after one or more of the following changes being made:

Cause

To view full details, sign in with your My Oracle Support account.

Don't have a My Oracle Support account? Click to get started!


In this Document
Symptoms
Changes
Cause
Solution
References


This document is being delivered to you via Oracle Support's Rapid Visibility (RaV) process and therefore has not been subject to an independent technical review.
My Oracle Support provides customers with access to over a million knowledge articles and a vibrant support community of peers and Oracle experts.