I've been considering lowering the timeout in apt from 120s to something like 10-30s for a year or two, but there's been some concern about high- latency connections. I personally do not think that 120s is a sensible timeout for one round trip.
There are also several options to prevent this issue on the network side: - do not provide DNS servers / resolve internet names - do not drop packets, but reject them - point a SRV record in your DNS server to a working HTTP host (either serving the archive, or 404, as long as it connects, it should be fine) We also had the same issue on some IPv6+IPv4 systems where the IPv6 is not reachable, but that's fixed in cosmic with happy eyeballs falling back to the next host within milliseconds (trying more and more hosts in parallel until one works). -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to apt in Ubuntu. https://bugs.launchpad.net/bugs/1766542 Title: Installation blocks when the machine is behind a proxy server Status in OEM Priority Project: Confirmed Status in apt package in Ubuntu: New Status in ubiquity package in Ubuntu: Incomplete Status in apt source package in Bionic: New Status in ubiquity source package in Bionic: New Bug description: When the machine is behind a proxy server, the installation will block for a while (several minutes) to retrieve the package lists. The timeouts are too long and makes user feels the machine may have some problems. The symptom is similar with bug #14599, but it seems the apt-setup module was rewritten. Another method to trigger this issue is to make the machine cannot access to the Internet, for instance: a wrong gateway. Image: 16.04 To manage notifications about this bug go to: https://bugs.launchpad.net/oem-priority/+bug/1766542/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : [email protected] Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
