Want to protect your cyber security and still get fast solutions? Ask a secure question today.Go Premium

  • Status: Solved
  • Priority: Medium
  • Security: Public
  • Views: 25473
  • Last Modified:

Apache wont start: "Unable to Open Logs"

I have Apache 2.0 setup on a Windows 2003 Server. I have been working on creating certificates for SSL. I created and signed my own certificate, then placed the key and certificate in the /conf/ssl.crt and /conf/ssl.key directories. Next, I changed the ssl.conf file to point to the new cert and key that were created. I saved the ssl.conf file and attempted to restart the service. When I restarted Apache, I received the following error:

Event Type:      Error
Event Source:      Apache Service
Event Category:      None
Event ID:      3299
Date:            3/31/2005
Time:            2:21:23 PM
User:            N/A
Computer:      xxxxx
The Apache service named  reported the following error:
>>> Unable to open logs     .

For more information, see Help and Support Center at http://go.microsoft.com/fwlink/events.asp.

I did not change anything in the httpd.conf file,it contains a directive that refers it to the ssl.conf file.

Can anyone help me troubleshoot this?


3 Solutions
Chances are, it's trying to open a log file for the SSL transactions, but the permissions on the directory where it is trying to place the log file aren't set properly.  Does the ssl.conf file have anything related to logs in it?
check your config file for following directives:

If they exist they should point to files with correct directory structure and apropriate permissions should be set.
for more details check  file which is referneced by ErrorLog directive in your httpd.conf file. In that file you will see more detailed explanation of problem.

3drcAuthor Commented:
Thanks for the suggestions, I will look into them and let you know what I find.

Concerto Cloud for Software Providers & ISVs

Can Concerto Cloud Services help you focus on evolving your application offerings, while delivering the best cloud experience to your customers? From DevOps to revenue models and customer support, the answer is yes!

Learn how Concerto can help you.

please post proper messages from your error_log too
and start apache from a command prompt under the account that is used to start the service and check the error messages, you could run filemon at the sametime (www.sysinternals.com) to see if you get any access denied's.
3drcAuthor Commented:
Sorry to take so long to get back.....

I looked at the httpd.conf file and realized that  you are not allowed to include "Listen 443" in the httpd.conf file when it is used in the SSL.conf file.

I removed the entry from httpd.conf,left it in the SSL.conf file, and everything is working.

Why woudn't any of this show up in the error logs? The error message from the OS event viewer was completely off in this case. I am not sure why it would claim "unable to open logs" when the problem was with a misplaced directive. Any reason for this?

In any case, thank you for the help. I wouldlike to award points, but I am not sure that any comments led e to the resolution of this problem. Can I split this 4 ways?

Hi: I had the same problem--unable to open logs. I stopped my IIS service--then restarted the apache service and things worked fine. Best of Luck

Featured Post

Free Tool: Port Scanner

Check which ports are open to the outside world. Helps make sure that your firewall rules are working as intended.

One of a set of tools we are providing to everyone as a way of saying thank you for being a part of the community.

Tackle projects and never again get stuck behind a technical roadblock.
Join Now