www-apache-bugdb mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Tom Gidden <...@swdb.com>
Subject config/3738: Name-based virtual hosts listening on multiple IP addresses
Date Thu, 21 Jan 1999 17:48:28 GMT

>Number:         3738
>Category:       config
>Synopsis:       Name-based virtual hosts listening on multiple IP addresses
>Confidential:   no
>Severity:       serious
>Priority:       medium
>Responsible:    apache
>State:          open
>Class:          sw-bug
>Submitter-Id:   apache
>Arrival-Date:   Thu Jan 21 09:50:01 PST 1999
>Originator:     gid@swdb.com
>Release:        1.3.3
Linux kryten 2.0.31 #9 Mon Dec 7 16:54:44 GMT 1998 i686 unknown
Apache/1.3.3 (Unix) PHP/3.0.5 mod_perl/1.16 mod_ssl/2.1.3 SSLeay/0.9.0b

This machine is running about 20 name-based VHs, all pointing to the same docroot which works
out which domain they came through, and localises the content based on that domain.   

We need to transfer the names to a new IP, so I put two VirtualHost sections with different
IPs but the same ServerName per server handled.

The server zombies, seg faults, and generally misbehaves itself.  No pertinent error logs.

Maybe I'm missing something.  If this is the case, then this is a doc-bug! =)

This site is already using about 512Mb RAM (mod_perl and DBI ballooning) so there isn't enough
memory to run a different Apache for the two IPs.
Unfortunately, as this is a live site, I can't take the server down for more than about 20
seconds at a time to come up with diagnostics or testing.
As a quick-fix, I have put a single VirtualHost entry on the new IP, which offers a non-localised
version of the site (a _bearable_ alternative)

The different localised domains are held by many providers in many countries, so the task
of getting the new IP propagated on all country domains is going to be a very big one.  Once
we've got a 98% or so propagation on the new IP, we'll switch machines.
[In order for any reply to be added to the PR database, ]
[you need to include <apbugs@Apache.Org> in the Cc line ]
[and leave the subject line UNCHANGED.  This is not done]
[automatically because of the potential for mail loops. ]
[If you do not include this Cc, your reply may be ig-   ]
[nored unless you are responding to an explicit request ]
[from a developer.                                      ]
[Reply only with text; DO NOT SEND ATTACHMENTS!         ]

View raw message