lol that was me ironic that I just hijacked this thread and said that reboots are not a bad thing! It's true I do have 30 IAX/SIP boxen that I don't reboot, they are all "slave" servers to the IAX/SIP/PRI "master" server, which I *do* reboot every night. The 30 boxen I did by cloning a single hdd and making specific changes to each box.
this underscores the importance of documenting everything, which I did for the 30, after I had what I felt was a good config, I documented each single step to clone the config, getting right down to things like reflashing the bios, and making sure that a specific brand and rev of nic was in a specific slot, and that nic used a specific IRQ, and that certain hdw like the onboard sound card in the chassis was disabled. Armed with such a document, a third party can come in and easily re-create your work, or troubleshoot it. The trick is getting the config just right in the first place. As I have said before, a lot of these issues can be resolved before they happen simply by not using random hardware and random distro, and to that end, it might serve Digium well to have a posted HCL and / or sell a certified barebones box and certify Asterisk on a specific RedHat and / or Debian, and if you use anything else, well, tough. I, myself, would prefer to buy this cerified solution instead of sweating through a from-scratch config and crossing your fingers and hoping it is stable. I'm sure a lot of other guys on this list would jump on it as well. -----Original Message----- From: Noah Miller [mailto:[EMAIL PROTECTED] Sent: Wednesday, September 14, 2005 11:00 AM To: [email protected] Subject: [Asterisk-Users] Re: Asterisk 1.0.9 long term stability > 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. It's not necessarily any specific component of asterisk or version of asterisk that can cause instability. It might have nothing to do with asterisk. One of our boxes is running 1.0.7 (with SIP phones) and it has run like a champ for months with no incidents. I had another box that crashed frequently until I was able to come up with a good combination of hardware and software versions. There are so many factors involved. I read a post on this list not too long ago that said the poster has about 30 different asterisk boxes running, and they are all identical - asterisk version, asterisk patches, OS version, OS patches, telephony hardware, general computer hardware, right on down to the bios revision on the motherboard. That was the only way he was able to maintain consistent stability across all 30 boxes. I wish I had time to be that organized! - Noah _______________________________________________ --Bandwidth and Colocation sponsored by Easynews.com -- Asterisk-Users mailing list [email protected] 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 [email protected] http://lists.digium.com/mailman/listinfo/asterisk-users To UNSUBSCRIBE or update options visit: http://lists.digium.com/mailman/listinfo/asterisk-users
