Menu
▾
▴
Re: [Astlinux-devel] Segfault Crash on astlinux-1.3-4232-509fbe
|
From: Josh A. <jm...@ho...> - 2019-06-19 18:51:15
|
Perhaps it would have been better if I said that everything is working fine in 13se except PJSIP, which I knew wouldn't work. ________________________________ From: Michael Keuter <li...@mk...> Sent: Wednesday, June 19, 2019 2:49 PM To: AstLinux Developers Mailing List Subject: Re: [Astlinux-devel] Segfault Crash on astlinux-1.3-4232-509fbe Am 19.06.2019 um 20:40 schrieb Josh Alberts <jm...@ho...<mailto:jm...@ho...>>: Lonnie, things seem to be working fine with 13se. It uses an older Asterisk 13 version (13.23.1) and PJSIP is not included! From: Lonnie Abelbeck <li...@lo...<mailto:li...@lo...>> Sent: Wednesday, June 19, 2019 12:13 PM To: AstLinux Developers Mailing List Subject: Re: [Astlinux-devel] Segfault Crash on astlinux-1.3-4232-509fbe Hi Josh, If you have the time, can you also test the ast13se version: -- upgrade-run-image upgrade https://s3.amazonaws.com/beta.astlinux-project/ast13se-firmware-1.x -- Granted chan_pjsip will not work with this version, but see if you are getting the same DAHDI crash. Thanks again for your testing help. Lonnie On Jun 19, 2019, at 8:47 AM, Josh Alberts <jm...@ho...<mailto:jm...@ho...>> wrote: Lonnie, I'm running an HP t5740 thinclient (with a 32-bit CPU) with a Digium TE122P card (firmware 1.12). I never knew about the asterisk -c command. That's very helpful. Thanks! Unfortunately, I'm not getting too far: pbx ~ # asterisk -c Asterisk 16.4.0, Copyright (C) 1999 - 2018, Digium, Inc. and others. Created by Mark Spencer <mar...@di...<mailto:mar...@di...>> Asterisk comes with ABSOLUTELY NO WARRANTY; type 'core show warranty' for details. This is free software, with components licensed under the GNU General Public License version 2 and other licenses; you are welcome to redistribute it under certain conditions. Type 'core show license' for details. ========================================================================= XSLT support not found. XML documentation may be incomplete. PBX UUID: 79ef0c49-1727-4912-907a-a3954cb63520 [Jun 19 09:33:31] NOTICE[1642]: loader.c:2377 load_modules: 323 modules will be loaded. Segmentation fault I have a custom module that I suspect could be causing issues. That's really of no concern here - I'll just disable it if that prevents a roadblock to upgrade. When I throw a noload for it into modules.conf, I get all the way: pbx ~ # asterisk -c Asterisk 16.4.0, Copyright (C) 1999 - 2018, Digium, Inc. and others. Created by Mark Spencer <mar...@di...<mailto:mar...@di...>> Asterisk comes with ABSOLUTELY NO WARRANTY; type 'core show warranty' for details. This is free software, with components licensed under the GNU General Public License version 2 and other licenses; you are welcome to redistribute it under certain conditions. Type 'core show license' for details. ========================================================================= XSLT support not found. XML documentation may be incomplete. PBX UUID: 79ef0c49-1727-4912-907a-a3954cb63520 [Jun 19 09:39:43] NOTICE[2020]: loader.c:2377 load_modules: 322 modules will be loaded. [ Initializing Custom Configuration Options ] [Jun 19 09:39:47] WARNING[2020]: res_odbc.c:606 load_odbc_config: The 'pooling', 'shared_connections', 'limit', and 'idlecheck' options were replaced by 'max_connections'. See res_odbc.conf.sample. [Jun 19 09:39:47] WARNING[2020]: res_odbc.c:606 load_odbc_config: The 'pooling', 'shared_connections', 'limit', and 'idlecheck' options were replaced by 'max_connections'. See res_odbc.conf.sample. [Jun 19 09:39:47] WARNING[2020]: features_config.c:1533 unsupported_handler: Parkinglots are no longer configurable in features.conf; parking is now handled by res_parking.conf [Jun 19 09:39:47] WARNING[2020]: features_config.c:1537 unsupported_handler: The option 'parkext' is no longer configurable in features.conf. [Jun 19 09:39:47] WARNING[2020]: features_config.c:1537 unsupported_handler: The option 'parkpos' is no longer configurable in features.conf. [Jun 19 09:39:47] WARNING[2020]: features_config.c:1537 unsupported_handler: The option 'context' is no longer configurable in features.conf. [Jun 19 09:39:47] NOTICE[2020]: dnsmgr.c:493 do_reload: Managed DNS entries will be refreshed every 300 seconds. [Jun 19 09:39:47] ERROR[2020]: cel.c:428 ast_cel_str_to_event_type: Unknown event name 'BRIDGE_START' [Jun 19 09:39:47] ERROR[2020]: config_options.c:798 aco_process_var: Error parsing events=APP_START,CHAN_START,CHAN_END,ANSWER,HANGUP,BRIDGE_START,BRIDGE_END at line 76 of [Jun 19 09:39:47] ERROR[2020]: config_options.c:544 process_category: In cel.conf: Processing options for general failed [Jun 19 09:39:47] NOTICE[2020]: cel.c:1614 load_module: Failed to process CEL configuration; using defaults [Jun 19 09:39:47] NOTICE[2020]: cdr.c:4508 cdr_toggle_runtime_options: CDR simple logging enabled. [Jun 19 09:39:48] ERROR[2020]: res_resolver_unbound.c:417 unbound_config_preapply: Failed to set hosts file to 'system' in unbound resolver: syntax error [Jun 19 09:39:48] NOTICE[2020]: res_smdi.c:1424 load_module: No SMDI interfaces are available to listen on, not starting SMDI listener. [Jun 19 09:39:48] WARNING[2020]: res_phoneprov.c:1230 get_defaults: Unable to find a valid server address or name. SIP channel loading... [Jun 19 09:39:48] NOTICE[2020]: chan_sip.c:31843 build_peer: The 'username' field for sip peers has been deprecated in favor of the term 'defaultuser' [Jun 19 09:39:48] ERROR[2020]: chan_motif.c:2681 custom_connection_handler: Connection 'local-jabber-account' configured on endpoint 'jingle-endpoint' could not be found [Jun 19 09:39:48] ERROR[2020]: config_options.c:798 aco_process_var: Error parsing connection=local-jabber-account at line 81 of [Jun 19 09:39:48] ERROR[2020]: config_options.c:572 process_category: In motif.conf: Processing options for jingle-endpoint failed [Jun 19 09:39:48] ERROR[2020]: chan_motif.c:2756 load_module: Unable to read config file motif.conf. Module loaded but not running. [Jun 19 09:39:48] NOTICE[2072]: chan_sip.c:24881 handle_response_peerpoke: Peer 'joshcisco' is now Reachable. (12ms / 6000ms) [Jun 19 09:39:49] ERROR[2020]: ari/config.c:312 process_config: No configured users for ARI [Jun 19 09:39:49] NOTICE[2020]: confbridge/conf_config_parser.c:2326 verify_default_profiles: Adding default_menu menu to app_confbridge [Jun 19 09:39:49] ERROR[2020]: config_options.c:528 process_category: Could not find config type for category 'agents' in 'agents.conf' [Jun 19 09:39:49] ERROR[2020]: app_agent_pool.c:2693 load_module: Unable to load config. Not loading module. [Jun 19 09:39:49] NOTICE[2020]: cel_custom.c:95 load_config: No mappings found in cel_custom.conf. Not logging CEL to custom CSVs. [Jun 19 09:39:49] ERROR[2020]: codec_dahdi.c:813 find_transcoders: Failed to open /dev/dahdi/transcode: No such file or directory [Jun 19 09:39:49] WARNING[2020]: app_voicemail.c:14216 actual_load_config: maxsilence should be less than minsecs or you may get empty messages [Jun 19 09:39:49] WARNING[2020]: res_hep_rtcp.c:161 load_module: res_hep is disabled; declining module load [Jun 19 09:39:49] WARNING[2020]: res_hep_pjsip.c:236 load_module: res_hep is disabled; declining module load [Jun 19 09:39:49] WARNING[2020]: loader.c:2381 load_modules: Some non-required modules failed to load. [Jun 19 09:39:49] ERROR[2020]: loader.c:2396 load_modules: res_resolver_unbound declined to load. [Jun 19 09:39:49] ERROR[2020]: loader.c:2396 load_modules: chan_motif declined to load. [Jun 19 09:39:49] ERROR[2020]: loader.c:2396 load_modules: res_pjsip_transport_websocket declined to load. [Jun 19 09:39:49] ERROR[2020]: loader.c:2396 load_modules: app_agent_pool declined to load. [Jun 19 09:39:49] ERROR[2020]: loader.c:2396 load_modules: cel_sqlite3_custom declined to load. [Jun 19 09:39:49] ERROR[2020]: loader.c:2396 load_modules: cdr_sqlite3_custom declined to load. [Jun 19 09:39:49] ERROR[2020]: loader.c:2396 load_modules: res_hep_rtcp declined to load. [Jun 19 09:39:49] ERROR[2020]: loader.c:2396 load_modules: res_hep_pjsip declined to load. Asterisk Ready. But then as soon as I go off-hook on a Dahdi channel: *CLI> Segmentation fault It's really starting to seem (to me) like this is a Dahdi isssue. I'm able to place calls in and out through chan_sip and chan_pjsip. It's only Dahdi (going off-hook or trying to call a Dahdi channel) that seems to have issues. With ast16, Dahdi is triggering the same jansson error in dmesg: [ 732.177325] asterisk[2437]: segfault at 1 ip b73d2dcd sp b39f38e0 error 4 in libjansson.so.4.11.1[b73ce000+b000] From: Lonnie Abelbeck <li...@lo...<mailto:li...@lo...>> Sent: Wednesday, June 19, 2019 9:22 AM To: AstLinux Developers Mailing List Subject: Re: [Astlinux-devel] Segfault Crash on astlinux-1.3-4232-509fbe 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...<mailto: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...<mailto: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...<mailto: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...<mailto: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...<mailto: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...<mailto: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 Michael http://www.mksolutions.info |
