I forgot to add to my previous email that I use this script to restart things when the server crashes like today..

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



On Wed, May 25, 2016 at 7:32 AM, Loren Tedford <lorentedford@gmail.com> wrote:
Greetings I had an episode again where the data center crashed on me for some reason..

Here is a pastebin of my /var/log/asterisk/messages file..
http://pastebin.com/sa9Wy3e9


I decided to ban an IP after looking at the logs however I still don't exactly see what caused the crash..

Here is a few lines before the major crash..

[May 25 03:30:05] NOTICE[4576] cdr.c: CDR simple logging enabled.
[May 25 03:30:05] NOTICE[4576] dnsmgr.c: Managed DNS entries will be refreshed every 300 seconds.
[May 25 03:30:05] NOTICE[4576] indications.c: Removed default indication country 'us'
[May 25 03:30:05] WARNING[4576] chan_dahdi.c: Ignoring switchtype
[May 25 03:30:05] WARNING[4576] chan_dahdi.c: Ignoring signalling
[May 25 03:30:05] WARNING[4576] chan_dahdi.c: Ignoring rxwink
[May 25 03:30:05] NOTICE[4576] chan_iax2.c: Ignoring bindport on reload
[May 25 03:30:05] NOTICE[4576] chan_iax2.c: Ignoring bindaddr on reload
[May 25 03:30:05] NOTICE[27342] app_rpt.c: Unable to open radio repeater configuration rpt.conf.  Radio Repeater disabled.
[May 25 03:30:05] NOTICE[27340] app_rpt.c: Unable to open radio repeater configuration rpt.conf.  Radio Repeater disabled.
[May 25 03:30:06] WARNING[27323] app_rpt.c: rpt_thread restarted on node 41715
[May 25 03:30:06] WARNING[27323] app_rpt.c: rpt_thread restarted on node 41834

In crontab -e I have this..

*/15 * * * * sh /etc/asterisk/stopez.sh

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


The above script kills ezstream and reloads the module so far this has worked well for about 6 months now but I do get this periodic crash every 2 or 3 months..