Apt-get update is almost endless

I forgot to tell, I use the internet through a proxy server, maybe that's the case. The problem is still here. And this also happens sometimes when apt-get upgrading, and i think that it really downloads the target file many-many times.

Still waiting for anyone to answer

Thanks for reporting this bug and helping make Ubuntu better.

To help us diagnose, please attach your /etc/apt/sources.list file and any files in /etc/apt/sources.list.d/

Thanks!

It's been a while, and I've made some tests. This happens not only in Gutsy Server, but also in GUI Hardy 8.04 with Synaptic and all the updates.

The problem occurs only if using proxy-server, both when using ~/.bashrc or apt.conf.d to set the proxy.

The sources.list is a pretty general one, i haven't made any changes to it. I tried to experiment, and leave only a couple of lines there, but the results were negative, proving that it's not the sources.list case.

Also, not only the Release.gpg file is downloaded thousands of times. Rarely, but also present, much larger files, like Packages.gz are being downloaded many-many times. And as I pay for the bandwith, this is really disturbing.

Turning of the proxy completely solves the problem, but i can turn it off only for testing purposes.

The proxy server is built with "Kerio WinRoute", and I think the problem lies within this piece of software. But apt (and also Synaptic) still lets itself download the files for thousands of times, which is not nice.

The complete contents of the /etc/apt directory are attached.

Hi Igor, thanks, btw, for taking the time to create this bug report,

This long-open bug report seems to be unique to your proxy, which I suspect is misconfigured in some way, so I'm going to mark it back to Incomplete.

If you can post a full tcpdump of the communication between your server and the proxy server, that might help identify whether or not it is a problem with the way apt does HTTP, or whether it is your server possibly mangling HTTP headers improperly.

To generate the tcpdump, first make sure tcpdump is installed, then run this:

tcpdump -n -s 1500 -w proxy.tcpdump host ip.address.of.proxy and port XX

where XX is the port your server communicates with the proxy on. If you have a transparent proxy, you'll want to just do host security.ubuntu.com.

Leave that running while you see the negative affects, then when you are done, use 'ctrl-C' to cancel it, and upload proxy.tcpdump to this bug report.

Please make sure this only contains publicly accessible communication, *or* mark the bug private before posting such a file.

As I suggested at the beginning, marking Incomplete. Feel free to return the status to 'New' after posting a tcpdump. Then somebody can take a look and confirm that it is the proxy's fault.

[Expired for apt (Ubuntu) because there has been no activity for 60 days.]