Server Fault is a question and answer site for system and network administrators. It's 100% free, no registration required.

Sign up
Here's how it works:
  1. Anybody can ask a question
  2. Anybody can answer
  3. The best answers are voted up and rise to the top

Very strange issue at work.

I have a very basic Apache configuration. Has a DocumentRoot, <Directory ...> section within which there is an Options +Indexes directive that isn't being honoured (I just get a 404 error when trying to access the directory listing).

The Apache I've build is set to be installed in /usr/local/apache22 however I've got a copy in a different path and am calling it with:

LD_LIBRARY_PATH=/tmp/apache22/lib /tmp/apache22/bin/httpd -f /tmp/test.conf

The configuration gets loaded successfully but doesn't honour the Directory, Location, or Option Indexes directives. In addition an error log is correctly being written to when requesting a bad URL, however the access log is NOT being written to when accessing a good URL.

A friend has tried the same configuration on a different machine using a differently compiled web server and it functions fine. So the configuration is not at fault. I'm wondering if perhaps Apache silently fails when not located in its destined directory...

share|improve this question

I'm not sure this is the right answer so I'll leave this question open for some time to see if there's a better one.

I rsync'd the entire build across to another server, placed it in the path it was built for, and it ran just as expected using the same config that was causing me grief earlier.

It makes me wonder why Apache doesn't complain or error when located in a different path to that for which it was built.. it just silently fails to operate as expected.

share|improve this answer

Your Answer


By posting your answer, you agree to the privacy policy and terms of service.

Not the answer you're looking for? Browse other questions tagged or ask your own question.