Sorry it was supposed to be every 12 hrs that's what I get for rushing around and not paying attention..

Loren Tedford (KC9ZHV) 
Email: lorentedford@gmail.com
Phone: 
Fax:
http://www.lorentedford.com
http://kc9zhv.com

Sent from Droid Turbo from Verizon wireless network

On May 2, 2016 10:09 AM, "Brent Weatherall" <va3bfw@gmail.com> wrote:
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, May 2, 2016 at 11:03 AM Loren Tedford <lorentedford@gmail.com> wrote:

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..

Loren Tedford (KC9ZHV) 
Email: lorentedford@gmail.com

Phone: 618-553-0806
Fax: 16185512755
http://www.lorentedford.com
http://kc9zhv.com

Sent from Droid Turbo from Verizon wireless network

On May 2, 2016 10:00 AM, "Brent Weatherall" <va3bfw@gmail.com> wrote:
Thanks for the cron script to try Loren. Hopefully the daily restart of ezstream will cure any issues.

On Mon, Apr 25, 2016 at 3:57 PM Loren Tedford <lorentedford@gmail.com> wrote:
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..



crontab -e 
* */12 * * * sh /etc/asterisk/stopez.sh


script that i use to reset ezstream..
root@server:/etc/asterisk# cat stopez.sh
#!/bin/bash
kill -9 $(pgrep ezstream)&
sleep 2s
kill -9 pgrep ezstream
sleep 2s
/usr/sbin/asterisk -rx "module reload"


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?

Thanks in advance for any suggestions
VA3BFW - Brent

_______________________________________________
App_rpt-users mailing list
App_rpt-users@ohnosec.org
http://ohnosec.org/cgi-bin/mailman/listinfo/app_rpt-users

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.