Run grep 404 /var/log/nginx-access.log.
grep 404 /var/log/nginx-access.log
Mission 55
Access log review
Filter training HTTP access lines for status and method clues.
Text and logsgrepwctail
Lesson 55 of 360
0/360 lessons
0/17 missions
Text and logs · 7 minutes
New learnerrank
0XP
0%complete
learner@clairos:/home/learner $
Unix ops lab: type a command, press Enter
Instructions
7 minutes
Click any instruction for the command details, the why, and the common mistake to avoid.
Run grep POST /var/log/nginx-access.log.
grep POST /var/log/nginx-access.log
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.
Find status codes and methods in web logs.
Search for 404 and POST.
Web operators use access logs to verify routing and probes.
- Only reading error logs.
- Ignoring unexpected methods.
Reference
Commands in this lesson.
grep [-i] <text> <file>
Find literal text inside a file.
wc [-l] <file>
Count lines, words, and characters.