Open nickygerritsen opened 8 years ago
Or maybe because app
is empty?
multi-worker with auto-push is not stable, it's a well-know issue. And Author always tell us "DO NOT USE IT IN PRODUCTION".
i have the same trouble without the "auto-push", only live and hls on;. if i increase the workers upper than 1, the stream don't work. (i can push, but i can't watch). My computer is dual-core, and i would like use 2 workers to increase the fps.
Worker number has nothing to do with fps here. Nginx will handle traffic on one core and I think you will first hit bandwidth limit. Encoder should use multiple cores, but server don't have to.
I am with @darktar The stream is not stable after I increase worker number to 2 from 1. I use ffmpeg to record the stream. But the process will hang there after recoding a few minutes.
hey can any one explain me what is worker_processes and worker_connections ?
So we have (roughly) the following config:
The rtmp wrapper starts an ffmpeg which streams a livestream from another source to the RTMP URL.
If I have
worker_processes 4
(or anything > 1), I can randomly not get the stream to play. Usingrtmpdump
it then hangs on receiving data.If I try some more times, it does work.
When I only have 1 worker process, everything always works.
Auto push is enabled, but I do seem to be getting errors in my debug log:
Am I correct in thinking that it uses the wrong slots? I.e. it disconnects from slot 3, but pushes to slot 0, 2 and 3. What happened to slot 1?