Having some weird probs using apt (0.1.9) through a squid proxy. The Squid is version 2.0.PATCH2, all systems mentioned are current Slink systems. When I do an ``apt-get upgrade'' from any system going through the proxy, the upgrade process stops several times with errors like:
--snip-- Error http://va.debian.org slink/main screen Couldn't connect to localhost:8000 Fetched 3215k in 18m28s (2901b/s) ERROR http://va.debian.org/debian/dists/frozen/main/binary-i386/misc/screen_3.7.4-9.deb Couldn't connect to localhost:8000 --snip-- this is (hopefully obviously) from the system that squid runs on. It goes through several downloads, then refuses the connection. There is nothing else using the proxy. The logs show: --snip-- Nov 15 16:17:57 Phalanx squid[8803]: clientSendMoreData: Deferring http://va.deb ian.org/debian/dists/frozen/main/binary-i386/devel/libc6-dev%5f2.0.7u-5.deb Nov 15 16:20:29 Phalanx squid[8803]: clientKeepaliveNextRequest: FD 18 Sending next Nov 15 16:20:36 Phalanx squid[8803]: clientSendMoreData: Deferring http://va.deb ian.org/debian/dists/frozen/main/binary-i386/misc/screen%5f3.7.4-9.deb Nov 15 16:27:28 Phalanx squid[8803]: clientKeepaliveNextRequest: FD 18 Sending next Nov 15 16:27:28 Phalanx squid[8803]: clientKeepaliveNextRequest: entry->swap_status == STORE_ABORTED Nov 15 16:27:38 Phalanx squid[8915]: Starting Squid Cache version 2.0.PATCH2 for i386-debian-linux-gnu... Nov 15 16:27:38 Phalanx squid[8915]: Process ID 8915 Nov 15 16:27:38 Phalanx squid[8915]: With 256 file descriptors available --snip-- Which is quite weird- it looks like the proxy is getting stopped and restarted for some reason. This is bad. What seems strange is that the problem only pops up when using apt-get. w3 browsing seems to work just fine. Any suggestions? PS: I'm not subscribed to the list (too high of a signal/noise ratio...) so if you have any suggestions, please cc to my reply address.
