nginx reload causing dropped requests

SplitIce mat999 at gmail.com
Fri Jan 21 06:11:39 MSK 2011


Ive seen it happen with google chrome a bit after reload  (
net::ERR_EMPTY_RESPONSE)

On Fri, Jan 21, 2011 at 2:08 PM, Mike Bell <mdb036 at gmail.com> wrote:

> Apologies - having looked closer I see the bug is with my python test
> client - python's httplib doesn't notice nginx has closed the connection -
> it's up to the application code to retry in this case.
>
> Cheers,
> Mike
>
> On 20 January 2011 17:45, Mike Bell <mdb036 at gmail.com> wrote:
>
>> Hi,
>>
>> I'm seeing dropped requests on nginx reload.  I'm using 0.8.53 compiled
>> from source.
>>
>> My configuration is nginx as a proxy in front of (currently) 2 apache
>> servers.
>>
>> It looks like if a client reuses a connection it had before the reload
>> (HTTP/1.1 style), then the server doesn't handle the request - from tcpdump,
>> I see the TCP connection is just reset with no response.
>>
>> Is this a known issue?  Is there some configuration option to stop the old
>> worker processes from dieing until the connections have all timed out?
>>
>> Cheers,
>> Mike
>>
>
>
> _______________________________________________
> nginx mailing list
> nginx at nginx.org
> http://nginx.org/mailman/listinfo/nginx
>
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://nginx.org/pipermail/nginx/attachments/20110121/8304643f/attachment.html>


More information about the nginx mailing list