Common Causes and Troubleshooting of MySQL Startup Failures

MySQL may fail to start due to two main categories: inability to access required system resources and incorrect configuration parameters.

1. Unable to access system resources

When the mysqld process runs under the mysql user, it may lack permission to files, directories, ports, or be blocked by SELinux/AppArmor policies. Checking permissions with commands such as sudo -u mysql touch /var/lib/mysql/b can reveal issues. If permissions are correct but access is still denied, the security policy may need to be adjusted or temporarily disabled.

Resource conflicts can also occur if another mysqld instance holds the data files, for example: mysqld --no-defaults --console --user mysql which shows errors like “Unable to lock ./ibdata1 error: 11”.

2. Parameter configuration errors

Incorrect options in MySQL configuration files often prevent startup. The order in which MySQL reads option files can be inspected with:

$ mysqld --verbose --help | grep "Default options " -A 1

To view the exact arguments that will be used, run: $ mysqld --print-defaults A typical debugging workflow adds parameters step‑by‑step, for example:

mysqld --no-defaults --console --log-error-verbosity=3 --user mysql --gtid_mode=on

This reveals that GTID_MODE=ON requires ENFORCE_GTID_CONSISTENCY=ON, and the server aborts if the dependency is missing.

By adjusting file permissions, SELinux/AppArmor policies, and correcting configuration options, most MySQL startup failures can be resolved.