Apt-proxy fails after first connection

Bug #355031 reported by Russel Winder on 2009-04-04
12
This bug affects 2 people
Affects Status Importance Assigned to Milestone
apt-proxy (Ubuntu)
Undecided
Unassigned

Bug Description

Apt-proxy used to work fine. at some time in teh last few weeks there has been a change soemwhere in the system such that it no longer works as it should.

After a restart:

root@dimen:~# /etc/init.d/apt-proxy restart
 * Stopping apt-proxy [ OK ]
 * Starting apt-proxy /usr/lib/python2.5/site-packages/twisted/manhole/telnet.py:8: DeprecationWarning: As of Twisted 2.1, twisted.protocols.telnet is deprecated. See twisted.conch.telnet for the current, supported API.
  from twisted.protocols import telnet
None
/usr/lib/python2.5/site-packages/twisted/manhole/telnet.py:8: DeprecationWarning: As of Twisted 2.1, twisted.protocols.telnet is deprecated. See twisted.conch.telnet for the current, supported API.
  from twisted.protocols import telnet
None
                                                                                                                                                                                 [ OK ]
root@dimen:~#

The first connection from a client proceeds fine, everything seems as it should be, working correctly. However on any subsequent connections, some of the Ubuntu repositories fail.

This happens using Aptitude or Upgrade Manager. Upgrade Manager gives apparently more detailed information, claiming that certain Package.gz files are not available. Clearly they are available so the problem is not with the repository. I don't think apt-proxy has changed recently though clearly there are now Twisted problems where there didn't used to be.

I cannot remember if the proxy ever worked after the start of the appearance of the startup error messages -- I have no written data and my memory is hazy on order of events.

This really needs fixing before the shift to Jaunty so that people with many Ubuntu boxes don't have to download vast amount individually for every machine.

|> lsb_release -rd
Description: Ubuntu 8.10
Release: 8.10
502 balin:~
|>

root@dimen:~# apt-cache policy apt-proxy
apt-proxy:
  Installed: 1.9.36.3+nmu1
  Candidate: 1.9.36.3+nmu1
  Version table:
 *** 1.9.36.3+nmu1 0
        500 http://dimen.russel.org.uk intrepid/universe Packages
        100 /var/lib/dpkg/status
root@dimen:~#

Russel Winder (russel) wrote :

I should add that the failure on second and subsequent lookups takes a a *very* long time. I guess the timeouts I have in apt-proxy are too long (but I thought they were the defaults). So generally it takes about 50mins for Aptitude to complete and update and many repositories are not actually updated.

Russel Winder (russel) wrote :

It appears that this is not a problem with Jaunty only with Intrepid. The implication being that it is something to do with the lookup of intrepid packages.

To post a comment you must log in.
This report contains Public information  Edit
Everyone can see this information.

Other bug subscribers