Understanding Apache Web Server logs
In our earlier topic, we have seen how to install with Apache web server, by following let us see how to configure, understanding each directive and understanding logs, etc.
It’s very important to understand what it logged in log files during troubleshooting any issues in Apache.
- How to install Apache Web Server in Red Hat Enterprise Linux 7 and Variants
- How to configure logging in Apache Web server
To log everything in Apache Web server the directives which assigned CustomLog and ErrorLog will be always underline inside the Virtual Host entry. If it resides out of Virtual Host it will be called as global server directive.
To get more detail in your access log entries use below custom directive.
CustomLog logs/access_log combined
combined logs will contain information like two additional pieces of information.
1. Where the client from.
2. Which browser used by the user.
To diagnostic more on error logs, we can change log level using below available directives.
Available Log Levels in Apache Web Server:
|notice||Normal but significant Condition|
|alert||Action must be taken immediately|
|emerg||Emergencies, when the server is unavailable|
|warn||While in the warning condition|
Logging information in Apache is a huge topic, here we are going to make the separate chunk of post related to Apache logging.
Below are the error codes need to be known from Apache logs.
|Informational log codes||Message|
|Successful log codes|
|Redirection log codes||Message|
|Server error codes||Messages|
|500||Internal server error|
|505||HTTP version not supported|
|Client error codes||Messages|
|405||Method not allowed|
|407||Proxy authentication required|
|413||Request entity too large|
|414||Request-URI too long|
|415||Unsupported media type|
|416||Requested range not satisfiable|
Subscribe now and stay with us for more information related to Apache.In upcoming posts, we can see more information how to log certainly required the piece of information in Apache.