Run systemctl status nginx.
systemctl status nginx
Mission 337
Service state triangulation
Compare status, active state, and journal evidence for one service.
Server operationssystemctljournalctl
Lesson 337 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 systemctl is-active nginx.
systemctl is-active nginx
Run journalctl -u nginx -n 2.
journalctl -u nginx -n 2
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.
Build repeatable confidence with confirming service health with three independent signals.
Start with systemctl status nginx, inspect the result, then continue in order.
Confirming service health with three independent signals helps operators explain what they know before they change anything.
- Skipping the output that proves confirming service health with three independent signals.
- Changing several things before recording a baseline.
Reference
Commands in this lesson.
systemctl status <service>
Inspect simulated service status.
journalctl -u <service>
Read simulated service journal entries.