Why does the mysqld.service have status 217 fail?

The mysqld.service failing with status code 217 typically indicates a problem with how the service is configured within the systemd environment. This error usually points to a failure during the service's initialization phase, before MySQL can even begin to start up properly. Here's a breakdown of common causes:

1. Incorrect User or Group Configuration:

- The most frequent cause is an issue with the user and group the mysqld process attempts to run under. If the specified user or group in the service file (usually /etc/systemd/system/mysqld.service or similar) doesn't exist, or doesn't have the necessary permissions, the service will fail. Verify the User and Group directives in the service file. For example:

User=mysql
Group=mysql

- Ensure the user 'mysql' and group 'mysql' (or whatever is specified in your configuration) exists on your system.

2. Incorrect Path to MySQL Executable:

- The ExecStart directive points to the MySQL server executable. An incorrect path can cause a status 217 failure. Double-check the path specified. For example:

ExecStart=/usr/sbin/mysqld --daemonize --pid-file=/var/run/mysqld/mysqld.pid

- Verify the file actually exists at that location.

3. Environment Variables or Configuration File Issues:

- The service might be expecting certain environment variables or configuration files to be present. Check the Environment directives in the service file and confirm they are correctly set. If the mysqld process cannot find its configuration file (usually my.cnf), it may fail early in startup.

4. Incorrect Working Directory:

- The WorkingDirectory directive specifies the directory where the process is started. If this is set to an invalid directory, a status 217 error could occur.

5. Permission Issues on Configuration Files or Directories:

- MySQL needs permission to read configuration files and write to data directories. Verify that the user under which MySQL runs has the correct permissions on all needed directories and files.

6. Systemd Syntax or Directive Errors:

- A misconfiguration in the systemd service file, for instance, a syntax error or incorrect directives, can result in failure. Always validate your service file syntax.

Troubleshooting Steps:

1. Inspect the Systemd Service File: Use sudo systemctl cat mysqld.service to view the full contents of the service file.

2. Check the system journal: Use sudo journalctl -u mysqld.service to see detailed error messages.

3. Verify user and group: Ensure the user and group specified in the service file exist with the command id mysql.

4. Verify file paths: Double-check paths specified for ExecStart, WorkingDirectory, and configuration files.

5. Permissions: Use the ls -l command to verify directory and file permissions.

6. Restart Daemon: After making changes to the service file, use sudo systemctl daemon-reload and restart sudo systemctl restart mysqld.service.

By checking these aspects carefully, you can usually identify the root cause behind the mysqld.service status 217 failure.

Learn more about this