* Warren Overholt: > Sorry, it took a while to find the right people to explain the > network configuration. A BlueCoat was recently installed, which > among other tasks is a proxy server. The bluecoat is supposed to be > an inline cache.
I guess it's the culprit here. Such issues are quite common, unfortunately. > The error I cut and pasted the messages from today was roughly > 2:45-3:00pm EST. The server's IP is 128.150.140.174. I have been > told that the BlueCoat's IP should not show up in the access logs. We've got a request from the .174 IP in our logs for the etch Release file, but no request at all for the corresponding Release.gpg file. I suppose the proxy it is caching an outdated copy for some reason. Obviously, the signature doesn't match the new file. > Given your response, will a solution like apt-proxy, approx, or > apt-cacher help me? This only works if those instances aren't behind the same proxy, and if you can download data from them in ways which your proxy doesn't affect. > Or will that only help me if I can have it's requests to > *.debian.org not be filtered? Filtering and caching is fine, but the proxy should honor aptitude's requests to bypass it. This way, you will still get the benefit of caching the actual package files. -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
