-4

I was working on Ubuntu 16.04.2 version where I had used "sudo apt install git"

The error I am getting is the following:

/root/Downloads/Screenshot from 2019-08-14 12-16-43(1).png error

  • 5
    Please don't post images of text. Copy and paste the text itself into your question and format it as code by selecting it and pressing Ctrl-K or by using the editor's {} icon. – cas Aug 14 at 8:15
0

The first three apt errors all happened with IP address 103.123.234.254, port 80.

The facts that this address was used both when connecting to in.archive.ubuntu.com and also security.ubuntu.com and that the DNS reverse lookup for that IP claims it to be anycast.estointernet.in rather than anything *.ubuntu.com suggest this may be a Content Delivery Network or some arrangement of your Internet Service Provider.

$ dig +short -x 103.123.234.254
anycast.estointernet.in.

The fourth error referred to IP address 91.189.91.23 for security.ubuntu.com.

$ dig +short -x 91.189.91.23
economy.canonical.com.

$ dig +short security.ubuntu.com
91.189.91.26
91.189.91.23    <-- note: here it is!
91.189.88.149
91.189.88.31
91.189.88.24
91.189.88.162

Looks like Canonical (the company that builds Ubuntu) has multiple servers on security.ubuntu.com... as expected, since the amount of traffic to it is probably huge. Each of those servers has a "proper name" in addition to the "umbrella" security.ubuntu.com, and your connection just happened to end up to server named economy.canonical.com. But it looks like that connection failed for some reason.

I don't very much like the idea that estointernet.in (your ISP, I assume) seems to be adding an another layer of reverse-proxy/cache/CDN technology in front of security.ubuntu.com: if that does not work perfectly, it may delay the availability of important security patches. But perhaps that's the only way they can deal with the amount of traffic to security.ubuntu.com they get.

To summarize: it looks like estointernet.in applies some sort of cache/proxy/CDN technology to connections going to Ubuntu's repository servers, and at the time of your connection, it looks like that technology did not work too well, and a fall-back to direct connection also failed, perhaps because of a crowded network somewhere between you and security.ubuntu.com

Your options are probably limited to reporting the problem to your internet connection provider and/or waiting until they fix it, or else trying a different network connection provider.

Your Answer

By clicking “Post Your Answer”, you agree to our terms of service, privacy policy and cookie policy

Not the answer you're looking for? Browse other questions tagged or ask your own question.