You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@httpd.apache.org by Rob Hartill <ro...@imdb.com> on 1996/04/29 02:36:55 UTC
WWW Form Bug Report: "VirtualHosts > 123 breaks logresolve/MAXIMUM_DNS" on BSDI (fwd)
not acked
Message-Id: <19...@taz.hyperreal.com>
From: zaphod@nbn.com
To: apache-bugs%apache.org@organic.com
Date: Sun Apr 28 17:34:29 1996
Subject: WWW Form Bug Report: "VirtualHosts > 123 breaks logresolve/MAXIMUM_DNS" on BSDI
Submitter: zaphod@nbn.com
Operating system: BSDI, version: 2.0.1
Version of Apache Used: 1.0.5
Extra Modules used: w/ & w/o mod_counter
URL exhibiting problem:
Symptoms:
--
Once the total number of VirtualHosts in conf/httpd.conf
exceeds 123, all access_logs (foreach virtual & for
the "real" host) stop resolving the remote hostnames.
I recently upgraded from 0.8.14 which had the same problem
to 1.0.5 and I am still encountering this bug.
Workaround: use the logresolve program in the support
directory to post-process the logs.
--
Backtrace:
--
--
----- End of forwarded message from zaphod@nbn.com -----
--
Rob Hartill (robh@imdb.com)
The Internet Movie Database (IMDb) http://www.imdb.com/
...more movie info than you can poke a stick at.
Re: WWW Form Bug Report: "VirtualHosts > 123 breaks logresolve/MAXIMUM_DNS" on BSDI (fwd)
Posted by Tony Sanders <sa...@bsdi.com>.
I would suspect ``limit openfiles.. unless anyone else has
seen this problem.
Rob Hartill writes:
>
> not acked
>
>
> Message-Id: <19...@taz.hyperreal.com>
> From: zaphod@nbn.com
> To: apache-bugs%apache.org@organic.com
> Date: Sun Apr 28 17:34:29 1996
> Subject: WWW Form Bug Report: "VirtualHosts > 123 breaks logresolve/MAXIMUM_DNS" on BSDI
>
> Submitter: zaphod@nbn.com
> Operating system: BSDI, version: 2.0.1
> Version of Apache Used: 1.0.5
> Extra Modules used: w/ & w/o mod_counter
> URL exhibiting problem:
>
> Symptoms:
> --
>
> Once the total number of VirtualHosts in conf/httpd.conf
> exceeds 123, all access_logs (foreach virtual & for
> the "real" host) stop resolving the remote hostnames.
>
> I recently upgraded from 0.8.14 which had the same problem
> to 1.0.5 and I am still encountering this bug.
>
> Workaround: use the logresolve program in the support
> directory to post-process the logs.
> --
>
> Backtrace:
> --
>
> --
>
> ----- End of forwarded message from zaphod@nbn.com -----
>
> --
> Rob Hartill (robh@imdb.com)
> The Internet Movie Database (IMDb) http://www.imdb.com/
> ...more movie info than you can poke a stick at.