Apple Event: May 7th at 7 am PT

Newsroom Update

Beginning in May, a special Today at Apple series titled “Made for Business” will offer small business owners and entrepreneurs free opportunities to learn how Apple products and services can support their growth and success. Learn more >

Looks like no one’s replied in a while. To start the conversation again, simply ask a new question.

Leopard server getting Apache error in log

I have a Mac mini running Leopard server (10 user) and I am getting an error in the system log

"May 3 14:52:25 mini01 org.apache.httpd[941]: SSLCertificateFile: file '/etc/certificates/Default.crt' does not exist or is empty"

I do NOT have web services running, nor is Apache 1.2 running. I was trying to update to A[ache 2.2 but it constantly failed so I just shut web services down (using this system for training NOT critical). How do I stop what appears to be Apache 2.2 from launching/looking for a non-existant SSL cerificate?

Mac mini, Mac OS X (10.5.8)

Posted on May 3, 2012 12:06 PM

Reply
1 reply

May 14, 2012 12:12 PM in response to JimTheo

The first question is which version of Apache is the one that's complaining?, and how did you shut it down?


If you installed Apache 2.2 you probably (at least should have) installed it somewhere other than /etc/httpd/ and you should know that Server Admin knows nothing about this version and will not control it, so turning off Web Service in Server Admin won't make an iota of difference.


Therefore you'll have to turn to whatever mechanism you are using to manage Apache - typically launchd, but you might have started it manually via apachectl.

Knowing that is going to be critical in shutting down Apache permanently.


Alternatively you could just fix the SSL error - you'll need to find the httpd.conf that's being used by Apache - the standard /etc/httpd/httpd.conf should be used by the default Apache 1.2, but a custom-built Apache could be looking anywhere. Somewhere in here you'll find a reference to the SSL certificate in question (or maybe you'll find an Include statement that pulls in an external configuration file that's trying to use it). Either way, find that config file and comment out the SSL statements and you should be good to go.

Leopard server getting Apache error in log

Welcome to Apple Support Community
A forum where Apple customers help each other with their products. Get started with your Apple ID.