apt-proxy crashes when accessed from localhost
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
apt-proxy (Ubuntu) |
Invalid
|
Undecided
|
Rolf Leggewie |
Bug Description
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,
2006/10/13 16:59 AKDT [Channel,
File "/usr/lib/
File "/usr/lib/
File "/usr/lib/
File "/usr/lib/
--- <exception caught here> ---
File "/usr/lib/
File "/usr/lib/
fetcher = dummyFetcher.
File "/usr/lib/
fetcher = fetcher_class(req)
File "/usr/lib/
File "/usr/lib/
File "/usr/lib/
c = tcp.Connector(host, port, factory, timeout, bindAddress, self)
File "/usr/lib/
raise error.ServiceNa
Changed in apt-proxy: | |
importance: | Undecided → Low |
Changed in apt-proxy: | |
importance: | Low → Undecided |
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?