Run tail -n 2 /var/log/nginx-access.log.
tail -n 2 /var/log/nginx-access.log
Mission 11
Log triage
Inspect access, error, auth, and service logs in a cautious order.
Text and logstailjournalctlgrep
Lesson 11 of 360
0/360 lessons
0/17 missions
Text and logs · 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 grep denied /var/log/auth.log.
grep denied /var/log/auth.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.
Compare app, service, and auth evidence.
Tail nginx access, then read the simulated nginx journal.
Incident triage is evidence gathering before action.
- Restarting a service before reading logs.
- Only checking one log source.
Reference
Commands in this lesson.
grep [-i] <text> <file>
Find literal text inside a file.
journalctl -u <service>
Read simulated service journal entries.