How to Fix MySQL Error #2002: Connecting to Local Server through Socket?

Resolving MySQL Error #2002: Connecting to Local Server through Socket

MySQL users often encounter Error #2002, indicating an inability to connect to the local MySQL server through the socket. This issue typically affects users running MAMP or similar platforms.

When investigating the error, users may find that the expected mysql.sock file in the /Applications/MAMP/tmp/mysql directory is missing. This can lead to confusion and the search for potential solutions.

One possible solution is to manually test MySQL by starting it with the full path:

/Applications/MAMP/Library/bin/mysql -u root -p

If this command succeeds, it suggests that MySQL can be accessed correctly using the full path. To fix the issue permanently, create a symbolic link from /tmp/mysql.sock to the actual socket location:

sudo ln -s /Applications/MAMP/tmp/mysql/mysql.sock /tmp/mysql.sock

Once this is done, MySQL should start normally using the usual command:

mysql -u root -p

If the above method fails, an alternative approach is to dynamically find the MySQL path:

$($(for dir in /usr/local/mysql/bin /usr/bin /usr/local/bin /Applications/MAMP/Library/bin /Applications/XAMPP/xamppfiles/bin; do [ -x "$dir/mysql" ] && echo "$dir/mysql" && break; done) -u root -p)

Executing this command should start MySQL without encountering the Error #2002. These steps should resolve the connectivity issue and allow users to access MySQL seamlessly through the socket.

The above is the detailed content of How to Fix MySQL Error #2002: Connecting to Local Server through Socket?. For more information, please follow other related articles on the PHP Chinese website!