[Asterisk-Users] Asterisk 1.0.9 long term stability
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 0x000c in ?? () #2 0x401ef4ba in usleep () from /lib/libc.so.6 #3 0x in ?? () #4 0x8a9fa304 in ?? () #5 0x8a9ffbe0 in ?? () #6 0x in ?? () #7 0x03e8 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 Langehttp://www.signuts.net/ ___ --Bandwidth and Colocation sponsored by Easynews.com -- Asterisk-Users mailing list Asterisk-Users@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
Re: [Asterisk-Users] Asterisk 1.0.9 long term stability
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. [EMAIL PROTECTED] 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 [EMAIL PROTECTED] # asterisk -rx "show version" Asterisk 1.0.3 built by [EMAIL PROTECTED] 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 0x000c in ?? () #2 0x401ef4ba in usleep () from /lib/libc.so.6 #3 0x in ?? () #4 0x8a9fa304 in ?? () #5 0x8a9ffbe0 in ?? () #6 0x in ?? () #7 0x03e8 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@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 ___ --Bandwidth and Colocation sponsored by Easynews.com -- Asterisk-Users mailing list Asterisk-Users@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
RE: [Asterisk-Users] Asterisk 1.0.9 long term stability
We have Asterisk 1.0 (CVS-v1-0-12/28/04-03:08:11 built by [EMAIL PROTECTED] on a i686 running Linux) and as a safe countermeasure we do a cron reboot every week. On four different locations. No more crashes. -Original Message- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of [EMAIL PROTECTED] Sent: Wednesday, September 14, 2005 12:11 PM To: Asterisk Users Mailing List - Non-Commercial Discussion Subject: Re: [Asterisk-Users] Asterisk 1.0.9 long term stability 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. [EMAIL PROTECTED] 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 [EMAIL PROTECTED] # asterisk -rx "show version" Asterisk 1.0.3 built by [EMAIL PROTECTED] 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 0x000c in ?? () > #2 0x401ef4ba in usleep () from /lib/libc.so.6 > #3 0x in ?? () > #4 0x8a9fa304 in ?? () > #5 0x8a9ffbe0 in ?? () > #6 0x in ?? () > #7 0x03e8 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@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 ___ --Bandwidth and Colocation sponsored by Easynews.com -- Asterisk-Users mailing list Asterisk-Users@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 ___ --Bandwidth and Colocation sponsored by Easynews.com -- Asterisk-Users mailing list Asterisk-Users@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
RE: [Asterisk-Users] Asterisk 1.0.9 long term stability <--threadhijack, why not reboot?
Just my opinions but A PBX should not require reboots EVER. Traditional proprietary PBX's don't require reboots and if Asterisk does then it has problems and is not ready to be a viable alternative IMHO. I am sure that some people will say they know of some proprietary PBX's that do require reboots. My response would be that my 'expectation' for ANY PBX and even servers in general is NO REBOOTS. I don't think that is unreasonable. This opinion has NOTHING to do with the whole Linux vs Windows Jihad. That is a whole other argument. I am strictly talking about PBX's regardless of if they are Linux or Windows or traditional proprietary or whatever. Rebooting at 3am everyday just because you can should not justify permitting the existance of problems that require it in the first place. I hope that makes sense. :) Again, just my 2 cents. -Original Message- From: Colin Anderson [mailto:[EMAIL PROTECTED] Sent: Wednesday, September 14, 2005 9:34 AM To: 'Asterisk Users Mailing List - Non-Commercial Discussion' Subject: RE: [Asterisk-Users] Asterisk 1.0.9 long term stability <--threadhijack, why not reboot? Disclaimer: Not a troll I'm curious as to this obsession with uptime is. All of the posts of this type are along the lines of "After X days, Y thing does not work but if I reload or reboot, it's OK" - so why not cron a reboot? Is it considered bad form or something like that? I reboot every night whether it is needed or not, not afraid to admit it, and everything works fine for me. We also do the "Sunday reboot" of all of our Windows servers as well as restarting all of the critical services such as IIS , SQL, Exchange etc nightly. It helps, a lot (Exchange is a notorious memory leaker) Of course, if your install processes calls 24/7 that's a different story. However, I expect that the majority of Asterisk installs are for a 9-to-5 type of operation. We run two shifts here, and we stop processing calls at 10 PM, and start again at about 6 AM - a large window of opportunity to reboot. Why not take advantage of it? I've also heard it said, something along the lines of: "If you have to reboot, your server isn't set up correctly" to which I say piffle. Even NASA has rebooted the Mars probes after they land and I understand that they run VXWorks, incidentally, the same RTOS that my Mitel 3300 uses, and *even Mitel* recommends periodic reboots, which we duly cron every night, 2 AM. 24/7/365 installs aside, is there a reason why reboots seem to be frowned upon? Again, not trolling, just curious. ___ --Bandwidth and Colocation sponsored by Easynews.com -- Asterisk-Users mailing list Asterisk-Users@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
RE: [Asterisk-Users] Asterisk 1.0.9 long term stability<--threadhijack, why not reboot?
Of course analog PBXs did not require reboots. On the other hand, my Call Manager PBX had to be rebooted weekly. Windows, you know. When a Asterisk-based "PBX" is built from two or more servers, each of which has capacity to handle the load, a periodic reboot of one of the servers does not have an impact on uptime. That's just good design, in my opinion. -Original Message- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of canuck15 Sent: Wednesday, September 14, 2005 12:20 PM To: 'Asterisk Users Mailing List - Non-Commercial Discussion' Subject: RE: [Asterisk-Users] Asterisk 1.0.9 long term stability<--threadhijack, why not reboot? Just my opinions but A PBX should not require reboots EVER. Traditional proprietary PBX's don't require reboots and if Asterisk does then it has problems and is not ready to be a viable alternative IMHO. I am sure that some people will say they know of some proprietary PBX's that do require reboots. My response would be that my 'expectation' for ANY PBX and even servers in general is NO REBOOTS. I don't think that is unreasonable. This opinion has NOTHING to do with the whole Linux vs Windows Jihad. That is a whole other argument. I am strictly talking about PBX's regardless of if they are Linux or Windows or traditional proprietary or whatever. Rebooting at 3am everyday just because you can should not justify permitting the existance of problems that require it in the first place. I hope that makes sense. :) Again, just my 2 cents. -Original Message- From: Colin Anderson [mailto:[EMAIL PROTECTED] Sent: Wednesday, September 14, 2005 9:34 AM To: 'Asterisk Users Mailing List - Non-Commercial Discussion' Subject: RE: [Asterisk-Users] Asterisk 1.0.9 long term stability <--threadhijack, why not reboot? Disclaimer: Not a troll I'm curious as to this obsession with uptime is. All of the posts of this type are along the lines of "After X days, Y thing does not work but if I reload or reboot, it's OK" - so why not cron a reboot? Is it considered bad form or something like that? I reboot every night whether it is needed or not, not afraid to admit it, and everything works fine for me. We also do the "Sunday reboot" of all of our Windows servers as well as restarting all of the critical services such as IIS , SQL, Exchange etc nightly. It helps, a lot (Exchange is a notorious memory leaker) Of course, if your install processes calls 24/7 that's a different story. However, I expect that the majority of Asterisk installs are for a 9-to-5 type of operation. We run two shifts here, and we stop processing calls at 10 PM, and start again at about 6 AM - a large window of opportunity to reboot. Why not take advantage of it? I've also heard it said, something along the lines of: "If you have to reboot, your server isn't set up correctly" to which I say piffle. Even NASA has rebooted the Mars probes after they land and I understand that they run VXWorks, incidentally, the same RTOS that my Mitel 3300 uses, and *even Mitel* recommends periodic reboots, which we duly cron every night, 2 AM. 24/7/365 installs aside, is there a reason why reboots seem to be frowned upon? Again, not trolling, just curious. ___ --Bandwidth and Colocation sponsored by Easynews.com -- Asterisk-Users mailing list Asterisk-Users@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 -- No virus found in this incoming message. Checked by AVG Anti-Virus. Version: 7.0.344 / Virus Database: 267.10.25/102 - Release Date: 9/14/2005 -- No virus found in this outgoing message. Checked by AVG Anti-Virus. Version: 7.0.344 / Virus Database: 267.10.25/102 - Release Date: 9/14/2005 ___ --Bandwidth and Colocation sponsored by Easynews.com -- Asterisk-Users mailing list Asterisk-Users@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
Re: [Asterisk-Users] Asterisk 1.0.9 long term stability <--threadhijack, why not reboot?
canuck15 wrote: Just my opinions but A PBX should not require reboots EVER. Traditional proprietary PBX's don't require reboots and if Asterisk does then it has problems and is not ready to be a viable alternative IMHO. I am sure that some people will say they know of some proprietary PBX's that do require reboots. My response would be that my 'expectation' for ANY PBX and even servers in general is NO REBOOTS. I don't think that is unreasonable. Your are 100% correct, of course. Subscriber telephone systems that are properly designed, even inexpensive ones, never need a reboot. In 25 or more years of working on and around business telephone systems, I have only found ONE that ever even remotely had such a requirement. If the mains power dipped low enough for just the right amount of time, the Power On Reset circuitry wouldn't do its job, and the CPU would be insane. At one point there was even a device that looked like a surge suppressor that would keep the mains power off for 15-30 seconds to overcome this and other potential problems that can come with summer storms. There are MANY other reasons that make Asterisk not yet ready for prime time, but that is a discussion that can wait for another time. John Novack ___ --Bandwidth and Colocation sponsored by Easynews.com -- Asterisk-Users mailing list Asterisk-Users@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
RE: [Asterisk-Users] Asterisk 1.0.9 long term stability <--threadhijack, why not reboot?
"Just reboot" is a bad attitude. If there is a memory leek, the fact that a reboot will free the leaked memory is not a good reason to not fix the memory leek. That kind of attitude is why windows does need regular reboots. -Original Message- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Matt Sent: Wednesday, September 14, 2005 11:00 AM To: Asterisk Users Mailing List - Non-Commercial Discussion Subject: Re: [Asterisk-Users] Asterisk 1.0.9 long term stability <--threadhijack, why not reboot? Yes.. because if a reboot is needed it isn't setup correctly. Reboots are a windows things. A correctly setup Linux server should never need rebooted. On 9/14/05, Colin Anderson <[EMAIL PROTECTED]> wrote: > Disclaimer: Not a troll > > I'm curious as to this obsession with uptime is. All of the posts of this > type are along the lines of "After X days, Y thing does not work but if I > reload or reboot, it's OK" - so why not cron a reboot? Is it considered bad > form or something like that? I reboot every night whether it is needed or > not, not afraid to admit it, and everything works fine for me. > > We also do the "Sunday reboot" of all of our Windows servers as well as > restarting all of the critical services such as IIS , SQL, Exchange etc > nightly. It helps, a lot (Exchange is a notorious memory leaker) > > Of course, if your install processes calls 24/7 that's a different story. > However, I expect that the majority of Asterisk installs are for a 9-to-5 > type of operation. We run two shifts here, and we stop processing calls at > 10 PM, and start again at about 6 AM - a large window of opportunity to > reboot. Why not take advantage of it? > > I've also heard it said, something along the lines of: "If you have to > reboot, your server isn't set up correctly" to which I say piffle. Even NASA > has rebooted the Mars probes after they land and I understand that they run > VXWorks, incidentally, the same RTOS that my Mitel 3300 uses, and *even > Mitel* recommends periodic reboots, which we duly cron every night, 2 AM. > > 24/7/365 installs aside, is there a reason why reboots seem to be frowned > upon? Again, not trolling, just curious. > ___ > --Bandwidth and Colocation sponsored by Easynews.com -- > > Asterisk-Users mailing list > Asterisk-Users@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 > ___ --Bandwidth and Colocation sponsored by Easynews.com -- Asterisk-Users mailing list Asterisk-Users@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 ___ --Bandwidth and Colocation sponsored by Easynews.com -- Asterisk-Users mailing list Asterisk-Users@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
RE: [Asterisk-Users] Asterisk 1.0.9 long term stability <--thread hijack, why not reboot?
Disclaimer: Not a troll I'm curious as to this obsession with uptime is. All of the posts of this type are along the lines of "After X days, Y thing does not work but if I reload or reboot, it's OK" - so why not cron a reboot? Is it considered bad form or something like that? I reboot every night whether it is needed or not, not afraid to admit it, and everything works fine for me. We also do the "Sunday reboot" of all of our Windows servers as well as restarting all of the critical services such as IIS , SQL, Exchange etc nightly. It helps, a lot (Exchange is a notorious memory leaker) Of course, if your install processes calls 24/7 that's a different story. However, I expect that the majority of Asterisk installs are for a 9-to-5 type of operation. We run two shifts here, and we stop processing calls at 10 PM, and start again at about 6 AM - a large window of opportunity to reboot. Why not take advantage of it? I've also heard it said, something along the lines of: "If you have to reboot, your server isn't set up correctly" to which I say piffle. Even NASA has rebooted the Mars probes after they land and I understand that they run VXWorks, incidentally, the same RTOS that my Mitel 3300 uses, and *even Mitel* recommends periodic reboots, which we duly cron every night, 2 AM. 24/7/365 installs aside, is there a reason why reboots seem to be frowned upon? Again, not trolling, just curious. ___ --Bandwidth and Colocation sponsored by Easynews.com -- Asterisk-Users mailing list Asterisk-Users@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
Re: [Asterisk-Users] Asterisk 1.0.9 long term stability <--thread hijack, why not reboot?
Yes.. because if a reboot is needed it isn't setup correctly. Reboots are a windows things. A correctly setup Linux server should never need rebooted. On 9/14/05, Colin Anderson <[EMAIL PROTECTED]> wrote: > Disclaimer: Not a troll > > I'm curious as to this obsession with uptime is. All of the posts of this > type are along the lines of "After X days, Y thing does not work but if I > reload or reboot, it's OK" - so why not cron a reboot? Is it considered bad > form or something like that? I reboot every night whether it is needed or > not, not afraid to admit it, and everything works fine for me. > > We also do the "Sunday reboot" of all of our Windows servers as well as > restarting all of the critical services such as IIS , SQL, Exchange etc > nightly. It helps, a lot (Exchange is a notorious memory leaker) > > Of course, if your install processes calls 24/7 that's a different story. > However, I expect that the majority of Asterisk installs are for a 9-to-5 > type of operation. We run two shifts here, and we stop processing calls at > 10 PM, and start again at about 6 AM - a large window of opportunity to > reboot. Why not take advantage of it? > > I've also heard it said, something along the lines of: "If you have to > reboot, your server isn't set up correctly" to which I say piffle. Even NASA > has rebooted the Mars probes after they land and I understand that they run > VXWorks, incidentally, the same RTOS that my Mitel 3300 uses, and *even > Mitel* recommends periodic reboots, which we duly cron every night, 2 AM. > > 24/7/365 installs aside, is there a reason why reboots seem to be frowned > upon? Again, not trolling, just curious. > ___ > --Bandwidth and Colocation sponsored by Easynews.com -- > > Asterisk-Users mailing list > Asterisk-Users@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 > ___ --Bandwidth and Colocation sponsored by Easynews.com -- Asterisk-Users mailing list Asterisk-Users@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
Re: [Asterisk-Users] Asterisk 1.0.9 long term stability <--thread hijack, why not reboot?
On Wednesday 14 September 2005 12:34, Colin Anderson wrote: > I'm curious as to this obsession with uptime is. All of the posts of this > type are along the lines of "After X days, Y thing does not work but if I > reload or reboot, it's OK" - so why not cron a reboot? Is it considered bad > form or something like that? I reboot every night whether it is needed or > not, not afraid to admit it, and everything works fine for me. Rebooting indicates that there is a problem that needs to be addressed. It has nothing to do with uptime wars but with reliability and stability. I don't care if the system's down for 3 minutes due to reboot, I am concerned that there is an underlying issue that you're merely masking by rebooting. > We also do the "Sunday reboot" of all of our Windows servers as well as > restarting all of the critical services such as IIS , SQL, Exchange etc > nightly. It helps, a lot (Exchange is a notorious memory leaker) Exactly. With closed-source proprietary applications you can't fix the problem so this is all you can do. With Asterisk and OSS you can fix it and increase code quality. Would you accept the need for a weekly reboot of your Nortel Option 11? How about if your car required you to remove the battery for two minutes once a month? Your VCR? How about a clock radio that had to be unplugged once a week to fix weird little issues? I put Asterisk into the same class as these kinds of devices. They must be up and stay up. If they need to be rebooted then there's an issue that needs to be addressed and corrected. > I've also heard it said, something along the lines of: "If you have to > reboot, your server isn't set up correctly" to which I say piffle. Even > NASA has rebooted the Mars probes after they land and I understand that > they run VXWorks, incidentally, the same RTOS that my Mitel 3300 uses, and > *even Mitel* recommends periodic reboots, which we duly cron every night, 2 > AM. Hmm, I guess I won't be buying any Mitel equipment. The MARS rovers were designed to be totally shut down as a last measure to ensure everything is starting up as they'd simulated on Earth and that there was no high-energy radiation glitches due to space travel. -A. ___ --Bandwidth and Colocation sponsored by Easynews.com -- Asterisk-Users mailing list Asterisk-Users@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
Re: [Asterisk-Users] Asterisk 1.0.9 long term stability <--thread hijack, why not reboot?
Andrew Kohlsmith wrote: Hmm, I guess I won't be buying any Mitel equipment. The MARS rovers were designed to be totally shut down as a last measure to ensure everything is starting up as they'd simulated on Earth and that there was no high-energy radiation glitches due to space travel. They designed it to be shut down. I guess that means it doesn't just roll over like a dead cow. You wouldn't design a crane controller so that it releases the load on reboot and then tries to return the cable to the pre-reboot position. The same principle applies here. If it's mission-critical, you might have to spend more on the hardware. A good example would be crosspoint switch modules that don't change state when the system is rebooted. That would prevent calls from being dropped as long as you don't design your system software to explicity clear all those modules at startup. I did hardware and software design for some devices that were usually placed in very remote areas(underwater, mountains, arctic are a few). We used a very low power clock device that would boot the cpu up. We did whatever needed to be done, set the clock registers for the next wakeup and shut down again. There were other ways to approach the problem, but this approach made coding easier, used less power and allowed us to get more functionality without increasing rom or ram size. If you only needed to take one simple measurement and store it to the ram, you could do a boot/run/shutoff every second and still achieve some additional battery runtime. ___ --Bandwidth and Colocation sponsored by Easynews.com -- Asterisk-Users mailing list Asterisk-Users@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
RE: [Asterisk-Users] Asterisk 1.0.9 long term stability <--thread hijack, why not reboot?
Great comments everyone thanks and thanks for not flaming me. >Rebooting indicates that there is a problem that needs to be addressed. It >has nothing to do with uptime wars but with reliability and stability. I >don't care if the system's down for 3 minutes due to reboot, I am concerned >that there is an underlying issue that you're merely masking by rebooting. In my case, I have the TDM04 static problem and that is the sole reason why I reboot. Granted, I'm running 1.0-stable and I understand it's fixed in -head or 1.2 or whatever but I don't want to go through the grief of upgrading to fix it and find out that other issues are introduced. A lot of guys say "upgrade, upgrade it's way better" but then I read posts like the gentleman this morning who has his console going crazy when he upgraded. My plan is to wait out the rest of the year until 1.2 has a few months under it's belt then upgrade (hey, isn't today the release day?). Until then, reboot to me is a perfectly acceptable alternative and it does not impact business operations one whit. You may feel differently, and yes, I concede that I am masking an underlying problem, but I am comfortable with it, my Asterisk server does not care, and it's transparent to my users,so why not? >Would you accept the need for a weekly reboot of your Nortel Option 11? How >about if your car required you to remove the battery for two minutes once a >month? Your VCR? How about a clock radio that had to be unplugged once a >week to fix weird little issues? See above. Yes I would accept it, provided that it would not impact normal operation and I as the administrator *or* enduser would not have to do anything special. However, *this* makes my sphincter shrink: http://slashdot.org/articles/02/07/22/0615221.shtml?tid=126 Obviously, that's no good. Best comment: RH support: Thanks for calling Red Hat! How may we help you? Pilot: "Uhh.. I'm spiraling towards the earth, both my engines are out, and my display says 'kernel panic' in white text on a black background." RH Support: "And what is the system model?" Pilot: "The F-22 jet.." RH support: If you read linux-kernel-bugtraq, you will see that you should have patched your kernel to 2.4.19-pre-alpha-revision-d before takeoff. But no problem, this is Linux after all. Do you have another F22 on your LAN? Just telnet in from there, su to root and restart sendmail. Pilot: @#$*! Redhat! I'm switching to Debian if I survive! >Hmm, I guess I won't be buying any Mitel equipment. Please don't. They are evil. Not so much the equipment but the corporate philosophy is something along the lines of "We're gonna hose our endusers more than any other telecom manufacturer" ___ --Bandwidth and Colocation sponsored by Easynews.com -- Asterisk-Users mailing list Asterisk-Users@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
Re: [Asterisk-Users] Asterisk 1.0.9 long term stability <--thread hijack, why not reboot?
On Thursday 15 September 2005 11:38, Paul wrote: > They designed it to be shut down. I guess that means it doesn't just > roll over like a dead cow. Actually dead cows aren't back-heavy. They typically just keep whatever position they were in when they took their last breath, much like the telco crosspoint switches. :-) > You wouldn't design a crane controller so that it releases the load on > reboot and then tries to return the cable to the pre-reboot position. > The same principle applies here. If it's mission-critical, you might > have to spend more on the hardware. A good example would be crosspoint I agree -- You need to spend more time on both hardware and software. For me, a phone system is like a file server or network switch -- it is *not* meant to be rebooted. If it needs to be periodically power-cycled then address the problem, don't simply put a cron script in. > I did hardware and software design for some devices that were usually > placed in very remote areas(underwater, mountains, arctic are a few). We > used a very low power clock device that would boot the cpu up. We did > whatever needed to be done, set the clock registers for the next wakeup > and shut down again. There were other ways to approach the problem, but > this approach made coding easier, used less power and allowed us to get > more functionality without increasing rom or ram size. If you only How did it save you ROM/RAM? I can see it saving having to put fancy power controller code and hardware in... Is that what you meant? > needed to take one simple measurement and store it to the ram, you could > do a boot/run/shutoff every second and still achieve some additional > battery runtime. Agreed but again -- you designed for this specific purpose. Asterisk isn't meant to boot up, answer the phone, process the call and shut down again until the next ring. (This would be an interesting approach to power savings though if your system boot time was fast enough and call volumes varied enough to make it worthwhile.) -A. ___ --Bandwidth and Colocation sponsored by Easynews.com -- Asterisk-Users mailing list Asterisk-Users@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
Re: [Asterisk-Users] Asterisk 1.0.9 long term stability <--thread hijack, why not reboot?
On Thu, Sep 15, 2005 at 10:04:15AM -0600, Colin Anderson wrote: > Great comments everyone thanks and thanks for not flaming me. > > >Rebooting indicates that there is a problem that needs to be addressed. It > > >has nothing to do with uptime wars but with reliability and stability. I > >don't care if the system's down for 3 minutes due to reboot, I am concerned > > >that there is an underlying issue that you're merely masking by rebooting. > > In my case, I have the TDM04 static problem and that is the sole reason why > I reboot. > Granted, I'm running 1.0-stable and I understand it's fixed in -head or 1.2 > or whatever > but I don't want to go through the grief of upgrading to fix it and find out > that other issues are introduced. Could you point to a specific issue? Any chance it could be backported to 1.0? This will mean less griff. > A lot of guys say "upgrade, upgrade it's > way better" but then I read posts like the gentleman this morning who has > his console going crazy when he upgraded. My plan is to wait out the rest > of the year until 1.2 has a few months under it's belt then upgrade (hey, > isn't today the release day?). > Until then, reboot to me is a perfectly acceptable alternative and it does > not impact business operations one whit. You may feel differently, and yes, > I concede that I am masking an underlying problem, > but I am comfortable with it, my Asterisk server does not care, and it's > transparent to my users,so why not? When do you reboot? every day? This is assuming that the problem hits you randomly, you will rebooot some time after the problem has begun. e.g: there is a resonable chance that around half of the time the problem will exist. The more frequent the reboots are the less chances (but not 0%) are for "bad voice", but more time your PBX is unavailble. -- Tzafrir Cohen | [EMAIL PROTECTED] | VIM is http://tzafrir.org.il | | a Mutt's [EMAIL PROTECTED] | | best ICQ# 16849755 | | friend ___ --Bandwidth and Colocation sponsored by Easynews.com -- Asterisk-Users mailing list Asterisk-Users@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
RE: [Asterisk-Users] Asterisk 1.0.9 long term stability <--thread hijack, why not reboot?
>Could you point to a specific issue? Any chance it could be backported >to 1.0? This will mean less griff. http://www.google.ca/search?q=tdm+static+site:lists.digium.com&hl=en&lr=&rls =GGLD,GGLD:2004-23,GGLD:en&start=10&sa=N >When do you reboot? every day? Yes I do but the problem, for me, manifests itself every 1+N days so reboot every day preempts this behavior since it *will* run fine for at least a day. It's when I let it sit for 3 or 4 days that it happens. Zaptel reload works too, but might as well reboot since it's just sitting there from 10 PM to 6 AM. AFAIC, it's actually minor, we run 4 cordless phones that are used casually, a few times a day so no biggie if the problem happens during business hours. It does not affect any other operation of the server, SIP & IAX & SpanDSP, Sendmail, cdr, everything is 100%. This is the only fly in the ointment. ___ --Bandwidth and Colocation sponsored by Easynews.com -- Asterisk-Users mailing list Asterisk-Users@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
Re: [Asterisk-Users] Asterisk 1.0.9 long term stability <--thread hijack, why not reboot?
Andrew Kohlsmith wrote: On Thursday 15 September 2005 11:38, Paul wrote: They designed it to be shut down. I guess that means it doesn't just roll over like a dead cow. Actually dead cows aren't back-heavy. They typically just keep whatever position they were in when they took their last breath, much like the telco crosspoint switches. :-) In order to argue that point I would have to do some rather inhumane research :-D You wouldn't design a crane controller so that it releases the load on reboot and then tries to return the cable to the pre-reboot position. The same principle applies here. If it's mission-critical, you might have to spend more on the hardware. A good example would be crosspoint I agree -- You need to spend more time on both hardware and software. For me, a phone system is like a file server or network switch -- it is *not* meant to be rebooted. If it needs to be periodically power-cycled then address the problem, don't simply put a cron script in. I did hardware and software design for some devices that were usually placed in very remote areas(underwater, mountains, arctic are a few). We used a very low power clock device that would boot the cpu up. We did whatever needed to be done, set the clock registers for the next wakeup and shut down again. There were other ways to approach the problem, but this approach made coding easier, used less power and allowed us to get more functionality without increasing rom or ram size. If you only How did it save you ROM/RAM? I can see it saving having to put fancy power controller code and hardware in... Is that what you meant? The short answer is that the coding was more linear. Boot, run a state observer, setup the clock chip for next alarm and write an I/O bit that kills the power bus feeding the CPU area of the board. When data was being unloaded through the serial port, I skipped the final write and looped back to the top of the state observer. needed to take one simple measurement and store it to the ram, you could do a boot/run/shutoff every second and still achieve some additional battery runtime. Agreed but again -- you designed for this specific purpose. Asterisk isn't meant to boot up, answer the phone, process the call and shut down again until the next ring. (This would be an interesting approach to power savings though if your system boot time was fast enough and call volumes varied enough to make it worthwhile.) I have seen windows systems that boot up and crash. Would this be a good start? ___ --Bandwidth and Colocation sponsored by Easynews.com -- Asterisk-Users mailing list Asterisk-Users@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
RE: [Asterisk-Users] Asterisk 1.0.9 long term stability <--thread hijack, why not reboot?
>Agreed but again -- you designed for this specific purpose. Asterisk isn't >meant to boot up, answer the phone, process the call and shut down again >until the next ring. (This would be an interesting approach to power savings >though if your system boot time was fast enough and call volumes varied >enough to make it worthwhile.) That's a friggin cool idea. I wonder if someone on the list will be inspired enough to run with this: http://www.linuxbios.org/index.php/FAQ#What_is_LinuxBIOS.3F Current fastest boot time is 3s. You can have a flash filesystem for Asterisk, which is supported. How would ring detection work? You would need a "Wake on POTS" or something like that. ___ --Bandwidth and Colocation sponsored by Easynews.com -- Asterisk-Users mailing list Asterisk-Users@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
RE: [Asterisk-Users] Asterisk 1.0.9 long term stability <--thread hijack, why not reboot?
--On September 15, 2005 4:26:01 PM -0600 Colin Anderson <[EMAIL PROTECTED]> wrote: Agreed but again -- you designed for this specific purpose. Asterisk isn't meant to boot up, answer the phone, process the call and shut down again until the next ring. (This would be an interesting approach to power savings though if your system boot time was fast enough and call volumes varied enough to make it worthwhile.) That's a friggin cool idea. I wonder if someone on the list will be inspired enough to run with this: http://www.linuxbios.org/index.php/FAQ#What_is_LinuxBIOS.3F Current fastest boot time is 3s. You can have a flash filesystem for Asterisk, which is supported. How would ring detection work? You would need a "Wake on POTS" or something like that. Most modern motherboards with some sort of integrated AMR/Modem platform support wake on interrupt for com port or for modem activity... an old style modem, wake on irq for comhackish. :) i'm sure that someone makes a 'ring to restart' box thoguh too... ___ --Bandwidth and Colocation sponsored by Easynews.com -- Asterisk-Users mailing list Asterisk-Users@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
RE: [Asterisk-Users] Asterisk 1.0.9 long term stability <--thread hijack, why not reboot?
--On September 14, 2005 10:34:29 AM -0600 Colin Anderson <[EMAIL PROTECTED]> wrote: Disclaimer: Not a troll I'm curious as to this obsession with uptime is. All of the posts of this type are along the lines of "After X days, Y thing does not work but if I reload or reboot, it's OK" - so why not cron a reboot? Is it considered bad form or something like that? I reboot every night whether it is needed or not, not afraid to admit it, and everything works fine for me. You obviously come from a land of Windows. I have machines that are up for years at a time internally, and externally months, depending on how often security patches or other critical upgrades need applying. That's how computers should run. MS is the crap that gets people into this damned bad habit of oh i rebooted and it's fixed. No it's NOT fixed, you just got rid of the symptoms, the BUG is still there. For most UNIX and derivitaves/workalikes reboots are unnecessary. Only if something is broken, or seriously wedged. We also do the "Sunday reboot" of all of our Windows servers as well as restarting all of the critical services such as IIS , SQL, Exchange etc nightly. It helps, a lot (Exchange is a notorious memory leaker) Yup, MS you need to because MS is broken. I've also heard it said, something along the lines of: "If you have to reboot, your server isn't set up correctly" to which I say piffle. Even NASA has rebooted the Mars probes after they land and I understand that they run VXWorks, incidentally, the same RTOS that my Mitel 3300 uses, and *even Mitel* recommends periodic reboots, which we duly cron every night, 2 AM. Mitel isn't exactly known for telco grade operations. And telco is usually the one that everyone quotes as being some of the most reliable systems in the world. Imagine if Cisco or Juniper had this flawed mentality? Or Fore? Or IBM? Or Acatel? Or Nortel? Yes I probably sound like a kook or a troll but so be it. If a system is doing repeatable operations, and cleaning up correctly after itself, and doing periodic maintenance correctly, a reboot should never, under any circumstances be necessary. Even restarting the services should be a rare item (hence one of my beefs with Apache mod_ssl). 24/7/365 installs aside, is there a reason why reboots seem to be frowned upon? Again, not trolling, just curious. ___ --Bandwidth and Colocation sponsored by Easynews.com -- Asterisk-Users mailing list Asterisk-Users@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
