Hello,
I’ve recently setup an allstar hub node and decided to stream it via broadcastify.
Setup has gone well - I’m running debian, with the allstar node running without issue, as well as streaming now being delivered via Broadcastify.
I’ve ran in to an issue where the ezstream process will occasionally pin at 100%. I can kill it fine, and asterisk gracefully resumes by creating a new working output stream.
Has anyone else encountered this cpu pinned usage? Will I have to set up something to monitor the process to kill it, so it restarts?
Here is what i did to get ezstream working I will be updating this forum as well as to my fix for ezstream locking open randomly basicly it kinda goes like this…
now to restart asterisk i run this customized script.
root@server:/etc/asterisk# cat restart.sh
#!/bin/bash
kill -9 $(pgrep ezstream)&
kill -9 pgrep ezstream
service asterisk stop
sleep 1s
killall asterisk
kill -9 $(pgrep ezstream)&
service asterisk stop
sleep 1s
service asterisk start
So far I have had no issues with ezstream since i did this…
···
On Mon, Apr 25, 2016 at 12:10 PM, Brent Weatherall va3bfw@gmail.com wrote:
Hello,
I’ve recently setup an allstar hub node and decided to stream it via broadcastify.
Setup has gone well - I’m running debian, with the allstar node running without issue, as well as streaming now being delivered via Broadcastify.
I’ve ran in to an issue where the ezstream process will occasionally pin at 100%. I can kill it fine, and asterisk gracefully resumes by creating a new working output stream.
Has anyone else encountered this cpu pinned usage? Will I have to set up something to monitor the process to kill it, so it restarts?
You do not need a password to unsubscribe, you can do it via email confirmation. If you have trouble unsubscribing, please send a message to the list detailing the problem.
On Mon, Apr 25, 2016 at 12:10 PM, Brent Weatherall va3bfw@gmail.com wrote:
Hello,
I’ve recently setup an allstar hub node and decided to stream it via broadcastify.
Setup has gone well - I’m running debian, with the allstar node running without issue, as well as streaming now being delivered via Broadcastify.
I’ve ran in to an issue where the ezstream process will occasionally pin at 100%. I can kill it fine, and asterisk gracefully resumes by creating a new working output stream.
Has anyone else encountered this cpu pinned usage? Will I have to set up something to monitor the process to kill it, so it restarts?
You do not need a password to unsubscribe, you can do it via email confirmation. If you have trouble unsubscribing, please send a message to the list detailing the problem.
The biggest issue with ezstream is that for some reason you get multiple instances of the program running… Not sure exactly what would be the best solution to actually fix this but the cron script is a big bandage with duck tape… I really wish I knew how to write code…
On Mon, Apr 25, 2016 at 12:10 PM, Brent Weatherall va3bfw@gmail.com wrote:
Hello,
I’ve recently setup an allstar hub node and decided to stream it via broadcastify.
Setup has gone well - I’m running debian, with the allstar node running without issue, as well as streaming now being delivered via Broadcastify.
I’ve ran in to an issue where the ezstream process will occasionally pin at 100%. I can kill it fine, and asterisk gracefully resumes by creating a new working output stream.
Has anyone else encountered this cpu pinned usage? Will I have to set up something to monitor the process to kill it, so it restarts?
You do not need a password to unsubscribe, you can do it via email confirmation. If you have trouble unsubscribing, please send a message to the list detailing the problem.
A quick look at that cron schedule looks like it would run every minute of the 0 hour and 12 hour. Did you just want it to run only once at 0 and 12? If that is the case you’d want:
0 */12 * * *.
I’ll let you know how it works out for stability. Thanks again.
On Mon, Apr 25, 2016 at 12:10 PM, Brent Weatherall va3bfw@gmail.com wrote:
Hello,
I’ve recently setup an allstar hub node and decided to stream it via broadcastify.
Setup has gone well - I’m running debian, with the allstar node running without issue, as well as streaming now being delivered via Broadcastify.
I’ve ran in to an issue where the ezstream process will occasionally pin at 100%. I can kill it fine, and asterisk gracefully resumes by creating a new working output stream.
Has anyone else encountered this cpu pinned usage? Will I have to set up something to monitor the process to kill it, so it restarts?
You do not need a password to unsubscribe, you can do it via email confirmation. If you have trouble unsubscribing, please send a message to the list detailing the problem.
On Mon, Apr 25, 2016 at 12:10 PM, Brent Weatherall va3bfw@gmail.com wrote:
Hello,
I’ve recently setup an allstar hub node and decided to stream it via broadcastify.
Setup has gone well - I’m running debian, with the allstar node running without issue, as well as streaming now being delivered via Broadcastify.
I’ve ran in to an issue where the ezstream process will occasionally pin at 100%. I can kill it fine, and asterisk gracefully resumes by creating a new working output stream.
Has anyone else encountered this cpu pinned usage? Will I have to set up something to monitor the process to kill it, so it restarts?
You do not need a password to unsubscribe, you can do it via email confirmation. If you have trouble unsubscribing, please send a message to the list detailing the problem.
Of course the 100% CPU is probably due to it waiting for some resource, rather than actually being loaded to 100%. Press “1” in top and look for the “%wa”
I found (like some others) that the problem is actually the “lame” program which vanishes for some reason. I run a script every 10 minutes that checks the pid for lame and restarts ezstream – but only if needed. I think that is better than killing ezstream when it is, in fact, running fine.
A quick look at that cron schedule looks like it would run every minute of the 0 hour and 12 hour. Did you just want it to run only once at 0 and 12? If that is the case you’d want:
0 */12 * * *.
I’ll let you know how it works out for stability. Thanks again.
The biggest issue with ezstream is that for some reason you get multiple instances of the program running… Not sure exactly what would be the best solution to actually fix this but the cron script is a big bandage with duck tape… I really wish I knew how to write code…
Here is what i did to get ezstream working I will be updating this forum as well as to my fix for ezstream locking open randomly basicly it kinda goes like this…
On Mon, Apr 25, 2016 at 12:10 PM, Brent Weatherall va3bfw@gmail.com wrote:
Hello,
I’ve recently setup an allstar hub node and decided to stream it via broadcastify.
Setup has gone well - I’m running debian, with the allstar node running without issue, as well as streaming now being delivered via Broadcastify.
I’ve ran in to an issue where the ezstream process will occasionally pin at 100%. I can kill it fine, and asterisk gracefully resumes by creating a new working output stream.
Has anyone else encountered this cpu pinned usage? Will I have to set up something to monitor the process to kill it, so it restarts?
To unsubscribe from this list please visit http://ohnosec.org/cgi-bin/mailman/listinfo/app_rpt-users and scroll down to the bottom of the page. Enter your email address and press the “Unsubscribe or edit options button”
You do not need a password to unsubscribe, you can do it via email confirmation. If you have trouble unsubscribing, please send a message to the list detailing the problem.
Ken, definitely confirmed on my last CPU spiking that lame’s process was no longer running. I’ll give your monitoring/restart script a try. Thanks for the info!
···
On Mon, May 2, 2016 at 11:26 AM Ken ke2n@cs.com wrote:
Of course the 100% CPU is probably due to it waiting for some resource, rather than actually being loaded to 100%. Press “1” in top and look for the “%wa”
I found (like some others) that the problem is actually the “lame” program which vanishes for some reason. I run a script every 10 minutes that checks the pid for lame and restarts ezstream – but only if needed. I think that is better than killing ezstream when it is, in fact, running fine.
A quick look at that cron schedule looks like it would run every minute of the 0 hour and 12 hour. Did you just want it to run only once at 0 and 12? If that is the case you’d want:
0 */12 * * *.
I’ll let you know how it works out for stability. Thanks again.
The biggest issue with ezstream is that for some reason you get multiple instances of the program running… Not sure exactly what would be the best solution to actually fix this but the cron script is a big bandage with duck tape… I really wish I knew how to write code…
Here is what i did to get ezstream working I will be updating this forum as well as to my fix for ezstream locking open randomly basicly it kinda goes like this…
On Mon, Apr 25, 2016 at 12:10 PM, Brent Weatherall va3bfw@gmail.com wrote:
Hello,
I’ve recently setup an allstar hub node and decided to stream it via broadcastify.
Setup has gone well - I’m running debian, with the allstar node running without issue, as well as streaming now being delivered via Broadcastify.
I’ve ran in to an issue where the ezstream process will occasionally pin at 100%. I can kill it fine, and asterisk gracefully resumes by creating a new working output stream.
Has anyone else encountered this cpu pinned usage? Will I have to set up something to monitor the process to kill it, so it restarts?
To unsubscribe from this list please visit http://ohnosec.org/cgi-bin/mailman/listinfo/app_rpt-users and scroll down to the bottom of the page. Enter your email address and press the “Unsubscribe or edit options button”
You do not need a password to unsubscribe, you can do it via email confirmation. If you have trouble unsubscribing, please send a message to the list detailing the problem.
Well my server is at it again 100% cpu usage for no reason kinda odd…
I did try Ken’s script however I am not sure that its working the way it should…
I did place the info in crontab -e I wonder if we are missing some sort of dependency that isn’t getting installed… Maybe their is an easier way to broadcast to Broadcastify…
Here is an image of what it looks like this evening…
On Mon, May 2, 2016 at 4:46 PM, Brent Weatherall va3bfw@gmail.com wrote:
Ken, definitely confirmed on my last CPU spiking that lame’s process was no longer running. I’ll give your monitoring/restart script a try. Thanks for the info!
On Mon, May 2, 2016 at 11:26 AM Ken ke2n@cs.com wrote:
Of course the 100% CPU is probably due to it waiting for some resource, rather than actually being loaded to 100%. Press “1” in top and look for the “%wa”
I found (like some others) that the problem is actually the “lame” program which vanishes for some reason. I run a script every 10 minutes that checks the pid for lame and restarts ezstream – but only if needed. I think that is better than killing ezstream when it is, in fact, running fine.
A quick look at that cron schedule looks like it would run every minute of the 0 hour and 12 hour. Did you just want it to run only once at 0 and 12? If that is the case you’d want:
0 */12 * * *.
I’ll let you know how it works out for stability. Thanks again.
The biggest issue with ezstream is that for some reason you get multiple instances of the program running… Not sure exactly what would be the best solution to actually fix this but the cron script is a big bandage with duck tape… I really wish I knew how to write code…
Here is what i did to get ezstream working I will be updating this forum as well as to my fix for ezstream locking open randomly basicly it kinda goes like this…
On Mon, Apr 25, 2016 at 12:10 PM, Brent Weatherall va3bfw@gmail.com wrote:
Hello,
I’ve recently setup an allstar hub node and decided to stream it via broadcastify.
Setup has gone well - I’m running debian, with the allstar node running without issue, as well as streaming now being delivered via Broadcastify.
I’ve ran in to an issue where the ezstream process will occasionally pin at 100%. I can kill it fine, and asterisk gracefully resumes by creating a new working output stream.
Has anyone else encountered this cpu pinned usage? Will I have to set up something to monitor the process to kill it, so it restarts?
To unsubscribe from this list please visit http://ohnosec.org/cgi-bin/mailman/listinfo/app_rpt-users and scroll down to the bottom of the page. Enter your email address and press the “Unsubscribe or edit options button”
You do not need a password to unsubscribe, you can do it via email confirmation. If you have trouble unsubscribing, please send a message to the list detailing the problem.
Well my server is at it again 100% cpu usage for no reason kinda odd…
I did try Ken’s script however I am not sure that its working the way it should…
I did place the info in crontab -e I wonder if we are missing some sort of dependency that isn’t getting installed… Maybe their is an easier way to broadcast to Broadcastify…
Here is an image of what it looks like this evening…
On Mon, May 2, 2016 at 4:46 PM, Brent Weatherall va3bfw@gmail.com wrote:
Ken, definitely confirmed on my last CPU spiking that lame’s process was no longer running. I’ll give your monitoring/restart script a try. Thanks for the info!
On Mon, May 2, 2016 at 11:26 AM Ken ke2n@cs.com wrote:
Of course the 100% CPU is probably due to it waiting for some resource, rather than actually being loaded to 100%. Press “1” in top and look for the “%wa”
I found (like some others) that the problem is actually the “lame” program which vanishes for some reason. I run a script every 10 minutes that checks the pid for lame and restarts ezstream – but only if needed. I think that is better than killing ezstream when it is, in fact, running fine.
A quick look at that cron schedule looks like it would run every minute of the 0 hour and 12 hour. Did you just want it to run only once at 0 and 12? If that is the case you’d want:
0 */12 * * *.
I’ll let you know how it works out for stability. Thanks again.
The biggest issue with ezstream is that for some reason you get multiple instances of the program running… Not sure exactly what would be the best solution to actually fix this but the cron script is a big bandage with duck tape… I really wish I knew how to write code…
Here is what i did to get ezstream working I will be updating this forum as well as to my fix for ezstream locking open randomly basicly it kinda goes like this…
On Mon, Apr 25, 2016 at 12:10 PM, Brent Weatherall va3bfw@gmail.com wrote:
Hello,
I’ve recently setup an allstar hub node and decided to stream it via broadcastify.
Setup has gone well - I’m running debian, with the allstar node running without issue, as well as streaming now being delivered via Broadcastify.
I’ve ran in to an issue where the ezstream process will occasionally pin at 100%. I can kill it fine, and asterisk gracefully resumes by creating a new working output stream.
Has anyone else encountered this cpu pinned usage? Will I have to set up something to monitor the process to kill it, so it restarts?
To unsubscribe from this list please visit http://ohnosec.org/cgi-bin/mailman/listinfo/app_rpt-users and scroll down to the bottom of the page. Enter your email address and press the “Unsubscribe or edit options button”
You do not need a password to unsubscribe, you can do it via email confirmation. If you have trouble unsubscribing, please send a message to the list detailing the problem.
Well my server is at it again 100% cpu usage for no reason kinda odd…
I did try Ken’s script however I am not sure that its working the way it should…
I did place the info in crontab -e I wonder if we are missing some sort of dependency that isn’t getting installed… Maybe their is an easier way to broadcast to Broadcastify…
Here is an image of what it looks like this evening…
On Mon, May 2, 2016 at 4:46 PM, Brent Weatherall va3bfw@gmail.com wrote:
Ken, definitely confirmed on my last CPU spiking that lame’s process was no longer running. I’ll give your monitoring/restart script a try. Thanks for the info!
On Mon, May 2, 2016 at 11:26 AM Ken ke2n@cs.com wrote:
Of course the 100% CPU is probably due to it waiting for some resource, rather than actually being loaded to 100%. Press “1” in top and look for the “%wa”
I found (like some others) that the problem is actually the “lame” program which vanishes for some reason. I run a script every 10 minutes that checks the pid for lame and restarts ezstream – but only if needed. I think that is better than killing ezstream when it is, in fact, running fine.
A quick look at that cron schedule looks like it would run every minute of the 0 hour and 12 hour. Did you just want it to run only once at 0 and 12? If that is the case you’d want:
0 */12 * * *.
I’ll let you know how it works out for stability. Thanks again.
The biggest issue with ezstream is that for some reason you get multiple instances of the program running… Not sure exactly what would be the best solution to actually fix this but the cron script is a big bandage with duck tape… I really wish I knew how to write code…
Here is what i did to get ezstream working I will be updating this forum as well as to my fix for ezstream locking open randomly basicly it kinda goes like this…
On Mon, Apr 25, 2016 at 12:10 PM, Brent Weatherall va3bfw@gmail.com wrote:
Hello,
I’ve recently setup an allstar hub node and decided to stream it via broadcastify.
Setup has gone well - I’m running debian, with the allstar node running without issue, as well as streaming now being delivered via Broadcastify.
I’ve ran in to an issue where the ezstream process will occasionally pin at 100%. I can kill it fine, and asterisk gracefully resumes by creating a new working output stream.
Has anyone else encountered this cpu pinned usage? Will I have to set up something to monitor the process to kill it, so it restarts?
To unsubscribe from this list please visit http://ohnosec.org/cgi-bin/mailman/listinfo/app_rpt-users and scroll down to the bottom of the page. Enter your email address and press the “Unsubscribe or edit options button”
You do not need a password to unsubscribe, you can do it via email confirmation. If you have trouble unsubscribing, please send a message to the list detailing the problem.
Well my server is at it again 100% cpu usage for no reason kinda odd…
I did try Ken’s script however I am not sure that its working the way it should…
I did place the info in crontab -e I wonder if we are missing some sort of dependency that isn’t getting installed… Maybe their is an easier way to broadcast to Broadcastify…
Here is an image of what it looks like this evening…
On Mon, May 2, 2016 at 4:46 PM, Brent Weatherall va3bfw@gmail.com wrote:
Ken, definitely confirmed on my last CPU spiking that lame’s process was no longer running. I’ll give your monitoring/restart script a try. Thanks for the info!
On Mon, May 2, 2016 at 11:26 AM Ken ke2n@cs.com wrote:
Of course the 100% CPU is probably due to it waiting for some resource, rather than actually being loaded to 100%. Press “1” in top and look for the “%wa”
I found (like some others) that the problem is actually the “lame” program which vanishes for some reason. I run a script every 10 minutes that checks the pid for lame and restarts ezstream – but only if needed. I think that is better than killing ezstream when it is, in fact, running fine.
A quick look at that cron schedule looks like it would run every minute of the 0 hour and 12 hour. Did you just want it to run only once at 0 and 12? If that is the case you’d want:
0 */12 * * *.
I’ll let you know how it works out for stability. Thanks again.
The biggest issue with ezstream is that for some reason you get multiple instances of the program running… Not sure exactly what would be the best solution to actually fix this but the cron script is a big bandage with duck tape… I really wish I knew how to write code…
Here is what i did to get ezstream working I will be updating this forum as well as to my fix for ezstream locking open randomly basicly it kinda goes like this…
On Mon, Apr 25, 2016 at 12:10 PM, Brent Weatherall va3bfw@gmail.com wrote:
Hello,
I’ve recently setup an allstar hub node and decided to stream it via broadcastify.
Setup has gone well - I’m running debian, with the allstar node running without issue, as well as streaming now being delivered via Broadcastify.
I’ve ran in to an issue where the ezstream process will occasionally pin at 100%. I can kill it fine, and asterisk gracefully resumes by creating a new working output stream.
Has anyone else encountered this cpu pinned usage? Will I have to set up something to monitor the process to kill it, so it restarts?
To unsubscribe from this list please visit http://ohnosec.org/cgi-bin/mailman/listinfo/app_rpt-users and scroll down to the bottom of the page. Enter your email address and press the “Unsubscribe or edit options button”
You do not need a password to unsubscribe, you can do it via email confirmation. If you have trouble unsubscribing, please send a message to the list detailing the problem.
Well my server is at it again 100% cpu usage for no reason kinda odd…
I did try Ken’s script however I am not sure that its working the way it should…
I did place the info in crontab -e I wonder if we are missing some sort of dependency that isn’t getting installed… Maybe their is an easier way to broadcast to Broadcastify…
Here is an image of what it looks like this evening…
On Mon, May 2, 2016 at 4:46 PM, Brent Weatherall va3bfw@gmail.com wrote:
Ken, definitely confirmed on my last CPU spiking that lame’s process was no longer running. I’ll give your monitoring/restart script a try. Thanks for the info!
On Mon, May 2, 2016 at 11:26 AM Ken ke2n@cs.com wrote:
Of course the 100% CPU is probably due to it waiting for some resource, rather than actually being loaded to 100%. Press “1” in top and look for the “%wa”
I found (like some others) that the problem is actually the “lame” program which vanishes for some reason. I run a script every 10 minutes that checks the pid for lame and restarts ezstream – but only if needed. I think that is better than killing ezstream when it is, in fact, running fine.
A quick look at that cron schedule looks like it would run every minute of the 0 hour and 12 hour. Did you just want it to run only once at 0 and 12? If that is the case you’d want:
0 */12 * * *.
I’ll let you know how it works out for stability. Thanks again.
The biggest issue with ezstream is that for some reason you get multiple instances of the program running… Not sure exactly what would be the best solution to actually fix this but the cron script is a big bandage with duck tape… I really wish I knew how to write code…
Here is what i did to get ezstream working I will be updating this forum as well as to my fix for ezstream locking open randomly basicly it kinda goes like this…
On Mon, Apr 25, 2016 at 12:10 PM, Brent Weatherall va3bfw@gmail.com wrote:
Hello,
I’ve recently setup an allstar hub node and decided to stream it via broadcastify.
Setup has gone well - I’m running debian, with the allstar node running without issue, as well as streaming now being delivered via Broadcastify.
I’ve ran in to an issue where the ezstream process will occasionally pin at 100%. I can kill it fine, and asterisk gracefully resumes by creating a new working output stream.
Has anyone else encountered this cpu pinned usage? Will I have to set up something to monitor the process to kill it, so it restarts?
To unsubscribe from this list please visit http://ohnosec.org/cgi-bin/mailman/listinfo/app_rpt-users and scroll down to the bottom of the page. Enter your email address and press the “Unsubscribe or edit options button”
You do not need a password to unsubscribe, you can do it via email confirmation. If you have trouble unsubscribing, please send a message to the list detailing the problem.
