Conditional error_log capability?

Our new ISP’s load balancer is going crazy, and is apparently issuing
partial HTTP requests constantly or something.

This is flooding the error log, and I’m wondering if there is a way to
disable the error_log conditionally? Or any other ideas?

Thanks.

2008/09/19 16:58:25 [info] 6950#0: *184 client closed prematurely
connection while reading client request line, client: 10.122.1.254,
server: foo.com
2008/09/19 16:58:25 [info] 6950#0: *185 client closed prematurely
connection while reading client request line, client: 10.122.1.254,
server: foo.com
2008/09/19 16:58:27 [info] 6950#0: *186 client closed prematurely
connection while reading client request line, client: 10.122.1.254,
server: foo.com
2008/09/19 16:58:27 [info] 6950#0: *187 client closed prematurely
connection while reading client request line, client: 10.122.1.254,
server: foo.com
2008/09/19 16:58:27 [info] 6950#0: *188 client closed prematurely
connection while reading client request line, client: 10.122.1.254,
server: foo.com
2008/09/19 16:58:28 [info] 6950#0: *189 client closed prematurely
connection while reading client request line, client: 10.122.1.254,
server: foo.com

I think something like this:
http://wiki.codemongers.com/HWLoadbalancerCheckErrors

However, error_log can’t be inside of a conditional block due to the
fact it can’t be in a location {} or possibly even server {} (I tried
something I thought would work and it told me it was invalid)

Anyone got any ideas? I am not sure if it’s the SYN-ACT-RST issue. I
think it’s just doing a quick port 80 check and not a proper http
request. I don’t want my logfiles to fill up because of this stuff…

On Sam 20.09.2008 20:51, mike wrote:

I think something like this:
http://wiki.codemongers.com/HWLoadbalancerCheckErrors

pay attention this does not work anymore.

BR

Aleks

On Sun, Sep 21, 2008 at 12:31 AM, Aleksandar L. [email protected]
wrote:

pay attention this does not work anymore.

Sorry, if it doesn’t work why isn’t the wiki updated?

I can only know what is given in documentation without reading every
line of code, and can’t review every single changelog out there. I
read each changelog I get nowadays, but don’t remember seeing anything
about this.

Anyway, this does not help me with my issue, either way.