Resolving MySQL Connection Error: Can't Connect to Local MySQL Server Through Socket

Error Analysis and Diagnosis

After installing MySQL on macOS using Homebrew, executing the mysql -u root command may result in ERROR 2002 (HY000), indicating an inability to connect to the local MySQL server through the socket /tmp/mysql.sock. The core reason for this error is that the MySQL server process (mysqld) is not running. The socket file serves as a communication bridge between the MySQL client and server; if the server is not started, this file does not exist, leading to connection failure.

Solution 1: Start the MySQL Service

The most direct solution is to start the MySQL service. Homebrew provides convenient service management commands:

brew services start mysql

After executing this command, Homebrew will start the MySQL daemon and ensure it runs automatically after system reboots. Once started successfully, attempt to connect again:

mysql -uroot

If the connection is successful, the issue is resolved. Additionally, for enhanced security, it is recommended to run mysql_secure_installation to set the root password and other security options.

Solution 2: Verify Process Status

If the problem persists after starting the service, verify whether the MySQL process is running using Activity Monitor. Open Activity Monitor, search for "mysqld" under "All Processes." If the process is not found, the service may have failed to start, requiring further investigation.

Solution 3: Fix Permission Issues

In some cases, permission issues may prevent MySQL from starting. For example, incorrect permissions on the data directory can block the mysqld process from accessing necessary files. Try the following commands to fix permissions:

sudo chown -R _mysql:mysql /usr/local/var/mysql
sudo mysql.server start

The first command sets ownership of the data directory to the MySQL user and group, while the second manually starts the MySQL service. If the permission issue is resolved, the connection should return to normal.

Solution 4: Reinstall MySQL

If the above methods are ineffective, there may be issues from the installation process. Reinstalling MySQL is recommended to ensure file integrity and correct configuration:

brew remove mysql
brew install mysql

After reinstalling, be sure to initialize the database as per Homebrew's instructions. Run brew info mysql for detailed guidance and execute commands similar to the following:

unset TMPDIR
mysql_install_db --verbose --user=`whoami` --basedir="$(brew --prefix mysql)" --datadir=/usr/local/var/mysql --tmpdir=/tmp

This ensures the correct creation of database tables, preventing startup failures due to missing system tables.

Additional Notes and Best Practices

The ERROR 2002 is not limited to macOS; it can occur on other Unix-like systems such as Linux, but the root cause is similar—MySQL service not running or incorrect socket file path. For instance, on Ubuntu systems, the default socket path might be /var/run/mysqld/mysqld.sock, and if permissions are misconfigured, a "Permission denied" error may arise. In such cases, check the permissions and ownership of the socket file to ensure the MySQL user has access rights.

To prevent such issues, it is advisable to start the MySQL service immediately after installation and configure it to start on boot. Use brew services list to check the status of managed services and ensure MySQL is running. Additionally, regularly update Homebrew and MySQL versions to benefit from the latest fixes and improvements.

Conclusion

ERROR 2002 (HY000) typically stems from the MySQL service not being started. By starting the service, verifying processes, fixing permissions, or reinstalling, this issue can be effectively resolved. Understanding the underlying mechanism—socket communication depends on service operation—facilitates quick diagnosis and repair, enhancing development efficiency.