This can be reproduced by hosting a mirror on S3. S3 has built in functionality that closes a connection after 100 requests. We were able to add comments to apt source that output every time a new connection was made and we confirmed every 100 requests that S3 did close the connection. Intermittently, we would get the Undetermined Error during one of the connection close events. Debug output confirmed there is a connection: close header. We also confirmed apt identified a 102 connection reset by peer event by printing the error.
So this isn't apache specific, I believe apache is just more prone to sending connection: close. Because of S3's behavior of closing connections every 100 requests, it became very noticeable to us. -- 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/1801338 Title: apt fails to properly handle server-side connection closure Status in apt package in Ubuntu: Triaged Status in apt source package in Xenial: New Status in apt source package in Bionic: Triaged Status in apt source package in Cosmic: Triaged Bug description: [Impact] In some cases, apt does not correctly handle server-side connection closure after a pipeline, and aborts the file being downloaded with an "Undetermined Error" when the connection has been closed. [Test case] This could be seen by running apt build-dep evince on cosmic with a recent apt with the pipelining fix (such as 1.6.6) against a local mirror running apache from trusty. It remains to be seen whether this is easily reproducible for anyone. [Regression potential] N/A yet. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/apt/+bug/1801338/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
