The premise of this question is unfortunately vague but I can't pinpoint a more specific issue. I upgraded a machine from nginx 1.6.3 to 1.8 and now issuing a
nginx -s quit does literally nothing. The command gives no output, the access_log and error_log files show nothing abnormal, even with the debug level enabled in all vhosts. There is also nothing in
/var/log/nginx/error.log other than "signal process started" notices.
pgrep nginx show that the processes stay there like nothing happened.
I understand that the quit signal doesn't necessarily stop nginx immediately since it's supposed to quit gracefully, but the issue here is that even if the machine is firewalled, isolated, and processing no requests,
nginx -s quit still does nothing. Under the exact same conditions with 1.6.3 the processes stop immediately.
I'm at a complete loss at how debug this issue and find the root cause but obviously something is amiss. Any help to point me into the right direction would be much appreciated.
Edit: The behaviour we are seeing is the following, step by step:
- apt-get update/upgrade a machine with nginx 1.6.3 to 1.8 (when prompted install the new /etc/nginx/nginx.conf)
sudo nginx -s quitfor the first time works as expected
sudo service nginx startbrings nginx back as expected
sudo nginx -s quitfor the second time does nothing any longer, and will stay as such even after rebooting
We tested this multiple times in a VM and the results are consistent. Perhaps it's a bug in 1.8?