Practical tools for system, network, security, and operations administrators.

SYS-C0026 · systemd & Services

Troubleshooting Failed Services

Read one failed unit, and do not restart it in a loop. Troubleshooting Failed Services.

Updated 25 October 2026 · Troubleshooting

This is an original planning guide. It is not a vendor manual, an official standard, or legal advice. Example addresses use documentation ranges. Review every command before you paste it.

What this hour is for

A failed service has a status and a journal. systemctl status names the unit. journalctl -u shows the lines. The journalctl builder drafts the filter. The restart-policy planner drafts a Restart= line. Neither tool connects to a host.

Write the unit name and the first error sentence. If you restart before you have that sentence, you will restart again. Do not set Restart=always to hide the error. Do not mask the unit to make the noise stop.

Do not disable a firewall or a confinement profile because the program would not start. That is a different fault. One unit, on a host you administer.

The change you can finish

Apply nothing while you are writing the note. When the lab window opens, it is one change on the host named in the ticket. Read the draft, then the host, then decide.

Rollback is the file, the package version, or the snapshot you saved first. You do not invent a rollback after the only copy is gone.

  1. Write the unit and the hostname.
  2. Draft the journalctl filter and read the real journal later, not during this writing.
  3. Copy the first error sentence into the ticket.
  4. Do not restart in a loop.
  5. Leave Restart= as a draft.
  6. Stop after one unit.

Mistakes that outlive the command

Troubleshooting Failed Services goes wrong in a small set of ways. The list is here so the ticket can forbid them before the window.

Decisions to write down

One decision for Troubleshooting Failed Services: One unit. The error sentence is written. No restart loop. No security control was disabled. And restart policy is a draft only.

Checks before you call it done

Confirm this before you call the change done: The unit name is written. One journal line is in the ticket, or the note says the journal was not opened yet. No mask was applied. No confinement tool was disabled. And the next change has its own page. If one of those fails, stop.

# One unit.
# Read the journal before a restart.
# Do not mask the unit.

Before you leave the host

Troubleshooting Failed Services ends when the hostname in the prompt matches the hostname in the ticket. If it does not, you are on the wrong host. Stop. A command that succeeded on the wrong host is not progress.

The draft stays a draft until a person has read the names in it. A generator does not log into the host and does not know which disk is empty. You delete a line that names a host, a path, or an account you did not write down.

192.0.2.10/24, gateway 192.0.2.1, 198.51.100.0/24, 203.0.113.0/24, and 2001:db8::/32 are documentation. example.com is a documentation name. They belong in the note. They are not values you leave on a host because a draft included them.

prompt-for-this is a reminder that a secret is missing. It is not a password, a key, or a token you save in the ticket or in git. The real secret stays in the password store.

One change is the window. If two things move and the result is wrong, you will not know which one did it. The next change waits for its own page.

If the same step fails twice, stop for the day. The failure is the result. Adding a forum command beside a half-applied change produces a host nobody can rebuild. Restore the copy you took first.

A second person reads the hostname and the change aloud. If they cannot find them in the ticket, the note is not done. Silence is not agreement. Then leave the host alone.

This page is a planning guide. It is not a vendor manual, not an official standard, and not permission to touch a host you do not administer. You do not disable a firewall, AppArmor, or SELinux to make a check pass.

Tools for this guide

These tools run in the browser on this site. They do not log into your machines.

More in this cluster

The pillar for this page, and the next published pages filed with it.