[linux] apt werkt niet meer, WTF?

[Geert Stappers]

On Thu, Feb 01, 2018 at 04:32:07PM +0100, paai wrote:
> On 01-02-18 16:10, Geert Stappers wrote:
> >On Thu, Feb 01, 2018 at 03:54:14PM +0100, paai wrote:
> >>Toen ik vanochtend mijn Kubuntu's wilde upgraden, kwamen ze opeens
> >>met de volgende meldingen:
> >>
> >>E: The repository 'http://nl.archive.ubuntu.com/ubuntu zesty
> >>Release' does no longer have a Release file.
> >>N: Updating from such a repository can't be done securely, and is
> >>therefore disabled by default.
> >>
> >Controleer netwerkverbinding en draai
> >
> >    apt update
> >    apt upgrade
> >
> 
> Ja, dat wilde ik doen toen het mis ging. Er is iets mis met de
> nameserver; ik kan google.com wel pingen, maar de ubuntu-servers
> niet.
> 

Vanaf hier ziet de wereld er anders uit.


| $ host nl.archive.ubuntu.com
| nl.archive.ubuntu.com is an alias for ubuntuarchive.bit.nl.
| ubuntuarchive.bit.nl is an alias for ftp.bit.nl.
| ftp.bit.nl has address 213.136.12.213
| ftp.bit.nl has IPv6 address 2001:7b8:3:37::21:3
| $ ping -c 3 nl.archive.ubuntu.com
| PING nl.archive.ubuntu.com(ftp.bit.nl (2001:7b8:3:37::21:3)) 56 data bytes
| 64 bytes from ftp.bit.nl (2001:7b8:3:37::21:3): icmp_seq=1 ttl=58 time=10.2 ms
| 64 bytes from ftp.bit.nl (2001:7b8:3:37::21:3): icmp_seq=2 ttl=58 time=11.3 ms
| 64 bytes from ftp.bit.nl (2001:7b8:3:37::21:3): icmp_seq=3 ttl=58 time=10.9 ms
| 
| --- nl.archive.ubuntu.com ping statistics ---
| 3 packets transmitted, 3 received, 0% packet loss, time 2002ms
| rtt min/avg/max/mdev = 10.209/10.815/11.316/0.473 ms
| $ ping4 -c 3 nl.archive.ubuntu.com
| PING ftp.bit.nl (213.136.12.213) 56(84) bytes of data.
| 64 bytes from ftp.bit.nl (213.136.12.213): icmp_seq=1 ttl=58 time=10.6 ms
| 64 bytes from ftp.bit.nl (213.136.12.213): icmp_seq=2 ttl=58 time=13.1 ms
| 64 bytes from ftp.bit.nl (213.136.12.213): icmp_seq=3 ttl=58 time=10.3 ms
| 
| --- ftp.bit.nl ping statistics ---
| 3 packets transmitted, 3 received, 0% packet loss, time 2002ms
| rtt min/avg/max/mdev = 10.332/11.375/13.130/1.248 ms
| $ 


Als het alleen een nameserver issue is,
kun je het even in /etc/hosts zetten.


Groeten
Geert Stappers
-- 
Leven en laten leven