I think that I finally have a clue as to why those empty pages were
returned.
I have perlbal as front, and it was set to maintain persistent connections
with the apache backend listening on localhost.
I also have some configuration of apache that would essentially deny access
to certain user agen
On Wed, Aug 26, 2009 at 8:16 AM, Perrin Harkins wrote:
> On Wed, Aug 26, 2009 at 11:12 AM, Igor Chudov wrote:
>> Do you refer to the response size, as opposed to request size?
>
> Yes.
>
>> If so... I like your idea. How would I do that?
>
> Just read the logging section of the apache docs. It's a
On Wed, Aug 26, 2009 at 11:12 AM, Igor Chudov wrote:
> Do you refer to the response size, as opposed to request size?
Yes.
> If so... I like your idea. How would I do that?
Just read the logging section of the apache docs. It's a common part
of the access log.
- Perrin
On Wed, Aug 26, 2009 at 8:58 AM, Perrin Harkins wrote:
> Igor,
>
> Why don't you try logging the request size from your mod_perl server?
> If it turns out that it knows when a request is zero bytes, you can
> just kill the process in a cleanup handler.
>
Do you refer to the response size, as opp
Igor,
Why don't you try logging the request size from your mod_perl server?
If it turns out that it knows when a request is zero bytes, you can
just kill the process in a cleanup handler.
Also, if you identify the PID of the broken process in this way, you
can look back through the logs to see wh
Fred, thanks. I am afraid that verify_backend is more of an expensive
distraction, than something actually useful.
At this point in time I will try setting both persist_backend and
verify_backend to off.
I am also considering changing MaxRequestsPerChild and setting it to
something like 1,000.
N
On Tue, Aug 25, 2009 at 7:20 PM, Igor Chudov wrote:
> My new perlbal.conf is included:
>
> REATE POOL dynamic
> pool dynamic add 127.0.0.1:10080
>
> CREATE SERVICE balancer
> SET listen = 0.0.0.0:80
> SET role = reverse_proxy
> SET pool = dynamic
> SET pe
