-
Notifications
You must be signed in to change notification settings - Fork 215
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
publishing broken (SIGCHLD) #54
Comments
Do you have |
Like @up, you have more than one worker process without auto-push.
|
|
With what you try to publish? Via FFmpeg? What command options you pass? |
ffmpeg, using
|
I have tested this again on a amd64 machine with the same configuration, same build and it works without errors. |
Any luck with latest nginx, nginx-rtmp master on Pi2? |
yes, publishing works again with nginx 1.9.12 and master (12595a2) on debian jessie on the raspberry 2 the issue can be closed if you want to |
Ok. Thank you for testing. |
Can you check latest master? Reverted some onMetaData code. |
publishing still works, but clients can only connect before publishing starts, not after. once publish started I can't connect to the stream anymore, be it a flash player or ffplay. it keeps playing for already connected clients though. ffplay gives up after some time
there's no indication of what's happening in nginxs debug log. here is ffplays debug output
|
That's really strange. |
I'll try that on my Pi2. But it take some time. |
I did some more testing, this seems to be unrelated that it runs on a raspberry. my amd64 machine has the same problem. no client can connect after publishing started. if you stop and restart publishing when clients still try to connect they suddenly connect fine and start receiving. |
It seems nginx 1.9.12 is acting up. 8c51396 works on nginx 1.9.10 but 1.9.12 will not let anyone connect anymore. I've tested latest master (2d4613c) on 1.9.10 and 1.9.12 and both had the same symptoms. I tested this on a amd64 machine and the raspberry pi. |
I've just tried nginx 1.9.10 on 8c51396 again. |
Did you tried latest |
I've been using the dev branch for a few months now without any issues regarding this. Though I didn't test it on a raspberry pi anymore since I've changed setups, only on the amd64 machine. Not sure when it started working again, I downgraded and didn't update for a while before updating nginx and trying out master/dev |
Concerning raspberry pi/ARM - if it was big-endian (which I don't know for sure), then you probably hit the the same issue I got on bigendian MIPS. Pull Request #308 should deal with that at least for RTMP protocol (not sure about HLS and DASH). I also got SIGCHLD in some situations. |
I am using nginx 1.9.7 on a raspberry pi 2 on debian jessie.
Publishing appears to be broken. I've tried ffmpeg and OBS, both had connection errors.
It worked with aruts branch (v1.1.7), but I'm not having any luck with this one (v1.1.7.9).
rtmp.conf
ffmpeg verbose output:
debug.log
The text was updated successfully, but these errors were encountered: