Temporary failure resolving

General support for the Pi-Star System
Post Reply
m3lox
Posts: 17
Joined: Wed Apr 11, 2018 6:54 pm
Location: Leeds, UK
Contact:

Temporary failure resolving

Post by m3lox »

Did the usual sudo pistar-update and Im getting this...
Any ideas please>?



Welcome to Pi-Star: v4.1.0-RC5

pi-star@pistar(ro):~$ sudo pistar-update
Updating OS...

Err:1 http://raspbian.raspberrypi.org/raspbian buster InRelease
Temporary failure resolving 'raspbian.raspberrypi.org'
Err:2 http://archive.raspberrypi.org/debian buster InRelease
Temporary failure resolving 'archive.raspberrypi.org'
Err:3 http://httpredir.debian.org/debian buster-backports InRelease
Temporary failure resolving 'httpredir.debian.org'
Reading package lists... Done
W: Failed to fetch http://raspbian.raspberrypi.org/raspbia ... er/InRelea se Temporary failure resolving 'raspbian.raspberrypi.org'
W: Failed to fetch http://archive.raspberrypi.org/debian/d ... /InRelease Temporary failure resolving 'archive.raspberrypi.org'
W: Failed to fetch http://httpredir.debian.org/debian/dist ... kports/InR elease Temporary failure resolving 'httpredir.debian.org'
W: Some index files failed to download. They have been ignored, or old ones used instead.
Reading package lists... Done
Building dependency tree
Reading state information... Done
Calculating upgrade... Done
The following packages will be upgraded:
libdrm-common libdrm2
2 upgraded, 0 newly installed, 0 to remove and 0 not upgraded.
Need to get 0 B/50.2 kB of archives.
After this operation, 4,096 B of additional disk space will be used.
(Reading database ... 42734 files and directories currently installed.)
Preparing to unpack .../libdrm-common_2.4.99-1~bpo10~1_all.deb ...
Unpacking libdrm-common (2.4.99-1~bpo10~1) over (2.4.97-1+rpi1) ...
Preparing to unpack .../libdrm2_2.4.99-1~bpo10~1_armhf.deb ...
Unpacking libdrm2:armhf (2.4.99-1~bpo10~1) over (2.4.97-1+rpi1) ...
Setting up libdrm-common (2.4.99-1~bpo10~1) ...
Setting up libdrm2:armhf (2.4.99-1~bpo10~1) ...
Processing triggers for libc-bin (2.28-10+rpi1) ...
Done
Checking nginx config
Stopping Services...
Done
Updating DV Binaries...
fatal: unable to access 'https://github.com/AndyTaylorTweet/Pi-Star_v4_Binaries_ Bin.git/': Could not resolve host: github.com
User avatar
KE0FHS
Posts: 1122
Joined: Wed Apr 11, 2018 8:40 pm
Location: Colorado, USA
Contact:

Re: Temporary failure resolving

Post by KE0FHS »

This happens sometimes. I think it is due to issues with their servers. Just try again later.
73, Toshen, KE0FHS
Playing with Pi-Star (unofficial notes about setting up and using Pi-Star):
https://amateurradionotes.com/pi-star.htm
n9mxq
Posts: 236
Joined: Sun Apr 29, 2018 12:12 pm

Re: Temporary failure resolving

Post by n9mxq »

I had this on both of my duplex hotspots. I found a simple reboot fixes it nicely.
Gene in Belvidere IL
Please don't email me with questions.
That's what these forums are for.
There's much more brainpower collected here
than I have alone.
m3lox
Posts: 17
Joined: Wed Apr 11, 2018 6:54 pm
Location: Leeds, UK
Contact:

Re: Temporary failure resolving

Post by m3lox »

Reboot, factory reset, reinstalled config backup file...
Still same :-(

fatal: unable to access 'https://github.com/AndyTaylorTweet/Pi-S ... s_Bin.git/': Could not resolve host: github.com
Updating /usr/local/bin...
fatal: unable to access 'https://github.com/AndyTaylorTweet/Pi-S ... s_Bin.git/': Could not resolve host: github.com
fatal: unable to access 'https://github.com/AndyTaylorTweet/Pi-S ... s_Bin.git/': Could not resolve host: github.com
Updates were not successfull, reverting to Pi-Star original files...
HEAD is now at fb626db Update DMRGateway to the 5 master version
Done
Updating Pi-Star Binaries...
fatal: unable to access 'https://github.com/AndyTaylorTweet/Pi-S ... _sbin.git/': Could not resolve host: github.com
Updating /usr/local/sbin...
fatal: unable to access 'https://github.com/AndyTaylorTweet/Pi-S ... _sbin.git/': Could not resolve host: github.com
fatal: unable to access 'https://github.com/AndyTaylorTweet/Pi-S ... _sbin.git/': Could not resolve host: github.com
Updates were not successfull, reverting to Pi-Star original files...
HEAD is now at 285423c Update pistar-upgrade
Done
Updating Hostfiles...
Done
Updating Dashboard...
fatal: unable to access 'https://github.com/AndyTaylorTweet/Pi-Star_DV_Dash.git/': Could not resolve host: github.com
Updating /var/www/dashboard...
fatal: unable to access 'https://github.com/AndyTaylorTweet/Pi-Star_DV_Dash.git/': Could not resolve host: github.com
fatal: unable to access 'https://github.com/AndyTaylorTweet/Pi-Star_DV_Dash.git/': Could not resolve host: github.com
Updates were not successfull, reverting to Pi-Star original files...
HEAD is now at 479f879 Update version.php
m3lox
Posts: 17
Joined: Wed Apr 11, 2018 6:54 pm
Location: Leeds, UK
Contact:

Re: Temporary failure resolving

Post by m3lox »

Sorted by a fresh download of Pi-Star and start again.
m3lox
Posts: 17
Joined: Wed Apr 11, 2018 6:54 pm
Location: Leeds, UK
Contact:

Re: Temporary failure resolving

Post by m3lox »

Hi.
Just wondering as I'm no expert here... If its an outage, how did the rebuild resolve it? Surely the PI would still be accessing the same servers, and would therfore still be not accessible?

Sent from my SM-G935F using Tapatalk

User avatar
YT5HOK
Posts: 30
Joined: Fri Aug 16, 2019 9:20 pm
Location: KN04fr

Re: Temporary failure resolving

Post by YT5HOK »

Errmmm.... Time has passed.
m3lox
Posts: 17
Joined: Wed Apr 11, 2018 6:54 pm
Location: Leeds, UK
Contact:

Re: Temporary failure resolving

Post by m3lox »

But the urls were accessible via a browser on the same network at the time of failing.

Sent from my SM-G935F using Tapatalk

AF6VN
Posts: 821
Joined: Fri Jul 20, 2018 1:15 am

Re: Temporary failure resolving

Post by AF6VN »

m3lox wrote: Mon Sep 30, 2019 11:56 am But the urls were accessible via a browser on the same network at the time of failing.

Sent from my SM-G935F using Tapatalk

Your browser may have cached an IP address and skipped the DNS look-up. Or the computer running the browser had the IP in a cache. Or it was using a different DNS server.

--
AF6VN
Dennis L Bieber
Post Reply