[arm-allstar] Update

[Larry]

As a comment -- I just updated 2 nodes 15 minutes ago and all went perfect.

Larry - N7FM


On 04/24/2018 08:37 AM, "Doug Crompton via arm-allstar" wrote:
> Can you access the hamvoip.org 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 <http://www.crompton.com/hamradio>*
>
>
>
>
> 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 : 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 10520 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 10520 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
>>
>> 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 (98.137.246.8) 56(84) bytes of data.
>> 64 bytes from media-router-fp2.prod1.media.vip.gq1.yahoo.com
>> (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
>> (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
>>
>> 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
>
> Visit the BBB and RPi2/3 web page - http://hamvoip.org
>