[arm-allstar] Update

Doug Crompton wa3dsp at gmail.com
Thu Apr 26 00:12:46 EST 2018


Andy,

I discussed your situation with Dave and I also talked to someone on my hub
that regularly uses a satellite. He is on hughesnet satellite and he
switched in the last few months to a new bird they have. He was having some
minor problems on the old one but says the new one is working well. I don't
remember if you specified who your provider was? We might see if anyone
else is using the same service that you are and having success.

I would suggest if at all possible that you take your node somewhere that
you can plug into Ethernet not on a satellite and see if it updates. It is
usually not necessary to do every update we put out. Only a few would be
more critical and we always identify that. Missing an update does not mean
you won't get that update later. Updates are cumulative so if you didn't
update in several months you would get all the updates that were published
during that time.


*73 Doug*

*WA3DSP*

*http://www.crompton.com/hamradio <http://www.crompton.com/hamradio>*




On Wed, Apr 25, 2018 at 11:53 AM, NV6V <nv6v at calaverasars.org> wrote:

> David,
>
>    I originally used 127.0.0.1 but found that option 1 was not even
> starting the script.  I added my ISP's dns and that got me through the
> first hurdle of option 1 but it still fails eventually.
>    I think I'll burn a new image tonight and start over.  No big deal,
> this node is a work in progress.  I'll see how the new image behaves with
> the update before I touch anything else and get back to you.
>
> Thanks for all the help!
>
> ---
> Andy
>
> On 2018-04-25 06:07, David McGough wrote:
>
>> Andy,
>>
>> I'm completely baffled as to what is going on. I'm sure the web servers
>> and package archives are on-line and accessible.
>>
>> What DNS server are you using---the local copy of bind9 on the
>> address 127.0.0.1 or other?
>>
>> 73, David KB4FXC
>>
>>
>>
>>
>> On Wed, 25 Apr 2018, NV6V wrote:
>>
>> David,
>>>
>>>     I was able to ping hamvoip.org, then I ran option 1 and the update
>>> failed.  From the bash prompt, I successfully retrieved the hamvoip.org
>>> web page then manually ran the update and it failed again.
>>>
>>> pacman log:
>>> [2018-04-23 16:12] [PACMAN] Running
>>> '/usr/local/hamvoip-pacman/bin/pacman --force --noconfirm --yes -Syu'
>>> [2018-04-23 16:12] [PACMAN] synchronizing package lists
>>> [2018-04-24 18:13] [PACMAN] Running
>>> '/usr/local/hamvoip-pacman/bin/pacman --force --noconfirm --yes -Syu'
>>> [2018-04-24 18:13] [PACMAN] synchronizing package lists
>>> [2018-04-25 05:10] [PACMAN] Running
>>> '/usr/local/hamvoip-pacman/bin/pacman --force --noconfirm --yes -Syu'
>>> [2018-04-25 05:10] [PACMAN] synchronizing package lists
>>> [2018-04-25 05:13] [PACMAN] Running
>>> '/usr/local/hamvoip-pacman/bin/pacman --force --noconfirm --yes -Syu'
>>> [2018-04-25 05:13] [PACMAN] synchronizing package lists
>>> ------
>>> Bash prompt attempt:
>>>
>>> [root at nv6v1 ~]# wget hamvoip.org
>>> --2018-04-25 05:13:24--  http://hamvoip.org/
>>> Resolving hamvoip.org (hamvoip.org)... 12.17.29.162
>>> Connecting to hamvoip.org (hamvoip.org)|12.17.29.162|:80... connected.
>>> HTTP request sent, awaiting response... 302 Found
>>> Location: https://hamvoip.org/ [following]
>>> --2018-04-25 05:13:35--  https://hamvoip.org/
>>> Connecting to hamvoip.org (hamvoip.org)|12.17.29.162|:443... connected.
>>> HTTP request sent, awaiting response... 200 OK
>>> Length: unspecified [text/html]
>>> Saving to: 'index.html.1'
>>>
>>> index.html.1            [ <=>                ]  66.27K  --.-KB/s    in
>>> 0.1s
>>>
>>> 2018-04-25 05:13:39 (450 KB/s) - 'index.html.1' saved [67862]
>>>
>>> [root at nv6v1 ~]# /usr/local/hamvoip-pacman/bin/pacman --force --noconfirm
>>> --yes -Syu
>>> :: Synchronizing package databases...
>>> error: failed retrieving file 'core.db' from hamvoip.org : Resolving
>>> timed out after 10520 milliseconds
>>> error: failed to update core (download library error)
>>> error: failed retrieving file 'extra.db' from hamvoip.org : Resolving
>>> timed out after 10519 milliseconds
>>> error: failed to update extra (download library error)
>>> error: failed retrieving file 'community.db' from hamvoip.org :
>>> Resolving timed out after 10521 milliseconds
>>> error: failed to update community (download library error)
>>> error: failed retrieving file 'alarm.db' from hamvoip.org : Resolving
>>> timed out after 10520 milliseconds
>>> error: failed to update alarm (download library error)
>>> error: failed retrieving file 'aur.db' from hamvoip.org : Resolving
>>> timed out after 10521 milliseconds
>>> error: failed to update aur (download library error)
>>> error: failed retrieving file 'hamvoip.db' from hamvoip.org : Resolving
>>> timed out after 10520 milliseconds
>>> error: failed to update hamvoip (download library error)
>>> error: failed to synchronize all databases
>>> [root at nv6v1 ~]#
>>>
>>> ---
>>> Ping:
>>>
>>> [root at nv6v1 ~]# ping hamvoip.org
>>> PING hamvoip.org (12.17.29.162) 56(84) bytes of data.
>>> 64 bytes from newplesk.inttek.net (12.17.29.162): icmp_seq=1 ttl=52
>>> time=698 ms
>>> 64 bytes from newplesk.inttek.net (12.17.29.162): icmp_seq=2 ttl=52
>>> time=708 ms
>>> 64 bytes from newplesk.inttek.net (12.17.29.162): icmp_seq=3 ttl=52
>>> time=708 ms
>>> 64 bytes from newplesk.inttek.net (12.17.29.162): icmp_seq=4 ttl=52
>>> time=1138 ms
>>> 64 bytes from newplesk.inttek.net (12.17.29.162): icmp_seq=5 ttl=52
>>> time=701 ms
>>> ^C
>>> --- hamvoip.org ping statistics ---
>>> 6 packets transmitted, 5 received, 16% packet loss, time 9709ms
>>> rtt min/avg/max/mdev = 698.034/791.001/1138.566/173.832 ms, pipe 2
>>> [root at nv6v1 ~]#
>>>
>>>
>>>
>>> ---
>>> Andy
>>>
>>>
>>> On 2018-04-25 03:35, David McGough wrote:
>>> > Andy,
>>> >
>>> > I enabled ping responses for the hamvoip.org server, since this might
>>> > help
>>> > with diagnostics.
>>> >
>>> > For a test, try to "pre-load" the DNS cache at your end by either
>>> > pinging
>>> > hamvoip.org or using wget to retrieve the index.html.  Then,
>>> > immediately
>>> > go a try to perform a pacman update. If pacman still fails, please send
>>> > any contents from the pacman log file: /var/log/pacman.log
>>> >
>>> > The pacman software retrieves the package updates via the hamvoip.org
>>> > web
>>> > server, just like using wget or looking at the webpage via a browser.
>>> > If
>>> > pacman still won't work, I'm suspecting some type of filtering on your
>>> > satellite link, even though that would seem unlikely since we're using
>>> > TLS encryption (https) on the web server.
>>> >
>>> > 73, David KB4FXC
>>> >
>>> >
>>> >
>>> > On Tue, 24 Apr 2018, "NV6V via arm-allstar" wrote:
>>> >
>>> >> This confirms I can get to the web site:
>>> >> [root at nv6v1 ~]# wget hamvoip.org
>>> >> --2018-04-24 10:44:45--  http://hamvoip.org/
>>> >> Resolving hamvoip.org (hamvoip.org)... 12.17.29.162
>>> >> Connecting to hamvoip.org (hamvoip.org)|12.17.29.162|:80...
>>> connected.
>>> >> HTTP request sent, awaiting response... 302 Found
>>> >> Location: https://hamvoip.org/ [following]
>>> >> --2018-04-24 10:44:57--  https://hamvoip.org/
>>> >> Connecting to hamvoip.org (hamvoip.org)|12.17.29.162|:443...
>>> >> connected.
>>> >> HTTP request sent, awaiting response... 200 OK
>>> >> Length: unspecified [text/html]
>>> >> Saving to: 'index.html'
>>> >>
>>> >> index.html                [  <=>                  ]  66.27K   101KB/s
>>> >> in 0.7s
>>> >>
>>> >> 2018-04-24 10:45:01 (101 KB/s) - 'index.html' saved [67862]
>>> >>
>>> >> ---
>>> >> Andy
>>> >>
>>> >> On 2018-04-24 09:49, Doug Crompton wrote:
>>> >> > Pings are turned off at hamvoip.org [1] for security reasons. It
>>> you
>>> >> > can access the web page it is working. We will have to figure out
>>> why
>>> >> > updates are not working for you thru the satellite.
>>> >> >
>>> >> > 73 Doug
>>> >> > WA3DSP
>>> >> > http://www.crompton.com/hamradio [2]
>>> >> >
>>> >> > On Tue, Apr 24, 2018 at 11:51 AM, NV6V <nv6v at calaverasars.org>
>>> wrote:
>>> >> >
>>> >> >> I can certainly access the website from my windows computer on the
>>> >> >> same router.  I can't ping hamvoip.org [1] from the pi, but it
>>> >> >> resolves to 12.17.29.162.  I can't ping that address from here at
>>> >> >> work either.  I just tried pinging hamvoip.org [1] from the pi
>>> again
>>> >> >> and it took 7 seconds (in my head) to resolve the address.  Still
>>> no
>>> >> >> returns.
>>> >> >>
>>> >> >> ---
>>> >> >> Andy
>>> >> >>
>>> >> >> On 2018-04-24 08:37, "Doug Crompton via arm-allstar" wrote:
>>> >> >> Can you access the hamvoip.org [1] website from your end?  I know
>>> >> >> others are
>>> >> >> using satellites but I have not heard of any update problems. Did
>>> it
>>> >> >> work
>>> >> >> before? Is this the first time you have done an update?
>>> >> >>
>>> >> >> *73 Doug*
>>> >> >>
>>> >> >> *WA3DSP*
>>> >> >>
>>> >> >> *http://www.crompton.com/hamradio [2]
>>> >> >> <http://www.crompton.com/hamradio [2]>*
>>> >> >>
>>> >> >> On Tue, Apr 24, 2018 at 11:18 AM, "NV6V via arm-allstar" <
>>> >> >> arm-allstar at hamvoip.org> wrote:
>>> >> >>
>>> >> >> Greetings List,
>>> >> >>
>>> >> >> My node (46739) has never successfully completed the update
>>> >> >> script
>>> >> >> (option 1).  I ran
>>> >> >> /usr/local/hamvoip-pacman/bin/pacman --force --noconfirm --yes
>>> -Syu
>>> >> >> manually and got this result:
>>> >> >> :: Synchronizing package databases...
>>> >> >> error: failed retrieving file 'core.db' from hamvoip.org [1] :
>>> >> >> Resolving
>>> >> >> timed out after 10520 milliseconds
>>> >> >> error: failed to update core (download library error)
>>> >> >> error: failed retrieving file 'extra.db' from hamvoip.org [1] :
>>> >> >> Resolving
>>> >> >> timed out after 10519 milliseconds
>>> >> >> error: failed to update extra (download library error)
>>> >> >> error: failed retrieving file 'community.db' from hamvoip.org [1]
>>> :
>>> >> >> Resolving
>>> >> >> timed out after 10520 milliseconds
>>> >> >> error: failed to update community (download library error)
>>> >> >> error: failed retrieving file 'alarm.db' from hamvoip.org [1] :
>>> >> >> Resolving
>>> >> >> timed out after 10520 milliseconds
>>> >> >> error: failed to update alarm (download library error)
>>> >> >> error: failed retrieving file 'aur.db' from hamvoip.org [1] :
>>> >> >> Resolving timed
>>> >> >> out after 10520 milliseconds
>>> >> >> error: failed to update aur (download library error)
>>> >> >> error: failed retrieving file 'hamvoip.db' from hamvoip.org [1] :
>>> >> >> Resolving
>>> >> >> timed out after 10520 milliseconds
>>> >> >> error: failed to update hamvoip (download library error)
>>> >> >> error: failed to synchronize all databases
>>> >> >>
>>> >> >> I can connect to nodes.
>>> >> >> What address is this script trying to resolve?
>>> >> >>
>>> >> >> Internet access is ViaSat satellite, which of course is very high
>>> >> >> latency:
>>> >> >> PING yahoo.com [3] (98.137.246.8) 56(84) bytes of data.
>>> >> >> 64 bytes from media-router-fp2.prod1.media.vip.gq1.yahoo.com [4]
>>> >> >> (98.137.246.8): icm     p_seq=1 ttl=52 time=669 ms
>>> >> >> 64 bytes from media-router-fp2.prod1.media.vip.gq1.yahoo.com [4]
>>> >> >> (98.137.246.8): icm     p_seq=2 ttl=52 time=655 ms
>>> >> >>
>>> >> >> But not 10 seconds worth.  Looks like maybe the host resolution is
>>> >> >> what
>>> >> >> takes so long initially.
>>> >> >>
>>> >> >> Any ideas for me to try?
>>> >> >>
>>> >> >> --
>>> >> >> Andy Thomas
>>> >> >> NV6V
>>> >> >> _______________________________________________
>>> >> >>
>>> >> >> arm-allstar mailing list
>>> >> >> arm-allstar at hamvoip.org
>>> >> >> http://lists.hamvoip.org/cgi-bin/mailman/listinfo/arm-allstar [5]
>>> >> >>
>>> >> >> Visit the BBB and RPi2/3 web page - http://hamvoip.org
>>> >> >>
>>> >> >> _______________________________________________
>>> >> >>
>>> >> >> arm-allstar mailing list
>>> >> >> arm-allstar at hamvoip.org
>>> >> >> http://lists.hamvoip.org/cgi-bin/mailman/listinfo/arm-allstar [5]
>>> >> >>
>>> >> >> Visit the BBB and RPi2/3 web page - http://hamvoip.org
>>> >> >
>>> >> >
>>> >> >
>>> >> > Links:
>>> >> > ------
>>> >> > [1] http://hamvoip.org
>>> >> > [2] http://www.crompton.com/hamradio
>>> >> > [3] http://yahoo.com
>>> >> > [4] http://media-router-fp2.prod1.media.vip.gq1.yahoo.com
>>> >> > [5] http://lists.hamvoip.org/cgi-bin/mailman/listinfo/arm-allstar
>>> >> _______________________________________________
>>> >>
>>> >> arm-allstar mailing list
>>> >> arm-allstar at hamvoip.org
>>> >> http://lists.hamvoip.org/cgi-bin/mailman/listinfo/arm-allstar
>>> >>
>>> >> Visit the BBB and RPi2/3 web page - http://hamvoip.org
>>> >>
>>>
>>>
>


More information about the arm-allstar mailing list