Apache's log files keep track of both access and errors. Find out how to read the logs to look for problems.
- [Instructor] An Apache web server keeps two primary logs;…the access log and the error log.…The access log contains information about clients trying…to access resources on the server.…Every resource that's requested from the server…gets a line in the log, along with…an HTTP status code for how the server responded.…That's true even if there was a document…or file requested that the server can't find.…To the server, a missing document isn't an error,…but rather a condition it can handle correctly…by returning a 404 or similar…status code back to the client.…
The error log on the other hand contains entries for…problems that the web server itself encounters.…Misconfigurations, warnings, and even things that software…like PHP prints to the log for troubleshooting…or other error reporting reasons.…The global specifications for these logs…are defined in the Apache configuration file.…There, we can set the location of the log files…and the level of information…or the specificity that they should contain.…
And down here at the bottom there are a few templates…
- Name the tool that is often used to find out what ports are open on a remote server.
- Explain what a firewall will do without any additional configuration.
- Identify what you append a rule to in iptables.
- Explain what needs to be added to a site to allow the use of HTTPS.
- List the two components of a keypair.