Run systemctl status backup.
systemctl status backup
Mission 87
Service failure review
Inspect a simulated inactive backup service.
Server operationssystemctljournalctl
Lesson 87 of 360
0/360 lessons
0/17 missions
Server operations · 8 minutes
New learnerrank
0XP
0%complete
learner@clairos:/home/learner $
Unix ops lab: type a command, press Enter
Instructions
8 minutes
Click any instruction for the command details, the why, and the common mistake to avoid.
Run journalctl -u backup.
journalctl -u backup
Run systemctl is-active backup.
systemctl is-active backup
Save progress
Keep learning across sessions.
Create a free account to sync completed lessons, XP, streaks, course status, and your next lesson across sessions.
Checking account status...
Progress sync is idle.
0XP
New learnerrank
0day streak
0best streak
0daily streak
0lessons
0courses
0missions
0tasks
Noverified
Progress sync stores completion IDs, scores, streaks, badges, and game settings. Terminal contents, editor snippets, lab scratch, email, and real names are never published on leaderboards or share cards.
Lesson support
What to notice while you play.
Read status, journal, and active state for an inactive service.
Use backup as the service name.
Good operators gather evidence before declaring an outage.
- Assuming inactive always means broken.
- Skipping service-specific logs.
Reference
Commands in this lesson.
systemctl status <service>
Inspect simulated service status.
journalctl -u <service>
Read simulated service journal entries.