[Asterisk-Users] Asterisk 1.0.9 long term stability

[info at beprojects.com]

Well I don't know how you could measure "long term" stability at the 
moment since 1.0.9 has only been out for about 2 months, but I can offer 
some insight on older versions.

We have one 1.0.3 box that has been up and running for 27+ weeks without 
an issue.  It is running SIP for ~ 30 phones and 1 Cisco gateway.

root at Asterisk-A# asterisk -rx "show uptime"
System uptime: 27 weeks, 1 day, 13 hours, 52 minutes, 57 seconds
Last reload: 3 weeks, 5 days, 18 hours, 29 minutes, 4 seconds

root at Asterisk-A # asterisk -rx "show version"
Asterisk 1.0.3 built by root at Asterisk-A on a i686 running Linux


We have another box that is running 1.0.7 with H.323 to an H.323 
gatekeeper and it is just acting as voicemail for a Cisco Call Manager. 
  It crashes at least 1-2 times per week.  Starting asterisk again 
brings it back up.  I don't know why it happens and I have been unable 
to get anything useful from the logs.  It just dies.

That said, from what I've seen in the past, if you are running SIP, it 
is very stable.  I know I've seen people mention that they have to 
restart it every week or so, but I haven't seen that so far.

Peder


Sig Lange wrote:
> I've been evaluating asterisk for quite some time now and am attempting 
> to create services on it. The system is simple right now. asterisk seems 
> to look up atleast every week if not more. I am running asterisk 1.0.9 
> and would like to find similiar experiences of long term stability.
> 
> I attempted to debug it, but my asterisk isn't compiled with all the 
> possible debugging flags, which flags in the Makefile should I enable to 
> help provide more information?
> 
> Here is what I have found so far.
> 
> gdb attach backtrace:
> (gdb) bt
> #0  0x401c4a76 in nanosleep () from /lib/libc.so.6
> #1  0x0000000c in ?? ()
> #2  0x401ef4ba in usleep () from /lib/libc.so.6
> #3  0x00000000 in ?? ()
> #4  0x8a9fa304 in ?? ()
> #5  0x8a9ffbe0 in ?? ()
> #6  0x00000000 in ?? ()
> #7  0x000003e8 in ?? ()
> #8  0x8a9fa504 in ?? ()
> #9  0x40678bbb in zt_handle_event (ast=0x8a9fa504) at chan_zap.c:590
> Previous frame inner to this frame (corrupt stack?)
> (gdb) info threads
> 
> This is definitely something in zaptel (zt_handle) but the other errors 
> like corrupt stack lead me to believe there is also something else wrong.
> 
> Any input would be greatly appreciated.
> -- 
> Sig Lange
> http://www.signuts.net/
> 
> 
> ------------------------------------------------------------------------
> 
> _______________________________________________
> --Bandwidth and Colocation sponsored by Easynews.com --
> 
> Asterisk-Users mailing list
> Asterisk-Users at lists.digium.com
> http://lists.digium.com/mailman/listinfo/asterisk-users
> To UNSUBSCRIBE or update options visit:
>    http://lists.digium.com/mailman/listinfo/asterisk-users