执行MySQL命令时遇未知变量错误，配置文件及进程查询异常

Let's work through fixing this issue step by step—you already made a smart first move checking the process list, so let's build on that:

1. Confirm Which Config Files MySQL Actually Uses #

First, make sure you're troubleshooting the right configuration files. Run this command to see the exact order and paths MySQL reads configs from:

mysql --help | grep "Default options"

You'll get output like this:

Default options are read from the following files in the given order:
/etc/my.cnf /etc/mysql/my.cnf ~/.my.cnf

If the files you checked (like 50-server.cnf or mysql.cnf) aren't listed here, MySQL might not even be loading them—this is a common pitfall with distro-specific setups (like Debian/Ubuntu's conf.d subdirectories).

2. Fix the bind-address Variable Error #

The "unknown variable" message almost always stems from two issues:

• Wrong section placement: bind-address is a [mysqld]-only setting. If you put it under [mysql], [client], or any other section, MySQL will throw this error. Open your config file and ensure it's formatted like this:

  [mysqld]
  bind-address = your_target_ip
  # Other mysqld-specific settings go here
  

• Typos or invalid values: Double-check for typos (e.g., bindaddress instead of bind-address) or invalid IPs. To listen on all network interfaces, use 0.0.0.0 (IPv4) or :: (IPv6 for MySQL 8.0+).

3. Repair Corrupted Configuration Files #

If your config files (my.cnf, 50-server.cnf, etc.) have abnormal content:

1. Backup first: Always save a copy of the corrupted files before making changes:

   sudo cp /etc/mysql/my.cnf /etc/mysql/my.cnf.bak
   sudo cp /etc/mysql/mysql.conf.d/50-server.cnf /etc/mysql/mysql.conf.d/50-server.cnf.bak
   

2. Restore default configs:
   • For Debian/Ubuntu systems, reconfigure the MySQL package to generate fresh default settings:

     sudo dpkg-reconfigure mysql-server-$(mysql --version | awk '{print $5}' | cut -d. -f1,2)
     

   • For RHEL/CentOS/Rocky Linux, reinstall the server package (make sure you've backed up your databases first!):

     sudo yum reinstall mysql-server
     

3. Manual repair: If you need to keep custom settings, cross-reference your corrupted file with the default config template for your MySQL version to fix missing or malformed lines.

4. Dig Into Process & Log Details #

You ran ps -aux | grep mysql—now use that output to debug further:

• Look for a mysqld process with a --defaults-file flag—this tells you exactly which config file the running instance is using.
• If MySQL won't start, check the error logs for granular details:

  # Debian/Ubuntu
  sudo tail -n 50 /var/log/mysql/error.log
  # RHEL/CentOS
  sudo tail -n 50 /var/log/mysqld.log
  # Systemd-based systems (all distros)
  sudo journalctl -u mysql -n 50
  

These logs will often point directly to the line in your config causing the problem.

5. Verify Config File Permissions #

MySQL can fail to read config files if permissions are incorrect. Set the proper permissions with:

sudo chmod 644 /etc/mysql/my.cnf /etc/mysql/mysql.conf.d/*.cnf
sudo chown root:root /etc/mysql/my.cnf /etc/mysql/mysql.conf.d/*.cnf

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