Symfony 2.8测试环境仅出现SQL错误：无此文件或目录

Hey there, let's dig into this head-scratcher—your Symfony test environments suddenly can't connect to MySQL, even though nothing in config/dependencies changed and they ran fine for months. Super annoying, but let's break this down step by step:

• First, rule out MySQL service issues
  Start by checking if the test MySQL instance is actually running. On most Linux systems, run:

  systemctl status mysql
  

  If it's stopped, restart it with systemctl start mysql. Then try connecting directly with the MySQL client to bypass Symfony entirely:

  mysql -u YOUR_TEST_USER -p -h YOUR_TEST_HOST YOUR_TEST_DB_NAME
  

  If this fails, the problem is with MySQL itself, not Symfony. If it works, move on to Symfony-specific checks.

• Double-check environment variables & config files
  Even if you swear you didn't touch anything, it's worth verifying your .env.test (or environment-specific config) has the correct DATABASE_URL. Look for typos in host, port, username, password, or database name. Sometimes CI/CD tools or deployment scripts can accidentally overwrite env vars—check if any recent pipeline changes might have messed this up.

• Verify MySQL user permissions
  Permissions can get borked unexpectedly (e.g., a teammate ran a cleanup script, or a MySQL update reset something). Log into your MySQL server with an admin account and run:

  SELECT user, host FROM mysql.user WHERE user='YOUR_TEST_USER';
  

  Make sure the host matches where your Symfony app is connecting from (e.g., localhost, 192.168.x.x, or % for any host). Then confirm the user has access to the test database:

  SHOW GRANTS FOR 'YOUR_TEST_USER'@'YOUR_HOST';
  

  If permissions are missing, re-add them:

  GRANT ALL PRIVILEGES ON YOUR_TEST_DB_NAME.* TO 'YOUR_TEST_USER'@'YOUR_HOST';
  FLUSH PRIVILEGES;
  

• Check network/firewall rules
  A sudden firewall rule change could block Symfony from reaching the test MySQL server. Test port connectivity with:

  nc -zv YOUR_TEST_HOST 3306
  

  (Or telnet YOUR_TEST_HOST 3306 if nc isn't installed.) If this fails, check the firewall on the MySQL server (e.g., ufw status on Ubuntu) or any network security groups if you're using cloud services. For local setups, ensure MySQL is listening on the correct interface—check my.cnf for the bind-address setting (it should be 0.0.0.0 to allow all interfaces, or your app's specific IP).

• Clear Symfony's test environment cache
  Sometimes stale cache can hold onto old connection settings, even if your config is correct. Clear the test cache with:

  php bin/console cache:clear --env=test
  

  You can also try deleting the var/cache/test directory manually to be thorough.

• Check MySQL error logs
  The MySQL error log is gold for debugging connection issues. On most systems, it's located at /var/log/mysql/error.log. Look for entries like "Access denied for user", "Connection refused", or "Max connections reached"—these will point you directly to the root cause.

• Check for max connection limits
  If your test environment has been running a lot of parallel tests lately, you might hit MySQL's max_connections limit. Check current usage with:

  SHOW GLOBAL STATUS LIKE 'Max_used_connections';
  

  Compare this to the max_connections value from SHOW VARIABLES LIKE 'max_connections';. If you're hitting the limit, you can increase it temporarily in my.cnf or adjust your test suite to use fewer parallel connections.

Start with the first step (direct MySQL client connection)—that'll quickly tell you if the problem is with MySQL or Symfony. Let me know if any of these steps uncover something, or if you have more details to share!

内容的提问来源于stack exchange，提问作者Yannick