<div>Thanks Maxim for your answer,</div><div><br></div>If I remove the keep alive directive, all happens as expected. Apparently, sending USR2 and WINCH solve the problem.<div><br></div><div>--<br clear="all">Regards<br> Jocelyn<br>
<br><br><div class="gmail_quote">On Mon, May 16, 2011 at 4:33 AM, Maxim Dounin <span dir="ltr"><<a href="mailto:mdounin@mdounin.ru">mdounin@mdounin.ru</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex;">
Hello!<br>
<div class="im"><br>
On Fri, May 13, 2011 at 07:24:12PM -0400, Jocelyn Mocquant wrote:<br>
<br>
> Hello,<br>
><br>
> I'm dealing with a problem. When reloading the nginx configuration,<br>
> all keepalived connections receive the TCP reset flag after I send a<br>
> HUP signal to the master process. If I comment the line responsible for<br>
> enabling the keepalive feature in the configuration, the problem<br>
> disappear (nginx version is 0.9.7).<br>
<br>
</div>On configuration reloading nginx starts new worker processes with<br>
new configuration and old worker processes are terminated as soon<br>
as they finish processing of requests. All keepalive connections<br>
in old workers are closed accordingly. HTTP/1.1 clients are<br>
required to handle keepalive connection close, so this shoudln't<br>
be a problem.<br>
<br>
It's not clear why you see RST instead of normal close with<br>
FIN/FIN+ACK/ACK (are you?), but this shouldn't the problem by<br>
itself anyway.<br>
<font color="#888888"><br>
Maxim Dounin<br>
</font><div><div></div><div class="h5"><br>
_______________________________________________<br>
nginx mailing list<br>
<a href="mailto:nginx@nginx.org">nginx@nginx.org</a><br>
<a href="http://nginx.org/mailman/listinfo/nginx" target="_blank">http://nginx.org/mailman/listinfo/nginx</a><br>
</div></div></blockquote></div><br></div>