In productionProintermediateService environment
The node works in a shell but fails as a service
Make a ROS service start reliably at boot without sourcing an interactive shell.
Pairs with Linux evidence toolkit in Robotics Development Setup & Recovery. Read the concept first, then diagnose it here.
Unlock this lab with ProOperator report
The executable works manually, but systemd reports `ros2: command not found`.
Ubuntu 24.04 setup emulator, isolated disk images, Linux recovery shell, ROS 2 Jazzy
System boundary
Trace only the relevant path.
systemd environmentROS underlayrobot executable
How this lab works
You diagnose it — no command list.
Open the repair workspace and gather your own evidence in a real terminal. No diagnostic commands are handed to you — finding the fault is the exercise. Stuck? Progressive hints unlock inside the workspace.
Verification
Your repair must pass more than the visible symptom.
- Service reaches active state
- ROS node appears after boot
- Hidden regression behavior
- Root cause explanation