Menu
▾
▴
astlinux-users — AstLinux Users Mailing List
You can subscribe to this list here.
| 2006 |
Jan
|
Feb
|
Mar
|
Apr
|
May
|
Jun
(1) |
Jul
(1) |
Aug
|
Sep
|
Oct
(2) |
Nov
(1) |
Dec
(20) |
|---|---|---|---|---|---|---|---|---|---|---|---|---|
| 2007 |
Jan
(91) |
Feb
(111) |
Mar
(226) |
Apr
(65) |
May
(197) |
Jun
(202) |
Jul
(92) |
Aug
(87) |
Sep
(120) |
Oct
(133) |
Nov
(89) |
Dec
(155) |
| 2008 |
Jan
(251) |
Feb
(136) |
Mar
(174) |
Apr
(149) |
May
(56) |
Jun
(32) |
Jul
(36) |
Aug
(171) |
Sep
(245) |
Oct
(244) |
Nov
(218) |
Dec
(272) |
| 2009 |
Jan
(113) |
Feb
(119) |
Mar
(192) |
Apr
(117) |
May
(93) |
Jun
(46) |
Jul
(80) |
Aug
(54) |
Sep
(109) |
Oct
(70) |
Nov
(145) |
Dec
(110) |
| 2010 |
Jan
(137) |
Feb
(87) |
Mar
(45) |
Apr
(157) |
May
(58) |
Jun
(99) |
Jul
(188) |
Aug
(136) |
Sep
(101) |
Oct
(100) |
Nov
(61) |
Dec
(60) |
| 2011 |
Jan
(84) |
Feb
(43) |
Mar
(70) |
Apr
(17) |
May
(69) |
Jun
(28) |
Jul
(43) |
Aug
(21) |
Sep
(151) |
Oct
(120) |
Nov
(84) |
Dec
(101) |
| 2012 |
Jan
(119) |
Feb
(82) |
Mar
(70) |
Apr
(115) |
May
(66) |
Jun
(131) |
Jul
(70) |
Aug
(65) |
Sep
(66) |
Oct
(86) |
Nov
(197) |
Dec
(81) |
| 2013 |
Jan
(65) |
Feb
(48) |
Mar
(32) |
Apr
(68) |
May
(98) |
Jun
(59) |
Jul
(41) |
Aug
(52) |
Sep
(42) |
Oct
(37) |
Nov
(10) |
Dec
(27) |
| 2014 |
Jan
(61) |
Feb
(34) |
Mar
(30) |
Apr
(52) |
May
(45) |
Jun
(40) |
Jul
(28) |
Aug
(9) |
Sep
(39) |
Oct
(69) |
Nov
(55) |
Dec
(19) |
| 2015 |
Jan
(13) |
Feb
(21) |
Mar
(5) |
Apr
(14) |
May
(30) |
Jun
(51) |
Jul
(31) |
Aug
(12) |
Sep
(29) |
Oct
(15) |
Nov
(24) |
Dec
(16) |
| 2016 |
Jan
(62) |
Feb
(76) |
Mar
(30) |
Apr
(43) |
May
(46) |
Jun
(62) |
Jul
(21) |
Aug
(49) |
Sep
(67) |
Oct
(27) |
Nov
(26) |
Dec
(38) |
| 2017 |
Jan
(7) |
Feb
(12) |
Mar
(69) |
Apr
(59) |
May
(54) |
Jun
(40) |
Jul
(76) |
Aug
(82) |
Sep
(92) |
Oct
(51) |
Nov
(32) |
Dec
(30) |
| 2018 |
Jan
(22) |
Feb
(25) |
Mar
(34) |
Apr
(35) |
May
(37) |
Jun
(21) |
Jul
(69) |
Aug
(55) |
Sep
(17) |
Oct
(67) |
Nov
(9) |
Dec
(5) |
| 2019 |
Jan
(19) |
Feb
(12) |
Mar
(15) |
Apr
(19) |
May
|
Jun
(27) |
Jul
(27) |
Aug
(25) |
Sep
(25) |
Oct
(27) |
Nov
(10) |
Dec
(14) |
| 2020 |
Jan
(22) |
Feb
(20) |
Mar
(36) |
Apr
(40) |
May
(52) |
Jun
(35) |
Jul
(21) |
Aug
(32) |
Sep
(71) |
Oct
(27) |
Nov
(11) |
Dec
(16) |
| 2021 |
Jan
(16) |
Feb
(21) |
Mar
(21) |
Apr
(27) |
May
(17) |
Jun
|
Jul
(2) |
Aug
(22) |
Sep
(23) |
Oct
(7) |
Nov
(11) |
Dec
(28) |
| 2022 |
Jan
(23) |
Feb
(18) |
Mar
(9) |
Apr
(15) |
May
(15) |
Jun
(7) |
Jul
(8) |
Aug
(15) |
Sep
(1) |
Oct
|
Nov
(11) |
Dec
(10) |
| 2023 |
Jan
(14) |
Feb
(10) |
Mar
(11) |
Apr
(13) |
May
(2) |
Jun
(30) |
Jul
(1) |
Aug
(15) |
Sep
(13) |
Oct
(3) |
Nov
(25) |
Dec
(5) |
| 2024 |
Jan
(3) |
Feb
(10) |
Mar
(9) |
Apr
|
May
(1) |
Jun
(15) |
Jul
(7) |
Aug
(10) |
Sep
(3) |
Oct
(8) |
Nov
(6) |
Dec
(15) |
| 2025 |
Jan
(3) |
Feb
(1) |
Mar
(7) |
Apr
(5) |
May
(13) |
Jun
(16) |
Jul
(1) |
Aug
(6) |
Sep
|
Oct
|
Nov
|
Dec
|
|
From: Michael K. <mic...@ip...> - 2017-09-28 23:14:33
|
Hi Michael
Lonnie mentioned that too. Was it a bad move upgrading to Asterisk 13 do you think?
Regards
Michael Knill
-----Original Message-----
From: Michael Keuter <li...@mk...>
Reply-To: AstLinux List <ast...@li...>
Date: Friday, 29 September 2017 at 9:04 am
To: AstLinux List <ast...@li...>
Subject: Re: [Astlinux-users] Asterisk Segfault in app_queue.so
> Am 28.09.2017 um 02:28 schrieb Michael Knill <mic...@ip...>:
>
> Hi Michael
>
> All my other VM systems only have a single core however when Monit told me that I was having resource issues, then I pushed it up to 2 cores.
> The thing is however that Monit didn't complain until queueing was configured but Asterisk did not crash until 2 cores were added.
> Note that this could be coincidence as there was not a lot of time between these events but we are going to try a faster single core to see if this fixes the problem.
>
> Here is my queueing module. Its actually an overflowing queue group which is how they wanted it to work. Not sure if this dialplan architecture is conducive to bad stuff happening?
>
> [subDialCustom-Queuegroup]
> ;ARG1 - Queue Group, ARG2 - CF and max queue time destination dial plan
> exten => start,1,Gosub(subSetConn,start,1(${ARG1},Queue Group))
> ;Set ext_cid for when a call is forwarded externally
> same => n,Set(__ext_cid=${IF($[${DB_EXISTS(${ARG1}/ext_cid)}]?${DB_RESULT}:${ext_cid})})
> same => n,GotoIf(${DB(${ARG1}/cfa)}?cfa)
> same => n,Set(queue_options=${IF($[${DB_EXISTS(${ARG1}/queue_options)}]?${DB_RESULT}:)})
> same => n,ExecIf(${DB(${ARG1}/natimer)}?set(queue_timeout=${DB(${ARG1}/natimer)}:set(queue_timeout=${default_natimerqg}))
> ;Set and check announcement file
> same => n,Set(announcefile=${IF($[${DB_EXISTS(${ARG1}/welcome_ann)}]?announce${DB_RESULT}:)})
> same => n,Set(announcefile=${IF($[${DB_EXISTS(${DB_RESULT}/audiofile)}]?${DB_RESULT}:${announcefile})})
> same => n,GotoIf($[${ISNULL(${announcefile})}]?bypass_filecheck)
> same => n,ExecIf($["${STAT(e,${monitor_path}${announcefile}.wav)}"="0"]?Goto(no_welcome_file))
> same => n(bypass_filecheck),Answer
> same => n,ExecIf($[${ISNULL(${announcefile})}]?NoOp(Do nothing):Playback(${monitor_path}${announcefile}))
> same => n,Queue(${ARG1},,,,10)
> same => n,MusicOnHold(default,1)
> same => n,Queue(Qoverflow1,,,,10)
> same => n,MusicOnHold(default,1)
> same => n,Queue(Qoverflow2,,,,10)
> same => n,MusicOnHold(default,1)
> same => n,Queue(Qoverflow3,,,,300)
> same => n,Hangup
> same => n(cfa),Dial(Local/${DB(${ARG1}/cfa)}@${ARG2})
> same => n,Hangup
> same => n(no_welcome_file),Log(WARNING,Welcome announcement ${announcefile} for Queue ${ARG1} does not exist)
> same => n,Hangup
>
> Thanks
>
> Regards
> Michael Knill
Hi Michael,
the dialplan looks OK to me.
Have you tried (for testing purpose) to use Asterisk 11?
I also never had this "low resources" warning.
How many concurrent call does the VM handle?
> -----Original Message-----
> From: Michael Keuter <li...@mk...>
> Reply-To: AstLinux List <ast...@li...>
> Date: Wednesday, 27 September 2017 at 5:55 pm
> To: AstLinux List <ast...@li...>
> Subject: Re: [Astlinux-users] Asterisk Segfault in app_queue.so
>
>
>> Am 27.09.2017 um 03:47 schrieb Michael Knill <mic...@ip...>:
>>
>> Actually I did have a thought. These problems could very well have started when an additional CPU was added to the VM!
>>
>> Regards
>> Michael Knill
>
> What Hypervisor and how many CPUs/Cores are you using?
>
> I have a few VMs running under Proxmox with "1 Socket, 2 Cores" (as described in our Wiki).
> But unfortunately none of them uses Queues.
>
>> -----Original Message-----
>> From: Michael Knill <mic...@ip...>
>> Date: Wednesday, 27 September 2017 at 10:56 am
>> To: AstLinux List <ast...@li...>
>> Subject: Re: [Astlinux-users] Asterisk Segfault in app_queue.so
>>
>> Damn it just happened again. I would like to report it to Digium but I suspect that they will want a backtrace (
>> Do you have any suggestions what else I can try?
>>
>> Regards
>> Michael Knill
>>
>> -----Original Message-----
>> From: Lonnie Abelbeck <li...@lo...>
>> Reply-To: AstLinux List <ast...@li...>
>> Date: Thursday, 21 September 2017 at 10:11 pm
>> To: AstLinux List <ast...@li...>
>> Subject: Re: [Astlinux-users] Asterisk Segfault in app_queue.so
>>
>> Hi Michael,
>>
>> I took a look at the Asterisk source and the last "segfault" fix to apps/app_queue.c was back in 2016-04-18, which is included in Asterisk 11.23.0. (AstLinux 1.2.8)
>>
>> Asterisk Git Repo:
>> http://git.asterisk.org/gitweb/?p=asterisk/asterisk.git;a=summary
>>
>> Scroll to bottom under "heads", you can compare different versions there, or browse the very latest under "master"
>> --
>> 7 weeks ago master shortlog | log | tree
>> --
>> Click "tree" on the master head line.
>>
>> In this case click "apps"
>> --
>> -rw-r--r-- 376684 app_queue.c blob | history | raw
>> --
>> Click "history" on the app_queue.c line.
>>
>> Typically a "segfault" fix will be in the commit message, so search in your browser.
>>
>> This exercise implies there are no upstream app_queue segfault fixes.
>>
>>
>> This is a handy skill to have, particularly when an Asterisk issue is fixed in one version and not another.
>>
>> Lonnie
>>
>> PS, Armin's note of ASTERISK-25975 appears to be duplicate of ASTERISK-25888 which was fixed as noted above.
>>
>> On Sep 21, 2017, at 2:22 AM, Michael Knill <mic...@ip...> wrote:
>>
>>> Oh dear. My busiest system too. Thanks goodness for safe_asterisk
>>>
>>> Sep 21 14:07:44 3037-QGPSC-CM1 user.info kernel: asterisk[1110]: segfault at 10 ip 00002b1ed1d4882c sp 00002b1ed728fcd0 error 4 in app_queue.so[2b1ed1d34000+35000]
>>> Sep 21 14:07:45 3037-QGPSC-CM1 user.info safe_asterisk: Asterisk exited on signal 11.
>>>
>>> Any ideas?
>>> Can I get a backtrace from Astlinux?
>>>
>>> Regards
>>> Michael Knill
>
> Michael
>
> http://www.mksolutions.info
Michael
http://www.mksolutions.info
------------------------------------------------------------------------------
Check out the vibrant tech community on one of the world's most
engaging tech sites, Slashdot.org! http://sdm.link/slashdot
_______________________________________________
Astlinux-users mailing list
Ast...@li...
https://lists.sourceforge.net/lists/listinfo/astlinux-users
Donations to support AstLinux are graciously accepted via PayPal to pa...@kr....
|
|
From: Michael K. <li...@mk...> - 2017-09-28 23:03:40
|
> Am 28.09.2017 um 23:14 schrieb Michael Knill <mic...@ip...>: > > Thanks sooooo much Lonnie. I think I may have found this one in my search but I did not look into it deep enough. > > It was initially reported on Asterisk 13.15 (which is the version I am running) with 13.14 not presenting the issue. > Although the scenario is not exactly what the customer does, I do know there are calls being transferred to other queue members. > > Im thinking I will probably need to revert to 13.14. > > Thanks again Lonnie. Really appreciate your help. > > Regards > Michael Knill Hi Michael, if you don't need any of the new features in Asterisk 13 (ARI/PJSIP/STASIS), I would rather downgrade to Asterisk 11 temporarily. Since the problem seems to occur only in 13. AstLinux 1.3.1 is on the way and includes important RTP/RCTP security fixes for both Asterisk 11 and 13. > -----Original Message----- > From: Lonnie Abelbeck <li...@lo...> > Reply-To: AstLinux List <ast...@li...> > Date: Friday, 29 September 2017 at 6:14 am > To: AstLinux List <ast...@li...> > Subject: Re: [Astlinux-users] Asterisk Segfault in app_queue.so > > Hi Michael, > > I did some googling and found this fairly recent Asterisk issue ... > > app_queue: Crash when handling hangup with incomplete data > https://issues.asterisk.org/jira/browse/ASTERISK-27166 > > which was closed and merged with ... > > app_queue: Crash when hanging up with realtime queues > https://issues.asterisk.org/jira/browse/ASTERISK-27006 > > At the end of ASTERISK-27006 "Niklas Larsson" offers a patch that solves it for him, though not a solution. > > From what I can tell, this app_queue segfault issue only applies to Asterisk 13, not Asterisk 11. > > Michael, are you using Asterisk 13 ? > > Lonnie > > > On Sep 27, 2017, at 7:28 PM, Michael Knill <mic...@ip...> wrote: > >> Hi Michael >> >> All my other VM systems only have a single core however when Monit told me that I was having resource issues, then I pushed it up to 2 cores. >> The thing is however that Monit didn't complain until queueing was configured but Asterisk did not crash until 2 cores were added. >> Note that this could be coincidence as there was not a lot of time between these events but we are going to try a faster single core to see if this fixes the problem. >> >> Here is my queueing module. Its actually an overflowing queue group which is how they wanted it to work. Not sure if this dialplan architecture is conducive to bad stuff happening? >> >> [subDialCustom-Queuegroup] >> ;ARG1 - Queue Group, ARG2 - CF and max queue time destination dial plan >> exten => start,1,Gosub(subSetConn,start,1(${ARG1},Queue Group)) >> ;Set ext_cid for when a call is forwarded externally >> same => n,Set(__ext_cid=${IF($[${DB_EXISTS(${ARG1}/ext_cid)}]?${DB_RESULT}:${ext_cid})}) >> same => n,GotoIf(${DB(${ARG1}/cfa)}?cfa) >> same => n,Set(queue_options=${IF($[${DB_EXISTS(${ARG1}/queue_options)}]?${DB_RESULT}:)}) >> same => n,ExecIf(${DB(${ARG1}/natimer)}?set(queue_timeout=${DB(${ARG1}/natimer)}:set(queue_timeout=${default_natimerqg})) >> ;Set and check announcement file >> same => n,Set(announcefile=${IF($[${DB_EXISTS(${ARG1}/welcome_ann)}]?announce${DB_RESULT}:)}) >> same => n,Set(announcefile=${IF($[${DB_EXISTS(${DB_RESULT}/audiofile)}]?${DB_RESULT}:${announcefile})}) >> same => n,GotoIf($[${ISNULL(${announcefile})}]?bypass_filecheck) >> same => n,ExecIf($["${STAT(e,${monitor_path}${announcefile}.wav)}"="0"]?Goto(no_welcome_file)) >> same => n(bypass_filecheck),Answer >> same => n,ExecIf($[${ISNULL(${announcefile})}]?NoOp(Do nothing):Playback(${monitor_path}${announcefile})) >> same => n,Queue(${ARG1},,,,10) >> same => n,MusicOnHold(default,1) >> same => n,Queue(Qoverflow1,,,,10) >> same => n,MusicOnHold(default,1) >> same => n,Queue(Qoverflow2,,,,10) >> same => n,MusicOnHold(default,1) >> same => n,Queue(Qoverflow3,,,,300) >> same => n,Hangup >> same => n(cfa),Dial(Local/${DB(${ARG1}/cfa)}@${ARG2}) >> same => n,Hangup >> same => n(no_welcome_file),Log(WARNING,Welcome announcement ${announcefile} for Queue ${ARG1} does not exist) >> same => n,Hangup >> >> Thanks >> >> Regards >> Michael Knill >> >> -----Original Message----- >> From: Michael Keuter <li...@mk...> >> Reply-To: AstLinux List <ast...@li...> >> Date: Wednesday, 27 September 2017 at 5:55 pm >> To: AstLinux List <ast...@li...> >> Subject: Re: [Astlinux-users] Asterisk Segfault in app_queue.so >> >> >>> Am 27.09.2017 um 03:47 schrieb Michael Knill <mic...@ip...>: >>> >>> Actually I did have a thought. These problems could very well have started when an additional CPU was added to the VM! >>> >>> Regards >>> Michael Knill >> >> What Hypervisor and how many CPUs/Cores are you using? >> >> I have a few VMs running under Proxmox with "1 Socket, 2 Cores" (as described in our Wiki). >> But unfortunately none of them uses Queues. >> >>> -----Original Message----- >>> From: Michael Knill <mic...@ip...> >>> Date: Wednesday, 27 September 2017 at 10:56 am >>> To: AstLinux List <ast...@li...> >>> Subject: Re: [Astlinux-users] Asterisk Segfault in app_queue.so >>> >>> Damn it just happened again. I would like to report it to Digium but I suspect that they will want a backtrace ( >>> Do you have any suggestions what else I can try? >>> >>> Regards >>> Michael Knill >>> >>> -----Original Message----- >>> From: Lonnie Abelbeck <li...@lo...> >>> Reply-To: AstLinux List <ast...@li...> >>> Date: Thursday, 21 September 2017 at 10:11 pm >>> To: AstLinux List <ast...@li...> >>> Subject: Re: [Astlinux-users] Asterisk Segfault in app_queue.so >>> >>> Hi Michael, >>> >>> I took a look at the Asterisk source and the last "segfault" fix to apps/app_queue.c was back in 2016-04-18, which is included in Asterisk 11.23.0. (AstLinux 1.2.8) >>> >>> Asterisk Git Repo: >>> http://git.asterisk.org/gitweb/?p=asterisk/asterisk.git;a=summary >>> >>> Scroll to bottom under "heads", you can compare different versions there, or browse the very latest under "master" >>> -- >>> 7 weeks ago master shortlog | log | tree >>> -- >>> Click "tree" on the master head line. >>> >>> In this case click "apps" >>> -- >>> -rw-r--r-- 376684 app_queue.c blob | history | raw >>> -- >>> Click "history" on the app_queue.c line. >>> >>> Typically a "segfault" fix will be in the commit message, so search in your browser. >>> >>> This exercise implies there are no upstream app_queue segfault fixes. >>> >>> >>> This is a handy skill to have, particularly when an Asterisk issue is fixed in one version and not another. >>> >>> Lonnie >>> >>> PS, Armin's note of ASTERISK-25975 appears to be duplicate of ASTERISK-25888 which was fixed as noted above. >>> >>> On Sep 21, 2017, at 2:22 AM, Michael Knill <mic...@ip...> wrote: >>> >>>> Oh dear. My busiest system too. Thanks goodness for safe_asterisk >>>> >>>> Sep 21 14:07:44 3037-QGPSC-CM1 user.info kernel: asterisk[1110]: segfault at 10 ip 00002b1ed1d4882c sp 00002b1ed728fcd0 error 4 in app_queue.so[2b1ed1d34000+35000] >>>> Sep 21 14:07:45 3037-QGPSC-CM1 user.info safe_asterisk: Asterisk exited on signal 11. >>>> >>>> Any ideas? >>>> Can I get a backtrace from Astlinux? >>>> >>>> Regards >>>> Michael Knill Michael http://www.mksolutions.info |
|
From: Michael K. <li...@mk...> - 2017-09-28 23:03:38
|
> Am 15.09.2017 um 03:40 schrieb Michael Knill <mic...@ip...>: > > Thanks Christopher. Good to know. I understand the APU2's run a bit cooler. > Yes its actually hard to get mSATA now. I was concerned about the PC Engines card but sounds like it may be the go! I often use the TRANSCEND MSA370 16GB mSATA for AstLinux boxes with mSATA. > Interestingly the outage that generated this email was not the ALIX after all. Coincidence only. > > Regards > Michael Knill > > From: AstLinux List <ast...@li...> > Reply-To: The Cadillac Kid <eld...@ya...>, AstLinux List <ast...@li...> > Date: Friday, 15 September 2017 at 10:21 am > To: AstLinux List <ast...@li...> > Cc: The Cadillac Kid <eld...@ya...> > Subject: Re: [Astlinux-users] Goodbye ALIX > > ive got about 150 APU1's and about 20 APU2's in the field... not on astlinux but on centos 6.X and asterisk 11 or 13 depending on version and so far all are solid.. for some reason the kernel takes a long time to boot on my APU2's I think I need a kernel bump and that will fix it.. but once up they dont crash.. > > im usingthe 4 gig ones and the mSata 16 card which seems to be solid as well.. > > they do get warm.. i have mine mounted to vented 1u Rack shelves. > -Christopher > > > From: Michael Knill <mic...@ip...> > To: AstLinux List <ast...@li...> > Sent: Thursday, September 14, 2017 8:03 PM > Subject: [Astlinux-users] Goodbye ALIX > > Hi all > > I have decided that my ALIX boxes will need to go except for the very small systems. > 1.2.10 with Asterisk 13 is just too much for these boxes and I am having to turn off stuff that I don't really want to. > It's a bit sad that I cant turn on Monit to tell me that my box is struggling because it makes the box struggle more ☹ > > Thankyou ALIX. You have done me well. > > PS. Is anyone using the APU2? APU1's seem to be going ok for me but superseded I believe by APU2. > > Regards > Michael Knill Michael http://www.mksolutions.info |
|
From: Michael K. <li...@mk...> - 2017-09-28 23:03:30
|
> Am 28.09.2017 um 02:28 schrieb Michael Knill <mic...@ip...>:
>
> Hi Michael
>
> All my other VM systems only have a single core however when Monit told me that I was having resource issues, then I pushed it up to 2 cores.
> The thing is however that Monit didn't complain until queueing was configured but Asterisk did not crash until 2 cores were added.
> Note that this could be coincidence as there was not a lot of time between these events but we are going to try a faster single core to see if this fixes the problem.
>
> Here is my queueing module. Its actually an overflowing queue group which is how they wanted it to work. Not sure if this dialplan architecture is conducive to bad stuff happening?
>
> [subDialCustom-Queuegroup]
> ;ARG1 - Queue Group, ARG2 - CF and max queue time destination dial plan
> exten => start,1,Gosub(subSetConn,start,1(${ARG1},Queue Group))
> ;Set ext_cid for when a call is forwarded externally
> same => n,Set(__ext_cid=${IF($[${DB_EXISTS(${ARG1}/ext_cid)}]?${DB_RESULT}:${ext_cid})})
> same => n,GotoIf(${DB(${ARG1}/cfa)}?cfa)
> same => n,Set(queue_options=${IF($[${DB_EXISTS(${ARG1}/queue_options)}]?${DB_RESULT}:)})
> same => n,ExecIf(${DB(${ARG1}/natimer)}?set(queue_timeout=${DB(${ARG1}/natimer)}:set(queue_timeout=${default_natimerqg}))
> ;Set and check announcement file
> same => n,Set(announcefile=${IF($[${DB_EXISTS(${ARG1}/welcome_ann)}]?announce${DB_RESULT}:)})
> same => n,Set(announcefile=${IF($[${DB_EXISTS(${DB_RESULT}/audiofile)}]?${DB_RESULT}:${announcefile})})
> same => n,GotoIf($[${ISNULL(${announcefile})}]?bypass_filecheck)
> same => n,ExecIf($["${STAT(e,${monitor_path}${announcefile}.wav)}"="0"]?Goto(no_welcome_file))
> same => n(bypass_filecheck),Answer
> same => n,ExecIf($[${ISNULL(${announcefile})}]?NoOp(Do nothing):Playback(${monitor_path}${announcefile}))
> same => n,Queue(${ARG1},,,,10)
> same => n,MusicOnHold(default,1)
> same => n,Queue(Qoverflow1,,,,10)
> same => n,MusicOnHold(default,1)
> same => n,Queue(Qoverflow2,,,,10)
> same => n,MusicOnHold(default,1)
> same => n,Queue(Qoverflow3,,,,300)
> same => n,Hangup
> same => n(cfa),Dial(Local/${DB(${ARG1}/cfa)}@${ARG2})
> same => n,Hangup
> same => n(no_welcome_file),Log(WARNING,Welcome announcement ${announcefile} for Queue ${ARG1} does not exist)
> same => n,Hangup
>
> Thanks
>
> Regards
> Michael Knill
Hi Michael,
the dialplan looks OK to me.
Have you tried (for testing purpose) to use Asterisk 11?
I also never had this "low resources" warning.
How many concurrent call does the VM handle?
> -----Original Message-----
> From: Michael Keuter <li...@mk...>
> Reply-To: AstLinux List <ast...@li...>
> Date: Wednesday, 27 September 2017 at 5:55 pm
> To: AstLinux List <ast...@li...>
> Subject: Re: [Astlinux-users] Asterisk Segfault in app_queue.so
>
>
>> Am 27.09.2017 um 03:47 schrieb Michael Knill <mic...@ip...>:
>>
>> Actually I did have a thought. These problems could very well have started when an additional CPU was added to the VM!
>>
>> Regards
>> Michael Knill
>
> What Hypervisor and how many CPUs/Cores are you using?
>
> I have a few VMs running under Proxmox with "1 Socket, 2 Cores" (as described in our Wiki).
> But unfortunately none of them uses Queues.
>
>> -----Original Message-----
>> From: Michael Knill <mic...@ip...>
>> Date: Wednesday, 27 September 2017 at 10:56 am
>> To: AstLinux List <ast...@li...>
>> Subject: Re: [Astlinux-users] Asterisk Segfault in app_queue.so
>>
>> Damn it just happened again. I would like to report it to Digium but I suspect that they will want a backtrace (
>> Do you have any suggestions what else I can try?
>>
>> Regards
>> Michael Knill
>>
>> -----Original Message-----
>> From: Lonnie Abelbeck <li...@lo...>
>> Reply-To: AstLinux List <ast...@li...>
>> Date: Thursday, 21 September 2017 at 10:11 pm
>> To: AstLinux List <ast...@li...>
>> Subject: Re: [Astlinux-users] Asterisk Segfault in app_queue.so
>>
>> Hi Michael,
>>
>> I took a look at the Asterisk source and the last "segfault" fix to apps/app_queue.c was back in 2016-04-18, which is included in Asterisk 11.23.0. (AstLinux 1.2.8)
>>
>> Asterisk Git Repo:
>> http://git.asterisk.org/gitweb/?p=asterisk/asterisk.git;a=summary
>>
>> Scroll to bottom under "heads", you can compare different versions there, or browse the very latest under "master"
>> --
>> 7 weeks ago master shortlog | log | tree
>> --
>> Click "tree" on the master head line.
>>
>> In this case click "apps"
>> --
>> -rw-r--r-- 376684 app_queue.c blob | history | raw
>> --
>> Click "history" on the app_queue.c line.
>>
>> Typically a "segfault" fix will be in the commit message, so search in your browser.
>>
>> This exercise implies there are no upstream app_queue segfault fixes.
>>
>>
>> This is a handy skill to have, particularly when an Asterisk issue is fixed in one version and not another.
>>
>> Lonnie
>>
>> PS, Armin's note of ASTERISK-25975 appears to be duplicate of ASTERISK-25888 which was fixed as noted above.
>>
>> On Sep 21, 2017, at 2:22 AM, Michael Knill <mic...@ip...> wrote:
>>
>>> Oh dear. My busiest system too. Thanks goodness for safe_asterisk
>>>
>>> Sep 21 14:07:44 3037-QGPSC-CM1 user.info kernel: asterisk[1110]: segfault at 10 ip 00002b1ed1d4882c sp 00002b1ed728fcd0 error 4 in app_queue.so[2b1ed1d34000+35000]
>>> Sep 21 14:07:45 3037-QGPSC-CM1 user.info safe_asterisk: Asterisk exited on signal 11.
>>>
>>> Any ideas?
>>> Can I get a backtrace from Astlinux?
>>>
>>> Regards
>>> Michael Knill
>
> Michael
>
> http://www.mksolutions.info
Michael
http://www.mksolutions.info
|
|
From: Michael K. <mic...@ip...> - 2017-09-28 21:15:12
|
Thanks sooooo much Lonnie. I think I may have found this one in my search but I did not look into it deep enough. It was initially reported on Asterisk 13.15 (which is the version I am running) with 13.14 not presenting the issue. Although the scenario is not exactly what the customer does, I do know there are calls being transferred to other queue members. Im thinking I will probably need to revert to 13.14. Thanks again Lonnie. Really appreciate your help. Regards Michael Knill -----Original Message----- From: Lonnie Abelbeck <li...@lo...> Reply-To: AstLinux List <ast...@li...> Date: Friday, 29 September 2017 at 6:14 am To: AstLinux List <ast...@li...> Subject: Re: [Astlinux-users] Asterisk Segfault in app_queue.so Hi Michael, I did some googling and found this fairly recent Asterisk issue ... app_queue: Crash when handling hangup with incomplete data https://issues.asterisk.org/jira/browse/ASTERISK-27166 which was closed and merged with ... app_queue: Crash when hanging up with realtime queues https://issues.asterisk.org/jira/browse/ASTERISK-27006 At the end of ASTERISK-27006 "Niklas Larsson" offers a patch that solves it for him, though not a solution. From what I can tell, this app_queue segfault issue only applies to Asterisk 13, not Asterisk 11. Michael, are you using Asterisk 13 ? Lonnie On Sep 27, 2017, at 7:28 PM, Michael Knill <mic...@ip...> wrote: > Hi Michael > > All my other VM systems only have a single core however when Monit told me that I was having resource issues, then I pushed it up to 2 cores. > The thing is however that Monit didn't complain until queueing was configured but Asterisk did not crash until 2 cores were added. > Note that this could be coincidence as there was not a lot of time between these events but we are going to try a faster single core to see if this fixes the problem. > > Here is my queueing module. Its actually an overflowing queue group which is how they wanted it to work. Not sure if this dialplan architecture is conducive to bad stuff happening? > > [subDialCustom-Queuegroup] > ;ARG1 - Queue Group, ARG2 - CF and max queue time destination dial plan > exten => start,1,Gosub(subSetConn,start,1(${ARG1},Queue Group)) > ;Set ext_cid for when a call is forwarded externally > same => n,Set(__ext_cid=${IF($[${DB_EXISTS(${ARG1}/ext_cid)}]?${DB_RESULT}:${ext_cid})}) > same => n,GotoIf(${DB(${ARG1}/cfa)}?cfa) > same => n,Set(queue_options=${IF($[${DB_EXISTS(${ARG1}/queue_options)}]?${DB_RESULT}:)}) > same => n,ExecIf(${DB(${ARG1}/natimer)}?set(queue_timeout=${DB(${ARG1}/natimer)}:set(queue_timeout=${default_natimerqg})) > ;Set and check announcement file > same => n,Set(announcefile=${IF($[${DB_EXISTS(${ARG1}/welcome_ann)}]?announce${DB_RESULT}:)}) > same => n,Set(announcefile=${IF($[${DB_EXISTS(${DB_RESULT}/audiofile)}]?${DB_RESULT}:${announcefile})}) > same => n,GotoIf($[${ISNULL(${announcefile})}]?bypass_filecheck) > same => n,ExecIf($["${STAT(e,${monitor_path}${announcefile}.wav)}"="0"]?Goto(no_welcome_file)) > same => n(bypass_filecheck),Answer > same => n,ExecIf($[${ISNULL(${announcefile})}]?NoOp(Do nothing):Playback(${monitor_path}${announcefile})) > same => n,Queue(${ARG1},,,,10) > same => n,MusicOnHold(default,1) > same => n,Queue(Qoverflow1,,,,10) > same => n,MusicOnHold(default,1) > same => n,Queue(Qoverflow2,,,,10) > same => n,MusicOnHold(default,1) > same => n,Queue(Qoverflow3,,,,300) > same => n,Hangup > same => n(cfa),Dial(Local/${DB(${ARG1}/cfa)}@${ARG2}) > same => n,Hangup > same => n(no_welcome_file),Log(WARNING,Welcome announcement ${announcefile} for Queue ${ARG1} does not exist) > same => n,Hangup > > Thanks > > Regards > Michael Knill > > -----Original Message----- > From: Michael Keuter <li...@mk...> > Reply-To: AstLinux List <ast...@li...> > Date: Wednesday, 27 September 2017 at 5:55 pm > To: AstLinux List <ast...@li...> > Subject: Re: [Astlinux-users] Asterisk Segfault in app_queue.so > > >> Am 27.09.2017 um 03:47 schrieb Michael Knill <mic...@ip...>: >> >> Actually I did have a thought. These problems could very well have started when an additional CPU was added to the VM! >> >> Regards >> Michael Knill > > What Hypervisor and how many CPUs/Cores are you using? > > I have a few VMs running under Proxmox with "1 Socket, 2 Cores" (as described in our Wiki). > But unfortunately none of them uses Queues. > >> -----Original Message----- >> From: Michael Knill <mic...@ip...> >> Date: Wednesday, 27 September 2017 at 10:56 am >> To: AstLinux List <ast...@li...> >> Subject: Re: [Astlinux-users] Asterisk Segfault in app_queue.so >> >> Damn it just happened again. I would like to report it to Digium but I suspect that they will want a backtrace ( >> Do you have any suggestions what else I can try? >> >> Regards >> Michael Knill >> >> -----Original Message----- >> From: Lonnie Abelbeck <li...@lo...> >> Reply-To: AstLinux List <ast...@li...> >> Date: Thursday, 21 September 2017 at 10:11 pm >> To: AstLinux List <ast...@li...> >> Subject: Re: [Astlinux-users] Asterisk Segfault in app_queue.so >> >> Hi Michael, >> >> I took a look at the Asterisk source and the last "segfault" fix to apps/app_queue.c was back in 2016-04-18, which is included in Asterisk 11.23.0. (AstLinux 1.2.8) >> >> Asterisk Git Repo: >> http://git.asterisk.org/gitweb/?p=asterisk/asterisk.git;a=summary >> >> Scroll to bottom under "heads", you can compare different versions there, or browse the very latest under "master" >> -- >> 7 weeks ago master shortlog | log | tree >> -- >> Click "tree" on the master head line. >> >> In this case click "apps" >> -- >> -rw-r--r-- 376684 app_queue.c blob | history | raw >> -- >> Click "history" on the app_queue.c line. >> >> Typically a "segfault" fix will be in the commit message, so search in your browser. >> >> This exercise implies there are no upstream app_queue segfault fixes. >> >> >> This is a handy skill to have, particularly when an Asterisk issue is fixed in one version and not another. >> >> Lonnie >> >> PS, Armin's note of ASTERISK-25975 appears to be duplicate of ASTERISK-25888 which was fixed as noted above. >> >> On Sep 21, 2017, at 2:22 AM, Michael Knill <mic...@ip...> wrote: >> >>> Oh dear. My busiest system too. Thanks goodness for safe_asterisk >>> >>> Sep 21 14:07:44 3037-QGPSC-CM1 user.info kernel: asterisk[1110]: segfault at 10 ip 00002b1ed1d4882c sp 00002b1ed728fcd0 error 4 in app_queue.so[2b1ed1d34000+35000] >>> Sep 21 14:07:45 3037-QGPSC-CM1 user.info safe_asterisk: Asterisk exited on signal 11. >>> >>> Any ideas? >>> Can I get a backtrace from Astlinux? >>> >>> Regards >>> Michael Knill ------------------------------------------------------------------------------ Check out the vibrant tech community on one of the world's most engaging tech sites, Slashdot.org! http://sdm.link/slashdot _______________________________________________ Astlinux-users mailing list Ast...@li... https://lists.sourceforge.net/lists/listinfo/astlinux-users Donations to support AstLinux are graciously accepted via PayPal to pa...@kr.... |
|
From: Michael K. <mic...@ip...> - 2017-09-28 21:03:41
|
Hi Michael
All my other VM systems only have a single core however when Monit told me that I was having resource issues, then I pushed it up to 2 cores.
The thing is however that Monit didn't complain until queueing was configured but Asterisk did not crash until 2 cores were added.
Note that this could be coincidence as there was not a lot of time between these events but we are going to try a faster single core to see if this fixes the problem.
Here is my queueing module. Its actually an overflowing queue group which is how they wanted it to work. Not sure if this dialplan architecture is conducive to bad stuff happening?
[subDialCustom-Queuegroup]
;ARG1 - Queue Group, ARG2 - CF and max queue time destination dial plan
exten => start,1,Gosub(subSetConn,start,1(${ARG1},Queue Group))
;Set ext_cid for when a call is forwarded externally
same => n,Set(__ext_cid=${IF($[${DB_EXISTS(${ARG1}/ext_cid)}]?${DB_RESULT}:${ext_cid})})
same => n,GotoIf(${DB(${ARG1}/cfa)}?cfa)
same => n,Set(queue_options=${IF($[${DB_EXISTS(${ARG1}/queue_options)}]?${DB_RESULT}:)})
same => n,ExecIf(${DB(${ARG1}/natimer)}?set(queue_timeout=${DB(${ARG1}/natimer)}:set(queue_timeout=${default_natimerqg}))
;Set and check announcement file
same => n,Set(announcefile=${IF($[${DB_EXISTS(${ARG1}/welcome_ann)}]?announce${DB_RESULT}:)})
same => n,Set(announcefile=${IF($[${DB_EXISTS(${DB_RESULT}/audiofile)}]?${DB_RESULT}:${announcefile})})
same => n,GotoIf($[${ISNULL(${announcefile})}]?bypass_filecheck)
same => n,ExecIf($["${STAT(e,${monitor_path}${announcefile}.wav)}"="0"]?Goto(no_welcome_file))
same => n(bypass_filecheck),Answer
same => n,ExecIf($[${ISNULL(${announcefile})}]?NoOp(Do nothing):Playback(${monitor_path}${announcefile}))
same => n,Queue(${ARG1},,,,10)
same => n,MusicOnHold(default,1)
same => n,Queue(Qoverflow1,,,,10)
same => n,MusicOnHold(default,1)
same => n,Queue(Qoverflow2,,,,10)
same => n,MusicOnHold(default,1)
same => n,Queue(Qoverflow3,,,,300)
same => n,Hangup
same => n(cfa),Dial(Local/${DB(${ARG1}/cfa)}@${ARG2})
same => n,Hangup
same => n(no_welcome_file),Log(WARNING,Welcome announcement ${announcefile} for Queue ${ARG1} does not exist)
same => n,Hangup
Thanks
Regards
Michael Knill
-----Original Message-----
From: Michael Keuter <li...@mk...>
Reply-To: AstLinux List <ast...@li...>
Date: Wednesday, 27 September 2017 at 5:55 pm
To: AstLinux List <ast...@li...>
Subject: Re: [Astlinux-users] Asterisk Segfault in app_queue.so
> Am 27.09.2017 um 03:47 schrieb Michael Knill <mic...@ip...>:
>
> Actually I did have a thought. These problems could very well have started when an additional CPU was added to the VM!
>
> Regards
> Michael Knill
What Hypervisor and how many CPUs/Cores are you using?
I have a few VMs running under Proxmox with "1 Socket, 2 Cores" (as described in our Wiki).
But unfortunately none of them uses Queues.
> -----Original Message-----
> From: Michael Knill <mic...@ip...>
> Date: Wednesday, 27 September 2017 at 10:56 am
> To: AstLinux List <ast...@li...>
> Subject: Re: [Astlinux-users] Asterisk Segfault in app_queue.so
>
> Damn it just happened again. I would like to report it to Digium but I suspect that they will want a backtrace (
> Do you have any suggestions what else I can try?
>
> Regards
> Michael Knill
>
> -----Original Message-----
> From: Lonnie Abelbeck <li...@lo...>
> Reply-To: AstLinux List <ast...@li...>
> Date: Thursday, 21 September 2017 at 10:11 pm
> To: AstLinux List <ast...@li...>
> Subject: Re: [Astlinux-users] Asterisk Segfault in app_queue.so
>
> Hi Michael,
>
> I took a look at the Asterisk source and the last "segfault" fix to apps/app_queue.c was back in 2016-04-18, which is included in Asterisk 11.23.0. (AstLinux 1.2.8)
>
> Asterisk Git Repo:
> http://git.asterisk.org/gitweb/?p=asterisk/asterisk.git;a=summary
>
> Scroll to bottom under "heads", you can compare different versions there, or browse the very latest under "master"
> --
> 7 weeks ago master shortlog | log | tree
> --
> Click "tree" on the master head line.
>
> In this case click "apps"
> --
> -rw-r--r-- 376684 app_queue.c blob | history | raw
> --
> Click "history" on the app_queue.c line.
>
> Typically a "segfault" fix will be in the commit message, so search in your browser.
>
> This exercise implies there are no upstream app_queue segfault fixes.
>
>
> This is a handy skill to have, particularly when an Asterisk issue is fixed in one version and not another.
>
> Lonnie
>
> PS, Armin's note of ASTERISK-25975 appears to be duplicate of ASTERISK-25888 which was fixed as noted above.
>
> On Sep 21, 2017, at 2:22 AM, Michael Knill <mic...@ip...> wrote:
>
>> Oh dear. My busiest system too. Thanks goodness for safe_asterisk
>>
>> Sep 21 14:07:44 3037-QGPSC-CM1 user.info kernel: asterisk[1110]: segfault at 10 ip 00002b1ed1d4882c sp 00002b1ed728fcd0 error 4 in app_queue.so[2b1ed1d34000+35000]
>> Sep 21 14:07:45 3037-QGPSC-CM1 user.info safe_asterisk: Asterisk exited on signal 11.
>>
>> Any ideas?
>> Can I get a backtrace from Astlinux?
>>
>> Regards
>> Michael Knill
Michael
http://www.mksolutions.info
------------------------------------------------------------------------------
Check out the vibrant tech community on one of the world's most
engaging tech sites, Slashdot.org! http://sdm.link/slashdot
_______________________________________________
Astlinux-users mailing list
Ast...@li...
https://lists.sourceforge.net/lists/listinfo/astlinux-users
Donations to support AstLinux are graciously accepted via PayPal to pa...@kr....
|
|
From: Lonnie A. <li...@lo...> - 2017-09-28 20:11:11
|
Hi Michael, I did some googling and found this fairly recent Asterisk issue ... app_queue: Crash when handling hangup with incomplete data https://issues.asterisk.org/jira/browse/ASTERISK-27166 which was closed and merged with ... app_queue: Crash when hanging up with realtime queues https://issues.asterisk.org/jira/browse/ASTERISK-27006 At the end of ASTERISK-27006 "Niklas Larsson" offers a patch that solves it for him, though not a solution. From what I can tell, this app_queue segfault issue only applies to Asterisk 13, not Asterisk 11. Michael, are you using Asterisk 13 ? Lonnie On Sep 27, 2017, at 7:28 PM, Michael Knill <mic...@ip...> wrote: > Hi Michael > > All my other VM systems only have a single core however when Monit told me that I was having resource issues, then I pushed it up to 2 cores. > The thing is however that Monit didn't complain until queueing was configured but Asterisk did not crash until 2 cores were added. > Note that this could be coincidence as there was not a lot of time between these events but we are going to try a faster single core to see if this fixes the problem. > > Here is my queueing module. Its actually an overflowing queue group which is how they wanted it to work. Not sure if this dialplan architecture is conducive to bad stuff happening? > > [subDialCustom-Queuegroup] > ;ARG1 - Queue Group, ARG2 - CF and max queue time destination dial plan > exten => start,1,Gosub(subSetConn,start,1(${ARG1},Queue Group)) > ;Set ext_cid for when a call is forwarded externally > same => n,Set(__ext_cid=${IF($[${DB_EXISTS(${ARG1}/ext_cid)}]?${DB_RESULT}:${ext_cid})}) > same => n,GotoIf(${DB(${ARG1}/cfa)}?cfa) > same => n,Set(queue_options=${IF($[${DB_EXISTS(${ARG1}/queue_options)}]?${DB_RESULT}:)}) > same => n,ExecIf(${DB(${ARG1}/natimer)}?set(queue_timeout=${DB(${ARG1}/natimer)}:set(queue_timeout=${default_natimerqg})) > ;Set and check announcement file > same => n,Set(announcefile=${IF($[${DB_EXISTS(${ARG1}/welcome_ann)}]?announce${DB_RESULT}:)}) > same => n,Set(announcefile=${IF($[${DB_EXISTS(${DB_RESULT}/audiofile)}]?${DB_RESULT}:${announcefile})}) > same => n,GotoIf($[${ISNULL(${announcefile})}]?bypass_filecheck) > same => n,ExecIf($["${STAT(e,${monitor_path}${announcefile}.wav)}"="0"]?Goto(no_welcome_file)) > same => n(bypass_filecheck),Answer > same => n,ExecIf($[${ISNULL(${announcefile})}]?NoOp(Do nothing):Playback(${monitor_path}${announcefile})) > same => n,Queue(${ARG1},,,,10) > same => n,MusicOnHold(default,1) > same => n,Queue(Qoverflow1,,,,10) > same => n,MusicOnHold(default,1) > same => n,Queue(Qoverflow2,,,,10) > same => n,MusicOnHold(default,1) > same => n,Queue(Qoverflow3,,,,300) > same => n,Hangup > same => n(cfa),Dial(Local/${DB(${ARG1}/cfa)}@${ARG2}) > same => n,Hangup > same => n(no_welcome_file),Log(WARNING,Welcome announcement ${announcefile} for Queue ${ARG1} does not exist) > same => n,Hangup > > Thanks > > Regards > Michael Knill > > -----Original Message----- > From: Michael Keuter <li...@mk...> > Reply-To: AstLinux List <ast...@li...> > Date: Wednesday, 27 September 2017 at 5:55 pm > To: AstLinux List <ast...@li...> > Subject: Re: [Astlinux-users] Asterisk Segfault in app_queue.so > > >> Am 27.09.2017 um 03:47 schrieb Michael Knill <mic...@ip...>: >> >> Actually I did have a thought. These problems could very well have started when an additional CPU was added to the VM! >> >> Regards >> Michael Knill > > What Hypervisor and how many CPUs/Cores are you using? > > I have a few VMs running under Proxmox with "1 Socket, 2 Cores" (as described in our Wiki). > But unfortunately none of them uses Queues. > >> -----Original Message----- >> From: Michael Knill <mic...@ip...> >> Date: Wednesday, 27 September 2017 at 10:56 am >> To: AstLinux List <ast...@li...> >> Subject: Re: [Astlinux-users] Asterisk Segfault in app_queue.so >> >> Damn it just happened again. I would like to report it to Digium but I suspect that they will want a backtrace ( >> Do you have any suggestions what else I can try? >> >> Regards >> Michael Knill >> >> -----Original Message----- >> From: Lonnie Abelbeck <li...@lo...> >> Reply-To: AstLinux List <ast...@li...> >> Date: Thursday, 21 September 2017 at 10:11 pm >> To: AstLinux List <ast...@li...> >> Subject: Re: [Astlinux-users] Asterisk Segfault in app_queue.so >> >> Hi Michael, >> >> I took a look at the Asterisk source and the last "segfault" fix to apps/app_queue.c was back in 2016-04-18, which is included in Asterisk 11.23.0. (AstLinux 1.2.8) >> >> Asterisk Git Repo: >> http://git.asterisk.org/gitweb/?p=asterisk/asterisk.git;a=summary >> >> Scroll to bottom under "heads", you can compare different versions there, or browse the very latest under "master" >> -- >> 7 weeks ago master shortlog | log | tree >> -- >> Click "tree" on the master head line. >> >> In this case click "apps" >> -- >> -rw-r--r-- 376684 app_queue.c blob | history | raw >> -- >> Click "history" on the app_queue.c line. >> >> Typically a "segfault" fix will be in the commit message, so search in your browser. >> >> This exercise implies there are no upstream app_queue segfault fixes. >> >> >> This is a handy skill to have, particularly when an Asterisk issue is fixed in one version and not another. >> >> Lonnie >> >> PS, Armin's note of ASTERISK-25975 appears to be duplicate of ASTERISK-25888 which was fixed as noted above. >> >> On Sep 21, 2017, at 2:22 AM, Michael Knill <mic...@ip...> wrote: >> >>> Oh dear. My busiest system too. Thanks goodness for safe_asterisk >>> >>> Sep 21 14:07:44 3037-QGPSC-CM1 user.info kernel: asterisk[1110]: segfault at 10 ip 00002b1ed1d4882c sp 00002b1ed728fcd0 error 4 in app_queue.so[2b1ed1d34000+35000] >>> Sep 21 14:07:45 3037-QGPSC-CM1 user.info safe_asterisk: Asterisk exited on signal 11. >>> >>> Any ideas? >>> Can I get a backtrace from Astlinux? >>> >>> Regards >>> Michael Knill |
|
From: Michael K. <mic...@ip...> - 2017-09-28 00:28:31
|
Hi Michael
All my other VM systems only have a single core however when Monit told me that I was having resource issues, then I pushed it up to 2 cores.
The thing is however that Monit didn't complain until queueing was configured but Asterisk did not crash until 2 cores were added.
Note that this could be coincidence as there was not a lot of time between these events but we are going to try a faster single core to see if this fixes the problem.
Here is my queueing module. Its actually an overflowing queue group which is how they wanted it to work. Not sure if this dialplan architecture is conducive to bad stuff happening?
[subDialCustom-Queuegroup]
;ARG1 - Queue Group, ARG2 - CF and max queue time destination dial plan
exten => start,1,Gosub(subSetConn,start,1(${ARG1},Queue Group))
;Set ext_cid for when a call is forwarded externally
same => n,Set(__ext_cid=${IF($[${DB_EXISTS(${ARG1}/ext_cid)}]?${DB_RESULT}:${ext_cid})})
same => n,GotoIf(${DB(${ARG1}/cfa)}?cfa)
same => n,Set(queue_options=${IF($[${DB_EXISTS(${ARG1}/queue_options)}]?${DB_RESULT}:)})
same => n,ExecIf(${DB(${ARG1}/natimer)}?set(queue_timeout=${DB(${ARG1}/natimer)}:set(queue_timeout=${default_natimerqg}))
;Set and check announcement file
same => n,Set(announcefile=${IF($[${DB_EXISTS(${ARG1}/welcome_ann)}]?announce${DB_RESULT}:)})
same => n,Set(announcefile=${IF($[${DB_EXISTS(${DB_RESULT}/audiofile)}]?${DB_RESULT}:${announcefile})})
same => n,GotoIf($[${ISNULL(${announcefile})}]?bypass_filecheck)
same => n,ExecIf($["${STAT(e,${monitor_path}${announcefile}.wav)}"="0"]?Goto(no_welcome_file))
same => n(bypass_filecheck),Answer
same => n,ExecIf($[${ISNULL(${announcefile})}]?NoOp(Do nothing):Playback(${monitor_path}${announcefile}))
same => n,Queue(${ARG1},,,,10)
same => n,MusicOnHold(default,1)
same => n,Queue(Qoverflow1,,,,10)
same => n,MusicOnHold(default,1)
same => n,Queue(Qoverflow2,,,,10)
same => n,MusicOnHold(default,1)
same => n,Queue(Qoverflow3,,,,300)
same => n,Hangup
same => n(cfa),Dial(Local/${DB(${ARG1}/cfa)}@${ARG2})
same => n,Hangup
same => n(no_welcome_file),Log(WARNING,Welcome announcement ${announcefile} for Queue ${ARG1} does not exist)
same => n,Hangup
Thanks
Regards
Michael Knill
-----Original Message-----
From: Michael Keuter <li...@mk...>
Reply-To: AstLinux List <ast...@li...>
Date: Wednesday, 27 September 2017 at 5:55 pm
To: AstLinux List <ast...@li...>
Subject: Re: [Astlinux-users] Asterisk Segfault in app_queue.so
> Am 27.09.2017 um 03:47 schrieb Michael Knill <mic...@ip...>:
>
> Actually I did have a thought. These problems could very well have started when an additional CPU was added to the VM!
>
> Regards
> Michael Knill
What Hypervisor and how many CPUs/Cores are you using?
I have a few VMs running under Proxmox with "1 Socket, 2 Cores" (as described in our Wiki).
But unfortunately none of them uses Queues.
> -----Original Message-----
> From: Michael Knill <mic...@ip...>
> Date: Wednesday, 27 September 2017 at 10:56 am
> To: AstLinux List <ast...@li...>
> Subject: Re: [Astlinux-users] Asterisk Segfault in app_queue.so
>
> Damn it just happened again. I would like to report it to Digium but I suspect that they will want a backtrace (
> Do you have any suggestions what else I can try?
>
> Regards
> Michael Knill
>
> -----Original Message-----
> From: Lonnie Abelbeck <li...@lo...>
> Reply-To: AstLinux List <ast...@li...>
> Date: Thursday, 21 September 2017 at 10:11 pm
> To: AstLinux List <ast...@li...>
> Subject: Re: [Astlinux-users] Asterisk Segfault in app_queue.so
>
> Hi Michael,
>
> I took a look at the Asterisk source and the last "segfault" fix to apps/app_queue.c was back in 2016-04-18, which is included in Asterisk 11.23.0. (AstLinux 1.2.8)
>
> Asterisk Git Repo:
> http://git.asterisk.org/gitweb/?p=asterisk/asterisk.git;a=summary
>
> Scroll to bottom under "heads", you can compare different versions there, or browse the very latest under "master"
> --
> 7 weeks ago master shortlog | log | tree
> --
> Click "tree" on the master head line.
>
> In this case click "apps"
> --
> -rw-r--r-- 376684 app_queue.c blob | history | raw
> --
> Click "history" on the app_queue.c line.
>
> Typically a "segfault" fix will be in the commit message, so search in your browser.
>
> This exercise implies there are no upstream app_queue segfault fixes.
>
>
> This is a handy skill to have, particularly when an Asterisk issue is fixed in one version and not another.
>
> Lonnie
>
> PS, Armin's note of ASTERISK-25975 appears to be duplicate of ASTERISK-25888 which was fixed as noted above.
>
> On Sep 21, 2017, at 2:22 AM, Michael Knill <mic...@ip...> wrote:
>
>> Oh dear. My busiest system too. Thanks goodness for safe_asterisk
>>
>> Sep 21 14:07:44 3037-QGPSC-CM1 user.info kernel: asterisk[1110]: segfault at 10 ip 00002b1ed1d4882c sp 00002b1ed728fcd0 error 4 in app_queue.so[2b1ed1d34000+35000]
>> Sep 21 14:07:45 3037-QGPSC-CM1 user.info safe_asterisk: Asterisk exited on signal 11.
>>
>> Any ideas?
>> Can I get a backtrace from Astlinux?
>>
>> Regards
>> Michael Knill
Michael
http://www.mksolutions.info
------------------------------------------------------------------------------
Check out the vibrant tech community on one of the world's most
engaging tech sites, Slashdot.org! http://sdm.link/slashdot
_______________________________________________
Astlinux-users mailing list
Ast...@li...
https://lists.sourceforge.net/lists/listinfo/astlinux-users
Donations to support AstLinux are graciously accepted via PayPal to pa...@kr....
|
|
From: Michael K. <li...@mk...> - 2017-09-27 07:55:19
|
> Am 27.09.2017 um 03:47 schrieb Michael Knill <mic...@ip...>: > > Actually I did have a thought. These problems could very well have started when an additional CPU was added to the VM! > > Regards > Michael Knill What Hypervisor and how many CPUs/Cores are you using? I have a few VMs running under Proxmox with "1 Socket, 2 Cores" (as described in our Wiki). But unfortunately none of them uses Queues. > -----Original Message----- > From: Michael Knill <mic...@ip...> > Date: Wednesday, 27 September 2017 at 10:56 am > To: AstLinux List <ast...@li...> > Subject: Re: [Astlinux-users] Asterisk Segfault in app_queue.so > > Damn it just happened again. I would like to report it to Digium but I suspect that they will want a backtrace ( > Do you have any suggestions what else I can try? > > Regards > Michael Knill > > -----Original Message----- > From: Lonnie Abelbeck <li...@lo...> > Reply-To: AstLinux List <ast...@li...> > Date: Thursday, 21 September 2017 at 10:11 pm > To: AstLinux List <ast...@li...> > Subject: Re: [Astlinux-users] Asterisk Segfault in app_queue.so > > Hi Michael, > > I took a look at the Asterisk source and the last "segfault" fix to apps/app_queue.c was back in 2016-04-18, which is included in Asterisk 11.23.0. (AstLinux 1.2.8) > > Asterisk Git Repo: > http://git.asterisk.org/gitweb/?p=asterisk/asterisk.git;a=summary > > Scroll to bottom under "heads", you can compare different versions there, or browse the very latest under "master" > -- > 7 weeks ago master shortlog | log | tree > -- > Click "tree" on the master head line. > > In this case click "apps" > -- > -rw-r--r-- 376684 app_queue.c blob | history | raw > -- > Click "history" on the app_queue.c line. > > Typically a "segfault" fix will be in the commit message, so search in your browser. > > This exercise implies there are no upstream app_queue segfault fixes. > > > This is a handy skill to have, particularly when an Asterisk issue is fixed in one version and not another. > > Lonnie > > PS, Armin's note of ASTERISK-25975 appears to be duplicate of ASTERISK-25888 which was fixed as noted above. > > On Sep 21, 2017, at 2:22 AM, Michael Knill <mic...@ip...> wrote: > >> Oh dear. My busiest system too. Thanks goodness for safe_asterisk >> >> Sep 21 14:07:44 3037-QGPSC-CM1 user.info kernel: asterisk[1110]: segfault at 10 ip 00002b1ed1d4882c sp 00002b1ed728fcd0 error 4 in app_queue.so[2b1ed1d34000+35000] >> Sep 21 14:07:45 3037-QGPSC-CM1 user.info safe_asterisk: Asterisk exited on signal 11. >> >> Any ideas? >> Can I get a backtrace from Astlinux? >> >> Regards >> Michael Knill Michael http://www.mksolutions.info |
|
From: Michael K. <mic...@ip...> - 2017-09-27 06:29:13
|
Damn it just happened again. I would like to report it to Digium but I suspect that they will want a backtrace ( Do you have any suggestions what else I can try? Regards Michael Knill -----Original Message----- From: Lonnie Abelbeck <li...@lo...> Reply-To: AstLinux List <ast...@li...> Date: Thursday, 21 September 2017 at 10:11 pm To: AstLinux List <ast...@li...> Subject: Re: [Astlinux-users] Asterisk Segfault in app_queue.so Hi Michael, I took a look at the Asterisk source and the last "segfault" fix to apps/app_queue.c was back in 2016-04-18, which is included in Asterisk 11.23.0. (AstLinux 1.2.8) Asterisk Git Repo: http://git.asterisk.org/gitweb/?p=asterisk/asterisk.git;a=summary Scroll to bottom under "heads", you can compare different versions there, or browse the very latest under "master" -- 7 weeks ago master shortlog | log | tree -- Click "tree" on the master head line. In this case click "apps" -- -rw-r--r-- 376684 app_queue.c blob | history | raw -- Click "history" on the app_queue.c line. Typically a "segfault" fix will be in the commit message, so search in your browser. This exercise implies there are no upstream app_queue segfault fixes. This is a handy skill to have, particularly when an Asterisk issue is fixed in one version and not another. Lonnie PS, Armin's note of ASTERISK-25975 appears to be duplicate of ASTERISK-25888 which was fixed as noted above. On Sep 21, 2017, at 2:22 AM, Michael Knill <mic...@ip...> wrote: > Oh dear. My busiest system too. Thanks goodness for safe_asterisk > > Sep 21 14:07:44 3037-QGPSC-CM1 user.info kernel: asterisk[1110]: segfault at 10 ip 00002b1ed1d4882c sp 00002b1ed728fcd0 error 4 in app_queue.so[2b1ed1d34000+35000] > Sep 21 14:07:45 3037-QGPSC-CM1 user.info safe_asterisk: Asterisk exited on signal 11. > > Any ideas? > Can I get a backtrace from Astlinux? > > Regards > Michael Knill > ------------------------------------------------------------------------------ > Check out the vibrant tech community on one of the world's most > engaging tech sites, Slashdot.org! http://sdm.link/slashdot_______________________________________________ > Astlinux-users mailing list > Ast...@li... > https://lists.sourceforge.net/lists/listinfo/astlinux-users > > Donations to support AstLinux are graciously accepted via PayPal to pa...@kr.... ------------------------------------------------------------------------------ Check out the vibrant tech community on one of the world's most engaging tech sites, Slashdot.org! http://sdm.link/slashdot _______________________________________________ Astlinux-users mailing list Ast...@li... https://lists.sourceforge.net/lists/listinfo/astlinux-users Donations to support AstLinux are graciously accepted via PayPal to pa...@kr.... |
|
From: Michael K. <mic...@ip...> - 2017-09-27 05:51:55
|
Actually I did have a thought. These problems could very well have started when an additional CPU was added to the VM! Regards Michael Knill -----Original Message----- From: Michael Knill <mic...@ip...> Date: Wednesday, 27 September 2017 at 10:56 am To: AstLinux List <ast...@li...> Subject: Re: [Astlinux-users] Asterisk Segfault in app_queue.so Damn it just happened again. I would like to report it to Digium but I suspect that they will want a backtrace ( Do you have any suggestions what else I can try? Regards Michael Knill -----Original Message----- From: Lonnie Abelbeck <li...@lo...> Reply-To: AstLinux List <ast...@li...> Date: Thursday, 21 September 2017 at 10:11 pm To: AstLinux List <ast...@li...> Subject: Re: [Astlinux-users] Asterisk Segfault in app_queue.so Hi Michael, I took a look at the Asterisk source and the last "segfault" fix to apps/app_queue.c was back in 2016-04-18, which is included in Asterisk 11.23.0. (AstLinux 1.2.8) Asterisk Git Repo: http://git.asterisk.org/gitweb/?p=asterisk/asterisk.git;a=summary Scroll to bottom under "heads", you can compare different versions there, or browse the very latest under "master" -- 7 weeks ago master shortlog | log | tree -- Click "tree" on the master head line. In this case click "apps" -- -rw-r--r-- 376684 app_queue.c blob | history | raw -- Click "history" on the app_queue.c line. Typically a "segfault" fix will be in the commit message, so search in your browser. This exercise implies there are no upstream app_queue segfault fixes. This is a handy skill to have, particularly when an Asterisk issue is fixed in one version and not another. Lonnie PS, Armin's note of ASTERISK-25975 appears to be duplicate of ASTERISK-25888 which was fixed as noted above. On Sep 21, 2017, at 2:22 AM, Michael Knill <mic...@ip...> wrote: > Oh dear. My busiest system too. Thanks goodness for safe_asterisk > > Sep 21 14:07:44 3037-QGPSC-CM1 user.info kernel: asterisk[1110]: segfault at 10 ip 00002b1ed1d4882c sp 00002b1ed728fcd0 error 4 in app_queue.so[2b1ed1d34000+35000] > Sep 21 14:07:45 3037-QGPSC-CM1 user.info safe_asterisk: Asterisk exited on signal 11. > > Any ideas? > Can I get a backtrace from Astlinux? > > Regards > Michael Knill > ------------------------------------------------------------------------------ > Check out the vibrant tech community on one of the world's most > engaging tech sites, Slashdot.org! http://sdm.link/slashdot_______________________________________________ > Astlinux-users mailing list > Ast...@li... > https://lists.sourceforge.net/lists/listinfo/astlinux-users > > Donations to support AstLinux are graciously accepted via PayPal to pa...@kr.... ------------------------------------------------------------------------------ Check out the vibrant tech community on one of the world's most engaging tech sites, Slashdot.org! http://sdm.link/slashdot _______________________________________________ Astlinux-users mailing list Ast...@li... https://lists.sourceforge.net/lists/listinfo/astlinux-users Donations to support AstLinux are graciously accepted via PayPal to pa...@kr.... |
|
From: Michael K. <mic...@ip...> - 2017-09-23 23:00:56
|
Thanks Lonnie. I might wait until I start using ACME (Lets Encrypt) which I plan to do in the future. Regards Michael Knill -----Original Message----- From: Lonnie Abelbeck <li...@lo...> Reply-To: AstLinux List <ast...@li...> Date: Saturday, 23 September 2017 at 10:27 pm To: AstLinux List <ast...@li...> Subject: Re: [Astlinux-users] Delay after Asterisk Dial when no DNS On Sep 22, 2017, at 11:10 PM, Michael Knill <mic...@ip...> wrote: > Thanks Lonnie. > Interesting - https://en.wikipedia.org/wiki/.local > > I think I will change them all to priv.<my domain> like you have. That has served me well for years. Though, if you were going to change your local domain names, if your ever wanted to generate ACME (Let's Encrypt) certificates locally (lots of reasons to do so) you may want to consider using global DNS names. ACME certs require global DNS domains that you have control over, and DNS providers the acme.sh script supports. Also you could still use priv.ipcsolutions.com.au domain on boxes and manually add a DNS host entry for pbx-123.deploy.ipcsolutions.com.au (just an example) where you have a global DNS entry for pbx-123.deploy.ipcsolutions.com.au you control for ACME certificates. Some might think it would be less confusing if the ACME cert DNS name was the same as the box host / domain configuration. Regardless you would be using split-horizon DNS, ie. the local devices (Local Domain checked) would see a private address for pbx-123.deploy.ipcsolutions.com.au, and you may not ever use the public pbx-123.deploy.ipcsolutions.com.au except for ACME certificate renewals. Something to think about. Lonnie ACME (Let's Encrypt) Certificates https://doc.astlinux-project.org/userdoc:tt_acme_certificates > -----Original Message----- > From: Lonnie Abelbeck <li...@lo...> > Reply-To: AstLinux List <ast...@li...> > Date: Saturday, 23 September 2017 at 1:44 pm > To: AstLinux List <ast...@li...> > Subject: Re: [Astlinux-users] Delay after Asterisk Dial when no DNS > > Holy wayback machine ... though what you quoted seems to be still valid. > > The "Local Domain" checkbox determines a dnsmasq configuration for whether the listed Domain is part of an upstream DNS zone or to create an independent local DNS zone. > > It would appear a Domain of "ipcsolutions.local" would have Local Domain checked (the default). with a thought: > > 1) Years ago using .local caused issues in some cases with clients using mDNS, Zeroconf, not sure if that is problem anymore, I'm suspecting newer OS client's are OK. > > Lonnie > > > On Sep 22, 2017, at 8:21 PM, Michael Knill <mic...@ip...> wrote: > >> Actually sorry if Local Domain is checked which is now going to be the case for virtually all my systems, then 3) is irrelevant anyway. >> >> Regards >> Michael Knill >> >> -----Original Message----- >> From: Michael Knill <mic...@ip...> >> Reply-To: AstLinux List <ast...@li...> >> Date: Saturday, 23 September 2017 at 11:18 am >> To: AstLinux List <ast...@li...> >> Subject: Re: [Astlinux-users] Delay after Asterisk Dial when no DNS >> >> Ok I have looked back through the Astlinux archives and found one of Lonnie's old posts. >> ------------------ >> ==== >> Single Interface (only External Interface: defined) configuration: >> 1) In the Network tab, make the Hostname: and Domain: match that of the upstream DNS server. >> 2) Uncheck the "Local Domain" box. >> 3) Make sure no IPv4 (or IPv6/nn) addresses are defined in any of the "Internal Interfaces:" section fields. >> ==== >> Now, in your case, you have internal interfaces/networks. As a rule the first defined internal interface (usually 1st LAN) will automatically have a /etc/hosts entry: >> -- >> INTIP HOSTNAME.DOMAIN HOSTNAME >> -- >> Note: Regardless if "Local Domain" is checked or unchecked, HOSTNAME will resolve to INTIP. The file /etc/hosts always has priority. >> >> So, if you have internal interfaces/networks the DOMAIN should normally be unique and "Local Domain" should be checked. For example DOMAIN could be "local' or I personally use "priv.abelbeck.com" as my AstLinux DOMAIN which does not occur anywhere in the public DNS. >> >> Define your DNS hosts for your local devices by using Network tab -> DNS Forwarder & DHCP Server { Configure DNS Hosts } >> These values will be automatically added to the /etc/hosts file for DNS, "Restart DNS" to apply the changes. >> >> Note the DHCP server will pass out DOMAIN so all local devices will have the scope of the *unique* local domain. >> --------------------- >> >> I have a couple of questions: >> 1) I don't quite understand '1) In the Network tab, make the Hostname: and Domain: match that of the upstream DNS server'. Could you please explain sorry? >> 2) Im assuming that basically all my systems (with an internal interface) should be ipcsolutions.local with 'Local Domain' checked? >> 3) I realise that the DNS requests below are for IPv6. Can I turn this off? >> >> Regards >> Michael Knill ------------------------------------------------------------------------------ Check out the vibrant tech community on one of the world's most engaging tech sites, Slashdot.org! http://sdm.link/slashdot _______________________________________________ Astlinux-users mailing list Ast...@li... https://lists.sourceforge.net/lists/listinfo/astlinux-users Donations to support AstLinux are graciously accepted via PayPal to pa...@kr.... |
|
From: Lonnie A. <li...@lo...> - 2017-09-23 12:27:07
|
On Sep 22, 2017, at 11:10 PM, Michael Knill <mic...@ip...> wrote: > Thanks Lonnie. > Interesting - https://en.wikipedia.org/wiki/.local > > I think I will change them all to priv.<my domain> like you have. That has served me well for years. Though, if you were going to change your local domain names, if your ever wanted to generate ACME (Let's Encrypt) certificates locally (lots of reasons to do so) you may want to consider using global DNS names. ACME certs require global DNS domains that you have control over, and DNS providers the acme.sh script supports. Also you could still use priv.ipcsolutions.com.au domain on boxes and manually add a DNS host entry for pbx-123.deploy.ipcsolutions.com.au (just an example) where you have a global DNS entry for pbx-123.deploy.ipcsolutions.com.au you control for ACME certificates. Some might think it would be less confusing if the ACME cert DNS name was the same as the box host / domain configuration. Regardless you would be using split-horizon DNS, ie. the local devices (Local Domain checked) would see a private address for pbx-123.deploy.ipcsolutions.com.au, and you may not ever use the public pbx-123.deploy.ipcsolutions.com.au except for ACME certificate renewals. Something to think about. Lonnie ACME (Let's Encrypt) Certificates https://doc.astlinux-project.org/userdoc:tt_acme_certificates > -----Original Message----- > From: Lonnie Abelbeck <li...@lo...> > Reply-To: AstLinux List <ast...@li...> > Date: Saturday, 23 September 2017 at 1:44 pm > To: AstLinux List <ast...@li...> > Subject: Re: [Astlinux-users] Delay after Asterisk Dial when no DNS > > Holy wayback machine ... though what you quoted seems to be still valid. > > The "Local Domain" checkbox determines a dnsmasq configuration for whether the listed Domain is part of an upstream DNS zone or to create an independent local DNS zone. > > It would appear a Domain of "ipcsolutions.local" would have Local Domain checked (the default). with a thought: > > 1) Years ago using .local caused issues in some cases with clients using mDNS, Zeroconf, not sure if that is problem anymore, I'm suspecting newer OS client's are OK. > > Lonnie > > > On Sep 22, 2017, at 8:21 PM, Michael Knill <mic...@ip...> wrote: > >> Actually sorry if Local Domain is checked which is now going to be the case for virtually all my systems, then 3) is irrelevant anyway. >> >> Regards >> Michael Knill >> >> -----Original Message----- >> From: Michael Knill <mic...@ip...> >> Reply-To: AstLinux List <ast...@li...> >> Date: Saturday, 23 September 2017 at 11:18 am >> To: AstLinux List <ast...@li...> >> Subject: Re: [Astlinux-users] Delay after Asterisk Dial when no DNS >> >> Ok I have looked back through the Astlinux archives and found one of Lonnie's old posts. >> ------------------ >> ==== >> Single Interface (only External Interface: defined) configuration: >> 1) In the Network tab, make the Hostname: and Domain: match that of the upstream DNS server. >> 2) Uncheck the "Local Domain" box. >> 3) Make sure no IPv4 (or IPv6/nn) addresses are defined in any of the "Internal Interfaces:" section fields. >> ==== >> Now, in your case, you have internal interfaces/networks. As a rule the first defined internal interface (usually 1st LAN) will automatically have a /etc/hosts entry: >> -- >> INTIP HOSTNAME.DOMAIN HOSTNAME >> -- >> Note: Regardless if "Local Domain" is checked or unchecked, HOSTNAME will resolve to INTIP. The file /etc/hosts always has priority. >> >> So, if you have internal interfaces/networks the DOMAIN should normally be unique and "Local Domain" should be checked. For example DOMAIN could be "local' or I personally use "priv.abelbeck.com" as my AstLinux DOMAIN which does not occur anywhere in the public DNS. >> >> Define your DNS hosts for your local devices by using Network tab -> DNS Forwarder & DHCP Server { Configure DNS Hosts } >> These values will be automatically added to the /etc/hosts file for DNS, "Restart DNS" to apply the changes. >> >> Note the DHCP server will pass out DOMAIN so all local devices will have the scope of the *unique* local domain. >> --------------------- >> >> I have a couple of questions: >> 1) I don't quite understand '1) In the Network tab, make the Hostname: and Domain: match that of the upstream DNS server'. Could you please explain sorry? >> 2) Im assuming that basically all my systems (with an internal interface) should be ipcsolutions.local with 'Local Domain' checked? >> 3) I realise that the DNS requests below are for IPv6. Can I turn this off? >> >> Regards >> Michael Knill |
|
From: Michael K. <mic...@ip...> - 2017-09-23 04:10:51
|
Thanks Lonnie. Interesting - https://en.wikipedia.org/wiki/.local I think I will change them all to priv.<my domain> like you have. Regards Michael Knill -----Original Message----- From: Lonnie Abelbeck <li...@lo...> Reply-To: AstLinux List <ast...@li...> Date: Saturday, 23 September 2017 at 1:44 pm To: AstLinux List <ast...@li...> Subject: Re: [Astlinux-users] Delay after Asterisk Dial when no DNS Holy wayback machine ... though what you quoted seems to be still valid. The "Local Domain" checkbox determines a dnsmasq configuration for whether the listed Domain is part of an upstream DNS zone or to create an independent local DNS zone. It would appear a Domain of "ipcsolutions.local" would have Local Domain checked (the default). with a thought: 1) Years ago using .local caused issues in some cases with clients using mDNS, Zeroconf, not sure if that is problem anymore, I'm suspecting newer OS client's are OK. Lonnie On Sep 22, 2017, at 8:21 PM, Michael Knill <mic...@ip...> wrote: > Actually sorry if Local Domain is checked which is now going to be the case for virtually all my systems, then 3) is irrelevant anyway. > > Regards > Michael Knill > > -----Original Message----- > From: Michael Knill <mic...@ip...> > Reply-To: AstLinux List <ast...@li...> > Date: Saturday, 23 September 2017 at 11:18 am > To: AstLinux List <ast...@li...> > Subject: Re: [Astlinux-users] Delay after Asterisk Dial when no DNS > > Ok I have looked back through the Astlinux archives and found one of Lonnie's old posts. > ------------------ > ==== > Single Interface (only External Interface: defined) configuration: > 1) In the Network tab, make the Hostname: and Domain: match that of the upstream DNS server. > 2) Uncheck the "Local Domain" box. > 3) Make sure no IPv4 (or IPv6/nn) addresses are defined in any of the "Internal Interfaces:" section fields. > ==== > Now, in your case, you have internal interfaces/networks. As a rule the first defined internal interface (usually 1st LAN) will automatically have a /etc/hosts entry: > -- > INTIP HOSTNAME.DOMAIN HOSTNAME > -- > Note: Regardless if "Local Domain" is checked or unchecked, HOSTNAME will resolve to INTIP. The file /etc/hosts always has priority. > > So, if you have internal interfaces/networks the DOMAIN should normally be unique and "Local Domain" should be checked. For example DOMAIN could be "local' or I personally use "priv.abelbeck.com" as my AstLinux DOMAIN which does not occur anywhere in the public DNS. > > Define your DNS hosts for your local devices by using Network tab -> DNS Forwarder & DHCP Server { Configure DNS Hosts } > These values will be automatically added to the /etc/hosts file for DNS, "Restart DNS" to apply the changes. > > Note the DHCP server will pass out DOMAIN so all local devices will have the scope of the *unique* local domain. > --------------------- > > I have a couple of questions: > 1) I don't quite understand '1) In the Network tab, make the Hostname: and Domain: match that of the upstream DNS server'. Could you please explain sorry? > 2) Im assuming that basically all my systems (with an internal interface) should be ipcsolutions.local with 'Local Domain' checked? > 3) I realise that the DNS requests below are for IPv6. Can I turn this off? > > Regards > Michael Knill > > -----Original Message----- > From: Michael Knill <mic...@ip...> > Reply-To: AstLinux List <ast...@li...> > Date: Saturday, 23 September 2017 at 9:58 am > To: AstLinux List <ast...@li...> > Subject: Re: [Astlinux-users] Delay after Asterisk Dial when no DNS > > Far out! I have found the problem and it all due to the fact that I don't know what I am doing ( > > When I do tcpdump on eth0 (WAN), every call I make e.g. even extension to extension does this: > 09:28:14.684997 IP 172.17.17.200.54004 > 172.17.17.1.domain: 60192+ AAAA? 3999-IBCBuild-CM1.ipcsolutions.local. (54) > 09:28:14.685599 IP 172.17.17.1.domain > 172.17.17.200.54004: 60192 NXDomain 0/0/0 (54) > 09:28:14.701505 IP 172.17.17.200.52348 > 172.17.17.1.domain: 26730+ AAAA? 3999-IBCBuild-CM1.ipcsolutions.local. (54) > 09:28:14.701989 IP 172.17.17.1.domain > 172.17.17.200.52348: 26730 NXDomain 0/0/0 (54) > > Why is it trying to resolve my local host? > When I check local domain it fixes this problem but is this the best practice? > Sorry Im a little confused! > > Regards > Michael Knill > > -----Original Message----- > From: Lonnie Abelbeck <li...@lo...> > Reply-To: AstLinux List <ast...@li...> > Date: Saturday, 23 September 2017 at 8:50 am > To: AstLinux List <ast...@li...> > Subject: Re: [Astlinux-users] Delay after Asterisk Dial when no DNS > > Hi Michael, > > It is my understanding that chan_sip trunks only does DNS lookups at (asterisk) startup unless you enable ... dnsmgr.conf -> enable=yes . Possibly registers always do DNS lookups, not certain. > > As long as local DNS entries are in your hosts file (Network tab -> DNS Forwarder & DHCP Server: { Configure DNS Hosts } it should work, I would guess. > > In the old days, I recall running Asterisk 1.2 and 1.4 on single core boxes like the PC Engines WRAP and Soekris net4801, and Asterisk DNS lookups were blocking and could *totally* lock-up a system when the WAN connection went down. I have not seen than behavior, personally, in quite some time. Multi-core and dnsmasq helps. > > Lonnie > > > On Sep 21, 2017, at 6:49 PM, Michael Knill <mic...@ip...> wrote: > >> Is it possible to resolve this problem E.g. if you lose your WAN (and therefore DNS), you can still make internal calls without the large delay? >> >> Regards >> Michael Knill >> ------------------------------------------------------------------------------ >> Check out the vibrant tech community on one of the world's most >> engaging tech sites, Slashdot.org! http://sdm.link/slashdot_______________________________________________ >> Astlinux-users mailing list >> Ast...@li... >> https://lists.sourceforge.net/lists/listinfo/astlinux-users >> >> Donations to support AstLinux are graciously accepted via PayPal to pa...@kr.... > > > ------------------------------------------------------------------------------ > Check out the vibrant tech community on one of the world's most > engaging tech sites, Slashdot.org! http://sdm.link/slashdot > _______________________________________________ > Astlinux-users mailing list > Ast...@li... > https://lists.sourceforge.net/lists/listinfo/astlinux-users > > Donations to support AstLinux are graciously accepted via PayPal to pa...@kr.... > > > ------------------------------------------------------------------------------ > Check out the vibrant tech community on one of the world's most > engaging tech sites, Slashdot.org! http://sdm.link/slashdot > _______________________________________________ > Astlinux-users mailing list > Ast...@li... > https://lists.sourceforge.net/lists/listinfo/astlinux-users > > Donations to support AstLinux are graciously accepted via PayPal to pa...@kr.... > > > ------------------------------------------------------------------------------ > Check out the vibrant tech community on one of the world's most > engaging tech sites, Slashdot.org! http://sdm.link/slashdot > _______________________________________________ > Astlinux-users mailing list > Ast...@li... > https://lists.sourceforge.net/lists/listinfo/astlinux-users > > Donations to support AstLinux are graciously accepted via PayPal to pa...@kr.... > > > ------------------------------------------------------------------------------ > Check out the vibrant tech community on one of the world's most > engaging tech sites, Slashdot.org! http://sdm.link/slashdot > _______________________________________________ > Astlinux-users mailing list > Ast...@li... > https://lists.sourceforge.net/lists/listinfo/astlinux-users > > Donations to support AstLinux are graciously accepted via PayPal to pa...@kr.... > > ------------------------------------------------------------------------------ Check out the vibrant tech community on one of the world's most engaging tech sites, Slashdot.org! http://sdm.link/slashdot _______________________________________________ Astlinux-users mailing list Ast...@li... https://lists.sourceforge.net/lists/listinfo/astlinux-users Donations to support AstLinux are graciously accepted via PayPal to pa...@kr.... |
|
From: Lonnie A. <li...@lo...> - 2017-09-23 03:44:03
|
Holy wayback machine ... though what you quoted seems to be still valid. The "Local Domain" checkbox determines a dnsmasq configuration for whether the listed Domain is part of an upstream DNS zone or to create an independent local DNS zone. It would appear a Domain of "ipcsolutions.local" would have Local Domain checked (the default). with a thought: 1) Years ago using .local caused issues in some cases with clients using mDNS, Zeroconf, not sure if that is problem anymore, I'm suspecting newer OS client's are OK. Lonnie On Sep 22, 2017, at 8:21 PM, Michael Knill <mic...@ip...> wrote: > Actually sorry if Local Domain is checked which is now going to be the case for virtually all my systems, then 3) is irrelevant anyway. > > Regards > Michael Knill > > -----Original Message----- > From: Michael Knill <mic...@ip...> > Reply-To: AstLinux List <ast...@li...> > Date: Saturday, 23 September 2017 at 11:18 am > To: AstLinux List <ast...@li...> > Subject: Re: [Astlinux-users] Delay after Asterisk Dial when no DNS > > Ok I have looked back through the Astlinux archives and found one of Lonnie's old posts. > ------------------ > ==== > Single Interface (only External Interface: defined) configuration: > 1) In the Network tab, make the Hostname: and Domain: match that of the upstream DNS server. > 2) Uncheck the "Local Domain" box. > 3) Make sure no IPv4 (or IPv6/nn) addresses are defined in any of the "Internal Interfaces:" section fields. > ==== > Now, in your case, you have internal interfaces/networks. As a rule the first defined internal interface (usually 1st LAN) will automatically have a /etc/hosts entry: > -- > INTIP HOSTNAME.DOMAIN HOSTNAME > -- > Note: Regardless if "Local Domain" is checked or unchecked, HOSTNAME will resolve to INTIP. The file /etc/hosts always has priority. > > So, if you have internal interfaces/networks the DOMAIN should normally be unique and "Local Domain" should be checked. For example DOMAIN could be "local' or I personally use "priv.abelbeck.com" as my AstLinux DOMAIN which does not occur anywhere in the public DNS. > > Define your DNS hosts for your local devices by using Network tab -> DNS Forwarder & DHCP Server { Configure DNS Hosts } > These values will be automatically added to the /etc/hosts file for DNS, "Restart DNS" to apply the changes. > > Note the DHCP server will pass out DOMAIN so all local devices will have the scope of the *unique* local domain. > --------------------- > > I have a couple of questions: > 1) I don't quite understand '1) In the Network tab, make the Hostname: and Domain: match that of the upstream DNS server'. Could you please explain sorry? > 2) Im assuming that basically all my systems (with an internal interface) should be ipcsolutions.local with 'Local Domain' checked? > 3) I realise that the DNS requests below are for IPv6. Can I turn this off? > > Regards > Michael Knill > > -----Original Message----- > From: Michael Knill <mic...@ip...> > Reply-To: AstLinux List <ast...@li...> > Date: Saturday, 23 September 2017 at 9:58 am > To: AstLinux List <ast...@li...> > Subject: Re: [Astlinux-users] Delay after Asterisk Dial when no DNS > > Far out! I have found the problem and it all due to the fact that I don't know what I am doing ( > > When I do tcpdump on eth0 (WAN), every call I make e.g. even extension to extension does this: > 09:28:14.684997 IP 172.17.17.200.54004 > 172.17.17.1.domain: 60192+ AAAA? 3999-IBCBuild-CM1.ipcsolutions.local. (54) > 09:28:14.685599 IP 172.17.17.1.domain > 172.17.17.200.54004: 60192 NXDomain 0/0/0 (54) > 09:28:14.701505 IP 172.17.17.200.52348 > 172.17.17.1.domain: 26730+ AAAA? 3999-IBCBuild-CM1.ipcsolutions.local. (54) > 09:28:14.701989 IP 172.17.17.1.domain > 172.17.17.200.52348: 26730 NXDomain 0/0/0 (54) > > Why is it trying to resolve my local host? > When I check local domain it fixes this problem but is this the best practice? > Sorry Im a little confused! > > Regards > Michael Knill > > -----Original Message----- > From: Lonnie Abelbeck <li...@lo...> > Reply-To: AstLinux List <ast...@li...> > Date: Saturday, 23 September 2017 at 8:50 am > To: AstLinux List <ast...@li...> > Subject: Re: [Astlinux-users] Delay after Asterisk Dial when no DNS > > Hi Michael, > > It is my understanding that chan_sip trunks only does DNS lookups at (asterisk) startup unless you enable ... dnsmgr.conf -> enable=yes . Possibly registers always do DNS lookups, not certain. > > As long as local DNS entries are in your hosts file (Network tab -> DNS Forwarder & DHCP Server: { Configure DNS Hosts } it should work, I would guess. > > In the old days, I recall running Asterisk 1.2 and 1.4 on single core boxes like the PC Engines WRAP and Soekris net4801, and Asterisk DNS lookups were blocking and could *totally* lock-up a system when the WAN connection went down. I have not seen than behavior, personally, in quite some time. Multi-core and dnsmasq helps. > > Lonnie > > > On Sep 21, 2017, at 6:49 PM, Michael Knill <mic...@ip...> wrote: > >> Is it possible to resolve this problem E.g. if you lose your WAN (and therefore DNS), you can still make internal calls without the large delay? >> >> Regards >> Michael Knill >> ------------------------------------------------------------------------------ >> Check out the vibrant tech community on one of the world's most >> engaging tech sites, Slashdot.org! http://sdm.link/slashdot_______________________________________________ >> Astlinux-users mailing list >> Ast...@li... >> https://lists.sourceforge.net/lists/listinfo/astlinux-users >> >> Donations to support AstLinux are graciously accepted via PayPal to pa...@kr.... > > > ------------------------------------------------------------------------------ > Check out the vibrant tech community on one of the world's most > engaging tech sites, Slashdot.org! http://sdm.link/slashdot > _______________________________________________ > Astlinux-users mailing list > Ast...@li... > https://lists.sourceforge.net/lists/listinfo/astlinux-users > > Donations to support AstLinux are graciously accepted via PayPal to pa...@kr.... > > > ------------------------------------------------------------------------------ > Check out the vibrant tech community on one of the world's most > engaging tech sites, Slashdot.org! http://sdm.link/slashdot > _______________________________________________ > Astlinux-users mailing list > Ast...@li... > https://lists.sourceforge.net/lists/listinfo/astlinux-users > > Donations to support AstLinux are graciously accepted via PayPal to pa...@kr.... > > > ------------------------------------------------------------------------------ > Check out the vibrant tech community on one of the world's most > engaging tech sites, Slashdot.org! http://sdm.link/slashdot > _______________________________________________ > Astlinux-users mailing list > Ast...@li... > https://lists.sourceforge.net/lists/listinfo/astlinux-users > > Donations to support AstLinux are graciously accepted via PayPal to pa...@kr.... > > > ------------------------------------------------------------------------------ > Check out the vibrant tech community on one of the world's most > engaging tech sites, Slashdot.org! http://sdm.link/slashdot > _______________________________________________ > Astlinux-users mailing list > Ast...@li... > https://lists.sourceforge.net/lists/listinfo/astlinux-users > > Donations to support AstLinux are graciously accepted via PayPal to pa...@kr.... > > |
|
From: Michael K. <mic...@ip...> - 2017-09-23 01:21:37
|
Actually sorry if Local Domain is checked which is now going to be the case for virtually all my systems, then 3) is irrelevant anyway. Regards Michael Knill -----Original Message----- From: Michael Knill <mic...@ip...> Reply-To: AstLinux List <ast...@li...> Date: Saturday, 23 September 2017 at 11:18 am To: AstLinux List <ast...@li...> Subject: Re: [Astlinux-users] Delay after Asterisk Dial when no DNS Ok I have looked back through the Astlinux archives and found one of Lonnie's old posts. ------------------ ==== Single Interface (only External Interface: defined) configuration: 1) In the Network tab, make the Hostname: and Domain: match that of the upstream DNS server. 2) Uncheck the "Local Domain" box. 3) Make sure no IPv4 (or IPv6/nn) addresses are defined in any of the "Internal Interfaces:" section fields. ==== Now, in your case, you have internal interfaces/networks. As a rule the first defined internal interface (usually 1st LAN) will automatically have a /etc/hosts entry: -- INTIP HOSTNAME.DOMAIN HOSTNAME -- Note: Regardless if "Local Domain" is checked or unchecked, HOSTNAME will resolve to INTIP. The file /etc/hosts always has priority. So, if you have internal interfaces/networks the DOMAIN should normally be unique and "Local Domain" should be checked. For example DOMAIN could be "local' or I personally use "priv.abelbeck.com" as my AstLinux DOMAIN which does not occur anywhere in the public DNS. Define your DNS hosts for your local devices by using Network tab -> DNS Forwarder & DHCP Server { Configure DNS Hosts } These values will be automatically added to the /etc/hosts file for DNS, "Restart DNS" to apply the changes. Note the DHCP server will pass out DOMAIN so all local devices will have the scope of the *unique* local domain. --------------------- I have a couple of questions: 1) I don't quite understand '1) In the Network tab, make the Hostname: and Domain: match that of the upstream DNS server'. Could you please explain sorry? 2) Im assuming that basically all my systems (with an internal interface) should be ipcsolutions.local with 'Local Domain' checked? 3) I realise that the DNS requests below are for IPv6. Can I turn this off? Regards Michael Knill -----Original Message----- From: Michael Knill <mic...@ip...> Reply-To: AstLinux List <ast...@li...> Date: Saturday, 23 September 2017 at 9:58 am To: AstLinux List <ast...@li...> Subject: Re: [Astlinux-users] Delay after Asterisk Dial when no DNS Far out! I have found the problem and it all due to the fact that I don't know what I am doing ( When I do tcpdump on eth0 (WAN), every call I make e.g. even extension to extension does this: 09:28:14.684997 IP 172.17.17.200.54004 > 172.17.17.1.domain: 60192+ AAAA? 3999-IBCBuild-CM1.ipcsolutions.local. (54) 09:28:14.685599 IP 172.17.17.1.domain > 172.17.17.200.54004: 60192 NXDomain 0/0/0 (54) 09:28:14.701505 IP 172.17.17.200.52348 > 172.17.17.1.domain: 26730+ AAAA? 3999-IBCBuild-CM1.ipcsolutions.local. (54) 09:28:14.701989 IP 172.17.17.1.domain > 172.17.17.200.52348: 26730 NXDomain 0/0/0 (54) Why is it trying to resolve my local host? When I check local domain it fixes this problem but is this the best practice? Sorry Im a little confused! Regards Michael Knill -----Original Message----- From: Lonnie Abelbeck <li...@lo...> Reply-To: AstLinux List <ast...@li...> Date: Saturday, 23 September 2017 at 8:50 am To: AstLinux List <ast...@li...> Subject: Re: [Astlinux-users] Delay after Asterisk Dial when no DNS Hi Michael, It is my understanding that chan_sip trunks only does DNS lookups at (asterisk) startup unless you enable ... dnsmgr.conf -> enable=yes . Possibly registers always do DNS lookups, not certain. As long as local DNS entries are in your hosts file (Network tab -> DNS Forwarder & DHCP Server: { Configure DNS Hosts } it should work, I would guess. In the old days, I recall running Asterisk 1.2 and 1.4 on single core boxes like the PC Engines WRAP and Soekris net4801, and Asterisk DNS lookups were blocking and could *totally* lock-up a system when the WAN connection went down. I have not seen than behavior, personally, in quite some time. Multi-core and dnsmasq helps. Lonnie On Sep 21, 2017, at 6:49 PM, Michael Knill <mic...@ip...> wrote: > Is it possible to resolve this problem E.g. if you lose your WAN (and therefore DNS), you can still make internal calls without the large delay? > > Regards > Michael Knill > ------------------------------------------------------------------------------ > Check out the vibrant tech community on one of the world's most > engaging tech sites, Slashdot.org! http://sdm.link/slashdot_______________________________________________ > Astlinux-users mailing list > Ast...@li... > https://lists.sourceforge.net/lists/listinfo/astlinux-users > > Donations to support AstLinux are graciously accepted via PayPal to pa...@kr.... ------------------------------------------------------------------------------ Check out the vibrant tech community on one of the world's most engaging tech sites, Slashdot.org! http://sdm.link/slashdot _______________________________________________ Astlinux-users mailing list Ast...@li... https://lists.sourceforge.net/lists/listinfo/astlinux-users Donations to support AstLinux are graciously accepted via PayPal to pa...@kr.... ------------------------------------------------------------------------------ Check out the vibrant tech community on one of the world's most engaging tech sites, Slashdot.org! http://sdm.link/slashdot _______________________________________________ Astlinux-users mailing list Ast...@li... https://lists.sourceforge.net/lists/listinfo/astlinux-users Donations to support AstLinux are graciously accepted via PayPal to pa...@kr.... ------------------------------------------------------------------------------ Check out the vibrant tech community on one of the world's most engaging tech sites, Slashdot.org! http://sdm.link/slashdot _______________________________________________ Astlinux-users mailing list Ast...@li... https://lists.sourceforge.net/lists/listinfo/astlinux-users Donations to support AstLinux are graciously accepted via PayPal to pa...@kr.... |
|
From: Michael K. <mic...@ip...> - 2017-09-23 01:17:51
|
Ok I have looked back through the Astlinux archives and found one of Lonnie's old posts. ------------------ ==== Single Interface (only External Interface: defined) configuration: 1) In the Network tab, make the Hostname: and Domain: match that of the upstream DNS server. 2) Uncheck the "Local Domain" box. 3) Make sure no IPv4 (or IPv6/nn) addresses are defined in any of the "Internal Interfaces:" section fields. ==== Now, in your case, you have internal interfaces/networks. As a rule the first defined internal interface (usually 1st LAN) will automatically have a /etc/hosts entry: -- INTIP HOSTNAME.DOMAIN HOSTNAME -- Note: Regardless if "Local Domain" is checked or unchecked, HOSTNAME will resolve to INTIP. The file /etc/hosts always has priority. So, if you have internal interfaces/networks the DOMAIN should normally be unique and "Local Domain" should be checked. For example DOMAIN could be "local' or I personally use "priv.abelbeck.com" as my AstLinux DOMAIN which does not occur anywhere in the public DNS. Define your DNS hosts for your local devices by using Network tab -> DNS Forwarder & DHCP Server { Configure DNS Hosts } These values will be automatically added to the /etc/hosts file for DNS, "Restart DNS" to apply the changes. Note the DHCP server will pass out DOMAIN so all local devices will have the scope of the *unique* local domain. --------------------- I have a couple of questions: 1) I don't quite understand '1) In the Network tab, make the Hostname: and Domain: match that of the upstream DNS server'. Could you please explain sorry? 2) Im assuming that basically all my systems (with an internal interface) should be ipcsolutions.local with 'Local Domain' checked? 3) I realise that the DNS requests below are for IPv6. Can I turn this off? Regards Michael Knill -----Original Message----- From: Michael Knill <mic...@ip...> Reply-To: AstLinux List <ast...@li...> Date: Saturday, 23 September 2017 at 9:58 am To: AstLinux List <ast...@li...> Subject: Re: [Astlinux-users] Delay after Asterisk Dial when no DNS Far out! I have found the problem and it all due to the fact that I don't know what I am doing ( When I do tcpdump on eth0 (WAN), every call I make e.g. even extension to extension does this: 09:28:14.684997 IP 172.17.17.200.54004 > 172.17.17.1.domain: 60192+ AAAA? 3999-IBCBuild-CM1.ipcsolutions.local. (54) 09:28:14.685599 IP 172.17.17.1.domain > 172.17.17.200.54004: 60192 NXDomain 0/0/0 (54) 09:28:14.701505 IP 172.17.17.200.52348 > 172.17.17.1.domain: 26730+ AAAA? 3999-IBCBuild-CM1.ipcsolutions.local. (54) 09:28:14.701989 IP 172.17.17.1.domain > 172.17.17.200.52348: 26730 NXDomain 0/0/0 (54) Why is it trying to resolve my local host? When I check local domain it fixes this problem but is this the best practice? Sorry Im a little confused! Regards Michael Knill -----Original Message----- From: Lonnie Abelbeck <li...@lo...> Reply-To: AstLinux List <ast...@li...> Date: Saturday, 23 September 2017 at 8:50 am To: AstLinux List <ast...@li...> Subject: Re: [Astlinux-users] Delay after Asterisk Dial when no DNS Hi Michael, It is my understanding that chan_sip trunks only does DNS lookups at (asterisk) startup unless you enable ... dnsmgr.conf -> enable=yes . Possibly registers always do DNS lookups, not certain. As long as local DNS entries are in your hosts file (Network tab -> DNS Forwarder & DHCP Server: { Configure DNS Hosts } it should work, I would guess. In the old days, I recall running Asterisk 1.2 and 1.4 on single core boxes like the PC Engines WRAP and Soekris net4801, and Asterisk DNS lookups were blocking and could *totally* lock-up a system when the WAN connection went down. I have not seen than behavior, personally, in quite some time. Multi-core and dnsmasq helps. Lonnie On Sep 21, 2017, at 6:49 PM, Michael Knill <mic...@ip...> wrote: > Is it possible to resolve this problem E.g. if you lose your WAN (and therefore DNS), you can still make internal calls without the large delay? > > Regards > Michael Knill > ------------------------------------------------------------------------------ > Check out the vibrant tech community on one of the world's most > engaging tech sites, Slashdot.org! http://sdm.link/slashdot_______________________________________________ > Astlinux-users mailing list > Ast...@li... > https://lists.sourceforge.net/lists/listinfo/astlinux-users > > Donations to support AstLinux are graciously accepted via PayPal to pa...@kr.... ------------------------------------------------------------------------------ Check out the vibrant tech community on one of the world's most engaging tech sites, Slashdot.org! http://sdm.link/slashdot _______________________________________________ Astlinux-users mailing list Ast...@li... https://lists.sourceforge.net/lists/listinfo/astlinux-users Donations to support AstLinux are graciously accepted via PayPal to pa...@kr.... ------------------------------------------------------------------------------ Check out the vibrant tech community on one of the world's most engaging tech sites, Slashdot.org! http://sdm.link/slashdot _______________________________________________ Astlinux-users mailing list Ast...@li... https://lists.sourceforge.net/lists/listinfo/astlinux-users Donations to support AstLinux are graciously accepted via PayPal to pa...@kr.... |
|
From: Michael K. <mic...@ip...> - 2017-09-22 23:57:38
|
Far out! I have found the problem and it all due to the fact that I don't know what I am doing (
When I do tcpdump on eth0 (WAN), every call I make e.g. even extension to extension does this:
09:28:14.684997 IP 172.17.17.200.54004 > 172.17.17.1.domain: 60192+ AAAA? 3999-IBCBuild-CM1.ipcsolutions.local. (54)
09:28:14.685599 IP 172.17.17.1.domain > 172.17.17.200.54004: 60192 NXDomain 0/0/0 (54)
09:28:14.701505 IP 172.17.17.200.52348 > 172.17.17.1.domain: 26730+ AAAA? 3999-IBCBuild-CM1.ipcsolutions.local. (54)
09:28:14.701989 IP 172.17.17.1.domain > 172.17.17.200.52348: 26730 NXDomain 0/0/0 (54)
Why is it trying to resolve my local host?
When I check local domain it fixes this problem but is this the best practice?
Sorry Im a little confused!
Regards
Michael Knill
-----Original Message-----
From: Lonnie Abelbeck <li...@lo...>
Reply-To: AstLinux List <ast...@li...>
Date: Saturday, 23 September 2017 at 8:50 am
To: AstLinux List <ast...@li...>
Subject: Re: [Astlinux-users] Delay after Asterisk Dial when no DNS
Hi Michael,
It is my understanding that chan_sip trunks only does DNS lookups at (asterisk) startup unless you enable ... dnsmgr.conf -> enable=yes . Possibly registers always do DNS lookups, not certain.
As long as local DNS entries are in your hosts file (Network tab -> DNS Forwarder & DHCP Server: { Configure DNS Hosts } it should work, I would guess.
In the old days, I recall running Asterisk 1.2 and 1.4 on single core boxes like the PC Engines WRAP and Soekris net4801, and Asterisk DNS lookups were blocking and could *totally* lock-up a system when the WAN connection went down. I have not seen than behavior, personally, in quite some time. Multi-core and dnsmasq helps.
Lonnie
On Sep 21, 2017, at 6:49 PM, Michael Knill <mic...@ip...> wrote:
> Is it possible to resolve this problem E.g. if you lose your WAN (and therefore DNS), you can still make internal calls without the large delay?
>
> Regards
> Michael Knill
> ------------------------------------------------------------------------------
> Check out the vibrant tech community on one of the world's most
> engaging tech sites, Slashdot.org! http://sdm.link/slashdot_______________________________________________
> Astlinux-users mailing list
> Ast...@li...
> https://lists.sourceforge.net/lists/listinfo/astlinux-users
>
> Donations to support AstLinux are graciously accepted via PayPal to pa...@kr....
------------------------------------------------------------------------------
Check out the vibrant tech community on one of the world's most
engaging tech sites, Slashdot.org! http://sdm.link/slashdot
_______________________________________________
Astlinux-users mailing list
Ast...@li...
https://lists.sourceforge.net/lists/listinfo/astlinux-users
Donations to support AstLinux are graciously accepted via PayPal to pa...@kr....
|
|
From: Lonnie A. <li...@lo...> - 2017-09-22 22:50:16
|
Hi Michael,
It is my understanding that chan_sip trunks only does DNS lookups at (asterisk) startup unless you enable ... dnsmgr.conf -> enable=yes . Possibly registers always do DNS lookups, not certain.
As long as local DNS entries are in your hosts file (Network tab -> DNS Forwarder & DHCP Server: { Configure DNS Hosts } it should work, I would guess.
In the old days, I recall running Asterisk 1.2 and 1.4 on single core boxes like the PC Engines WRAP and Soekris net4801, and Asterisk DNS lookups were blocking and could *totally* lock-up a system when the WAN connection went down. I have not seen than behavior, personally, in quite some time. Multi-core and dnsmasq helps.
Lonnie
On Sep 21, 2017, at 6:49 PM, Michael Knill <mic...@ip...> wrote:
> Is it possible to resolve this problem E.g. if you lose your WAN (and therefore DNS), you can still make internal calls without the large delay?
>
> Regards
> Michael Knill
> ------------------------------------------------------------------------------
> Check out the vibrant tech community on one of the world's most
> engaging tech sites, Slashdot.org! http://sdm.link/slashdot_______________________________________________
> Astlinux-users mailing list
> Ast...@li...
> https://lists.sourceforge.net/lists/listinfo/astlinux-users
>
> Donations to support AstLinux are graciously accepted via PayPal to pa...@kr....
|
|
From: Michael K. <mic...@ip...> - 2017-09-22 22:20:42
|
Thanks Michael. Will be a little while before I go PJSIP though. Regards Michael Knill -----Original Message----- From: Michael Keuter <li...@mk...> Reply-To: AstLinux List <ast...@li...> Date: Friday, 22 September 2017 at 6:43 pm To: AstLinux List <ast...@li...> Subject: Re: [Astlinux-users] Delay after Asterisk Dial when no DNS > Am 22.09.2017 um 01:49 schrieb Michael Knill <mic...@ip...>: > > Is it possible to resolve this problem E.g. if you lose your WAN (and therefore DNS), you can still make internal calls without the large delay? > > Regards > Michael Knill Just for info: in Asterisk 14 Digium added new DNS related stuff (but only for PJSIP): http://blogs.asterisk.org/2016/08/10/res_resolver_unbound/ Michael http://www.mksolutions.info ------------------------------------------------------------------------------ Check out the vibrant tech community on one of the world's most engaging tech sites, Slashdot.org! http://sdm.link/slashdot _______________________________________________ Astlinux-users mailing list Ast...@li... https://lists.sourceforge.net/lists/listinfo/astlinux-users Donations to support AstLinux are graciously accepted via PayPal to pa...@kr.... |
|
From: Michael K. <li...@mk...> - 2017-09-22 08:43:08
|
> Am 22.09.2017 um 01:49 schrieb Michael Knill <mic...@ip...>: > > Is it possible to resolve this problem E.g. if you lose your WAN (and therefore DNS), you can still make internal calls without the large delay? > > Regards > Michael Knill Just for info: in Asterisk 14 Digium added new DNS related stuff (but only for PJSIP): http://blogs.asterisk.org/2016/08/10/res_resolver_unbound/ Michael http://www.mksolutions.info |
|
From: Michael K. <mic...@ip...> - 2017-09-22 02:40:13
|
Cool thanks Lonnie I would probably rather specify the MAX_DELAY actually if I had to specify something e.g. set to 1 second. Realistically though if I need to add something to bypass the check then there is a risk that I will forget to remove it. Good option though. Regards Michael Knill -----Original Message----- From: Lonnie Abelbeck <li...@lo...> Reply-To: AstLinux List <ast...@li...> Date: Friday, 22 September 2017 at 10:56 am To: AstLinux List <ast...@li...> Subject: Re: [Astlinux-users] Power outages and SIP Trunks Hi Michael, Great it works for you. Thanks for the feedback. If "a little annoying during build" means while testing when no internet connection, you could define your own variable, ex. IPCSOLUTIONS_TARGET_HOST Updated script by sourcing /etc/rc.conf and using IPCSOLUTIONS_TARGET_HOST if it is defined: https://gist.github.com/abelbeck/5f2b6e0c23ffc0394826cd4681a35879 In this case if IPCSOLUTIONS_TARGET_HOST is not defined, the value 8.8.4.4 (or whatever you set as the default) will be used. During setup you could define in your /mnt/kd/rc.conf.d/users.conf file to point to localhost or some internal IP address -- IPCSOLUTIONS_TARGET_HOST="127.0.0.1" -- Track revisions here: (missed a dollar-sign in revision #2) Click "View" for any revision. https://gist.github.com/abelbeck/5f2b6e0c23ffc0394826cd4681a35879/revisions OR, just add the rc.elocal script as the last step in your build, OR leave the "chmod 755 /mnt/kd/rc.elocal" to the very end or push to install time. Lonnie On Sep 21, 2017, at 7:05 PM, Michael Knill <mic...@ip...> wrote: > Thanks Lonnie this script works perfectly. > Its going to be a little annoying during build but its worth it! > > Regards > Michael Knill > > -----Original Message----- > From: Lonnie Abelbeck <li...@lo...> > Reply-To: AstLinux List <ast...@li...> > Date: Tuesday, 19 September 2017 at 11:02 am > To: AstLinux List <ast...@li...> > Subject: Re: [Astlinux-users] Power outages and SIP Trunks > > Hi Michael, > > I'm not sure if this will help, but here is a rc.elocal script that waits until a target host can be pinged ... > > Startup delay using /mnt/kd/rc.elocal > https://gist.github.com/abelbeck/5f2b6e0c23ffc0394826cd4681a35879 > > Make the file executable, test in your lab, ideally change the IPv4 address to your SIP provider or such. > > Note you can't use DNS names since the resolver is not configured at this point. > > Probably disable WANDELAY when using this. > > Lonnie > > > On Sep 17, 2017, at 5:55 PM, Michael Knill <mic...@ip...> wrote: > >> Hi All >> >> Im starting to see a number of issues on my SIP Trunks when there is a power outage at the site. I assume the issues is when both the modem and Astlinux appliance are power reset, if the modem does not come up as fast as Astlinux, the PPPoE interface will not be available for Asterisk and for some reason the SIP Trunk stays down until you do a reload. >> >> Yes there is a WAN delay parameter for this but is there something else I can do to make this a bit more robust? >> Does anyone know what actually causes this? Why does it not keep trying? Does it just give up when there is no route? >> Should I maybe have a static default route with a high metric pointing to null or something else? >> >> Regards >> Michael Knill > > > > ------------------------------------------------------------------------------ > Check out the vibrant tech community on one of the world's most > engaging tech sites, Slashdot.org! http://sdm.link/slashdot > _______________________________________________ > Astlinux-users mailing list > Ast...@li... > https://lists.sourceforge.net/lists/listinfo/astlinux-users > > Donations to support AstLinux are graciously accepted via PayPal to pa...@kr.... > > > ------------------------------------------------------------------------------ > Check out the vibrant tech community on one of the world's most > engaging tech sites, Slashdot.org! http://sdm.link/slashdot > _______________________________________________ > Astlinux-users mailing list > Ast...@li... > https://lists.sourceforge.net/lists/listinfo/astlinux-users > > Donations to support AstLinux are graciously accepted via PayPal to pa...@kr.... > > ------------------------------------------------------------------------------ Check out the vibrant tech community on one of the world's most engaging tech sites, Slashdot.org! http://sdm.link/slashdot _______________________________________________ Astlinux-users mailing list Ast...@li... https://lists.sourceforge.net/lists/listinfo/astlinux-users Donations to support AstLinux are graciously accepted via PayPal to pa...@kr.... |
|
From: Lonnie A. <li...@lo...> - 2017-09-22 00:56:37
|
Hi Michael, Great it works for you. Thanks for the feedback. If "a little annoying during build" means while testing when no internet connection, you could define your own variable, ex. IPCSOLUTIONS_TARGET_HOST Updated script by sourcing /etc/rc.conf and using IPCSOLUTIONS_TARGET_HOST if it is defined: https://gist.github.com/abelbeck/5f2b6e0c23ffc0394826cd4681a35879 In this case if IPCSOLUTIONS_TARGET_HOST is not defined, the value 8.8.4.4 (or whatever you set as the default) will be used. During setup you could define in your /mnt/kd/rc.conf.d/users.conf file to point to localhost or some internal IP address -- IPCSOLUTIONS_TARGET_HOST="127.0.0.1" -- Track revisions here: (missed a dollar-sign in revision #2) Click "View" for any revision. https://gist.github.com/abelbeck/5f2b6e0c23ffc0394826cd4681a35879/revisions OR, just add the rc.elocal script as the last step in your build, OR leave the "chmod 755 /mnt/kd/rc.elocal" to the very end or push to install time. Lonnie On Sep 21, 2017, at 7:05 PM, Michael Knill <mic...@ip...> wrote: > Thanks Lonnie this script works perfectly. > Its going to be a little annoying during build but its worth it! > > Regards > Michael Knill > > -----Original Message----- > From: Lonnie Abelbeck <li...@lo...> > Reply-To: AstLinux List <ast...@li...> > Date: Tuesday, 19 September 2017 at 11:02 am > To: AstLinux List <ast...@li...> > Subject: Re: [Astlinux-users] Power outages and SIP Trunks > > Hi Michael, > > I'm not sure if this will help, but here is a rc.elocal script that waits until a target host can be pinged ... > > Startup delay using /mnt/kd/rc.elocal > https://gist.github.com/abelbeck/5f2b6e0c23ffc0394826cd4681a35879 > > Make the file executable, test in your lab, ideally change the IPv4 address to your SIP provider or such. > > Note you can't use DNS names since the resolver is not configured at this point. > > Probably disable WANDELAY when using this. > > Lonnie > > > On Sep 17, 2017, at 5:55 PM, Michael Knill <mic...@ip...> wrote: > >> Hi All >> >> Im starting to see a number of issues on my SIP Trunks when there is a power outage at the site. I assume the issues is when both the modem and Astlinux appliance are power reset, if the modem does not come up as fast as Astlinux, the PPPoE interface will not be available for Asterisk and for some reason the SIP Trunk stays down until you do a reload. >> >> Yes there is a WAN delay parameter for this but is there something else I can do to make this a bit more robust? >> Does anyone know what actually causes this? Why does it not keep trying? Does it just give up when there is no route? >> Should I maybe have a static default route with a high metric pointing to null or something else? >> >> Regards >> Michael Knill > > > > ------------------------------------------------------------------------------ > Check out the vibrant tech community on one of the world's most > engaging tech sites, Slashdot.org! http://sdm.link/slashdot > _______________________________________________ > Astlinux-users mailing list > Ast...@li... > https://lists.sourceforge.net/lists/listinfo/astlinux-users > > Donations to support AstLinux are graciously accepted via PayPal to pa...@kr.... > > > ------------------------------------------------------------------------------ > Check out the vibrant tech community on one of the world's most > engaging tech sites, Slashdot.org! http://sdm.link/slashdot > _______________________________________________ > Astlinux-users mailing list > Ast...@li... > https://lists.sourceforge.net/lists/listinfo/astlinux-users > > Donations to support AstLinux are graciously accepted via PayPal to pa...@kr.... > > |
|
From: Michael K. <mic...@ip...> - 2017-09-22 00:05:45
|
Thanks Lonnie this script works perfectly. Its going to be a little annoying during build but its worth it! Regards Michael Knill -----Original Message----- From: Lonnie Abelbeck <li...@lo...> Reply-To: AstLinux List <ast...@li...> Date: Tuesday, 19 September 2017 at 11:02 am To: AstLinux List <ast...@li...> Subject: Re: [Astlinux-users] Power outages and SIP Trunks Hi Michael, I'm not sure if this will help, but here is a rc.elocal script that waits until a target host can be pinged ... Startup delay using /mnt/kd/rc.elocal https://gist.github.com/abelbeck/5f2b6e0c23ffc0394826cd4681a35879 Make the file executable, test in your lab, ideally change the IPv4 address to your SIP provider or such. Note you can't use DNS names since the resolver is not configured at this point. Probably disable WANDELAY when using this. Lonnie On Sep 17, 2017, at 5:55 PM, Michael Knill <mic...@ip...> wrote: > Hi All > > Im starting to see a number of issues on my SIP Trunks when there is a power outage at the site. I assume the issues is when both the modem and Astlinux appliance are power reset, if the modem does not come up as fast as Astlinux, the PPPoE interface will not be available for Asterisk and for some reason the SIP Trunk stays down until you do a reload. > > Yes there is a WAN delay parameter for this but is there something else I can do to make this a bit more robust? > Does anyone know what actually causes this? Why does it not keep trying? Does it just give up when there is no route? > Should I maybe have a static default route with a high metric pointing to null or something else? > > Regards > Michael Knill ------------------------------------------------------------------------------ Check out the vibrant tech community on one of the world's most engaging tech sites, Slashdot.org! http://sdm.link/slashdot _______________________________________________ Astlinux-users mailing list Ast...@li... https://lists.sourceforge.net/lists/listinfo/astlinux-users Donations to support AstLinux are graciously accepted via PayPal to pa...@kr.... |
|
From: Michael K. <mic...@ip...> - 2017-09-21 23:49:27
|
Is it possible to resolve this problem E.g. if you lose your WAN (and therefore DNS), you can still make internal calls without the large delay? Regards Michael Knill |
63 messages has been excluded from this view by a project administrator.
