HUP signal to nginx doesn't work Ubuntu14

Maxim Dounin mdounin at mdounin.ru
Thu Jun 4 02:14:29 UTC 2015


Hello!

On Wed, Jun 03, 2015 at 05:06:57PM -0500, Kunal Pariani wrote:

> Hello, 
> Am seeing an issue while sending HUP signal to nginx (for config reload) on Ubuntu14. It just kills the master process & doesn't start the new worker processes. The same works just fine on CentOS 6.6 64-bit 
> 
> $ ps -eaf | grep nginx 
> zimbra 10860 1 0 16:05 ? 00:00:00 nginx: master process /opt/zimbra/nginx/sbin/nginx -c /opt/zimbra/conf/nginx.conf 
> zimbra 10861 10860 0 16:05 ? 00:00:00 nginx: worker process 
> zimbra 10862 10860 0 16:05 ? 00:00:00 nginx: worker process 
> zimbra 10863 10860 0 16:05 ? 00:00:00 nginx: worker process 
> zimbra 10864 10860 0 16:05 ? 00:00:00 nginx: worker process 
> zimbra 18638 25945 0 16:22 pts/0 00:00:00 grep nginx 
> zimbra 19994 1 0 Jun02 ? 00:01:51 /usr/bin/perl -w /opt/zimbra/libexec/zmstat-nginx 
> $ 
> $ kill -HUP 10860 
> $ 
> $ ps -eaf | grep nginx 
> zimbra 10861 1 0 16:05 ? 00:00:00 nginx: worker process <------ same old worker processes & master process is killed 
> zimbra 10862 1 0 16:05 ? 00:00:00 nginx: worker process 
> zimbra 10863 1 0 16:05 ? 00:00:00 nginx: worker process 
> zimbra 10864 1 0 16:05 ? 00:00:00 nginx: worker process 
> zimbra 18666 18641 0 16:22 pts/1 00:00:00 tail -f log/nginx.log 
> zimbra 18986 25945 0 16:23 pts/0 00:00:00 grep nginx 
> zimbra 19994 1 0 Jun02 ? 00:01:51 /usr/bin/perl -w /opt/zimbra/libexec/zmstat-nginx 
> $ 
> 
> From nginx.log, i can see the SIGHUP is received 
> 2015/06/03 16:23:14 [notice] 10860#0: signal 1 (SIGHUP) received, reconfiguring 
> 2015/06/03 16:23:14 [debug] 10860#0: wake up, sigio 0 
> 2015/06/03 16:23:14 [notice] 10860#0: reconfiguring 
> 2015/06/03 16:23:14 [debug] 10860#0: posix_memalign: 00000000021EAA50:16384 @16 
> 2015/06/03 16:23:14 [debug] 10860#0: posix_memalign: 000000000223D570:32768 @16 
> 
> Any ideas on why this doesn't work on ubuntu only ? 

It looks like master process dies for some reason.  First of all I 
would recommend you to test if you are able to reproduce the 
problem without 3rd party (or your own) modules/patches.

See also http://wiki.nginx.org/Debugging for some basic debugging 
hints.

-- 
Maxim Dounin
http://nginx.org/



More information about the nginx mailing list