<!DOCTYPE html PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN">
<html>
<head>
<meta content="text/html;charset=ISO-8859-1" http-equiv="Content-Type">
</head>
<body bgcolor="#ffffff" text="#000000">
Not true for me, a restart, if not mandatory, is a good idea, let's say
weekly or more depending on the usage.<br>
My side is asterisk servers as gateways with thousands of calls a day
(at least 10.000 minutes a day).<br>
<br>
I have asterisk(s) running for a long time( 4 years and more), with ss7
links and without, just as a b2bua.<br>
I just see that Asterisk sometime doesn't close the connections
correctly (or the other party).<br>
As an example, we have some servers redirecting to a specific provider,
after a few days even with no actives calls, some connections stay
open, probably due to the provider (no control on that)...<br>
Then restarting asterisk is, for me, the only solution.<br>
<br>
Another case is the ss7 links.<br>
After a few days, some channels dies, the only solution is again to
restart asterisk and Dahdi(zaptel).<br>
<br>
I don't say it's due to Asterisk, I just say it's not a bad idea to
have a cron with a 'restart when convenient' to have servers always up.<br>
<br>
Regards,<br>
<br>
Olivier<br>
<br>
<br>
Jeff LaCoursiere a écrit :
<blockquote
cite="mid:alpine.BSF.2.00.0904231832100.62099@phoenix.jeff.net"
type="cite">
<pre wrap="">On Thu, 23 Apr 2009, Darrick Hartman wrote:
</pre>
<blockquote type="cite">
<pre wrap="">Rob Hillis wrote:
</pre>
<blockquote type="cite">
<pre wrap="">Kurian Thayil wrote:
</pre>
<blockquote type="cite">
<pre wrap="">On Wed, 2009-04-22 at 15:24 +1000, Lee, John (Sydney) wrote:
</pre>
<blockquote type="cite">
<pre wrap="">Daily Asterisk restart
</pre>
</blockquote>
<pre wrap="">Do you think its mandatory in production env?????
</pre>
</blockquote>
<pre wrap="">Daily? No. However, after implementing a weekly restart of Asterisk,
I've found the instance of lockups and CPU utilisation spikes have
decreased significantly.
</pre>
</blockquote>
<pre wrap="">Unless you're using some unstable modules, there really should be no
need to restart Asterisk. Is there a certain activity that is causing
these lockups? I have low power systems which haven't had Asterisk
restarted in months many times. Granted, these are mostly low call
volume systems, but unless there is a memory leak, you should not needed
to restart the Asterisk process. (my guess is one of the modules you
are using has some sort of problem).
</pre>
</blockquote>
<pre wrap=""><!---->
I had a 1.2 instance running over a year and a half with a ton of live
calls to a custom AGI. If you are having to restart asterisk something
must be wrong.
j
_______________________________________________
-- Bandwidth and Colocation Provided by <a class="moz-txt-link-freetext" href="http://www.api-digital.com">http://www.api-digital.com</a> --
asterisk-users mailing list
To UNSUBSCRIBE or update options visit:
<a class="moz-txt-link-freetext" href="http://lists.digium.com/mailman/listinfo/asterisk-users">http://lists.digium.com/mailman/listinfo/asterisk-users</a>
</pre>
</blockquote>
</body>
</html>