Run grep 404 /var/log/nginx-access.log.
grep 404 /var/log/nginx-access.log
Mission 219
Access log triage
Search access logs for status and route signals.
Text and logsgreptailwc
Lesson 219 of 360
0/360 lessons
0/17 missions
Text and logs · 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 grep 200 /var/log/nginx-access.log.1.
grep 200 /var/log/nginx-access.log.1
Run wc -l /var/log/nginx-access.log.
wc -l /var/log/nginx-access.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.
Search access logs for status and route signals.
Run the commands in order and compare the outputs.
Junior operators build confidence by gathering evidence before changing systems.
- Skipping the inspection step.
- Assuming one command tells the whole story.
Reference
Commands in this lesson.
grep [-i] <text> <file>
Find literal text inside a file.
wc [-l] <file>
Count lines, words, and characters.