Signal9Signal9 — home
online
back to labs

Troubleshoot: A Service That Won't Start

MediumLinux+ Exam Prep15-25 min
The brief

A systemd service won't start and you have the captured journal. Work it methodically — read the error, form a hypothesis, verify, fix. The journal is /root/case/journal.txt, the unit is named in /root/case/assignment.env.

Record and fix under /root/case:

1. Identify the ExecStart path in the unit that doesn't exist (the broken path) → /root/case/rootcause.txt.

2. Find where the daemon is actually installed and record the full path of its executable (directory and filename, not just the directory) → /root/case/binary.txt.

3. Fix ExecStart in the unit file to point at the real binary (keep its --config argument).

The service and paths vary per session. See /root/case/brief.txt.

What you'll do
  • Read a systemd failure from the journal (status 203/EXEC)
  • Form and verify a hypothesis about the missing executable
  • Locate where the binary really lives
  • Correct the unit's ExecStart path

Hands-on lab: you work on a real Linux box in your browser, graded on the machine's actual state.