connect (113: No route to host) Could not connect to :80 (91.189.88.24), connection timed out Could not connect to :80 (91.189.91.14), connection timed out Could not connect to :80 (91.189.91.24), connection timed out Could not connect to :80 (91.189.88.174), connection timed out Could not connect to :80 (91.189.91.23), connection timed out Could not connect to :80 (91.189.88.149), connection timed out Could not connect to :80 (91.189.88.31), connection timed out Could not connect to :80 (91.189.91.26), connection timed out Could not connect to :80 (91.189.88.162), connection timed out connect (113: No route to host) Could not connect to :80 (91.189.88.173), connection timed out Could not connect to :80 (91.189.88.24), connection timed out Could not connect to :80 (91.189.88.162), connection timed out Could not connect to :80 (91.189.88.31), connection timed out Could not connect to :80 (91.189.88.149), connection timed out This is the message I get every time I try to apt update: I can do, for example, ping to from my container, and i get a correct response, the same happens with curl, for example: curl I even disabled ufw for a moment in order to check if I had any firewall problem, but even after that, the problem persisted.
I applied the same steps today without any success. $ find /etc/apt/ -name "*.I solved a similar problem some time ago after reading about problems with ubuntu 18.04 and ipv6, using the following solutions:ġ- forcing ipv4 while doing apt update (sudo apt -o Acquire::ForceIPv4=true update)Ģ- modifying /etc/gai.conf, un commenting this line: precedence ::ffff:0:0/96 100ģ- Adding a dns to /etc/systemd/nf, which ends whit a line like: “DNS Servers: 8.8.4.4” (without quotes )Ĥ- modifying /etc/nf in order to add the following lines: EDIT: output "requested" in this answer is here.
Ign:1 bionic-updates/main amd64 apport all 2.20.9-0ubuntu7.17Įrr:1 bionic-updates/main amd64 apport all 2.20.9-0ubuntu7.17Ĥ03 URLBlockDownload Į: Failed to fetch 403 URLBlockDownload Į: Unable to fetch some archives, maybe run apt-get update or try with -fix-missing? This generates output like ant 500 bionic-updates/universe amd64 Packagesġ upgraded, 0 newly installed, 0 to remove and 46 not upgraded.Īfter this operation, 20,5 kB of additional disk space will be used. helps visualizing in columns) $ for p in $(sudo apt list -upgradable 2> /dev/null | sed 's/\/.*//' | tail +2 | sed -e ':a' -e 'N' -e '$!ba' -e 's/\n/ /g') do printf "%30s" $p apt policy $p 2> /dev/null | tail +6 | head -1 done To find which repo each one belonged, I used ( printf "%30s". This was obtained with $ sudo apt list -upgradable 2> /dev/null | sed 's/\/.*//' | tail +2 | sed -e ':a' -e 'N' -e '$!ba' -e 's/\n/ /g'
#Sudo apt update failed to fetch Pc
What is a possible solution (other than connecting the PC without a proxy)?Ĭomplete list of packages not installed ant ant-optional apport apport-gtk fwupd fwupdate fwupdate-signed gettext gettext-base jarwrapper junit4 libasm-java libcommons-collections3-java libcommons-compress-java libcommons-httpclient-java libdb5.3 libdb5.3-java libdb5.3-java-jni libecj-java libequinox-osgi-java libhsqldb1.8.0-java libjetty9-java libnss-systemd libobjenesis-java libpam-systemd libservlet3.1-java libsystemd0 libtomcat8-java linux-generic linux-headers-generic linux-image-generic openjdk-11-jdk openjdk-11-jdk-headless openjdk-11-jre openjdk-11-jre-headless openjdk-8-jdk openjdk-8-jdk-headless openjdk-8-jre openjdk-8-jre-headless python-pip-whl python3-pip snapd systemd How is it possible that some of the packages can be installed and some cannot?
#Sudo apt update failed to fetch install
I could update many of the packages with no problem, and I ended up with 48 that I cannot install.Īll of the packages not installed belong to bionic-updates/universe or bionic-updates/main.Īnd most are related to java, jdk, linux, systemd.īut there are packages from bionic-updates/universe and bionic-updates/main that I can install (I just installed qemu and bsdutils). I had a lot of packages with available updates (more than 200, I guess). I am running Ubuntu 18.04LTS, behind a proxy. What makes this question different (I guess) from the others I have seen is the following. This is yet another question regarding the error message E: Failed to fetch.
0 kommentar(er)
