The following reply was made to PR general/1247; it has been noted by GNATS.
From: JDC <[EMAIL PROTECTED]>
To: [EMAIL PROTECTED] (Rodent of Unusual Size)
Cc: [EMAIL PROTECTED], [EMAIL PROTECTED], [EMAIL PROTECTED]
Subject: Re: general/1247: Main server configuration & VirtualHosts are botched
Date: Sun, 19 Oct 1997 22:07:03 -0700 (PDT)
> > This results in quite a lot of logging -- as well as all of the
> > VirtualHosts working (!!).
>
> Good. Can you send along some of the 'lots of logging' messages?
> Are they talking about overlaps?
The output shows repetitious amounts of the following:
[Sun Oct 19 21:57:08 1997] [warn] NameVirtualHost 206.190.135.249:80 has no
VirtualHosts
One for each entry I have inserted.
To give you an *ACTUAL* configuration entry:
LogLevel debug
NameVirtualHost 206.190.135.249
<VirtualHost archaic-ruins.parodius.com>
User typhoonz
Group users
DocumentRoot /home/typhoonz/WWW
ServerName archaic-ruins.parodius.com
ScriptAlias /cgi-bin/ /home/typhoonz/WWW/cgi-bin/
ErrorLog logs/null
TransferLog logs/null
</VirtualHost>
All of our <VirtualHost> entries look like this now; the
result is that all <VirtualHost>'s work, but our main
server "www.parodius.com" (also "parodius.com") goes to
the <VirtualHost> defined above. This <VirtualHost> is
the first in the list.
> Erm, there's only *one* server defined outside the
> <VirtualHost> containers - the default or "main" server.
> Try listing the main server's details inside its own <VirtualHost>
> container, and changing the global ServerName to "localhost". That
> way, *all* of your working servers should be defined by
> <VirtualHost> blocks, including the main one.
This seems more like an "excuse" to get around the bug; I don't
mean to seem like an asshole, but I am not willing to try this.
I'd prefer the bug be fixed rather than have some "configuration
hack". Sorry if that's rude :-(.
> Oh, and by the way - NameVirtualHost should appear *once* for each
> IP address that has multiple name-vhosts on it, and these
> occurrences of NameVirtualHost should be before and outside any
> <VirtualHost> containers.
And it is so above. We have one IP, and multiple VHosts. We
do not have multiple IPs of any sort.
I hope you're online this evening; possibly you can find me
online and we can deal with this real-time. Emails back
and forth really do help, but they can never really let you
diagnose the problem up-front.
Thanks again.
--
| Jeremy Chadwick [EMAIL PROTECTED] |
| System/Network/Security Administrator [EMAIL PROTECTED]
|
| http://yoshi.parodius.com/ "OUCH! WHAT DO YOU DO?" |
