Back to commands

Hosting Operations

Read-only

Check Failed Dependencies for a Service

A service fails after startup, but the real blocker may be a dependent unit such as Redis, networking, a mount, or a socket.

Command

systemctl list-dependencies app-worker --failed --no-pager

Before you run this

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

When not to use it: Do not assume every dependency failure is causal; inspect the dependency logs and timeline.

Expected output

A dependency tree containing failed units under the target service.

System impact

Read-only. Nothing changes. systemctl prints failed dependencies for the requested unit.

Recovery / rollback: no state is changed.

When to use it

Use when a service failure mentions connection refused, missing mounts, network targets, sockets, or required local services.

When not to use it

Do not assume every dependency failure is causal; inspect the dependency logs and timeline.

next steps

Related commands

Hosting Operations Read-only

Print Runtime Paths and User From systemd

Confirm the user, working directory, env file, and ExecStart systemd is actually using.

systemctl show app-worker --property=FragmentPath,DropInPaths,EnvironmentFiles,ExecStart,User,WorkingDirectory --no-pager
Hosting Operations Can be slow

Find the First Failure Line for One Unit

The first failure line is often more useful than the last restart message.

journalctl -u app-worker -b --no-pager -o short-iso | grep -m1 -E 'ERROR|Failed|status='
Hosting Operations Can be slow

Build a Restart Loop Timeline

Restart loops make more sense when you line up starts, failures, and counters.

journalctl -u app-worker -b --no-pager -o short-iso | grep -E 'Started|Failed|Scheduled restart|Main process exited'
Hosting Operations Read-only

Spot Stale systemd Timers

The suspicious timer is the one with no next run.

systemctl list-timers --all --no-pager --plain | awk 'NR==1 || $1=="n/a" || /backup\.timer|logrotate\.timer/'
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.