[Date Prev][Date Next] [Thread Prev][Thread Next] [Date Index] [Thread Index]

Bug#569026: apache2-mpm-worker: Configured DocumentRoot for vhost ignored by compiled variable



The IP/DNS resolves fine.
And I haven't touched the vhost config for this domain (apart from adding
SSL) before the update, and it was working since several months now.
I also suspected SSL as an error source, as I have only implemented it just
before the Apache update.
But even with SSL, all was working fine before the actual Apache update.

Even now, when I remove the SSL vhost info, and disable SSL it is not
working.
The only problem is, that it is just for this one Domain.

Now I'm not sure, but I might see another problem.
I did run a

# apache2ctl -t -D DUMP_VHOSTS

And it was showing me the IP info and the corresponding Domain.
For the Domain I have problems with, it is showing me 127.0.0.1, so
localhost as IP.
Now, the server name is the domain name, so is more or less 127.0.0.1.

But I don't know if this could cause the problem.
I wouldn't rule out a config problem, but looking at the fact the vhost
config is ok, and has been working in this current state since months, I
would
more suspect a change within the application which is causing the problem.

Regards,
Christian

-----Original Message-----
From: Stefan Fritsch [mailto:sf@sfritsch.de] 
Sent: 10 February 2010 20:35
To: Christian Gerbrandt
Cc: 569026@bugs.debian.org
Subject: Re: Bug#569026: apache2-mpm-worker: Configured DocumentRoot for
vhost ignored by compiled variable

On Tuesday 09 February 2010, Christian Gerbrandt wrote:
> Version: 2.2.14-6

> I got several vhosts configured on my machine. They were all  working 
> fine until I updated to 2.2.14 (Debian). For some unknown  (for me) 
> reason, one of the vhosts is not working anymore in the  way, that it 
> will not use the DocumentRoot configured within the  vhosts 
> configuration file, and tried to look for the htdocs in the  compiled 
> default location, which is /etc/apache2/htdocs

In general, this means that a request is not matched by any virtual host.
You should check that the target IP address and the name provided in the
Host: header of the request actually matches one of the virtual host
definitions.

>From which version did you upgrade? From 2.2.14-5 to 2.2.14-6 the compiled
default changed from /htdocs to /etc/apache2/htdocs. But this would mean
that you should have gotten "File does not exist: /htdocs"
errors before.

If you have upgraded from before 2.2.12, the problem may be related to the
added support for TLS server name indication (name based virtual hosts with
SSL). This changed the behaviour for some setups that tried to use SSL name
based virtual hosts before (even if the were not properly supported).

Cheers,
Stefan

Attachment: smime.p7s
Description: S/MIME cryptographic signature


Reply to: