Systemd Troubleshooting: 15 Commands Every Linux Admin Should Know

When services fail, speed matters. Use a repeatable sequence: status, logs, dependencies, restart behavior, unit config.

15 key commands

• systemctl status <service>
• journalctl -u <service> -n 100 --no-pager
• journalctl -u <service> -f
• systemctl cat <service>
• systemctl show <service> -p ExecStart -p Environment -p FragmentPath
• systemctl list-dependencies <service>
• systemctl is-enabled <service>
• systemctl is-active <service>
• systemctl reset-failed <service>
• systemctl restart <service>
• systemctl daemon-reload
• systemd-analyze blame
• systemd-analyze critical-chain
• journalctl -p err -b
• systemctl edit <service>

Common failure patterns

Restart loops, permission/env-file issues, bad ordering/dependency declarations, and stale overrides.

Incident notes template

Document symptom, start time, impacted services, root cause, fix, and prevention action.

Final takeaway

Systemd troubleshooting becomes predictable when you always run the same triage workflow.