|
Home > Archive > Apache Server configuration support > November 2004 > Include directive problem: "could not open document config file"
You are viewing an archived Text-only version of the thread.
To view this thread in it's original format and/or if you want to reply to
this thread please [click here]
| Author |
Include directive problem: "could not open document config file"
|
|
| Adrian Holovaty 2004-11-16, 2:50 pm |
| All,
In my httpd.conf (Apache 2.0.52), I have the line
"Include /home/foo/bar/extra.conf", but I get this error message when I
try to start Apache:
could not open document config file /home/foo/bar/extra.conf
I tried chowning the file to 777, and it still doesn't work. For
some reason, Apache isn't able to access it.
Yes, /home/foo/bar is a valid file, and its contents are valid. I know
this because the exact same file worked properly on my previous Linux
distribution. (I upgraded from Fedora Core 2 to 3, in case that
matters.)
I su'ed into the "apache" user, which is the user that my Apache runs
as, and I was able to read /home/foo/bar/extra.conf and list the files
in that directory.
This is a puzzler. Thanks for any help.
Adrian
| |
| Davide Bianchi 2004-11-16, 2:50 pm |
| On 2004-11-15, Adrian Holovaty <holovaty@gmail.com> wrote:
> could not open document config file /home/foo/bar/extra.conf
In the error log there should be some more explanatory message.
Davide
--
If Bill Gates had a nickel for every time Windows crashed... Oh wait, he
does!
-- From a Slashdot.org post
| |
| Adrian Holovaty 2004-11-16, 2:50 pm |
| On Mon, 15 Nov 2004 05:38:20 +0000, Davide Bianchi wrote:
> On 2004-11-15, Adrian Holovaty <holovaty@gmail.com> wrote:
>
> In the error log there should be some more explanatory message.
Nope, nothing in the error log. I even set "LogLevel debug", and
nothing is showing up there.
Adrian
| |
| Davide Bianchi 2004-11-18, 5:54 pm |
| On 2004-11-15, Adrian Holovaty <holovaty@gmail.com> wrote:
> could not open document config file /home/foo/bar/extra.conf
In the error log there should be some more explanatory message.
Davide
--
If Bill Gates had a nickel for every time Windows crashed... Oh wait, he
does!
-- From a Slashdot.org post
| |
| Adrian Holovaty 2004-11-21, 2:48 am |
| On Mon, 15 Nov 2004 05:38:20 +0000, Davide Bianchi wrote:
> On 2004-11-15, Adrian Holovaty <holovaty@gmail.com> wrote:
>
> In the error log there should be some more explanatory message.
Nope, nothing in the error log. I even set "LogLevel debug", and
nothing is showing up there.
Adrian
| |
| G Whittington 2004-11-28, 11:31 am |
| quote:
Originally posted by Adrian Holovaty
All,
In my httpd.conf (Apache 2.0.52), I have the line
"Include /home/foo/bar/extra.conf", but I get this error message when I
try to start Apache:
could not open document config file /home/foo/bar/extra.conf
I tried chowning the file to 777, and it still doesn't work. For
some reason, Apache isn't able to access it.
Yes, /home/foo/bar is a valid file, and its contents are valid. I know
this because the exact same file worked properly on my previous Linux
distribution. (I upgraded from Fedora Core 2 to 3, in case that
matters.)
I su'ed into the "apache" user, which is the user that my Apache runs
as, and I was able to read /home/foo/bar/extra.conf and list the files
in that directory.
This is a puzzler. Thanks for any help.
Adrian
I have seen this problem too with Fedora OS running SELinux. Try disabling/modifying the SELinux policy that you are using for httpd (apache) and see if that helps.
If you are running Fedora 3 you can use the 'Security Level' tool ('Security Level Configuration') from the System Settings menu. This allows you for disable the SELinux protection for the daemon. Try this option to see if it fixes the problem (if so you have found the source of the problem at least). |
|
|
|
|