I don't believe that any special fix is need for ubiquity given that the
bug and fix were in apt, so I'm setting this task to Invalid.
** Changed in: ubiquity (Ubuntu Bionic)
Status: New => Invalid
** Tags removed: rls-bb-incoming
--
You received this bug notification because you are a m
** Changed in: ubiquity (Ubuntu)
Status: Incomplete => Confirmed
** Changed in: ubiquity (Ubuntu)
Status: Confirmed => Fix Released
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1766542
** Changed in: oem-priority
Status: Confirmed => Fix Released
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1766542
Title:
Installation blocks when the machine is behind a proxy server
To ma
This bug was fixed in the package apt - 1.6.2
---
apt (1.6.2) unstable; urgency=medium
* Fix build with new gtest (Closes: #897149)
* Handle a missed case of timed out ip addresses (LP: #1766542)
* Lower default network timeouts from 120s to 30s
* apt-key: Pass all instead of
I had to tweak the time outs a bit, as I quickly get some errors from
the networking stack (like 7s or so), but I could successfully verify
the fix now, using a standard ubuntu:bionic lxd container, and modifying
the routes, and setting a lower timeout:
+ ip r del default
+ ip r add default via 10
Hello Robert, or anyone else affected,
Accepted apt into bionic-proposed. The package will build now and be
available at https://launchpad.net/ubuntu/+source/apt/1.6.2 in a few
hours, and then in the -proposed repository.
Please help us by testing this new package. See
https://wiki.ubuntu.com/Te
** Description changed:
- 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.
+ [Impact]
+ APT takes a long time to notice when c
** Changed in: apt (Ubuntu Bionic)
Status: New => In Progress
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1766542
Title:
Installation blocks when the machine is behind a proxy server
To ma
This bug was fixed in the package apt - 1.7.0~alpha0ubuntu2
---
apt (1.7.0~alpha0ubuntu2) cosmic; urgency=medium
[ David Kalnischkies ]
* Add boilerplate plural form to po/apt-all.pot
* don't try SRV requests based on IP addresses
* use 127.0.0.1 instead of localhost as defaul
** Changed in: apt (Ubuntu)
Status: Triaged => Fix Committed
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1766542
Title:
Installation blocks when the machine is behind a proxy server
To man
** Tags added: id-5af9ea356db8cb2d4eb3d4e7
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1766542
Title:
Installation blocks when the machine is behind a proxy server
To manage notifications about t
For the apt side, that's the first commit in
https://salsa.debian.org/apt-team/apt/merge_requests/18/
I'll also upload that to bionic eventually; but xenial would also need
the happy eyeballs changes, which were a bit large (although, isolated).
--
You received this bug notification because you
I don't think we can realistically go lower than 2x30s - I think the
intention is to add the mirror and security separately and comment them
out if they don't work or something, so they need to be in seperate apt
runs. Unless, of course, we write a tool in python or something that
does update there
It seems we are experiencing a bug in apt in bionic WRT the 90s timeout.
With happy eyeballs, we added a new place where stuff can timeout; and
we did not mark these IP addresses as failed, hence they were always
retried, and thus you saw it attempting to connect 3 times to
tw.archive.ubuntu.com.
@Julian,
Here is the archive of logs. Sorry I forgot to attach it before.
** Attachment added: "var-log-installer-18_04.tgz"
https://bugs.launchpad.net/ubuntu/+source/ubiquity/+bug/1766542/+attachment/5143739/+files/var-log-installer-18_04.tgz
--
You received this bug notification because y
I don't see how we can achieve an overall timeout. We only have per
connect() timeouts available, and we run multiple apt processes /
fetches. We can limit the individual connect() timeout to 30s, but
overall? I think we do one attempt for archive.ubuntu.com / mirror and a
another for security, so
Hi @Steve,
IMO, it would be great that the period is less than 30 seconds in total.
In this case, the updating operation is always failed. Users should know that
the Internet is not available before setting a proxy server. They may expect to
have a minimum timeout or pre-configure the proxy serve
> Significant blockings -
> "Retrieving file 1 of 3", 90 seconds
> "Retrieving file 1 of 1", 32 seconds
Does this mean that in 18.04, the full delay you see is 122 seconds?
Is that considered acceptable, or not?
--
You received this bug notification because you are a member of Ubuntu
Bugs, whic
Image: ubuntu-18.04-desktop-amd64.iso
Significant blockings -
"Retrieving file 1 of 3", 90 seconds
"Retrieving file 1 of 1", 32 seconds
The behavior is different from 16.04.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bug
Here is how I setup the environment:
1. prepare a broadband gateway. This time I use LEDE with VirtualBox. I can
upload the VM image if necessary.
2. add a firewall rule on the gateway: all http/https traffic from LAN port
will be redirected to a IP which is not used by any machine.
3. install Ub
Image: ubuntu-16.04.4-desktop-amd64.iso
Significant blockings -
"Retrieving file 1 of 93", 30 seconds
"Retrieving file 1 of 31", 3 minutes
** Attachment added: "var-log-installer-16_04.tgz"
https://bugs.launchpad.net/oem-priority/+bug/1766542/+attachment/5141168/+files/var-log-installer-16_04
OK, so archive.ubuntu.com has 4 and 4 A entries, meaning that
16.04 waits 16 minutes (8 * 2 minutes)
18.04 waits 2 minutes, 2 seconds (2 minutes + 8 * 250 milliseconds)
Now we can shorten that further to one of the following:
* 12 seconds (10 + 8 * 250 ms)
* 22 seconds (20 + 8 * 250 ms)
* 3
The default time out now is:
- 120s * #ip-addresses before bionic
- 120s + 250ms * #ip-addresses for bionic
That's a substantial improvement. I still think we should lower the
timeout from 120s to 20s for cosmic, bringing this down to 20s + 250ms *
#ipaddr (if we estimate up to 4 ip addresses, it
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
Robert, can you please provide complete steps to reproduce this bug? My
understanding from discussion elsewhere that this is specific to oem-
config mode; is that correct?
If your network is incorrectly configured and you have a route to the
Internet but traffic is dropped, it is expected that an
** Tags added: rls-bb-incoming
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1766542
Title:
Installation blocks when the machine is behind a proxy server
To manage notifications about this bug go t
** Changed in: ubiquity (Ubuntu)
Importance: Undecided => High
** Also affects: apt (Ubuntu)
Importance: Undecided
Status: New
** Also affects: apt (Ubuntu Bionic)
Importance: Undecided
Status: New
** Also affects: ubiquity (Ubuntu Bionic)
Importance: High
Status
Tried the 18.04 daily build (http://cdimage.ubuntu.com/ubuntu/daily-
live/20180424/bionic-desktop-amd64.iso), and it has the same issue.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1766542
Title:
need test results on 18.04.
** Changed in: oem-priority
Status: New => Confirmed
** Changed in: oem-priority
Importance: Undecided => High
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1766
** Also affects: oem-priority
Importance: Undecided
Status: New
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1766542
Title:
Installation blocks when the machine is behind a proxy server
30 matches
Mail list logo
