hit 64 virtual host limit but only 1 log file

I've been running Apache 1.3x on my local Windows PC for a few years
now, mimicking the remote Linux server set up as best can be expected
from a Win box.

I use name based vhosts for access to clientdomain.localhost, plus
unique port assignments for access from a test Mac via 192.168.0.x:1234

This was working great until I added the 65th vhost. Now Apache just
churns away, unable to connect to anything. As soon as the number of
vhosts drops back down to 64, everything is normal again.

All of the info I've found on vhost limits only mentions the number of
file descriptors if using separate log files per vhost. That's not the
case here - it's a single access log and a single error log that all
vhosts dump into.

Are there any suggestions of what else might be causing this, and how to
overcome it? Running multiple servers would be a huge pain, assuming I
could even get it to work, and recompiling Apache isn't an option for me.

Thanks for any insight.

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

ktc wrote:
> Are there any suggestions of what else might be causing this, and how to
> overcome it? Running multiple servers would be a huge pain, assuming I
> could even get it to work, and recompiling Apache isn't an option for me.
>
> Thanks for any insight.

Perhaps it's using to many resources on your machine. Try setting the
number of child threads to a lower number.

- --
Brendan Gillatt | GPG Key: 0xBF6A0D94
brendan {a} brendangillatt (dot) co (dot) uk
http://www.brendangillatt.co.uk
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.7 (MingW32)

iD8DBQFHyXAKuv4tpb9qDZQRAsduAKCOFZLKUHG4tCXnRIS/a3UlLKpDbACcDejP
fbA+aF15+dgDRdHvzC3WGGo=
=eC3P
-----END PGP SIGNATURE-----

Davide Bianchi wrote:
> On 2008-03-01, ktc <kt2656@gmail.com> wrote:
>> I've been running Apache 1.3x on my local Windows PC for a few years
>> This was working great until I added the 65th vhost. Now Apache just
>> churns away
>
> It could be a limitation of your OS (that you didn't specified),

It's WinXP with 2GB memory. System resources should not be an issue, but
who knows what Windows is doing behind the scenes. I was hoping there
was some other Apache config setting that might be putting a default
limit that could be easily changed.

> I've
> over 200 vhosts on a single Linux machine, so I tend to discount a
> problem in Apache itself. Have you considered the idea of jumping
> the shark?

I did run dual-boot for a while. My most-used Windows apps won't run on
wine or cross-over office and there aren't any viable alternatives that
are native to Linux, so I gave it up.

Any other suggestions?

Brendan Gillatt wrote:
>
> Perhaps it's using to many resources on your machine. Try setting the
> number of child threads to a lower number.

ThreadsPerChild 50

That is the default. Setting it higher or lower doesn't have any effect.
I tried various combinations with MaxRequestsPerChild and some other
parameters but no dice. :( Thanks for the idea, though.

ktc wrote:
>
> I use name based vhosts for access to clientdomain.localhost, plus
> unique port assignments for access from a test Mac via 192.168.0.x:1234
>
> This was working great until I added the 65th vhost.

The problem seems to be related to the 65th port, not the vhost itself.

The Apache 1.3 doc notes a known bug to the Listen directive, but the
supporting info I found on the wayback machine indicates they were
addressed early in the 1.3 life, fixed long before the 1.3.39 that I'm
running now.

Maybe I'll have to think of some other way to get access from the Mac.
That's the only reason for all the extra ports.

On Sat, 01 Mar 2008 09:21:28 -0600, ktc
<kt2656@gmail.com> wrote:

>Davide Bianchi wrote:
>> On 2008-03-01, ktc <kt2656@gmail.com> wrote:
>>> I've been running Apache 1.3x on my local Windows PC for a few years
>>> This was working great until I added the 65th vhost. Now Apache just
>>> churns away
>>
>> It could be a limitation of your OS (that you didn't specified),
>
>It's WinXP with 2GB memory. System resources should not be an issue, but
>who knows what Windows is doing behind the scenes. I was hoping there
>was some other Apache config setting that might be putting a default
>limit that could be easily changed.
>
>> I've
>> over 200 vhosts on a single Linux machine, so I tend to discount a
>> problem in Apache itself. Have you considered the idea of jumping
>> the shark?
>
>I did run dual-boot for a while. My most-used Windows apps won't run on
>wine or cross-over office and there aren't any viable alternatives that
>are native to Linux, so I gave it up.
>
>Any other suggestions?

Run a LAMP (Linux Apache MySQL Perl/PHP) appliance in
VMware Player (free).
http://www.vmware.com/appliances/

As long as you don't run an Xserver in the appliance,
the performance sould be good enough for testing
purposes.
--
( Kees
)
c[_] Dictionaries are to language as the periodic table
is to the universe. If the two disagree, you don't
change the universe. (Vicki Rosenzweig) (#422)

Kees Nuyt wrote:
>
> Run a LAMP (Linux Apache MySQL Perl/PHP) appliance in
> VMware Player (free).
> http://www.vmware.com/appliances/

oooooooo, this sounds promising. :)
I've got about 40GB set aside on one hard drive that I thought about
using for a Linux partition, but this might be even better.

thanks