Introduction
While troubleshooting Apache-related issues on a server managed through cPanel/WHM, you may encounter errors requesting a more detailed logging level. Increasing the Apache LogLevel helps generate more verbose logs, making it easier to identify the root cause of issues such as failed requests, permission problems, or module-related errors.
You may see an error similar to the following in the Apache logs:
[client IP.AD.DR.ES] [host website_url.tld] In order to get more info about fail reason try to change LogLevel to Info in httpd.conf and restart Apache
In such cases, adjusting the Apache LogLevel to Info or another suitable level can provide additional debugging information.
Prerequisites
Before proceeding, ensure the following requirements are met:
- Root access to WHM
- A server running cPanel/WHM
- Apache web server installed and active
- Basic understanding of Apache logging
Steps to Change Apache Log Level in WHM
1. Log in to WHM
Access WHM using the root user credentials.
2. Navigate to Apache Global Configuration
Go to:
WHM → Service Configuration → Apache Configuration → Global Configuration
3. Modify the LogLevel
Locate the LogLevel setting.
Change the current value to the required level, such as:
info
Common log levels include:
emergalertcriterrorwarnnoticeinfodebug
For troubleshooting purposes, info or debug is typically used.
4. Save the Configuration
Scroll to the bottom of the page and click the blue Save button.
5. Rebuild Configuration and Restart Apache
After saving, click:
Rebuild Configuration and Restart Apache
This applies the new logging configuration and restarts the Apache service.
6. Replicate the Issue
Perform the same action that originally triggered the error.
Then review the Apache logs again for more detailed information.
Apache logs are commonly located at:
/var/log/apache2/error_log
or
/usr/local/apache/logs/error_log
depending on the server configuration.
Conclusion
Changing the Apache LogLevel in WHM is a useful troubleshooting step when additional debugging information is required. Increasing the verbosity of logs helps administrators identify and resolve web server issues more efficiently. Once troubleshooting is completed, it is recommended to revert the LogLevel back to its default value to avoid excessive log generation and unnecessary disk usage.