On 2015-03-03 13:34, Christos Trochalakis wrote:
Hello Christos,
I wasn't able to reproduce this behaviour. I tried reloading and
restarting nginx, while at the same time, I kept an http and a spdy
connection open.
Everything worked as expected, the connection was terminated after 5
secs (the recent graceful stop change) and nginx was restarted
successfully.
Sorry for not being entirely clear. It happens only after some amount of traffic
has hit the server.
And it's on every server we upgraded to nginx-full from backports.
Are you sure you are using the latest /etc/init.d/nginx and
/etc/default/nginx? Make sure the STOP_SCHEDULE variable is set
correctly.
Yes, and everything in those two files is from the debian package as is.
| # dpkg-query -W -f='${Conffiles}\n' nginx-common |grep default\/nginx; \
| md5sum /etc/default/nginx |awk '{print " "$2" "$1}'
| /etc/default/nginx 596fbc1f5712caaa02e8c799a4e2a01f
| /etc/default/nginx 596fbc1f5712caaa02e8c799a4e2a01f
...
#STOP_SCHEDULE="QUIT/5/TERM/5/KILL/5"
If everything is ok, could you provide some steps to reproduce it?
To reproduce it here, it's restart nginx, wait a bit, try to reload, and hit
the bug.
We had not a single successful reload/restart ever with nginx-full from
backports, except
on test or local machines with literally no traffic.
If you have a better idea on how to debug this further i'd gladly help you sort
this out!
greets,
michael
--
To UNSUBSCRIBE, email to [email protected]
with a subject of "unsubscribe". Trouble? Contact [email protected]
