Can't connect to local MySQL server through socket '/tmp/mysql.sock' (2)

Troubleshooting basic server issues

Ensuring that MySQL server is running

Let's not assume. Issues could be as simple as the MySQL server not running:

sudo systemctl status mysql
# or, if you're using init.d scripts
sudo service mysql status
# Replies with a 'zzz', anybody need coffee?


Verifying socket availability

The /tmp/mysql.sock file should physically exist. If it doesn't, we need to find it or consider creating it:

# Search like a detective for the socket file
find / -type s -name "mysql.sock" 2>/dev/null
# If not found, create a symbolic link, like a road sign for MySQL
ln -s /actual/path/to/mysql.sock /tmp/mysql.sock


Permanent symbolic links

To persist symbolic links, consider these options:

• Edit .profile: Add symbolic link creation command.
• Create alias: Add an alias to your shell profile, like .bashrc or .zshrc: alias fixmysql='ln -s /actual/mysql.sock /tmp/mysql.sock'.

Dealing with non-standard issues

Adjust client configuration

my.cnf or .cnf might harbor the wrong client settings. Ensure they're in sync with the server:

[client]
socket=/correct/path/to/mysql.sock
# "The socket is a lie" - Portal fans, anyone?


Socket-less connection

TCP/IP can be your friend if the socket file is acting up:

mysql -u yourusername -p -h 127.0.0.1
# No socket, no problem! 🎉


Try MAMP

Mac users, MAMP could spare you the headache by providing a MySQL-friendly environment.

Maintain connections and configurations

Modifying server path

Change socket path if MySQL uses an unusual one:

[mysqld]
socket=/your/path/to/mysql.sock


Symbolic links and system startup

Ensure links persist across reboots via cron or systemd. Also, ensure MySQL is part of the startup services.

Confirm consistent access

Last but not least, check MySQL’s status in System Preferences or Services, and verify your access by confirming a password prompt when connecting to MySQL.