Working with system logs is one of the most common tasks a Linux service administrator performs. Knowing where to find these logs and how to parse them into just the information you need saves time and effort in troubleshooting and resolution. In this hands-on lab, we will practice pulling data from the logs of a web server.
Learning Objectives
Successfully complete this lab by achieving the following learning objectives:
- Attempt to `curl` the Address on the Local Host
Run the following command:
curl -I localhost
- Determine How Many Times 10.0.1.10 Has Accessed the Website
Run the following command:
sudo cat /var/log/httpd/access_log | grep -E "^10.0.1.10" | wc -l
- Attempt to Reach the Web Server via `http://PUBLIC_IP/index.html`
Run the following command:
sudo tail -f /var/log/httpd/access_logAttempt to reach the website via public IP (not 10.0.1.10) from your computer as http://PUBLIC_IP/index.html.
- Find the New Entry in the Log
Run the following command to view the entry that was appended to the end of the log:
sudo tail -f /var/log/httpd/access_logNote the "200" after "HTTP/1.1"; this signifies a valid destination.
- Attempt to Reach the Web Server via `http://PUBLIC_IP/server.html`
While running
tailon the access log, attempt to reach the/server.htmlpath:curl http://PUBLIC_IP/server.htmlNote the 404 status code; this signifies the path did not resolve to a valid page.
