Unusual Apache error_log entries

Question

Level 1

10 points

Unusual Apache error_log entries

My Apache error_log (and my wife's) are full of these:

[Mon Feb 04 13:19:31 2013] [error] [client 127.0.0.1] File does not exist: /Library/WebServer/Documents/crls
[Mon Feb 04 13:19:31 2013] [error] [client 127.0.0.1] File does not exist: /Library/WebServer/Documents/crls
[Mon Feb 04 13:19:31 2013] [error] [client 127.0.0.1] File does not exist: /Library/WebServer/Documents/crls
[Mon Feb 04 13:27:56 2013] [error] [client 127.0.0.1] File does not exist: /Library/WebServer/Documents/crls
[Mon Feb 04 13:27:56 2013] [error] [client 127.0.0.1] File does not exist: /Library/WebServer/Documents/crls

They seem to appear randomly. We've wondered whether it was Safari, Versions or something else causing them, but they appear even when those are quit.

Sometimes they're a bit different:

[Fri Aug 17 15:09:05 2012] [error] [client 127.0.0.1] File does not exist: /Library/WebServer/Documents/ThawtePremiumServerCA.crl

or:

[Thu Aug 23 08:51:07 2012] [error] [client 127.0.0.1] File does not exist: /Library/WebServer/Documents/SVRSecureG3.cer

They've appeared for as long as I can remember (so probably from Snow Leopard onwards) and they drive us a bit crazy!

It's just one of those things that's always been annoying and it'd be wonderful if someone out there knew what the issue was.

Many thanks in anticipation!

iMac, OS X Mountain Lion (10.8.2)

Posted on Feb 4, 2013 6:09 AM

Reply

Answer 1

UptimeJeff

Level 4

3,479 points

Feb 4, 2013 1:17 PM in response to tillathenun

Looks like a config error related to SSL.. as you noted, probably carried over from old system.

Search your apache config files for a reference to these files.. try something like this:

sudo grep -R "

SVRSecureG3

" /etc/apache2

or

sudo grep -R "

crls

" /etc/apache2

Reply

Answer 2

mrmuppet

Level 1

4 points

Feb 5, 2013 2:01 AM in response to UptimeJeff

Thanks very much for the reply.

No luck though - those commands didn't seem to do anything.

One odd thing is that, when I restart Apache, it does take a while before the errors start appearing again.

They also happen when I'm not using it so it must be something the machine's doing in the background.

---

Just noticed I posted this reply using my developer account, hence the different profile name!

Message was edited by: mrmuppet

Reply

Answer 3

stechico

Level 1

9 points

Apr 23, 2013 9:00 PM in response to mrmuppet

Here's what I did to temporarly fix the problem:

* Made an empty file:

touch /your-path/empty-file

* Made symlinks to the empty-file

ln -s /your-path/empty-file {filename that does not exist}

HTH (for now)

Reply

Answer 4

tillathenun Author

Level 1

10 points

Apr 24, 2013 1:35 AM in response to tillathenun

So, I actually found out what the problem was...

I used to have a hacked version of the Adobe CS suite (shameful, I know) and in the etc/hosts file were loads of IP addresses redirected to 127.0.0.1 (localhost).

Removing them all stopped the errors.

So, moral of the story, always buy your software! 🙂

Reply