[arm-allstar] Asterisk crashing when Echolink connected
Matt
matt at m0lmk.co.uk
Mon May 30 04:31:14 EST 2016
It's odd that it seems to be stable without changing anything apart from
the echolink.conf file. A rouge whitespace maybe?
David, I've ran the commands you suggested and no have the following in
simpleusb_tune_usb.conf
[root at allstar asterisk]# cat /etc/asterisk/simpleusb_tune_usb.conf
[usb]
; name=usb
; devicenum=1
devstr=1-1.5:1.0
rxmixerset=500
txmixaset=500
txmixbset=500
I've rebooted the node and all seems ok. I'll keep an eye on it for the
next few hours and see what happens.
All help much appreciated.
Matt
M0LMK
> David McGough via arm-allstar <mailto:arm-allstar at hamvoip.org>
> 30 May 2016 at 10:16
> Another option to hand editing the simpleusb_tune_usb file.conf is to let
> Asterisk set the device for you. On a single node system, try:
>
> ...login as root
>
> asterisk -vvvvrgc
>
> susb tune save
> exit
>
>
> With this procedure, you can insure that the correct device string, from
> Asterisk's perspective, gets saved.
>
> 73, David KB4FXC
>
>
>
>
>
> _______________________________________________
>
> arm-allstar mailing list
> arm-allstar at hamvoip.org
> http://lists.hamvoip.org/cgi-bin/mailman/listinfo/arm-allstar
>
> Visit the BBB and RPi2 web page - http://hamvoip.org
> kk6ecm <mailto:kk6ecm at gmail.com>
> 30 May 2016 at 10:06
> From lsusb, the computer believes the usb interface is at Bus 1,
> device 4, but devstr says the usb interface is at bus 1, device 1.
> This looks like an issue to me. I'd edit the tune file, devstar=1-4.
>
> Thanks,
> Bob
> k6ecm
> 73
>
> Sent from iPad
>
>
> On May 29, 2016, at 11:25 PM, Matt via arm-allstar
> <arm-allstar at hamvoip.org <mailto:arm-allstar at hamvoip.org>> wrote:
>
>> Thanks all.
>>
>> After a successful few hours with the RPi3, I have now moved it back
>> onto the RPi2 and left it running all night.
>>
>> I have witnessed no crashes since I changed the echolink servers in
>> the echolink.conf file.
>>
>> Bob, in answer to your questions, The node does one of 3 things when
>> Echolink crashes.
>>
>> 1. The local RF output will drop part way through the connection
>> telemetry message and reconnect a few seconds later. This is more
>> noticeable when connecting to a node with a long connection message
>> like the echolink test server.
>> 2. The local RF won't output anything and becomes unresponsive to any
>> over the air DTMF. In this case, allmon shows the echolink node as
>> "connecting" and highlights the table row orange. Allmon accepts
>> disconnect requests for the node that is "connecting" but does not
>> actually disconnect it. I have to reboot the Pi to clear this.
>> 3. The worst failure mode. Same as above where allmon shows the node
>> as "connecting" but this time it locks the RF output to TX a silent
>> carrier.
>>
>> Here's the output of lsusb and the contents of my
>> simpleusb_tune_usb.conf...
>>
>> [root at allstar ~]# lsusb
>> Bus 001 Device 004: ID 0d8c:013c C-Media Electronics, Inc. CM108
>> Audio Controller
>> Bus 001 Device 003: ID 0424:ec00 Standard Microsystems Corp.
>> SMSC9512/9514 Fast Ethernet Adapter
>> Bus 001 Device 002: ID 0424:9514 Standard Microsystems Corp. SMC9514 Hub
>> Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
>> [root at allstar ~]# cat /etc/asterisk/simpleusb_tune_usb.conf
>> [usb]
>> ; name=usb
>> ; devicenum=1
>> devstr=1-1:1.0
>> rxmixerset=500
>> txmixaset=500
>> txmixbset=500
>> [root at allstar ~]#
>>
>> Thanks,
>>
>> Matt
>>> kk6ecm via arm-allstar <mailto:arm-allstar at hamvoip.org>
>>> 30 May 2016 at 05:50
>>> In my experience, the errors indicated in the first email always
>>> occur when asterisk is unhappy with a conf file. This can occur when
>>> asterisk does not receive expected results from an attempt to access
>>> a USB device, or can occur when there is an error in the file,
>>> either from my mistake, or a memory problem e.g. sd card corrupted.
>>>
>>> A couple of questions. what is the evidence, other than not crashing
>>> when Echolink is not connected that the node is running properly? Is
>>> it really running correctly?
>>>
>>> Second, does devstr=<bus-device> in your usb_tune file match the
>>> device address in lsusb?
>>>
>>> Thanks,
>>> Bob
>>> k6ecm
>>> 73
>>>
>>> Sent from iPad
>>>
>>>
>>> On May 29, 2016, at 5:37 PM, Doug Crompton via arm-allstar
>>> <arm-allstar at hamvoip.org <mailto:arm-allstar at hamvoip.org>> wrote:
>>>
>>>> Matt,
>>>>
>>>> It would be interesting if it turned out to be the server settings
>>>> but I have played with many server settings over the years and
>>>> never had a crash. The echolink code has been stable for a long
>>>> time. If you can narrow this down so we could test it here it would
>>>> be helpful.
>>>>
>>>> Have you looked at echolink dbdump and dbget in the client. Does
>>>> the database populate before you have the crash?
>>>>
>>>> dbdump in the client is kind of useless in that it just scrolls all
>>>> the nodes out. You can do
>>>>
>>>> asterisk -rx "echolink dbdump" | more or send it to a file.
>>>>
>>>> My current servers:
>>>>
>>>> server1=server1.echolink.org <http://server1.echolink.org>
>>>> ;server2=server5.echolink.org <http://server5.echolink.org>
>>>> server3=server3.echolink.org <http://server3.echolink.org>
>>>> server2=naeast.echolink.org <http://naeast.echolink.org>
>>>>
>>>> The code requires three servers. Half the time there are not three
>>>> that actually work and if you look at address resolution on the
>>>> servers you will see that many are really the same IP address. At
>>>> the moment server 2,3,NAEAST and NAWEST all have the same IP.
>>>>
>>>> Name: server1.echolink.org <http://server1.echolink.org>
>>>> Address: 174.129.36.165
>>>>
>>>> server2.echolink.org <http://server2.echolink.org> canonical
>>>> name = server3.echolink.org <http://server3.echolink.org>.
>>>> Name: server3.echolink.org <http://server3.echolink.org>
>>>> Address: 174.129.209.125
>>>>
>>>> Name: server3.echolink.org <http://server3.echolink.org>
>>>> Address: 174.129.209.125
>>>>
>>>> Name: server4.echolink.org <http://server4.echolink.org>
>>>> Address: 50.18.55.39
>>>>
>>>> Name: server5.echolink.org <http://server5.echolink.org>
>>>> Address: 68.178.144.151
>>>>
>>>> naeast.echolink.org <http://naeast.echolink.org> canonical name
>>>> = server3.echolink.org <http://server3.echolink.org>.
>>>> Name: server3.echolink.org <http://server3.echolink.org>
>>>> Address: 174.129.209.125
>>>>
>>>> nawest.echolink.org <http://nawest.echolink.org> canonical name
>>>> = server3.echolink.org <http://server3.echolink.org>.
>>>> Name: server3.echolink.org <http://server3.echolink.org>
>>>> Address: 174.129.209.125
>>>>
>>>> None of the echolink servers including ones not listed here seem to
>>>> return pings which is strange. I thought they use to.
>>>>
>>>> *73 Doug
>>>> WA3DSP
>>>> http://www.crompton.com/hamradio*
>>>>
>>>>
>>>> ------------------------------------------------------------------------
>>>> Date: Sun, 29 May 2016 19:57:02 +0100
>>>> To: arm-allstar at hamvoip.org <mailto:arm-allstar at hamvoip.org>
>>>> Subject: Re: [arm-allstar] Asterisk crashing when Echolink connected
>>>> From: arm-allstar at hamvoip.org <mailto:arm-allstar at hamvoip.org>
>>>> CC: matt at m0lmk.co.uk <mailto:matt at m0lmk.co.uk>
>>>>
>>>> Hi David,
>>>>
>>>> I'll keep it on the list if you don't mind as it may help others if
>>>> this problem comes up again. I have a working theory but I need to
>>>> do a bit more testing to confirm.
>>>>
>>>> Here are these servers listed in my echolink.conf...
>>>>
>>>> server1=servers.echolink.org <http://servers.echolink.org>
>>>> server2=naeast.echolink.org <http://naeast.echolink.org>
>>>> server3=backup.echolink.org <http://backup.echolink.org>
>>>>
>>>> I noticed that the crash happened just after this line in the
>>>> asterisk console..
>>>>
>>>> -- Received OK from Echolink server servers.echolink.org
>>>> <http://servers.echolink.org>
>>>> -- Received OK from Echolink server backup.echolink.org
>>>> <http://backup.echolink.org>
>>>> allstar*CLI>
>>>> Disconnected from Asterisk server
>>>> Executing last minute cleanups
>>>>
>>>> So, I've changed the servers to the following...
>>>>
>>>> server1=europe.echolink.org <http://europe.echolink.org>
>>>> server2=servers.echolink.org <http://servers.echolink.org>
>>>> server3=backup.echolink.org <http://backup.echolink.org>
>>>>
>>>> And now it only connects to a single server in the asterisk console...
>>>>
>>>> -- Call changed from OUTBOUND to *ECHOTEST*
>>>> -- Name changed from OUTBOUND to (Conference [9]) CONF
>>>> -- Received OK from Echolink server europe.echolink.org
>>>> <http://europe.echolink.org>
>>>> -- Directory pgm done downloading(partial,compressed), 377 records
>>>>
>>>> And have been up for 20 minutes without a crash. Maybe the problem
>>>> was a bad server in the echolink pool?
>>>>
>>>> In answer to your questions.
>>>>
>>>> Is IPv6 networking in this mixture anywhere? - We have an ipv6
>>>> tunnel set up on our main router but all internal networking is ipv4
>>>> What are your Echolink and AllStar node numbers? 43412 (AllStar),
>>>> 214700 (Echolink)
>>>> Does the crash occur when connecting to all Echolink nodes (like
>>>> the Echolink *ECHOTEST* conference server, node #9999)? Happens on
>>>> all nodes I have tried
>>>> Does AllStar connectivity work properly? Yes. I have not seen any
>>>> asterisk crashes when not connected or when connected to an allstar
>>>> node
>>>>
>>>> My current echolink.conf
>>>>
>>>> [el0]
>>>> confmode=no
>>>> call=MB7IBK-L ; Change this!
>>>> pwd=pypassword ; Change this!
>>>> name=MB7IBK ; Change this to your real name!
>>>> qth=Broadstairs, UK ; Change this to your actual QTH!
>>>> email=matt at m0lmk.co.uk <mailto:email=matt at m0lmk.co.uk> ; Change this!
>>>> maxstns=20
>>>> rtcptimeout=10
>>>> node=214700 ; Echolink node number - Change this!
>>>> recfile=/tmp/recorded.gsm
>>>> astnode=43412 ; Change this to your active Allstar node
>>>> number!
>>>> context=radio-secure
>>>> server1=europe.echolink.org <http://europe.echolink.org>
>>>> server2=servers.echolink.org <http://servers.echolink.org>
>>>> server3=backup.echolink.org <http://backup.echolink.org>
>>>> ;server1=servers.echolink.org <http://servers.echolink.org>
>>>> ;server2=naeast.echolink.org <http://naeast.echolink.org>
>>>> ;server3=backup.echolink.org <http://backup.echolink.org>
>>>> ; Change following setting to your parameters
>>>> freq=145.2125
>>>> tone=103.5
>>>> lat=51.36242
>>>> lon=1.44442
>>>> power=1
>>>> height=1
>>>> gain=0
>>>> dir=0
>>>> ;deny=
>>>> ;permit=
>>>>
>>>>
>>>>
>>>> Hope that helps.
>>>>
>>>> Matt
>>>> M0LMK
>>>>
>>>> David McGough via arm-allstar <mailto:arm-allstar at hamvoip.org>
>>>> 29 May 2016 at 19:46
>>>> Hi Matt,
>>>>
>>>> As others have mentioned, I've not seen this issue previously.
>>>> I've got a
>>>> few questions to try and help debug this, feel free to send my
>>>> a private
>>>> e-mail with answers, if you would prefer.
>>>>
>>>> Is IPv6 networking in this mixture anywhere?
>>>>
>>>> What are your Echolink and AllStar node numbers?
>>>>
>>>> Does the crash occur when connecting to all Echolink nodes
>>>> (like the
>>>> Echolink *ECHOTEST* conference server, node #9999)?
>>>>
>>>> If only specific node numbers cause the crash, what nodes are they?
>>>>
>>>> Does AllStar connectivity work properly?
>>>>
>>>>
>>>> Thanks,
>>>>
>>>> 73, David KB4FXC
>>>>
>>>>
>>>>
>>>> _______________________________________________
>>>>
>>>> arm-allstar mailing list
>>>> arm-allstar at hamvoip.org <mailto:arm-allstar at hamvoip.org>
>>>> http://lists.hamvoip.org/cgi-bin/mailman/listinfo/arm-allstar
>>>>
>>>> Visit the BBB and RPi2 web page - http://hamvoip.org
>>>> Matt via arm-allstar <mailto:arm-allstar at hamvoip.org>
>>>> 29 May 2016 at 19:31
>>>> Results so far...
>>>>
>>>> RPi 3 still shows the same behavior although not as often. I've
>>>> now changed the power supply and am still seeing the same
>>>> issue. The last thing on my list is the interface but I don't
>>>> have a spare so that's going to be tough to test.
>>>>
>>>> It seems to only crash asterisk when initially connecting to a
>>>> remote node and as soon as asterisk restarts, the connection
>>>> works fine.
>>>>
>>>> How very odd.
>>>>
>>>> Matt
>>>> M0LMK
>>>>
>>>> _______________________________________________
>>>>
>>>> arm-allstar mailing list
>>>> arm-allstar at hamvoip.org <mailto:arm-allstar at hamvoip.org>
>>>> http://lists.hamvoip.org/cgi-bin/mailman/listinfo/arm-allstar
>>>>
>>>> Visit the BBB and RPi2 web page - http://hamvoip.org
>>>>
>>>>
>>>>
>>>> _______________________________________________ arm-allstar mailing
>>>> list arm-allstar at hamvoip.org <mailto:arm-allstar at hamvoip.org>
>>>> http://lists.hamvoip.org/cgi-bin/mailman/listinfo/arm-allstar Visit
>>>> the BBB and RPi2 web page - http://hamvoip.org
>>>> _______________________________________________
>>>>
>>>> arm-allstar mailing list
>>>> arm-allstar at hamvoip.org <mailto:arm-allstar at hamvoip.org>
>>>> http://lists.hamvoip.org/cgi-bin/mailman/listinfo/arm-allstar
>>>>
>>>> Visit the BBB and RPi2 web page - http://hamvoip.org
>>> _______________________________________________
>>>
>>> arm-allstar mailing list
>>> arm-allstar at hamvoip.org
>>> http://lists.hamvoip.org/cgi-bin/mailman/listinfo/arm-allstar
>>>
>>> Visit the BBB and RPi2 web page -http://hamvoip.org
>>> Doug Crompton via arm-allstar <mailto:arm-allstar at hamvoip.org>
>>> 30 May 2016 at 01:37
>>> Matt,
>>>
>>> It would be interesting if it turned out to be the server settings
>>> but I have played with many server settings over the years and never
>>> had a crash. The echolink code has been stable for a long time. If
>>> you can narrow this down so we could test it here it would be helpful.
>>>
>>> Have you looked at echolink dbdump and dbget in the client. Does the
>>> database populate before you have the crash?
>>>
>>> dbdump in the client is kind of useless in that it just scrolls all
>>> the nodes out. You can do
>>>
>>> asterisk -rx "echolink dbdump" | more or send it to a file.
>>>
>>> My current servers:
>>>
>>> server1=server1.echolink.org <http://server1.echolink.org>
>>> ;server2=server5.echolink.org <http://server5.echolink.org>
>>> server3=server3.echolink.org <http://server3.echolink.org>
>>> server2=naeast.echolink.org <http://naeast.echolink.org>
>>>
>>> The code requires three servers. Half the time there are not three
>>> that actually work and if you look at address resolution on the
>>> servers you will see that many are really the same IP address. At
>>> the moment server 2,3,NAEAST and NAWEST all have the same IP.
>>>
>>> Name: server1.echolink.org <http://server1.echolink.org>
>>> Address: 174.129.36.165
>>>
>>> server2.echolink.org <http://server2.echolink.org> canonical name
>>> = server3.echolink.org <http://server3.echolink.org>.
>>> Name: server3.echolink.org <http://server3.echolink.org>
>>> Address: 174.129.209.125
>>>
>>> Name: server3.echolink.org <http://server3.echolink.org>
>>> Address: 174.129.209.125
>>>
>>> Name: server4.echolink.org <http://server4.echolink.org>
>>> Address: 50.18.55.39
>>>
>>> Name: server5.echolink.org <http://server5.echolink.org>
>>> Address: 68.178.144.151
>>>
>>> naeast.echolink.org <http://naeast.echolink.org> canonical name
>>> = server3.echolink.org <http://server3.echolink.org>.
>>> Name: server3.echolink.org <http://server3.echolink.org>
>>> Address: 174.129.209.125
>>>
>>> nawest.echolink.org <http://nawest.echolink.org> canonical name
>>> = server3.echolink.org <http://server3.echolink.org>.
>>> Name: server3.echolink.org <http://server3.echolink.org>
>>> Address: 174.129.209.125
>>>
>>> None of the echolink servers including ones not listed here seem to
>>> return pings which is strange. I thought they use to.
>>>
>>> *73 Doug
>>> WA3DSP
>>> http://www.crompton.com/hamradio*
>>>
>>>
>>> _______________________________________________
>>>
>>> arm-allstar mailing list
>>> arm-allstar at hamvoip.org
>>> http://lists.hamvoip.org/cgi-bin/mailman/listinfo/arm-allstar
>>>
>>> Visit the BBB and RPi2 web page - http://hamvoip.org
>>> Matt via arm-allstar <mailto:arm-allstar at hamvoip.org>
>>> 29 May 2016 at 19:57
>>> Hi David,
>>>
>>> I'll keep it on the list if you don't mind as it may help others if
>>> this problem comes up again. I have a working theory but I need to
>>> do a bit more testing to confirm.
>>>
>>> Here are these servers listed in my echolink.conf...
>>>
>>> server1=servers.echolink.org <http://servers.echolink.org>
>>> server2=naeast.echolink.org <http://naeast.echolink.org>
>>> server3=backup.echolink.org <http://backup.echolink.org>
>>>
>>> I noticed that the crash happened just after this line in the
>>> asterisk console..
>>>
>>> -- Received OK from Echolink server servers.echolink.org
>>> <http://servers.echolink.org>
>>> -- Received OK from Echolink server backup.echolink.org
>>> <http://backup.echolink.org>
>>> allstar*CLI>
>>> Disconnected from Asterisk server
>>> Executing last minute cleanups
>>>
>>> So, I've changed the servers to the following...
>>>
>>> server1=europe.echolink.org <http://europe.echolink.org>
>>> server2=servers.echolink.org <http://servers.echolink.org>
>>> server3=backup.echolink.org <http://backup.echolink.org>
>>>
>>> And now it only connects to a single server in the asterisk console...
>>>
>>> -- Call changed from OUTBOUND to *ECHOTEST*
>>> -- Name changed from OUTBOUND to (Conference [9]) CONF
>>> -- Received OK from Echolink server europe.echolink.org
>>> <http://europe.echolink.org>
>>> -- Directory pgm done downloading(partial,compressed), 377 records
>>>
>>> And have been up for 20 minutes without a crash. Maybe the problem
>>> was a bad server in the echolink pool?
>>>
>>> In answer to your questions.
>>>
>>> Is IPv6 networking in this mixture anywhere? - We have an ipv6
>>> tunnel set up on our main router but all internal networking is ipv4
>>> What are your Echolink and AllStar node numbers? 43412 (AllStar),
>>> 214700 (Echolink)
>>> Does the crash occur when connecting to all Echolink nodes (like the
>>> Echolink *ECHOTEST* conference server, node #9999)? Happens on all
>>> nodes I have tried
>>> Does AllStar connectivity work properly? Yes. I have not seen any
>>> asterisk crashes when not connected or when connected to an allstar node
>>>
>>> My current echolink.conf
>>>
>>> [el0]
>>> confmode=no
>>> call=MB7IBK-L ; Change this!
>>> pwd=pypassword ; Change this!
>>> name=MB7IBK ; Change this to your real name!
>>> qth=Broadstairs, UK ; Change this to your actual QTH!
>>> email=matt at m0lmk.co.uk ; Change this!
>>> maxstns=20
>>> rtcptimeout=10
>>> node=214700 ; Echolink node number - Change this!
>>> recfile=/tmp/recorded.gsm
>>> astnode=43412 ; Change this to your active Allstar node
>>> number!
>>> context=radio-secure
>>> server1=europe.echolink.org <http://europe.echolink.org>
>>> server2=servers.echolink.org <http://servers.echolink.org>
>>> server3=backup.echolink.org <http://backup.echolink.org>
>>> ;server1=servers.echolink.org <http://servers.echolink.org>
>>> ;server2=naeast.echolink.org <http://naeast.echolink.org>
>>> ;server3=backup.echolink.org <http://backup.echolink.org>
>>> ; Change following setting to your parameters
>>> freq=145.2125
>>> tone=103.5
>>> lat=51.36242
>>> lon=1.44442
>>> power=1
>>> height=1
>>> gain=0
>>> dir=0
>>> ;deny=
>>> ;permit=
>>>
>>>
>>>
>>> Hope that helps.
>>>
>>> Matt
>>> M0LMK
>>>
>>> _______________________________________________
>>>
>>> arm-allstar mailing list
>>> arm-allstar at hamvoip.org
>>> http://lists.hamvoip.org/cgi-bin/mailman/listinfo/arm-allstar
>>>
>>> Visit the BBB and RPi2 web page - http://hamvoip.org
>>> David McGough via arm-allstar <mailto:arm-allstar at hamvoip.org>
>>> 29 May 2016 at 19:46
>>> Hi Matt,
>>>
>>> As others have mentioned, I've not seen this issue previously. I've
>>> got a
>>> few questions to try and help debug this, feel free to send my a private
>>> e-mail with answers, if you would prefer.
>>>
>>> Is IPv6 networking in this mixture anywhere?
>>>
>>> What are your Echolink and AllStar node numbers?
>>>
>>> Does the crash occur when connecting to all Echolink nodes (like the
>>> Echolink *ECHOTEST* conference server, node #9999)?
>>>
>>> If only specific node numbers cause the crash, what nodes are they?
>>>
>>> Does AllStar connectivity work properly?
>>>
>>>
>>> Thanks,
>>>
>>> 73, David KB4FXC
>>>
>>>
>>>
>>> _______________________________________________
>>>
>>> arm-allstar mailing list
>>> arm-allstar at hamvoip.org
>>> http://lists.hamvoip.org/cgi-bin/mailman/listinfo/arm-allstar
>>>
>>> Visit the BBB and RPi2 web page - http://hamvoip.org
>>
>> _______________________________________________
>>
>> arm-allstar mailing list
>> arm-allstar at hamvoip.org <mailto:arm-allstar at hamvoip.org>
>> http://lists.hamvoip.org/cgi-bin/mailman/listinfo/arm-allstar
>>
>> Visit the BBB and RPi2 web page - http://hamvoip.org
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.hamvoip.org/pipermail/arm-allstar/attachments/20160530/6ee9cc03/attachment-0001.html>
More information about the arm-allstar
mailing list