thenorm
Posts: 11
Joined: Mon Feb 24, 2014 2:05 am

failures during sudo apt-get upgrade

Sun Jan 07, 2018 1:23 am

I'm getting continuous "failure resolving 'mirrordirector.raspbian.org' msgs.
Does this indicate some problem with server?

User avatar
d3vCr0w
Posts: 7
Joined: Tue Jul 18, 2017 10:32 am

Re: failures during sudo apt-get upgrade

Sun Jan 07, 2018 5:53 am

Hi, I did a ping to mirrordirector.raspbian.org and it seems like the server is ok, can you try doing a ping to that address from a different computer?

User avatar
rpdom
Posts: 15234
Joined: Sun May 06, 2012 5:17 am
Location: Chelmsford, Essex, UK

Re: failures during sudo apt-get upgrade

Sun Jan 07, 2018 9:10 am

thenorm wrote:
Sun Jan 07, 2018 1:23 am
I'm getting continuous "failure resolving 'mirrordirector.raspbian.org' msgs.
Does this indicate some problem with server?
It usually indicates an issue with your internet connection. Failure to resolve the name means that your computer (Pi) is unable to find out the IP address of the server called 'mirrordirector.raspbian.org'. That is almost certainly a problem at your end.

Try these general network troubleshooting commands and post exactly what they show you:

Code: Select all

cat /etc/resolv.conf
ping -c 1 8.8.8.8
ping -c 1 google.com
ip route
ip addr
Some may take a short while to respond.

thenorm
Posts: 11
Joined: Mon Feb 24, 2014 2:05 am

Re: failures during sudo apt-get upgrade

Fri Jan 12, 2018 11:17 pm

Strange thing is I'm using SSH here and my PC has a perfectly good internet connection. I'm afraid it may be some setting in the router and that's all a mystery to me.

Well here's what I got.

[email protected]:~ $ cat /etc/resolv.conf
# Generated by resolvconf
nameserver 2607:f428:ffff:ffff::1
nameserver 2607:f428:ffff:ffff::2
[email protected]:~ $
[email protected]:~ $ ping -c 1 8.8.8.8
PING 8.8.8.8 (8.8.8.8) 56(84) bytes of data.
64 bytes from 8.8.8.8: icmp_seq=1 ttl=54 time=27.5 ms

--- 8.8.8.8 ping statistics ---
1 packets transmitted, 1 received, 0% packet loss, time 0ms
rtt min/avg/max/mdev = 27.548/27.548/27.548/0.000 ms
[email protected]:~ $ ping -c 1 google.com
ping: google.com: Temporary failure in name resolution
[email protected]:~ $ ip route
default via 192.168.1.1 dev wlan0 src 192.168.1.108 metric 303
192.168.1.0/24 dev wlan0 proto kernel scope link src 192.168.1.108 metric 303
[email protected]:~ $ ip addr
1: lo: <LOOPBACK,UP,LOWER_UP> mtu 65536 qdisc noqueue state UNKNOWN group default qlen 1
link/loopback 00:00:00:00:00:00 brd 00:00:00:00:00:00
inet 127.0.0.1/8 scope host lo
valid_lft forever preferred_lft forever
inet6 ::1/128 scope host
valid_lft forever preferred_lft forever
2: eth0: <NO-CARRIER,BROADCAST,MULTICAST,UP> mtu 1500 qdisc pfifo_fast state DOWN group default qlen 1000
link/ether b8:27:eb:ee:7d:34 brd ff:ff:ff:ff:ff:ff
inet6 fe80::ba27:ebff:feee:7d34/64 scope link tentative
valid_lft forever preferred_lft forever
3: wlan0: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc pfifo_fast state UP group default qlen 1000
link/ether b8:27:eb:bb:28:61 brd ff:ff:ff:ff:ff:ff
inet 192.168.1.108/24 brd 192.168.1.255 scope global wlan0
valid_lft forever preferred_lft forever
inet6 2600:6c52:7580:59:0:f852:cb3f:bcb2/128 scope global noprefixroute dynamic
valid_lft 1178130sec preferred_lft 573330sec
inet6 fe80::ba27:ebff:febb:2861/64 scope link
valid_lft forever preferred_lft forever
[email protected]:~ $

Return to “Troubleshooting”