<!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">
Steve Edwards escribió:
<blockquote cite="mid:Pine.LNX.4.64.0909081719500.16029@fs.sedwards.com"
type="cite">Un-top-posting...
<br>
<br>
<blockquote type="cite">From: <a class="moz-txt-link-abbreviated" href="mailto:asterisk-users-bounces@lists.digium.com">asterisk-users-bounces@lists.digium.com</a>
[<a class="moz-txt-link-freetext" href="mailto:asterisk-users-bounces@lists.digium.com">mailto:asterisk-users-bounces@lists.digium.com</a>] On Behalf Of
abdelkader
<br>
<br>
I am using Asterisk 1.4.22 in a debian 4.0 with a kernel version
2.6.18-6-amd64 (SMP). The processor type is Intel(R) Xeon(R) CPU E5420
@ 2.50GHz.
<br>
<br>
Sometimes, I get a strange behavior from asterisk: The CLI commands
does not work and Asterisk cannot receive calls. The output of every
CLI command is that command is not known (no such command).
<br>
</blockquote>
<br>
Just grasping at straws...
<br>
<br>
How often does this happen?
<br>
<br>
Does "sudo lsof | grep /usr/lib/asterisk/modules/" show the modules you
expect?
<br>
<br>
<blockquote type="cite">From: <a class="moz-txt-link-abbreviated" href="mailto:asterisk-users-bounces@lists.digium.com">asterisk-users-bounces@lists.digium.com</a>
[<a class="moz-txt-link-freetext" href="mailto:asterisk-users-bounces@lists.digium.com">mailto:asterisk-users-bounces@lists.digium.com</a>] On Behalf Of Mindaugas
Kezys
<br>
<br>
Asterisk sometimes goes to sleep. (And never wakes-up).
<br>
<br>
Restart it and all will be fine again.
<br>
<br>
We have a watchdog which sends SIP OPTIONS packet to Asterisk and if it
does not respond � restarts it.
<br>
</blockquote>
<br>
Please share :)
<br>
<br>
On Wed, 9 Sep 2009, Lee, John (Sydney) wrote:
<br>
<br>
<blockquote type="cite">I have a cron job that restarts Asterisk
every night. This is supposed to be an old Asterisk best practice for
1.2.* but I think it does not harm.
<br>
</blockquote>
<br>
Unless you're running 24x7x365.
<br>
<br>
I have a 1.2.7 system (with custom hacks) that needs to be restarted
every 3 or 4 months due to a memory leak.
<br>
<br>
I had (until last weekend) a 1.2.2x system that had been running for
over <b>600 days</b>.
<br>
<br>
Both systems handle about <b>15k calls a day.</b>
<br>
</blockquote>