Run systemctl status nginx.
systemctl status nginx
Mission 20
Service inspection
Compare simulated service status and journal output before taking action.
Server operationssystemctljournalctltail
Lesson 20 of 360
0/360 lessons
0/17 missions
Server operations · 9 minutes
New learnerrank
0XP
0%complete
learner@clairos:/home/learner $
Unix ops lab: type a command, press Enter
Instructions
9 minutes
Click any instruction for the command details, the why, and the common mistake to avoid.
Run journalctl -u nginx.
journalctl -u nginx
Run tail -n 2 /var/log/nginx-error.log.
tail -n 2 /var/log/nginx-error.log
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 service status and matching logs together.
Check nginx status, then journalctl -u nginx.
Service triage is a habit of status plus evidence.
- Only checking process lists.
- Ignoring service-specific logs.
Reference
Commands in this lesson.
systemctl status <service>
Inspect simulated service status.
journalctl -u <service>
Read simulated service journal entries.