Forum: NGINX nginx -s reload problem

Eb7a3635952459ea2a437d81de0ba0ae?d=identicon&s=25 Harold.Miao (Guest)
on 2014-06-16 09:20
(Received via mailing list)
hi all

I use a endless rtmp stream

/usr/local/nginx/wsgi/ffmpeg  -i  haha.mp4 -c:v libx264 -b:v 500k -c:a
copy
 -f flv rtmp://172.16.205.50:1936/publish/you

as you known, if  I use nginx -s reload , then I got a lot of  "nginx:
worker process is shutting down"

pplive   15355 13642  0 14:56 ?        00:00:00 nginx: worker process
is shutting down
pplive   15356 13642  0 14:56 ?        00:00:00 nginx: worker process
is shutting down
pplive   15357 13642  0 14:56 ?        00:00:00 nginx: worker process
is shutting down
pplive   15358 13642  0 14:56 ?        00:00:00 nginx: worker process
is shutting down
pplive   15359 13642  0 14:56 ?        00:00:00 nginx: worker process
is shutting down
pplive   15360 13642  0 14:56 ?        00:00:00 nginx: worker process
is shutting down

​

because the connection will not quit, so "nginx: worker process is
shutting
down"  more and more

so How to aviod this status  using "nginx -s reload"


--

Best Regards,
Harold Miao
Eb7a3635952459ea2a437d81de0ba0ae?d=identicon&s=25 Harold.Miao (Guest)
on 2014-07-22 22:16
(Received via mailing list)
Do you have any good suggestions?

Thanks in advance!

Roman Arutyunyan <arutyunyan.roman@gmail.com>于2014年7月21日星期一写道:

>>
>> pplive   15359 13642  0 14:56 ?        00:00:00 nginx: worker process is
shutting down
>> --
>> .
>> Visit this group at http://groups.google.com/group/nginx-rtmp.
>> For more options, visit https://groups.google.com/d/optout.
>>
>
>
>
> --
> --
> Roman Arutyunyan
>


--

Best Regards,
Harold Miao
1266aa99d1601b47bbd3ec22affbb81c?d=identicon&s=25 B.R. (Guest)
on 2014-07-23 00:44
(Received via mailing list)
That worker states indicates that the old workers are still busy.

Signaling nginx for a reload (through 'reload' service command or
sending
HUP to the master, which all does the latter), *graciously* shuts old
workers down, that means leaving them finishing what they are doing
without
accepting new tasks.
You have resources to learn how to control nginx
<http://nginx.org/en/docs/control.html>​
​.​


So: your workers are busy.
If you look at your network table, you will most probably find out that
those processes are attached to existing connections.

​You may want to dig on why those workers are busy and the reason for
the
connections being held open (file transfer? connection​ timeout not
expired? request being processed?)
---
*B. R.*
Please log in before posting. Registration is free and takes only a minute.
Existing account

NEW: Do you have a Google/GoogleMail, Yahoo or Facebook account? No registration required!
Log in with Google account | Log in with Yahoo account | Log in with Facebook account
No account? Register here.