I wouldn't recommend a reload. More than once I've issued a "reload" to Asterisk and it just sat there, never actually reloaded. Went into limbo, wouldn't accept any future commands either. Had to kill -9 the process and load it again. Plus certain changes you make, like certain changes to the iax.conf file, don't get loaded when you do a reload. I spent an hour trying to fix a problem, modify the iax, reload asterisk, problem still there. Finally stopped asterisk, started it clean, problem was gone, same exact config.
As far as "stop now" and starting it again. I don't truly see the need. Every once in a while I've had to do it to fix a quality issue or memory problem or something odd. Maybe instead of once a day, once a week. Would probably be good. I may implement this myself. I'd recommend the "asterisk -rx "stop now" && /usr/sbin/safe_asterisk" method to accomplish your goal. Maybe even a "stop now" && sleep 1 && killall -9 asterisk && sleep 1 && /usr/sbin/safe_asterisk" Would take a little longer, but would ensure Asterisk is dead before reloading it. -----Original Message----- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Matt G Sent: Monday, October 18, 2004 5:12 PM To: Asterisk Users Mailing List - Non-Commercial Discussion Subject: [Asterisk-Users] Quick question regarding daily restart of asterisk Hi All, I have a quick question regarding restarting (and/or stopping/restarting) asterisk daily -- Should it be done? I've seen conflicting answers, some people have told me that the only reason for asterisk to be stopped/started daily was for mpg123 causing many childs, which has since been fixed using 'no buffer' or 'nb' appended to the line in musiconhold.conf. Others have told me there is no reason whatsoever to restart/stop it, yet there's instructions on how to do it on the wiki, are these just outdated? Is there any other reason why one would want to stop and restart asterisk daily? (or at any other scheduled time?) On a related note, is asterisk -rx "restart now" the equivalent of asterisk -rx "stop now" && /usr/sbin/safe_asterisk (or whatever command is used to restart it)?. I have a job cronned on a slackware system to restart it daily using -rx "restart now" and it creates a new PID, and Process Time, but when I run the same thing on Redhat 9 I get an error saying that it exited on sig 13. I'm sure this is just a redhat specific thing as this isn't the only problem I'm running into, but it would be nice to find some answers. Thanks, Matt _______________________________________________ Asterisk-Users mailing list [EMAIL PROTECTED] http://lists.digium.com/mailman/listinfo/asterisk-users To UNSUBSCRIBE or update options visit: http://lists.digium.com/mailman/listinfo/asterisk-users _______________________________________________ Asterisk-Users mailing list [EMAIL PROTECTED] http://lists.digium.com/mailman/listinfo/asterisk-users To UNSUBSCRIBE or update options visit: http://lists.digium.com/mailman/listinfo/asterisk-users
