According to the nginx changelog, it's been fixed in 1.19.1
part of changelog http://nginx.org/en/CHANGES
Changes with nginx 1.19.107 Jul 2020
*) Change: the "lingering_close", "lingering_time", and
"lingering_timeout" directives now work when
On Sat, 15 Dec 2018 23:03:27 -0600 James Renken
wrote:
> This bug is still present for me in version 1.14.1-1~bpo9+1.
I can confirm this as well; nginx 1.14.1-1~bpo9+1 does not restart
properly as sockets are not removed upon stop and nginx complains that
the address is already in use when
This bug is still present for me in version 1.14.1-1~bpo9+1.
SIGQUITs are still being sent, and sockets are not being cleaned up, as of
1.10.3-1+deb9u1 and 1.13.3-1~bpo9+1.
Package: nginx
Version: 1.9.10-1
Severity: normal
Tags: patch
Hello,
It turns out that the way that Debian implements stopping nginx is by
sending it, through the start-stop-daemon's --retry option a SIGQUIT to
nginx, which is interpreted by nginx as a "gradeful shutdown", but it
turns out is
5 matches
Mail list logo
