MySQL服务启动失败求助：Bugzilla服务器无法访问

Hey there, let's work through this MySQL issue together. Since you've already confirmed sufficient disk space and added swap for InnoDB, let's focus on the next most likely causes for that systemd startup error.

1. Grab Detailed MySQL Error Logs #

The journalctl -xe output is useful, but MySQL's native error logs will give you way more specific details about what's blocking startup. Depending on your Linux distribution, you'll find this log at one of these paths:

• /var/log/mysql/error.log
• /var/lib/mysql/$(hostname).err

Run this command to pull the latest 50 lines:

tail -n 50 /var/log/mysql/error.log

Keep an eye out for keywords like InnoDB corruption, permission denied, stale lock file, or invalid configuration—these are the most common culprits here.

2. Fix MySQL Data Directory Permissions #

Accidental permission changes (like running a MySQL command with sudo) can mess up ownership of the data directory, preventing the service from accessing files. Check and correct permissions with these commands:

# Verify current ownership
ls -ld /var/lib/mysql
ls -l /var/lib/mysql | head -10

# Set correct ownership (mysql user/group should own everything here)
chown -R mysql:mysql /var/lib/mysql
chmod 750 /var/lib/mysql

3. Clear Stale PID Lock Files #

If MySQL crashed unexpectedly, it might leave a stale PID file that blocks startup. Look for it at:

• /var/run/mysqld/mysqld.pid

Delete it and try starting the service again:

rm -f /var/run/mysqld/mysqld.pid
systemctl start mysql

4. Validate MySQL Configuration Syntax #

A tiny typo or invalid setting in my.cnf (or my.ini) can break startup. Run this command to check for configuration errors:

mysqld --validate-config

Pay extra attention to InnoDB-related settings since you adjusted swap for it—misconfigured values like innodb_buffer_pool_size or innodb_log_file_size often cause startup failures.

5. Try InnoDB Force Recovery #

If InnoDB hit corruption during the crash, you might need to force it to recover. Edit your my.cnf file, find the [mysqld] section, and add:

innodb_force_recovery = 1

Start with level 1 (the least intrusive option) and only increment to higher levels (up to 6) if level 1 doesn't work. Once MySQL starts successfully, immediately back up all your data—this setting is not safe for long-term production use.

If you can share the actual last 30 lines of journalctl -xe or the MySQL error log, we can pinpoint the exact issue much faster.

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