back to labs
Service Won't Start: Fix the Unit
EasyRHCSA Prep15-20 minThe brief
A service fails to start and the boot log shows an EXEC failure. Its unit file points ExecStart at a binary that doesn't exist. Your per-session assignment is in /root/case/assignment.env (SERVICE, BINARY = the correct executable path). Read /root/case/service.log, fix the unit's ExecStart to the correct binary, and enable the service so it starts on boot. Grading reads the unit file and the enablement symlink (systemd isn't PID 1 on a lab box, so the durable on-disk config is what's graded, not a running service).
What you'll do
- Read the failure log to see why the service won't start
- Fix ExecStart in the unit to the correct binary path
- Enable the service so it starts on boot
Hands-on lab: you work on a real Linux box in your browser, graded on the machine's actual state.