Menu
▾
▴
Re: [Astlinux-devel] Segfault Crash on astlinux-1.3-4232-509fbe
|
From: Josh A. <jm...@ho...> - 2019-06-19 13:51:44
|
That new printout at login is quite helpful! RAM: 1959 MB I've attached my modules.conf. The only changes I believe I've made to it are the two at the bottom. chan_xgcp is a module made by Karl Brose as a replacement for chan_mgcp. As such, I added the noload for chan_mgcp since the two can't be running at the same time. However, I added a noload for chan_xgcp and found that it was preventing asterisk 16 from starting at all. ________________________________ From: Lonnie Abelbeck <li...@lo...> Sent: Wednesday, June 19, 2019 9:34 AM To: AstLinux Developers Mailing List Subject: Re: [Astlinux-devel] Segfault Crash on astlinux-1.3-4232-509fbe Josh, I just tested with a 32-bit test box with Asterisk 16 -- upgrade-run-image upgrade https://s3.amazonaws.com/beta.astlinux-project/ast16-firmware-1.x -- Asterisk behaved just fine. Possibly you have some modules.conf unneeded "noload" ? How much RAM is in your box ? Lonnie > On Jun 19, 2019, at 8:22 AM, Lonnie Abelbeck <li...@lo...> wrote: > > Hi Josh, > > Something is not right here... > > Testing tips: > > make sure asterisk is stopped (using CLI) > -- > service asterisk stop > -- > > Then start via > -- > asterisk -c > -- > > That will give you more context where the crash is occurring. > > BTW, what hardware are you using ? > > Lonnie > > > > >> On Jun 19, 2019, at 8:15 AM, Josh Alberts <jm...@ho...> wrote: >> >> I tried the ast16 devel build, and this time, Asterisk is crashing before I get a chance to do anything. From dmesg (I tried restarting it twice): >> >> [ 44.698144] asterisk[1476]: segfault at 3c00 ip 081ee3f3 sp bfea5a10 error 4 in asterisk[8048000+2d2000] >> [ 75.397478] asterisk[1621]: segfault at 3c00 ip 081ee3f3 sp bfae0140 error 4 in asterisk[8048000+2d2000] >> [ 83.550674] asterisk[1671]: segfault at 3c00 ip 081ee3f3 sp bfdfff10 error 4 in asterisk[8048000+2d2000] >> >> >> From: Lonnie Abelbeck <li...@lo...> >> Sent: Tuesday, June 18, 2019 4:54 PM >> To: AstLinux Developers Mailing List >> Subject: Re: [Astlinux-devel] Segfault Crash on astlinux-1.3-4232-509fbe >> >> Hi Josh, >> >> As a mini-clue "libjansson.so" is only referenced by the "asterisk" binary, not by any of the asterisk modules. >> >> You might test again but use ast16 ... your Asterisk 13 configs should be fine for a quick test. >> >> Understand you have a somewhat unique setup using DAHDI, chan_sip and chan_pjsip all at the same time. And on 32-bit hardware. Agreed it should all work though. >> >> Lonnie >> >> >> >>> On Jun 18, 2019, at 3:16 PM, Lonnie Abelbeck <li...@lo...> wrote: >>> >>> Hi Josh, >>> >>> If you can, more clues would be great. >>> >>> Like if it is precisely reproducible, or if the crash varies ... and what is going on in the dialplan. >>> >>> Lonnie >>> >>> >>> >>> >>>> On Jun 18, 2019, at 3:10 PM, Josh Alberts <jm...@ho...> wrote: >>>> >>>> I'm using both PJSIP and chan_sip (on different ports, of course). >>>> >>>> Come to think of it, all of the test calls that I generated either originated or terminated to/from the same Dahdi channel, so maybe Dahdi is playing into this? Wish I could have tested more but I had to get the system back up. Like I said, I would be glad to upgrade again and investigate further if that would help. >>>> >>>> From: Michael Keuter <li...@mk...> >>>> Sent: Tuesday, June 18, 2019 4:06 PM >>>> To: AstLinux Developers Mailing List >>>> Subject: Re: [Astlinux-devel] Segfault Crash on astlinux-1.3-4232-509fbe >>>> >>>> >>>>> Am 18.06.2019 um 21:56 schrieb Josh Alberts <jm...@ho...>: >>>>> >>>>> I tried upgrading from astlinux-1.3.5.2 i686 to astlinux-1.3-4232-509fbe. When Asterisk receives a call, when a Dahdi channel goes off-hook, or basically in response to any other user-generated action, Asterisk immediately crashes and I see this in the dmesg output: >>>>> >>>>> segfault at 1 ip 40421dcd sp 4334a990 error 4 in libjansson.so.4.11.1[4041d000+b000] >>>>> >>>>> I reverted back to 1.3.5.2 (Thanks for the Revert to Previous feature!) but I could try the development build again if that would help you guys figure out what's going on. >>>>> >>>>> Josh >>>> >>>> So that means: >>>> >>>> Asterisk 13.24.1 versus Asterisk 13.27.0 >>>> >>>> Are you using PJSIP already or chan_sip? >>>> >>>> I have been running that build on a few boxes successfully for a week, although none of my boxes uses DAHDI … >>>> Does anyone else on this list is using Asterisk 13.27.0 together with DAHDI? >>>> >>>> Michael >>>> >>>> http://www.mksolutions.info >>>> >>>> >>>> >>>> >>>> >>>> _______________________________________________ >>>> Astlinux-devel mailing list >>>> Ast...@li... >>>> https://lists.sourceforge.net/lists/listinfo/astlinux-devel >>>> _______________________________________________ >>>> Astlinux-devel mailing list >>>> Ast...@li... >>>> https://lists.sourceforge.net/lists/listinfo/astlinux-devel >>> >>> >>> >>> _______________________________________________ >>> Astlinux-devel mailing list >>> Ast...@li... >>> https://lists.sourceforge.net/lists/listinfo/astlinux-devel >> >> >> >> _______________________________________________ >> Astlinux-devel mailing list >> Ast...@li... >> https://lists.sourceforge.net/lists/listinfo/astlinux-devel >> _______________________________________________ >> Astlinux-devel mailing list >> Ast...@li... >> https://lists.sourceforge.net/lists/listinfo/astlinux-devel > > > > _______________________________________________ > Astlinux-devel mailing list > Ast...@li... > https://lists.sourceforge.net/lists/listinfo/astlinux-devel _______________________________________________ Astlinux-devel mailing list Ast...@li... https://lists.sourceforge.net/lists/listinfo/astlinux-devel |
