Skip to content

Did you know?

systemctl --failed lists every service that failed to start.

A quick health check after a reboot or an upgrade.

Explained

After a reboot or a big upgrade, one command tells you whether any systemd unit is in trouble:

systemctl --failed
  UNIT              LOAD   ACTIVE SUB    DESCRIPTION
● php8.4-fpm.service loaded failed failed The PHP 8.4 FastCGI Process Manager

1 loaded units listed.

If the list is empty, every service started. If not, look at the unit’s status and its log for the current boot:

systemctl status php8.4-fpm
journalctl -u php8.4-fpm -b --no-pager | tail -30

Fix the cause (often a configuration error the log points to), then start the service again. A unit stays listed as failed until it starts successfully or you clear the state:

sudo systemctl reset-failed

Add systemctl --failed --no-legend to monitoring scripts: it prints nothing when everything is healthy, which makes it easy to alert on any output.

Learn more

← All tech tips · Suggest a fix

Back to top