Job for mysql.service failed because the control process exited with error code
The MySQL/MariaDB service failed to start — the real reason is in the MySQL error log.
Seen on:
MySQL
Meaning
Common causes: disk full, corrupted InnoDB files after a crash, bad my.cnf options after an edit, wrong permissions on /var/lib/mysql, or port already in use.
Common causes
- Invalid option in my.cnf
- Disk full
- Permissions on the data directory
- InnoDB corruption / redo log mismatch after upgrade
- Another process on port 3306
⚡ Quick fix
- Read the log: journalctl -u mysql and /var/log/mysql/error.log
- Revert recent config changes
- Free disk space
- Fix ownership: chown -R mysql:mysql /var/lib/mysql
Detailed fix by platform
Linux
sudo journalctl -u mysql -n 80 --no-pager && sudo tail -n 80 /var/log/mysql/error.log
How to diagnose
- Log — First [ERROR] line?
- Change — Recent config edit or upgrade?
🧠 Still stuck? Analyze your error
Paste the full message, response headers or stack trace — we'll detect the platform and point to the most likely cause.
Was this page helpful?
Report a correction or suggest an improvement
Last updated 2 Oct 2026