Really, what I would do is to set up a daily restart point when there is
no or very little activity, something like running nightly:
asterisk -rx stop when convenient
and then having the monitoring script restart it immediately. Do you need
to unload the zaptel modules as well or is
, January 29, 2008 9:49 AM
To: Asterisk Users Mailing List - Non-Commercial Discussion
Subject: Re: [asterisk-users] Asterisk mem leak behavior?
I've tried exiting the CLI in hopes that my being in there, though it
wouldn't make any sense, was keeping it from restarting. No luck.
I've already setup
, January 29, 2008 9:49 AM
*To:* Asterisk Users Mailing List - Non-Commercial Discussion
*Subject:* Re: [asterisk-users] Asterisk mem leak behavior?
I've tried exiting the CLI in hopes that my being in there, though it
wouldn't make any sense, was keeping it from restarting. No luck.
I've
I've tried exiting the CLI in hopes that my being in there, though it
wouldn't make any sense, was keeping it from restarting. No luck.
I've already setup a cron script to restart asterisk at night when there is
no traffic going over it. But I hate to just treat the symptoms. I want to
solve the
Kevin,
After upgrading to the latest build of everything have you seen the problem
anymore?
Don't know yet, waiting for it to break ( not a good feeling as you know)
What's your hardware and software configs? Maybe we can find a similarity in
our systems.
It's a dell poweredge with
So here is my setup.
Hardware:
Intel P3 1.2 Ghz
1 GB RAM
36 GB Drives Mirrored
Software:
CentOS 5
2.6.18 Kernel
Asterisk 1.4.14
Zaptel 1.4.7 (redfone)
LIbpri 1.4.2
I'm using TDMoE with my PRI using a product called fonebridge from a company
called redfone. They require that I use their own
What if you issue restart now and then ctrl-c or ctrl-d out of Asterisk?
IMO TMDoE support is very legacy I don't think its really been
maintained since the 1.0 builds.
On Jan 29, 2008 1:24 AM, Mark Greene [EMAIL PROTECTED] wrote:
So here is my setup.
Hardware:
Intel P3 1.2 Ghz
1 GB RAM
36
