# Keepalived Connections Reset after reloading the configuration (HUP Signal)

**URL:** <https://www.ruby-forum.com/t/keepalived-connections-reset-after-reloading-the-configuration-hup-signal/206958>\
**Category:** NGINX\
**Created:** [May 14, 2011, 1:24am UTC](https://www.ruby-forum.com/t/keepalived-connections-reset-after-reloading-the-configuration-hup-signal/206958 "2011-05-14T01:24:33Z")\
**Posts on this page:** 3\
**Page:** 1

<div class="post-metadata">

**Author:** ![luislavena](https://www.ruby-forum.com/letter_avatar_proxy/v4/letter/l/0ea827/32.png) [@luislavena](https://www.ruby-forum.com/u/luislavena)\
**Post date:** [May 14, 2011, 1:24am UTC](https://www.ruby-forum.com/t/keepalived-connections-reset-after-reloading-the-configuration-hup-signal/206958/1 "2011-05-14T01:24:33Z")

</div>

Hello,

I’m dealing with a problem. When reloading the nginx configuration,  
all keepalived connections receive the TCP reset flag after I send a  
HUP signal to the master process. If I comment the line responsible for  
enabling the keepalive feature in the configuration, the problem  
disappear (nginx version is 0.9.7).

Thanks in advance,  
Jocelyn Mocquant

Posted at Nginx Forum:

> **[Keepalived Connections Reset after reloading the configuration (HUP Signal)](https://forum.nginx.org/read.php?2,197927,197927#msg-197927)**
>
> Hello, I'm dealing with a problem. When reloading the nginx configuration, all keepalived connections receive the TCP reset flag after I send a HUP signal to the master process. If I comment the line responsible for enabling the keepalive feature in...

---

<div class="post-metadata">

**Author:** ![Jocelyn\_Mocquant](https://www.ruby-forum.com/letter_avatar_proxy/v4/letter/j/c57346/32.png) [@Jocelyn\_Mocquant](https://www.ruby-forum.com/u/Jocelyn_Mocquant)\
**Post date:** [May 16, 2011, 1:33pm UTC](https://www.ruby-forum.com/t/keepalived-connections-reset-after-reloading-the-configuration-hup-signal/206958/2 "2011-05-16T13:33:50Z")

</div>

Hello!

On Fri, May 13, 2011 at 07:24:12PM -0400, Jocelyn Mocquant wrote:

> Hello,
> 
> I’m dealing with a problem. When reloading the nginx configuration,  
> all keepalived connections receive the TCP reset flag after I send a  
> HUP signal to the master process. If I comment the line responsible for  
> enabling the keepalive feature in the configuration, the problem  
> disappear (nginx version is 0.9.7).

On configuration reloading nginx starts new worker processes with  
new configuration and old worker processes are terminated as soon  
as they finish processing of requests. All keepalive connections  
in old workers are closed accordingly. HTTP/1.1 clients are  
required to handle keepalive connection close, so this shoudln’t  
be a problem.

It’s not clear why you see RST instead of normal close with  
FIN/FIN+ACK/ACK (are you?), but this shouldn’t the problem by  
itself anyway.

Maxim D.

---

<div class="post-metadata">

**Author:** ![Jocelyn\_Mocquant](https://www.ruby-forum.com/letter_avatar_proxy/v4/letter/j/c57346/32.png) [@Jocelyn\_Mocquant](https://www.ruby-forum.com/u/Jocelyn_Mocquant)\
**Post date:** [May 17, 2011, 12:12am UTC](https://www.ruby-forum.com/t/keepalived-connections-reset-after-reloading-the-configuration-hup-signal/206958/3 "2011-05-17T00:12:43Z")

</div>

Thanks Maxim for your answer,

If I remove the keep alive directive, all happens as expected.  
Apparently,  
sending USR2 and WINCH solve the problem.

–  
Regards  
Jocelyn