Wondering how to resolve HTTPD: could not open error log file? We can help you.

As part of our Server Management Services, we assist our customers with several cPanel queries.

Today, let us see how our Support techs proceed to resolve it.

How to resolve HTTPD: could not open error log file?

httpd is the Apache HyperText Transfer Protocol (HTTP) server program. It is designed to be run as a standalone daemon process. When used like this it will create a pool of child processes or threads to handle requests.

It is a piece of software that listens for network requests (which are expressed using the Hypertext Transfer Protocol) and responds to them. It is open source and many entities use it to host their websites.

Also, It provides a channel for the communication needs of applications.

Typically, httpd error looks as shown below:

Permission denied: httpd: could not open error log file

Usually, issue occurs if incorrect permissions on /exlibris/aleph/u20_1/alephe/apache/logs/error_log and access_log files:

[root@xxxxxxx logs]$ ls -lrt
-rw-r–r– 1 root root 12870329 Apr 3 12:05 access_log
-rw-r–r– 1 root root 119632 Apr 3 12:05 error_log

Today, let us see the steps followed by our Support Techs to resolve this httpd issue.

1. Firstly, su or sudo to root.

2. Then, change the permissions:

[root@xxxxxxx logs]# chmod 666 error_log
[root@xxxxxxx logs]# chmod 666 access_log

3. ls -lrt should then show:

[root@xxxxxxx logs]# ls -lrt
-rw-rw-rw- 1 root root 12870329 Apr 3 12:05 access_log
-rw-rw-rw- 1 root root 119632 Apr 3 12:05 error_log

4. Finally, exit root and start apache as “aleph” with util w/3/6:

/exlibris/aleph/u20_1/alephe/apache/bin/apachectl restart: httpd not running, trying to start
/exlibris/aleph/u20_1/alephe/apache/bin/apachectl restart: httpd started

[Stuck in between? We’d be glad to assist you]

Conclusion

In short, today we saw steps followed by our Support Techs to resolve HTTPD error log.