While the mentioned Debian bug [1] describes an issue that is related to the one reported here (also reported upstream at [2], and fixed with [3]), this specific bug is not related with the sockets that are note being removed after the graceful shutdown (SIGQUIT).
This request is to substitute # ExecStop sends SIGSTOP (graceful stop) to the nginx process. with # ExecStop sends SIGQUIT (graceful stop) to the nginx process. in nginx.service since the comment is currently mentioning the wrong signal (ExecStop is indeed sending SIGQUIT instead of SIGSTOP already). Since this is a very small, low priority change, I forwarded it to debian at https://salsa.debian.org/nginx-team/nginx/-/merge_requests/14. This should be enough to get this bug closed. However, we may want to file a separate bug to track [1] in case we want [3] backported. [1] https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=821111 [2] https://trac.nginx.org/nginx/ticket/753 [3] http://hg.nginx.org/nginx/rev/7cbf6389194b ** Bug watch added: trac.nginx.org/nginx/ #753 http://trac.nginx.org/nginx/ticket/753 ** Tags removed: needs-upstream-report -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1919965 Title: nginx-common nginx.service comments use wrong signal To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nginx/+bug/1919965/+subscriptions -- ubuntu-bugs mailing list [email protected] https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
