# Reload / HUP signal not working anymore

**URL:** <https://www.ruby-forum.com/t/reload-hup-signal-not-working-anymore/207887>\
**Category:** NGINX\
**Created:** [June 5, 2011, 2:05pm UTC](https://www.ruby-forum.com/t/reload-hup-signal-not-working-anymore/207887 "2011-06-05T14:05:00Z")\
**Posts on this page:** 14\
**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:** [June 5, 2011, 2:05pm UTC](https://www.ruby-forum.com/t/reload-hup-signal-not-working-anymore/207887/1 "2011-06-05T14:05:00Z")

</div>

I’m running the current stable version of Nginx (nginx: nginx version:  
nginx/1.0.4), but reloading my configs doesn’t work anymore. Instead  
I’ve to restart nginx on all webservers to get it reloading my configs,  
but that takes some time I can’t lose.

I’ve a main config (nginx.conf) that loads up all configs from the  
/domains/ folder. When altering a config inside the /domains/ folder,  
reloading nginx with the -HUP signal or with the nginx -s reload  
command, it doesn’t use the change I just made.

I run into this problem recently, but cannot really say if it’s since  
1.0.4 or since 1.0.3. as we’ve updated directly from 1.0.2.

If there is more information required from my side, just say so. I’ve  
spent hours debugging this thing now 🙂

Posted at Nginx Forum:

> **[Reload / HUP signal not working anymore](https://forum.nginx.org/read.php?2,204070,204070#msg-204070)**
>
> I'm running the current stable version of Nginx (nginx: nginx version: nginx/1.0.4), but reloading my configs doesn't work anymore. Instead I've to restart nginx on all webservers to get it reloading my configs, but that takes some time I can't lose....

---

<div class="post-metadata">

**Author:** ![Renedx](https://www.ruby-forum.com/letter_avatar_proxy/v4/letter/r/df788c/32.png) [@Renedx](https://www.ruby-forum.com/u/Renedx)\
**Post date:** [June 5, 2011, 2:06pm UTC](https://www.ruby-forum.com/t/reload-hup-signal-not-working-anymore/207887/2 "2011-06-05T14:06:15Z")

</div>

On Sun, Jun 05, 2011 at 08:04:25AM -0400, Renedx wrote:

> I run into this problem recently, but cannot really say if it’s since  
> 1.0.4 or since 1.0.3. as we’ve updated directly from 1.0.2.
> 
> If there is more information required from my side, just say so. I’ve  
> spent hours debugging this thing now 🙂

What does “nginx -t” show ?

–  
Igor S.

---

<div class="post-metadata">

**Author:** ![Renedx](https://www.ruby-forum.com/letter_avatar_proxy/v4/letter/r/df788c/32.png) [@Renedx](https://www.ruby-forum.com/u/Renedx)\
**Post date:** [June 5, 2011, 2:25pm UTC](https://www.ruby-forum.com/t/reload-hup-signal-not-working-anymore/207887/3 "2011-06-05T14:25:24Z")

</div>

## Igor S. Wrote:

> [removed\_email\_address@domain.invalid](mailto:removed_email_address@domain.invalid)  
> [mailman.nginx.org archive](http://nginx.org/mailman/listinfo/nginx)

nginx: the configuration file /etc/nginx/nginx.conf syntax is ok  
nginx: configuration file /etc/nginx/nginx.conf test is successful

Restart works as expected, its only reload that looks like it’s doing  
nothing at all! Error log has nothing either.

Posted at Nginx Forum:  
[http://forum.nginx.org/read.php?2,204070,204076#msg-204076](http://forum.nginx.org/read.php?2,204070,204076#msg-204076)

---

<div class="post-metadata">

**Author:** ![Renedx](https://www.ruby-forum.com/letter_avatar_proxy/v4/letter/r/df788c/32.png) [@Renedx](https://www.ruby-forum.com/u/Renedx)\
**Post date:** [June 5, 2011, 2:30pm UTC](https://www.ruby-forum.com/t/reload-hup-signal-not-working-anymore/207887/4 "2011-06-05T14:30:21Z")

</div>

On Sun, Jun 5, 2011 at 7:04 PM, Renedx [removed\_email\_address@domain.invalid](mailto:removed_email_address@domain.invalid) wrote:

> I’ve a main config (nginx.conf) that loads up all configs from the  
> /domains/ folder. When altering a config inside the /domains/ folder,  
> reloading nginx with the -HUP signal or with the nginx -s reload  
> command, it doesn’t use the change I just made.

I just tested on ubuntu 10.04 and freebsd 8.2 and both seemed ok with  
config reloading.

---

<div class="post-metadata">

**Author:** ![Renedx](https://www.ruby-forum.com/letter_avatar_proxy/v4/letter/r/df788c/32.png) [@Renedx](https://www.ruby-forum.com/u/Renedx)\
**Post date:** [June 5, 2011, 2:53pm UTC](https://www.ruby-forum.com/t/reload-hup-signal-not-working-anymore/207887/5 "2011-06-05T14:53:19Z")

</div>

Hi Igor,

I work at the same company as ReneDX, so I can deliver you with some  
data.

nginx -v shows:  
nginx: nginx version: nginx/1.0.4

Kind regards

Posted at Nginx Forum:

> **[Re: Reload / HUP signal not working anymore](https://forum.nginx.org/read.php?2,204070,204085#msg-204085)**
>
> I'm running the current stable version of Nginx (nginx: nginx version: nginx/1.0.4), but reloading my configs doesn't work anymore. Instead I've to restart nginx on all webservers to get it reloading my configs, but that takes some time I can't lose....

---

<div class="post-metadata">

**Author:** ![Renedx](https://www.ruby-forum.com/letter_avatar_proxy/v4/letter/r/df788c/32.png) [@Renedx](https://www.ruby-forum.com/u/Renedx)\
**Post date:** [June 5, 2011, 2:53pm UTC](https://www.ruby-forum.com/t/reload-hup-signal-not-working-anymore/207887/6 "2011-06-05T14:53:56Z")

</div>

OS is CentOS 5.6

Posted at Nginx Forum:

> **[Re: Reload / HUP signal not working anymore](https://forum.nginx.org/read.php?2,204070,204086#msg-204086)**
>
> I'm running the current stable version of Nginx (nginx: nginx version: nginx/1.0.4), but reloading my configs doesn't work anymore. Instead I've to restart nginx on all webservers to get it reloading my configs, but that takes some time I can't lose....

---

<div class="post-metadata">

**Author:** ![Renedx](https://www.ruby-forum.com/letter_avatar_proxy/v4/letter/r/df788c/32.png) [@Renedx](https://www.ruby-forum.com/u/Renedx)\
**Post date:** [June 5, 2011, 2:54pm UTC](https://www.ruby-forum.com/t/reload-hup-signal-not-working-anymore/207887/7 "2011-06-05T14:54:33Z")

</div>

Ah, and -V shows:  
nginx -V  
nginx: nginx version: nginx/1.0.4  
nginx: built by gcc 4.1.2 20080704 (Red Hat 4.1.2-50)  
nginx: TLS SNI support disabled  
nginx: configure arguments: --prefix=/usr --sbin-path=/usr/sbin/nginx  
–conf-path=/etc/nginx/nginx.conf  
–error-log-path=/var/log/nginx/error.log  
–pid-path=/var/run/nginx/nginx.pid --lock-path=/var/lock/nginx.lock  
–with-http\_ssl\_module --with-http\_realip\_module --with-http\_flv\_module  
–with-http\_gzip\_static\_module --http-log-path=/var/log/nginx/access.log  
–http-client-body-temp-path=/var/tmp/nginx/client/  
–http-proxy-temp-path=/var/tmp/nginx/proxy/  
–http-fastcgi-temp-path=/var/tmp/nginx/fcgi/ --with-ipv6

Posted at Nginx Forum:

> **[Re: Reload / HUP signal not working anymore](https://forum.nginx.org/read.php?2,204070,204087#msg-204087)**
>
> I'm running the current stable version of Nginx (nginx: nginx version: nginx/1.0.4), but reloading my configs doesn't work anymore. Instead I've to restart nginx on all webservers to get it reloading my configs, but that takes some time I can't lose....

---

<div class="post-metadata">

**Author:** ![Renedx](https://www.ruby-forum.com/letter_avatar_proxy/v4/letter/r/df788c/32.png) [@Renedx](https://www.ruby-forum.com/u/Renedx)\
**Post date:** [June 5, 2011, 2:37pm UTC](https://www.ruby-forum.com/t/reload-hup-signal-not-working-anymore/207887/8 "2011-06-05T14:37:09Z")

</div>

On Sun, Jun 05, 2011 at 08:24:52AM -0400, Renedx wrote:

> ## Igor S. Wrote:
> 
> > On Sun, Jun 05, 2011 at 08:04:25AM -0400, Renedx  
> > wrote:  
> > What does “nginx -t” show ?

> nginx: the configuration file /etc/nginx/nginx.conf syntax is ok  
> nginx: configuration file /etc/nginx/nginx.conf test is successful
> 
> Restart works as expected, its only reload that looks like it’s doing  
> nothing at all! Error log has nothing either.

What does “nginx -V” show ?  
What OS ?

–  
Igor S.

---

<div class="post-metadata">

**Author:** ![Renedx](https://www.ruby-forum.com/letter_avatar_proxy/v4/letter/r/df788c/32.png) [@Renedx](https://www.ruby-forum.com/u/Renedx)\
**Post date:** [June 5, 2011, 10:30pm UTC](https://www.ruby-forum.com/t/reload-hup-signal-not-working-anymore/207887/9 "2011-06-05T22:30:04Z")

</div>

Hello!

On Sun, Jun 05, 2011 at 09:30:55PM +0200, Srebrenko Šehić wrote:

> –http-client-body-temp-path=/var/nginx/tmp/client\_body\_temp  
> This worked just fine with 0.8.50 which I recently upgraded from.  
> Please show global error log at notice level (at least) during  
> (and after) sending SIGHUP.

Maxim D.

---

<div class="post-metadata">

**Author:** ![Renedx](https://www.ruby-forum.com/letter_avatar_proxy/v4/letter/r/df788c/32.png) [@Renedx](https://www.ruby-forum.com/u/Renedx)\
**Post date:** [June 5, 2011, 9:31pm UTC](https://www.ruby-forum.com/t/reload-hup-signal-not-working-anymore/207887/10 "2011-06-05T21:31:20Z")

</div>

I can confirm this bug too. What I noticed is that eg. changes to  
directive “proxy\_intercept\_errors on;” have no effect until you issue  
a full restart.

ssehic@amd64:/home/ssehic$ /usr/local/sbin/nginx -V  
nginx: nginx version: nginx/1.0.3  
nginx: TLS SNI support enabled  
nginx: configure arguments: --prefix=/etc/nginx  
–conf-path=/etc/nginx/nginx.conf --sbin-path=/usr/local/sbin/nginx  
–pid-path=/var/run/nginx.pid --lock-path=/var/nginx/tmp/nginx.lock  
–http-client-body-temp-path=/var/nginx/tmp/client\_body\_temp  
–http-proxy-temp-path=/var/nginx/tmp/proxy\_temp  
–http-fastcgi-temp-path=/var/nginx/tmp/fastcgi\_temp  
–http-log-path=/var/log/nginx/access.log  
–error-log-path=/var/log/nginx/error.log --user=\_nginx --group=\_nginx  
–with-http\_ssl\_module --with-http\_stub\_status\_module  
–with-http\_perl\_module --with-debug

ssehic@amd64:/home/ssehic$ uname -a  
OpenBSD amd64.lab 4.8 GENERIC.MP#7 amd64

This worked just fine with 0.8.50 which I recently upgraded from.

Cheers,  
Srebrenko

---

<div class="post-metadata">

**Author:** ![Renedx](https://www.ruby-forum.com/letter_avatar_proxy/v4/letter/r/df788c/32.png) [@Renedx](https://www.ruby-forum.com/u/Renedx)\
**Post date:** [June 5, 2011, 11:05pm UTC](https://www.ruby-forum.com/t/reload-hup-signal-not-working-anymore/207887/11 "2011-06-05T23:05:30Z")

</div>

On Sun, Jun 5, 2011 at 10:40 PM, Srebrenko Šehić [removed\_email\_address@domain.invalid](mailto:removed_email_address@domain.invalid)  
wrote:

> > Please show global error log at notice level (at least) during  
> > (and after) sending SIGHUP.

For my test case, this was caused by caching of 404 pages which was on  
while I was doing my testing on proxy\_intercept\_errors on/off. HUP  
works as designed.

Sorry for ths fuss and false alarm.

Cheers,  
Srebrenko

---

<div class="post-metadata">

**Author:** ![Renedx](https://www.ruby-forum.com/letter_avatar_proxy/v4/letter/r/df788c/32.png) [@Renedx](https://www.ruby-forum.com/u/Renedx)\
**Post date:** [June 5, 2011, 10:41pm UTC](https://www.ruby-forum.com/t/reload-hup-signal-not-working-anymore/207887/12 "2011-06-05T22:41:11Z")

</div>

On Sun, Jun 5, 2011 at 10:29 PM, Maxim D. [removed\_email\_address@domain.invalid](mailto:removed_email_address@domain.invalid)  
wrote:

> Please show global error log at notice level (at least) during  
> (and after) sending SIGHUP.

Here you go:

2011/06/05 22:37:42 [notice] 108#0: signal 1 (SIGHUP) received,  
reconfiguring  
2011/06/05 22:37:42 [notice] 108#0: reconfiguring  
2011/06/05 22:37:42 [notice] 108#0: using the “kqueue” event method  
2011/06/05 22:37:42 [notice] 108#0: start worker processes  
2011/06/05 22:37:42 [notice] 108#0: start worker process 24157  
2011/06/05 22:37:42 [notice] 108#0: start worker process 9796  
2011/06/05 22:37:42 [notice] 108#0: start cache manager process 4289  
2011/06/05 22:37:42 [notice] 108#0: start cache loader process 18265  
2011/06/05 22:37:42 [notice] 12509#0: gracefully shutting down  
2011/06/05 22:37:42 [notice] 26295#0: gracefully shutting down  
2011/06/05 22:37:42 [notice] 26295#0: exiting  
2011/06/05 22:37:42 [notice] 12509#0: exiting  
2011/06/05 22:37:42 [notice] 26295#0: exit  
2011/06/05 22:37:42 [notice] 12509#0: exit  
2011/06/05 22:37:42 [notice] 22338#0: exiting  
2011/06/05 22:37:42 [notice] 26133#0: exiting  
2011/06/05 22:37:42 [notice] 108#0: signal 23 (SIGIO) received  
2011/06/05 22:37:42 [notice] 108#0: signal 20 (SIGCHLD) received  
2011/06/05 22:37:42 [notice] 108#0: cache loader process 22338 exited  
with code 0  
2011/06/05 22:37:42 [notice] 108#0: cache manager process 26133 exited  
with code 0  
2011/06/05 22:37:42 [notice] 108#0: worker process 12509 exited with  
code 0  
2011/06/05 22:37:42 [notice] 108#0: worker process 26295 exited with  
code 0  
2011/06/05 22:37:42 [notice] 108#0: signal 20 (SIGCHLD) received  
2011/06/05 22:37:43 [notice] 108#0: signal 23 (SIGIO) received  
2011/06/05 22:37:43 [notice] 108#0: signal 23 (SIGIO) received  
2011/06/05 22:37:43 [notice] 108#0: signal 23 (SIGIO) received  
2011/06/05 22:37:43 [notice] 108#0: signal 23 (SIGIO) received  
2011/06/05 22:37:43 [notice] 108#0: signal 23 (SIGIO) received  
2011/06/05 22:37:43 [notice] 108#0: signal 23 (SIGIO) received  
2011/06/05 22:37:43 [notice] 108#0: signal 23 (SIGIO) received  
2011/06/05 22:37:43 [notice] 108#0: signal 23 (SIGIO) received  
2011/06/05 22:37:43 [notice] 108#0: signal 23 (SIGIO) received  
2011/06/05 22:37:43 [debug] 4289#0: http file cache expire  
2011/06/05 22:37:43 [debug] 4289#0: http file cache size: 0  
2011/06/05 22:37:43 [debug] 4289#0: http file cache expire  
2011/06/05 22:37:43 [debug] 4289#0: http file cache size: 0  
2011/06/05 22:37:43 [debug] 4289#0: http file cache expire  
2011/06/05 22:37:43 [debug] 4289#0: http file cache size: 0  
2011/06/05 22:37:43 [debug] 4289#0: http file cache expire  
2011/06/05 22:37:43 [debug] 4289#0: http file cache size: 0  
2011/06/05 22:37:43 [debug] 4289#0: http file cache expire  
2011/06/05 22:37:43 [debug] 4289#0: http file cache size: 0  
2011/06/05 22:37:43 [debug] 4289#0: http file cache expire  
2011/06/05 22:37:43 [debug] 4289#0: http file cache size: 0  
2011/06/05 22:37:43 [debug] 4289#0: http file cache expire  
2011/06/05 22:37:43 [debug] 4289#0: http file cache size: 0  
2011/06/05 22:37:43 [debug] 4289#0: http file cache expire  
2011/06/05 22:37:43 [debug] 4289#0: http file cache size: 0  
2011/06/05 22:37:43 [debug] 4289#0: http file cache expire  
2011/06/05 22:37:43 [debug] 4289#0: http file cache size: 0  
2011/06/05 22:37:43 [notice] 108#0: signal 23 (SIGIO) received  
2011/06/05 22:37:43 [notice] 108#0: signal 23 (SIGIO) received  
2011/06/05 22:37:43 [notice] 108#0: signal 23 (SIGIO) received  
2011/06/05 22:37:43 [notice] 108#0: signal 23 (SIGIO) received  
2011/06/05 22:37:43 [notice] 108#0: signal 23 (SIGIO) received

---

<div class="post-metadata">

**Author:** ![Renedx](https://www.ruby-forum.com/letter_avatar_proxy/v4/letter/r/df788c/32.png) [@Renedx](https://www.ruby-forum.com/u/Renedx)\
**Post date:** [June 6, 2011, 10:25am UTC](https://www.ruby-forum.com/t/reload-hup-signal-not-working-anymore/207887/13 "2011-06-06T10:25:10Z")

</div>

Hi Maxim,

We run into the open file limit on the nginx user, should check my  
config better next time, the error log does give me errors after  
rechecking error\_log in the global config:  
open() “/var/log/nginx/domains/[domain].log” failed (24: Too many open  
files)

So this is indeed an error on our side. Thanks for helping out!

Posted at Nginx Forum:

> **[Re: Reload / HUP signal not working anymore](https://forum.nginx.org/read.php?2,204070,204254#msg-204254)**
>
> I'm running the current stable version of Nginx (nginx: nginx version: nginx/1.0.4), but reloading my configs doesn't work anymore. Instead I've to restart nginx on all webservers to get it reloading my configs, but that takes some time I can't lose....

---

<div class="post-metadata">

**Author:** ![Renedx](https://www.ruby-forum.com/letter_avatar_proxy/v4/letter/r/df788c/32.png) [@Renedx](https://www.ruby-forum.com/u/Renedx)\
**Post date:** [June 6, 2011, 12:20am UTC](https://www.ruby-forum.com/t/reload-hup-signal-not-working-anymore/207887/14 "2011-06-06T00:20:51Z")

</div>

Hello!

On Sun, Jun 05, 2011 at 08:54:11AM -0400, DeviaVir wrote:

> –with-http\_gzip\_static\_module --http-log-path=/var/log/nginx/access.log  
> –http-client-body-temp-path=/var/tmp/nginx/client/  
> –http-proxy-temp-path=/var/tmp/nginx/proxy/  
> –http-fastcgi-temp-path=/var/tmp/nginx/fcgi/ --with-ipv6

The same as to Srebrenko Šehić:

Please show global error log at notice level (at least) during  
(and after) sending SIGHUP.

Maxim D.
