apt-proxy crashes when accessed from localhost

[Joshua Kugler]

Binary package hint: apt-proxy

Dapper, all up to date, apt-proxy version 1.9.33ubuntu1

Accessing it from other hosts, it runs fine, but when I try to access it via a localhost URL (or even the machine's name from that machine), it dies with this traceback:

2006/10/13 16:59 AKDT [Channel,26,127.0.0.1] Unhandled error in Deferred:
2006/10/13 16:59 AKDT [Channel,26,127.0.0.1] Traceback (most recent call last):
          File "/usr/lib/python2.4/site-packages/twisted/web/http.py", line 557, in requestReceived
            self.process()
          File "/usr/lib/python2.4/site-packages/apt_proxy/apt_proxy.py", line 1400, in process
            self.fetch()
          File "/usr/lib/python2.4/site-packages/apt_proxy/apt_proxy.py", line 1482, in fetch
            (dummyFetcher, 0, running,), None)
          File "/usr/lib/python2.4/site-packages/twisted/internet/defer.py", line 182, in addCallbacks
            self._runCallbacks()
        --- <exception caught here> ---
          File "/usr/lib/python2.4/site-packages/twisted/internet/defer.py", line 307, in _runCallbacks
            self.result = callback(self.result, *args, **kw)
          File "/usr/lib/python2.4/site-packages/apt_proxy/apt_proxy.py", line 1451, in fetch_real
            fetcher = dummyFetcher.apEndTransfer(fetcher_class)
          File "/usr/lib/python2.4/site-packages/apt_proxy/apt_proxy.py", line 463, in apEndTransfer
            fetcher = fetcher_class(req)
          File "/usr/lib/python2.4/site-packages/apt_proxy/apt_proxy.py", line 317, in __init__
            self.activate(request)
          File "/usr/lib/python2.4/site-packages/apt_proxy/apt_proxy.py", line 616, in activate
            ClientFactory(self), request.backend.config.timeout)
          File "/usr/lib/python2.4/site-packages/twisted/internet/posixbase.py", line 392, in connectTCP
            c = tcp.Connector(host, port, factory, timeout, bindAddress, self)
          File "/usr/lib/python2.4/site-packages/twisted/internet/tcp.py", line 840, in __init__
            raise error.ServiceNameUnknownError(string="%s (%r)" % (e, port))
        twisted.internet.error.ServiceNameUnknownError: Service name given as port is unknown: service/proto not found ('').

[Joshua Kugler (jkugler)]

Additional information:

It's not just from the localhost. Apt-proxy is crashing if it is access by a VM running on the machine that is running apt-proxy.

Example:

Machine xxx.xxx.xxx.249 is running VMWare Server, with bridged networking

Machine xxx.xxx.xxx.247 is a virtual machine running on the above machine, with its network connection being bridged out over the same interface that hosts .249.

When it tries to access the apt-proxy instance on .249, apt-proxy crashes with the above traceback. Most odd.

Is this a VMWare bug of some kind? But network bridging is supposed to be transparent to a VM.

Any ideas?

[Joshua Kugler (jkugler)]

Found a work around here:
http://www.ubuntuforums.org/showpost.php?p=1104006&postcount=3

Delete the line

Acquire::http::Proxy "false";

from apt.conf.

For whatever reason, apt-proxy now works just fine from localhost, as well as the second scenario in which it's a different VM on the same machine.

[Joshua Kugler (jkugler)]

I'm also running into situations where I have been required to delete the "Acquire proxy line" from a machine's apt.conf even if it is another physical machine (i.e. not localhost, not a VM on the Apt Proxy machine).

[Rolf Leggewie (r0lf)]

Joshua, thank you for the report.

Do you still experience this problem?

[Rolf Leggewie (r0lf)]

From the lack of response, I will assume that the issue is no longer present. Feel free to reopen this report with more information.