I have deployed several 1.8.3.2 systems as upgrades of customers systems and now I am seeing random crashes. For some reason the builds lock up and stop taking sip connections. Existing calls stay on but when the user hangs up no new calls or reg attempts work. In most cases a "core restart now" cleans things up. Some times I have to kill the asterisk process. The stability of 1.8.2 was poor but it is worse with 1.8.3.2 any ideas of how I can approach solving this. Thanks Bryant -------------- next part -------------- An HTML attachment was scrubbed... URL: <http://lists.digium.com/pipermail/asterisk-users/attachments/20110405/c91f1564/attachment.htm>
On Tuesday 05 April 2011 20:10:48 Bryant Zimmerman wrote:> I have deployed several 1.8.3.2 systems as upgrades of customers systems > and now I am seeing random crashes. For some reason the builds lock up > and stop taking sip connections. Existing calls stay on but when the > user hangs up no new calls or reg attempts work. In most cases a "core > restart now" cleans things up. Some times I have to kill the asterisk > process. The stability of 1.8.2 was poor but it is worse with 1.8.3.2 > any ideas of how I can approach solving this.This sounds like a deadlock of some kind. Asterisk has a debugging facility built-in for finding this type of problem, but you will need to compile in DONT_OPTIMIZE and DEBUG_THREADS. Also, it would be helpful, but not entirely necessary, to compile in BETTER_BACKTRACES. Once the problem occurs with the recompiled binary, issuing a "core show locks" should turn up an indication of where the problem lies. -- Tilghman
On Tue, 2011-04-05 at 21:10 -0400, Bryant Zimmerman wrote:> I have deployed several 1.8.3.2 systems as upgrades of customers > systems and now I am seeing random crashes. For some reason the builds > lock up and stop taking sip connections. Existing calls stay on but > when the user hangs up no new calls or reg attempts work. In most > cases a "core restart now" cleans things up. Some times I have to kill > the asterisk process. The stability of 1.8.2 was poor but it is worse > with 1.8.3.2 any ideas of how I can approach solving this. > > Thanks > > Bryant > --Could it be this issue? https://issues.asterisk.org/view.php?id=18818 Mind you, this one will only affect you if you use RealTime architecture -- Ishfaq Malik Software Developer PackNet Ltd Office: 0161 660 3062
We also see the random freeze of asterisk 1.8.3.2. We do use realtime. I have just applied the patch and will see how our environment holds. I will report back to the issue mentioned by Ishfaq Michel Verbraak *InterCommIT bv* ** On 06-04-11 09:44, Ishfaq Malik wrote:> On Tue, 2011-04-05 at 21:10 -0400, Bryant Zimmerman wrote: >> I have deployed several 1.8.3.2 systems as upgrades of customers >> systems and now I am seeing random crashes. For some reason the builds >> lock up and stop taking sip connections. Existing calls stay on but >> when the user hangs up no new calls or reg attempts work. In most >> cases a "core restart now" cleans things up. Some times I have to kill >> the asterisk process. The stability of 1.8.2 was poor but it is worse >> with 1.8.3.2 any ideas of how I can approach solving this. >> >> Thanks >> >> Bryant >> -- > Could it be this issue? > > https://issues.asterisk.org/view.php?id=18818 > > Mind you, this one will only affect you if you use RealTime architecture >-------------- next part -------------- An HTML attachment was scrubbed... URL: <http://lists.digium.com/pipermail/asterisk-users/attachments/20110406/57f866ec/attachment.htm>
On 4/5/11 6:10 PM, Bryant Zimmerman wrote:> I have deployed several 1.8.3.2 systems as upgrades of customers systems and now I > am seeing random crashes. For some reason the builds lock up and stop taking sip > connections. Existing calls stay on but when the user hangs up no new calls or reg > attempts work. In most cases a "core restart now" cleans things up. Some times I > have to kill the asterisk process. The stability of 1.8.2 was poor but it is worse > with 1.8.3.2 any ideas of how I can approach solving this.We've upgraded our system over the weekend from 1.4.35 to 1.8.3.2 For the past couple of days, we had several random hangs(most of the time "core stop now" didn't work, I had to kill -9 the process) Also the PRI behavior seems to be slightly different, we can't hear any early media sounds on 800 numbers that goes through AT&T. I finally downgraded it back to 1.6.2.17, now everything work. -- Edwin Lam <edwin.lam at officegeneral.com> Systems Engineer, OfficeWyze, Inc. Ph: +1 415 439 4988 Fax: +1 415 283 3370 http://pgpkeys.mit.edu:11371/pks/lookup?op=get&search=0xD6506D20
On 4/5/11 6:10 PM, Bryant Zimmerman wrote:> I have deployed several 1.8.3.2 systems as upgrades of customers systemsand now I> am seeing random crashes. For some reason the builds lock up and stoptaking sip> connections. Existing calls stay on but when the user hangs up no newcalls or reg> attempts work. In most cases a "core restart now" cleans things up. Sometimes I> have to kill the asterisk process. The stability of 1.8.2 was poor but itis worse> with 1.8.3.2 any ideas of how I can approach solving this.From: "Edwin Lam" <edwin.lam at officegeneral.com> Sent: Wednesday, April 06, 2011 5:37 PM We've upgraded our system over the weekend from 1.4.35 to 1.8.3.2 For the past couple of days, we had several random hangs(most of the time "core stop now" didn't work, I had to kill -9 the process) Also the PRI behavior seems to be slightly different, we can't hear any early media sounds on 800 numbers that goes through AT&T. I finally downgraded it back to 1.6.2.17, now everything work. Edwin Thanks for your response. I have added the patch for 18818 per Michel Verbrask's recomendation. It appers that it has made quite a difference. I don't have an PRI connections as all of our PRI's are connected via SIP gateways. I did run into serveral instances wher I had to kill -9 the process as well but post patch I have been in good shape know on wood. I hope there will be a new release that will address the stability issues very soon if they release 1.8.4 without cleaning this up I won't move unitl it is addressed. For Now 1.8.3..2 is very bad. Thanks Bryant -------------- next part -------------- An HTML attachment was scrubbed... URL: <http://lists.digium.com/pipermail/asterisk-users/attachments/20110406/aedbbd9b/attachment.htm>
On Apr 6, 2011, at 8:54 PM, Edwin Lam <edwin.lam at officegeneral.com> wrote:> On 4/6/11 3:02 PM, Bryant Zimmerman wrote: >> >> Thanks for your response. I have added the patch for 18818 per >> Michel Verbrask's >> recomendation. It appers that it has made quite a difference. I >> don't have an PRI >> connections as all of our PRI's are connected via SIP gateways. I >> did run into >> serveral instances wher I had to kill -9 the process as well but >> post patch I have >> been in good shape know on wood. I hope there will be a new release >> that will >> address the stability issues very soon if they release 1.8.4 >> without cleaning this >> up I won't move unitl it is addressed. > > looking back at the messages file for the past 2 days. it > just hanged on totally different events none of which related > to Local channels. > > as far as the PRI not hearing early media issue. here's the > excerpt from the messages file after "pri debug on" command: > > ********************* > > -- Executing [18008291011 at out_going_x:1] Dial("SIP/... Parts Removed see origional response> -- Processing IE 30 (cs0, Progress Indicator) > -- PROGRESS with cause code 127 received > -- DAHDI/34-1 is making progress passing it to SIP/4988-6-00000b45 > > *********************************** > > i used the same SIP station to dial the same 800 number > on both versions (1.8.3.2 & 1.6.2.17). the output are > pretty much identical except on 1.8.3.2, after the > "PROGRESS with cause code 127..." message. i would hear > nothing until the other side timed out & hang up, whereas on > 1.6.2.17. i got the "DAHDI/... is making progress passing it to > SIP..." > message and can hear the early media from the other side. > > >> For Now 1.8.3..2 is very bad. > > agreed...From: "Satish Patel" <satish_lx at hotmail.com> Sent: Thursday, April 07, 2011 8:22 AM Oh! Boy, Is it ture 1.8.3 is unstable? We are planning to put this in production. Please suggest me what should I do? Satish For me 1.8.3.2 has been the worst build that I have tried to use as far a stability in a very long time. We are having issues with deadlocks and voicemail. I don't have a good option for you if you want to run 1.8 currently the most stable release version I have found is 1.8.2.3 but I am having the Voicemail issues there as well. Things like messages not deleting propperly and hanging up the mail box so users can't check them. -------------- next part -------------- An HTML attachment was scrubbed... URL: <http://lists.digium.com/pipermail/asterisk-users/attachments/20110407/0993ebe7/attachment.htm>
On Apr 7, 2011, at 8:51 AM, Ishfaq Malik <ish at pack-net.co.uk> wrote:> On Thu, 2011-04-07 at 08:37 -0400, Bryant Zimmerman wrote: >> >> On Apr 6, 2011, at 8:54 PM, Edwin Lam <edwin.lam at officegeneral.com> >> wrote: >> >>> On 4/6/11 3:02 PM, Bryant Zimmerman wrote: >>>> >>>> Thanks for your response. I have added the patch for 18818 per >>>> Michel Verbrask's >>>> recomendation. It appers that it has made quite a difference. I >>>> don't have an PRI >>>> connections as all of our PRI's are connected via SIP gateways. I >>>> did run into >>>> serveral instances wher I had to kill -9 the process as well but >>>> post patch I have >>>> been in good shape know on wood. I hope there will be a new >> release >>>> that will >>>> address the stability issues very soon if they release 1.8.4 >>>> without cleaning this >>>> up I won't move unitl it is addressed. >>> >>> looking back at the messages file for the past 2 days. it >>> just hanged on totally different events none of which related >>> to Local channels. >>> >>> as far as the PRI not hearing early media issue. here's the >>> excerpt from the messages file after "pri debug on" command: >>> >>> ********************* >>> >>> -- Executing [18008291011 at out_going_x:1] Dial("SIP/ >> >> ... Parts Removed see origional response >> >>> -- Processing IE 30 (cs0, Progress Indicator) >>> -- PROGRESS with cause code 127 received >>> -- DAHDI/34-1 is making progress passing it to SIP/4988-6-00000b45 >>> >>> *********************************** >>> >>> i used the same SIP station to dial the same 800 number >>> on both versions (1.8.3.2 & 1.6.2.17). the output are >>> pretty much identical except on 1.8.3.2, after the >>> "PROGRESS with cause code 127..." message. i would hear >>> nothing until the other side timed out & hang up, whereas on >>> 1.6.2.17. i got the "DAHDI/... is making progress passing it to >>> SIP..." >>> message and can hear the early media from the other side. >>> >>> >>>> For Now 1.8.3..2 is very bad. >>> >>> agreed... >> >> From: "Satish Patel" <satish_lx at hotmail.com> >> Sent: Thursday, April 07, 2011 8:22 AM >> Oh! Boy, >> >> Is it ture 1.8.3 is unstable? We are planning to put this in >> production. Please suggest me what should I do? >> >> >> Satish >> >> For me 1.8.3.2 has been the worst build that I have tried to use as >> far a stability in a very long time. We are having issues >> with deadlocks and voicemail. >> I don't have a good option for you if you want to run 1.8 currently >> the most stable release version I have found is 1.8.2.3 but I am >> having the Voicemail issues there as well. >> Things like messages not deleting propperly and hanging up the mail >> box so users can't check them. > > 1.8.2 is unusable if you use RealTime without the patch in this issue > > https://issues.asterisk.org/bug_view_advanced_page.php?bug_id=18403 > >From: "Satish Patel" <satish_lx at hotmail.com> Sent: Thursday, April 07, 2011 9:06 AM We don't have realtime configuration everything is in plain text file. Is 1.8.3 has realtime issue or general issue? Satish I have seen my issues with the realtime disabled and using just plain text. The issues get worse for me when we move to our realtime confgs. So from my perspective I would say you might get farther with realtime off but I would not bank on it. -------------- next part -------------- An HTML attachment was scrubbed... URL: <http://lists.digium.com/pipermail/asterisk-users/attachments/20110407/dc888849/attachment.htm>
2011/4/7 Bryant Zimmerman <BryantZ at zktech.com>> > For me 1.8.3.2 has been the worst build that I have tried to use as far a > stability in a very long time.Hi, If my memory serves me right, first usable 1.4 version was 1.4.21 or something. Time will tell if things are improving and hopefully next 1.10 would be usable from the very start (from 1.10.0). Is the asterisk testing framework easy enough to work with so that we could feed new tests into it and help devs to identify such regressions before GA release ? Cheers -------------- next part -------------- An HTML attachment was scrubbed... URL: <http://lists.digium.com/pipermail/asterisk-users/attachments/20110407/d9127bbd/attachment.htm>
_____ From: asterisk-users-bounces at lists.digium.com [mailto:asterisk-users-bounces at lists.digium.com] On Behalf Of Olivier Sent: Thursday, April 07, 2011 10:27 AM To: bryantz at zktech.com; Asterisk Users Mailing List - Non-Commercial Discussion Subject: Re: [asterisk-users] Asterisk 1.8.3 2011/4/7 Bryant Zimmerman <BryantZ at zktech.com> For me 1.8.3.2 has been the worst build that I have tried to use as far a stability in a very long time. Hi, If my memory serves me right, first usable 1.4 version was 1.4.21 or something. Time will tell if things are improving and hopefully next 1.10 would be usable from the very start (from 1.10.0). Is the asterisk testing framework easy enough to work with so that we could feed new tests into it and help devs to identify such regressions before GA release ? Cheers [Danny Nicholas] 1.4.21 was the last ZAPTEL version. All versions from 1.4.22 forward have been DAHDI. Stability and usability depend on what variables you throw at it and your relative skill set. -------------- next part -------------- An HTML attachment was scrubbed... URL: <http://lists.digium.com/pipermail/asterisk-users/attachments/20110407/2768a4b5/attachment.htm>
2011/4/7 Danny Nicholas <danny at debsinc.com>> ------------------------------ > > *From:* asterisk-users-bounces at lists.digium.com [mailto: > asterisk-users-bounces at lists.digium.com] *On Behalf Of *Olivier > *Sent:* Thursday, April 07, 2011 10:27 AM > *To:* bryantz at zktech.com; Asterisk Users Mailing List - Non-Commercial > Discussion > *Subject:* Re: [asterisk-users] Asterisk 1.8.3 > > > > > > 2011/4/7 Bryant Zimmerman <BryantZ at zktech.com> > > > For me 1.8.3.2 has been the worst build that I have tried to use as far a > stability in a very long time. > > > Hi, > > If my memory serves me right, first usable 1.4 version was 1.4.21 or > something. > Time will tell if things are improving and hopefully next 1.10 would be > usable from the very start (from 1.10.0). > > Is the asterisk testing framework easy enough to work with so that we could > feed new tests into it and help devs to identify such regressions before GA > release ? > > Cheers > > > > *[Danny Nicholas] * > > *1.4.21 was the last ZAPTEL version. All versions from 1.4.22 forward > have been DAHDI. * >True.> *Stability and usability depend on what variables you throw at it and your > relative skill set.* >Of course> > -- > _____________________________________________________________________ > -- Bandwidth and Colocation Provided by http://www.api-digital.com -- > New to Asterisk? Join us for a live introductory webinar every Thurs: > http://www.asterisk.org/hello > > asterisk-users mailing list > To UNSUBSCRIBE or update options visit: > http://lists.digium.com/mailman/listinfo/asterisk-users >-------------- next part -------------- An HTML attachment was scrubbed... URL: <http://lists.digium.com/pipermail/asterisk-users/attachments/20110407/0e042add/attachment.htm>
---------------------------------------- From: "Chris Owen" <owenc at hubris.net> Sent: Thursday, April 07, 2011 9:37 AM To: "Asterisk Users Mailing List - Non-Commercial Discussion" <asterisk-users at lists.digium.com> Subject: Re: [asterisk-users] Asterisk 1.8.3 Best I can tell, multi-tenant parking also hasn't worked in any of the 1.8.x releases. Chris Chris I have not been able to get multi-tenant parking stable there either. I gave up yesterday on 1.8.3.2 as I could not get it stable with any number of patches I could find. I fell back to 1.8.2.3 as that is the last version that I have been able to run production with. My customers have now been happy for the last 24 hours. I also tried 1.8.4 rc and the stability did not appear to be much better then 1.8.3.2 I hope they don't release 1.8.4 until the stability issues are addressed more rc version with fixes would be ideal. The longer these items drag out the worse it gets for users to know what to use. I would ask the developers to hold 1.8.4 until some of these items can be fixed and rolled in. Bryant -------------- next part -------------- An HTML attachment was scrubbed... URL: <http://lists.digium.com/pipermail/asterisk-users/attachments/20110408/4ac28f0f/attachment.htm>