Back to commands

Linux Survival Basics

Read-only

Reset Failed State After Capturing Evidence

systemctl --failed still shows an old service failure after the issue was fixed, and you need to clear the recorded failed state deliberately.

Command

systemctl reset-failed app-worker

Before you run this

System impact: Read-only. Low when scoped to the shown target.

When not to use it: Do not run it before collecting status and journal evidence, and do not confuse clearing state with fixing the service.

Expected output

Either no output or a short confirmation that the failed state was reset.

System impact

Read-only. systemd clears the recorded failed state for the service, so future --failed output reflects new failures.

When to use it

Use after documenting or fixing a failure when the failed state itself is stale noise.

When not to use it

Do not run it before collecting status and journal evidence, and do not confuse clearing state with fixing the service.

Recovery / rollback

There is no meaningful undo for clearing the marker; use saved logs or incident notes for prior evidence.

next steps

Related commands

Linux Survival Basics Read-only

Print the Exact systemd Exit Fields

Turn a noisy service failure into four fields you can paste into an incident note.

systemctl show app-worker --property=Result,ExecMainCode,ExecMainStatus,NRestarts --no-pager
Linux Survival Basics Read-only

Check If a Service Is Active

Get a clean yes-or-no service state without the full status page.

systemctl is-active nginx
Study mapping

Use this as independent command practice: read the notes, predict the output, then compare it with the example before using a real shell.

  • LPIC-1 style command-line practice
  • LFCS style performance-task practice
  • Linux+ style troubleshooting review

Independent study support only. No affiliation, endorsement, exam dumps, or real exam questions.