Menu
▾
▴
astlinux-devel — The AstLinux development environment, compilation, etc
You can subscribe to this list here.
| 2008 |
Jan
|
Feb
|
Mar
(41) |
Apr
(35) |
May
(18) |
Jun
(5) |
Jul
(4) |
Aug
(37) |
Sep
(9) |
Oct
(20) |
Nov
(50) |
Dec
(217) |
|---|---|---|---|---|---|---|---|---|---|---|---|---|
| 2009 |
Jan
(212) |
Feb
(76) |
Mar
(113) |
Apr
(88) |
May
(130) |
Jun
(54) |
Jul
(208) |
Aug
(223) |
Sep
(112) |
Oct
(63) |
Nov
(131) |
Dec
(103) |
| 2010 |
Jan
(247) |
Feb
(130) |
Mar
(43) |
Apr
(92) |
May
(40) |
Jun
(43) |
Jul
(43) |
Aug
(80) |
Sep
(44) |
Oct
(74) |
Nov
(21) |
Dec
(46) |
| 2011 |
Jan
(36) |
Feb
(11) |
Mar
(21) |
Apr
(33) |
May
(4) |
Jun
(12) |
Jul
(5) |
Aug
(20) |
Sep
|
Oct
(64) |
Nov
(26) |
Dec
(71) |
| 2012 |
Jan
(13) |
Feb
(24) |
Mar
(11) |
Apr
(2) |
May
(10) |
Jun
(5) |
Jul
(13) |
Aug
(7) |
Sep
(26) |
Oct
(22) |
Nov
(17) |
Dec
(16) |
| 2013 |
Jan
(6) |
Feb
(6) |
Mar
(6) |
Apr
(8) |
May
(20) |
Jun
|
Jul
(1) |
Aug
(4) |
Sep
(18) |
Oct
(3) |
Nov
(14) |
Dec
(33) |
| 2014 |
Jan
(26) |
Feb
(6) |
Mar
(69) |
Apr
(10) |
May
|
Jun
(8) |
Jul
(18) |
Aug
(22) |
Sep
(19) |
Oct
(17) |
Nov
|
Dec
(4) |
| 2015 |
Jan
(14) |
Feb
(18) |
Mar
|
Apr
|
May
(26) |
Jun
(8) |
Jul
(9) |
Aug
(10) |
Sep
(15) |
Oct
(2) |
Nov
(30) |
Dec
(33) |
| 2016 |
Jan
(1) |
Feb
(24) |
Mar
(19) |
Apr
(1) |
May
|
Jun
(3) |
Jul
(1) |
Aug
(1) |
Sep
(20) |
Oct
(5) |
Nov
(14) |
Dec
(4) |
| 2017 |
Jan
(15) |
Feb
(35) |
Mar
(10) |
Apr
(9) |
May
(14) |
Jun
(33) |
Jul
(1) |
Aug
(27) |
Sep
(7) |
Oct
|
Nov
(10) |
Dec
(15) |
| 2018 |
Jan
(29) |
Feb
|
Mar
(2) |
Apr
(1) |
May
(11) |
Jun
|
Jul
(1) |
Aug
(8) |
Sep
(11) |
Oct
(22) |
Nov
(9) |
Dec
(13) |
| 2019 |
Jan
(1) |
Feb
(7) |
Mar
(3) |
Apr
(21) |
May
(34) |
Jun
(36) |
Jul
(18) |
Aug
(17) |
Sep
(19) |
Oct
(8) |
Nov
(3) |
Dec
|
| 2020 |
Jan
|
Feb
(4) |
Mar
(8) |
Apr
(29) |
May
(50) |
Jun
(8) |
Jul
(2) |
Aug
(10) |
Sep
(1) |
Oct
(7) |
Nov
(9) |
Dec
(19) |
| 2021 |
Jan
(2) |
Feb
(9) |
Mar
(6) |
Apr
(21) |
May
(13) |
Jun
(11) |
Jul
(2) |
Aug
(1) |
Sep
(3) |
Oct
(26) |
Nov
(2) |
Dec
(16) |
| 2022 |
Jan
(8) |
Feb
(7) |
Mar
(1) |
Apr
(13) |
May
(1) |
Jun
(4) |
Jul
(4) |
Aug
(1) |
Sep
(1) |
Oct
|
Nov
|
Dec
(1) |
| 2023 |
Jan
(2) |
Feb
(3) |
Mar
(16) |
Apr
|
May
(2) |
Jun
(1) |
Jul
(4) |
Aug
(13) |
Sep
(8) |
Oct
(6) |
Nov
(4) |
Dec
|
| 2024 |
Jan
(3) |
Feb
(3) |
Mar
|
Apr
|
May
(1) |
Jun
|
Jul
(5) |
Aug
|
Sep
(1) |
Oct
|
Nov
(5) |
Dec
|
| 2025 |
Jan
(4) |
Feb
(2) |
Mar
|
Apr
(11) |
May
(1) |
Jun
(9) |
Jul
(18) |
Aug
|
Sep
|
Oct
|
Nov
|
Dec
|
|
From: Josh A. <jm...@ho...> - 2019-06-19 18:40:44
|
Lonnie, things seem to be working fine with 13se. ________________________________ From: Lonnie Abelbeck <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...> 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...> > 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...> > 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...> > 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...> 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 _______________________________________________ Astlinux-devel mailing list Ast...@li... https://lists.sourceforge.net/lists/listinfo/astlinux-devel |
|
From: Josh A. <jm...@ho...> - 2019-06-19 18:36:30
|
No, they aren't. At least, I made sure to configure them on separate ports. If there's a way I can confirm that, I'd be glad to check. ________________________________ From: The Cadillac Kid via Astlinux-devel <ast...@li...> Sent: Wednesday, June 19, 2019 2:34 PM To: AstLinux Developers Mailing List Cc: The Cadillac Kid Subject: Re: [Astlinux-devel] Segfault Crash on astlinux-1.3-4232-509fbe I came in late to this... his chan_sip and pjsip arent trying to both bind to the same service and port are they? ie both UDP 5060? On Wednesday, June 19, 2019, 2:06:51 PM EDT, Michael Keuter <li...@mk...> wrote: > Am 19.06.2019 um 19:53 schrieb Lonnie Abelbeck <li...@lo...<mailto:li...@lo...>>: > > Hi Josh, > > Hmmm, looking at your modules.conf, you have > -- > noload => res_timing_pthread.so > noload => res_timing_timerfd.so > -- > Why are those disabled ? > >> I have a custom module that I suspect could be causing issues. > > Adding custom binaries has me concerned ... what is the output of: > -- > show-union > -- > > Lonnie Because I guess he is using DAHDI as its timig source … >> On Jun 19, 2019, at 8:51 AM, Josh Alberts <jm...@ho...<mailto:jm...@ho...>> wrote: >> >> 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...<mailto: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...<mailto: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...<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 _______________________________________________ Astlinux-devel mailing list Ast...@li...<mailto:Ast...@li...> https://lists.sourceforge.net/lists/listinfo/astlinux-devel |
|
From: The C. K. <eld...@ya...> - 2019-06-19 18:34:53
|
I came in late to this... his chan_sip and pjsip arent trying to both bind to the same service and port are they? ie both UDP 5060?
On Wednesday, June 19, 2019, 2:06:51 PM EDT, Michael Keuter <li...@mk...> wrote:
> Am 19.06.2019 um 19:53 schrieb Lonnie Abelbeck <li...@lo...>:
>
> Hi Josh,
>
> Hmmm, looking at your modules.conf, you have
> --
> noload => res_timing_pthread.so
> noload => res_timing_timerfd.so
> --
> Why are those disabled ?
>
>> I have a custom module that I suspect could be causing issues.
>
> Adding custom binaries has me concerned ... what is the output of:
> --
> show-union
> --
>
> Lonnie
Because I guess he is using DAHDI as its timig source …
>> On Jun 19, 2019, at 8:51 AM, Josh Alberts <jm...@ho...> wrote:
>>
>> 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
Michael
http://www.mksolutions.info
_______________________________________________
Astlinux-devel mailing list
Ast...@li...
https://lists.sourceforge.net/lists/listinfo/astlinux-devel
|
|
From: Josh A. <jm...@ho...> - 2019-06-19 18:34:46
|
I can't remember if this modules.conf was auto-generated or if I copied it over from an older Astlinux machine. I don't know what res_timing_pthread.so or res_timing_timerfd.so are. I'm not sure what the stock modules.conf looks like, but I see no reason why I can't switch back to that if you think it would help (and if you can point me to it). Here's the output of show-union. I'm not exactly sure what this command does, but three of the results seem odd to me (noted below) /oldroot/mnt/asturw/mnt/usbhd/.wh.__dir_opaque /oldroot/mnt/asturw/mnt/usb/.wh.__dir_opaque /oldroot/mnt/asturw/mnt/usb/hd/.wh.__dir_opaque /oldroot/mnt/asturw/mnt/usb/hd/recordings/.wh.__dir_opaque /oldroot/mnt/asturw/mnt/usb/hd/recordings/20180116-213815-12108261879-t.wav (this is a recording made with mixmonitor) /oldroot/mnt/asturw/etc/udev/rules.d/70-persistent-net.rules /oldroot/mnt/asturw/etc/shadow /oldroot/mnt/asturw/etc/shadow- /oldroot/mnt/asturw/etc/passwd /oldroot/mnt/asturw/etc/passwd- /oldroot/mnt/asturw/etc/sudoers /oldroot/mnt/asturw/etc/group /oldroot/mnt/asturw/etc/group- /oldroot/mnt/asturw/etc/gshadow /oldroot/mnt/asturw/etc/gshadow- /oldroot/mnt/asturw/stat/var/www/admin/.htpasswd /oldroot/mnt/asturw/stat/var/lib/asterisk/agi-bin/pulsar.agi (custom AGI script I don't really use anymore) /oldroot/mnt/asturw/.rnd /oldroot/mnt/asturw/usr/lib/asterisk/modules/chan_xgcp.so (this is the module I disabled in modules.conf) ________________________________ From: Lonnie Abelbeck <li...@lo...> Sent: Wednesday, June 19, 2019 1:53 PM To: AstLinux Developers Mailing List Subject: Re: [Astlinux-devel] Segfault Crash on astlinux-1.3-4232-509fbe Hi Josh, Hmmm, looking at your modules.conf, you have -- noload => res_timing_pthread.so noload => res_timing_timerfd.so -- Why are those disabled ? > I have a custom module that I suspect could be causing issues. Adding custom binaries has me concerned ... what is the output of: -- show-union -- Lonnie > On Jun 19, 2019, at 8:51 AM, Josh Alberts <jm...@ho...> wrote: > > 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 > <modules.conf>_______________________________________________ > 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 |
|
From: Michael K. <li...@mk...> - 2019-06-19 18:06:37
|
> Am 19.06.2019 um 19:53 schrieb Lonnie Abelbeck <li...@lo...>: > > Hi Josh, > > Hmmm, looking at your modules.conf, you have > -- > noload => res_timing_pthread.so > noload => res_timing_timerfd.so > -- > Why are those disabled ? > >> I have a custom module that I suspect could be causing issues. > > Adding custom binaries has me concerned ... what is the output of: > -- > show-union > -- > > Lonnie Because I guess he is using DAHDI as its timig source … >> On Jun 19, 2019, at 8:51 AM, Josh Alberts <jm...@ho...> wrote: >> >> 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 Michael http://www.mksolutions.info |
|
From: Lonnie A. <li...@lo...> - 2019-06-19 17:53:54
|
Hi Josh, Hmmm, looking at your modules.conf, you have -- noload => res_timing_pthread.so noload => res_timing_timerfd.so -- Why are those disabled ? > I have a custom module that I suspect could be causing issues. Adding custom binaries has me concerned ... what is the output of: -- show-union -- Lonnie > On Jun 19, 2019, at 8:51 AM, Josh Alberts <jm...@ho...> wrote: > > 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 > <modules.conf>_______________________________________________ > Astlinux-devel mailing list > Ast...@li... > https://lists.sourceforge.net/lists/listinfo/astlinux-devel |
|
From: Lonnie A. <li...@lo...> - 2019-06-19 16:13:10
|
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...> 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...> > 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...> > 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...> > 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...> 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 |
|
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 |
|
From: Josh A. <jm...@ho...> - 2019-06-19 13:48:05
|
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...> 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...> 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...> 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...> 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 |
|
From: Lonnie A. <li...@lo...> - 2019-06-19 13:34:29
|
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 |
|
From: Lonnie A. <li...@lo...> - 2019-06-19 13:22:14
|
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 |
|
From: Josh A. <jm...@ho...> - 2019-06-19 13:16:08
|
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 |
|
From: Lonnie A. <li...@lo...> - 2019-06-18 20:54:23
|
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 |
|
From: John N. <jn...@co...> - 2019-06-18 20:44:02
|
Josh Alberts wrote: > I wish I was better at taking notes in crisis mode! > Don't we all!! John Novack -- Dog is my Co-Pilot |
|
From: Josh A. <jm...@ho...> - 2019-06-18 20:27:30
|
Here's what I can say based on how far I can still scroll back in my Putty window: When I went off-hook on the Dahdi channel, I didn't see the usual "starting simple switch...." output - it just went straight to "Disconnected from Asterisk server" When the call came in through a PJSIP endpoint, I remember that it got as far as the Dial command which is pointed at the Dahdi channel. But that is beyond what I can scroll back to. I wish I was better at taking notes in crisis mode! ________________________________ From: Lonnie Abelbeck <li...@lo...> Sent: Tuesday, June 18, 2019 4:16 PM To: AstLinux Developers Mailing List Subject: Re: [Astlinux-devel] Segfault Crash on astlinux-1.3-4232-509fbe 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 |
|
From: Lonnie A. <li...@lo...> - 2019-06-18 20:17:06
|
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 |
|
From: Josh A. <jm...@ho...> - 2019-06-18 20:11:09
|
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 |
|
From: Josh A. <jm...@ho...> - 2019-06-18 20:09:03
|
Ast13. Sorry, I forgot you couldn't glean that just from looking at the Astlinux version 🙂 ________________________________ From: Lonnie Abelbeck <li...@lo...> Sent: Tuesday, June 18, 2019 4:03 PM To: AstLinux Developers Mailing List Subject: Re: [Astlinux-devel] Segfault Crash on astlinux-1.3-4232-509fbe Hi Josh, Thanks for reporting. What Asterisk version did you try ? ex. ast13se, ast13 or ast16 ? Lonnie > On Jun 18, 2019, at 2:56 PM, Josh Alberts <jm...@ho...> wrote: > > 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 > _______________________________________________ > 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 |
|
From: Michael K. <li...@mk...> - 2019-06-18 20:07:09
|
> 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 |
|
From: Lonnie A. <li...@lo...> - 2019-06-18 20:03:20
|
Hi Josh, Thanks for reporting. What Asterisk version did you try ? ex. ast13se, ast13 or ast16 ? Lonnie > On Jun 18, 2019, at 2:56 PM, Josh Alberts <jm...@ho...> wrote: > > 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 > _______________________________________________ > Astlinux-devel mailing list > Ast...@li... > https://lists.sourceforge.net/lists/listinfo/astlinux-devel |
|
From: Josh A. <jm...@ho...> - 2019-06-18 19:56:25
|
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 |
|
From: Armin T. <Arm...@tu...> - 2019-06-14 12:00:01
|
Hello all, could somebody provide me with a hint on how to flush all connection table entries from ip_conntrack or nf_conntrack? Could we get conntrack-tools enabled? Armin. |
|
From: Michael K. <mic...@ip...> - 2019-06-10 08:08:10
|
Far out. I just tested AMI: VoicemailRefresh again and it does not work any more. Did an AMI debug and it successfully performs the refresh but it does not work.
It also did not work on 13.27 so there must be something unrelated to the MWI bugs in 13.24.
Looks like I will need to do a 'voicemail reload' to make this work. Not optimal but my only option at this stage.
Regards
Michael Knill
On 28/4/19, 9:11 am, "Lonnie Abelbeck" <li...@lo...> wrote:
Thanks for the report, Michael.
Asterisk 13.23.1 appears to be a solid choice.
Lonnie
> On Apr 27, 2019, at 5:25 PM, Michael Knill <mic...@ip...> wrote:
>
> Hi Devs
>
> I can confirm that after 5 days in the lab, the AMI: VoicemailRefresh is still working fine on Asterisk 13.23.1.
>
> Regards
> Michael Knill
>
> On 23/4/19, 7:33 am, "Michael Knill" <mic...@ip...> wrote:
>
> Hi Devs
>
> Ok I am doing some more testing as I want to get this sorted.
> I have now reverted to Asterisk 13.23.1 and have removed mailbox polling in voicemail.conf.
> Surprisingly AMI: VoicemailRefresh IS WORKING after all!
> What I am suspecting is that it did work when I tested previously but it was just very delayed and I was assuming it was some other watchdog process changing the MWI's. I have confirmed that this is not the case e.g. I left for quite a while and there status did not change.
> As such, I'm going to keep testing over the next few days and if there is no change in the time then I'm going to assume that this version is ok. If not then I'm going to need to go to 13.26.0.
>
> I will keep you posted.
>
> Regards
> Michael Knill
>
> On 22/4/19, 10:38 pm, "Lonnie Abelbeck" <li...@lo...> wrote:
>
> Hi Christopher,
>
> Thanks much for sharing your insights.
>
>> a while back I built a box i call WOPR which uses a series of VMs on a rather large server...
>
> WOPR, I love it, great classic movie reference.
>
> Have you used WOPR to find a solid 13.x alternative to your old 11.x version ? Possibly Asterisk 13.23.1 ?
>
> Lonnie
>
>
>
>
>> On Apr 22, 2019, at 6:39 AM, The Cadillac Kid via Astlinux-devel <ast...@li...> wrote:
>>
>> 13.24.1 is broken in more than one way.. I did a test run emulating one of my 2000 line production systems and found that as the mailbixes get lazier and lazier so does the dialplan.. call processing slows down.. Macros and gosubs seem to get slower and slower as the number of calls get processed and voicemails get left.. (the production sites are still running on old 11.20.6)
>>
>> a while back I built a box i call WOPR which uses a series of VMs on a rather large server to emulate stations registering and placing calls on the "subject".. (a physical i7 4770k with 8 gigs ram).. scripts on aastra(mitel) 68xx series physical phones make the phones answer, place calls on hold, transfer, etc.. since audio files play, they also can leave Voicemails.. the WOPR box estensions.. answer , play RTP, hang up, xfer etc. its the best emulation of a hotel environment I could create without 100s of FXO ports wired to 100s of FXS ports.
>>
>> it seems to me the more voicemails that get left on a system running 13.24.1 the slower it gets to send out MWI notifies regardless of the pollmailboxes settings.. I also run an externnotify script and some users get VM2email.. the email process is offloaded.. so the email command is simply a catcher for the email data.
>>
>> when I put the bleeding edge 16 on the "subject" machine it seems the issues went away.. im not ready to put 16 on a 2000 line production yet but seems like maybe the big is "fixed"...
>>
>> when I put 11.20.6 back on the subject all my issues went away (well other than the RTP port leaks and occasional chan_sip freezes that 11.20.6 had anyway on high volume systems)
>>
>> granted my tests arent with astlinux as I outgrew it some time ago for production but does give some insight into asterisk itself..
>>
>> my asterisk installations are "beat down".. I only compile the modules I need to use and none more.. my normal load is about 50 modules..
>> -Christopher
>
>
> _______________________________________________
> 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
|
|
From: Bill L. <wr...@gm...> - 2019-05-30 22:06:50
|
> Or simply don't use Google to send email :-) Google works. It's "my own" that doesn't work. Bill |
|
From: Lonnie A. <li...@lo...> - 2019-05-30 22:00:34
|
> On May 30, 2019, at 4:54 PM, Bill Lewis <wr...@gm...> wrote:
>
>
> Lonnie,
>
> On 5/30/2019 4:42 PM, Lonnie Abelbeck wrote:
>> Bill,
>>
>> No, the
>> --
>> Advanced Configuration:
>>
>> User System Variables: {Edit User Variables}
>> --
>> is in /mnt/kd/rc.conf.d/user.conf
>>
>
>> No reboot or 'gen-rc-conf' is needed if you ...
>> Apply the change by clicking ... {Reload/Restart} [Restart SMTP Mail] _x_ Confirm
>>
>> If the directory /mnt/kd/rc.conf.d exists /mnt/kd/rc.conf is ignored.
>>
> OK, from your original message:
>
> > You can define the SMTP_FROM rc.conf variable to change that IIRC.
>
> I took that to mean I should edit rc.conf when the Edit Configuration Files tab appeared. I see now that isn't want you meant.
> I've undone what I did before. Rebooted again.
>
> Now I've made the edit to /mnt/kd/rc.conf.d/user.conf
>
> That worked, in that the error msg from the server now refers to bi...@wr... rather than ro...@wr....
>
> Still doesn't send the mail though. :-) Now it's complaining:
>
> Access denied. You are not obviously not localhost.
>
>
> So now I'm getting totally off the topic, but you may find this to be amusing. I looked on Google for that error msg and got exactly one hit. And it's from the brother of my friend who hosts wrljet.com for me! So ... at this point it's over to him.
>
> Bill
Or simply don't use Google to send email :-)
Lonnie
|
28 messages has been excluded from this view by a project administrator.
