-
Notifications
You must be signed in to change notification settings - Fork 6
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
With outstreamcmd= set, shutdown/restart of Asterisk is not reliable #338
Comments
The solution here is probably not to change app_rpt, but to make a monolithic item for app_rpt to kill on shutdown. |
What do you really mean by this, exactly?
All Asterisk modules are expected to clean up anything they started. If |
Could be. I haven't really spent time debugging yet. What APPEARS to be happening is that Asterisk/app_rpt is killing off the parent bash/sh process but then lame is re-parenting it's PID in a way that systemd is detecting as being part of the Asterisk group of PIDs but not to Asterisk/app_rpt. I was just thinking that a quick-and-easy fix might be to make sure that the Broadcastify process is a single-shot application that talks over a socket or something to the item that actually doing the lame/ezstream process. |
I noticed that when using outstreamcmd the CPU pegs at 100% when astres.sh is issued. I stopped using it for now. Also the huge delay is quite normal for broadcastify style streaming. Even when using a local streaming server. |
With the "broadcastify" setup as documented with
outstreamcmd
, shutting down or restarting asterisk withsystemctl
is not reliable. It's either very slow or fails. Asterisk/app_rpt should be killing off any spawned processes at shutdown.The text was updated successfully, but these errors were encountered: