On Sun, Mar 20, 2011 at 04:22:43PM +0100, Eus wrote: > Hi! > > On Sun, 2011-03-20 at 14:53 +0000, Mark Hindley wrote: > > > Having applied the patch could you do /etc/init.d/apt-cacher stop and > > then ensure there isn't an apt-cacher [libcurl] thread still running (ps > > -lfC apt-cacher ought to show it). If there is, kill that pid (or wait 5 > > minutes for it to exit itself) and then restart. > > It still does not work. However, I think I've discovered the culprit. v> > After reading apt-cacher source code, I sent SIGUSR1 to the daemon and > saw the following snippet in apt-cacher/error.log for the first "Bad > header line": > --- 8< ---------------------------------------------------- > Sun Mar 20 15:48:27 2011|debug [13565]: Sending libcurl > http://de.archive.ubuntu.com/ubuntu/dists/maverick/main/i18n/Translation-en.bz2 > Sun Mar 20 15:48:27 2011|debug [13565]: Entering critical section : > connect libcurl > Sun Mar 20 15:48:27 2011|debug [13565]: Connection to running libcurl > process found on /var/cache/apt-cacher/libcurl.socket > Sun Mar 20 15:48:27 2011|debug [13565]: Exiting critical section > Sun Mar 20 15:48:27 2011|debug [13566]: libcurl: connection from > IO::Socket::UNIX=GLOB(0x97da768) > Sun Mar 20 15:48:27 2011|debug [13566]: Libcurl: thawed request > http://de.archive.ubuntu.com/ubuntu/dists/maverick/main/i18n/Translation-en.bz2, > 1, > Sun Mar 20 15:48:27 2011|debug [13566]: Init new libcurl object > Sun Mar 20 15:48:27 2011|debug [13566]: Add curl handle #2: for > http://de.archive.ubuntu.com/ubuntu/dists/maverick/main/i18n/Translation-en.bz2 > Sun Mar 20 15:48:27 2011|debug [13566]: libcurl: setting up for HEAD > request > Sun Mar 20 15:48:27 2011|debug CURLINFO_TEXT [13566]: About to connect() > to de.archive.ubuntu.com port 80 (#0) > Sun Mar 20 15:48:27 2011|debug CURLINFO_TEXT [13566]: Trying > 141.30.3.82... > Sun Mar 20 15:48:27 2011|debug CURLINFO_TEXT [13566]: Connected to > de.archive.ubuntu.com (141.30.3.82) port 80 (#0) > Sun Mar 20 15:48:27 2011|debug CURLINFO_TEXT [13566]: HTTP 1.0, assume > close after body > Sun Mar 20 15:48:27 2011|debug CURLINFO_TEXT [13566]: Expire cleared > Sun Mar 20 15:48:27 2011|debug CURLINFO_TEXT [13566]: Closing connection > #0 > Sun Mar 20 15:48:27 2011|debug [13566]: curl handle #2 completed, > status: 0 > Sun Mar 20 15:48:27 2011|debug [13566]: libcurl active transfers: 0 > Sun Mar 20 15:48:27 2011|debug [13565]: libcurl reading of headers > complete > Sun Mar 20 15:48:27 2011|debug [13565]: Found EOF marker and status > FrT;@2|$1|0$0| > Sun Mar 20 15:48:27 2011|debug [13565]: HEAD request error: 404 Not > Found Reusing existing file > Sun Mar 20 15:48:27 2011|debug [13565]: Entering critical section : file > download decision > Sun Mar 20 15:48:27 2011|debug [13565]: Exiting critical section > Sun Mar 20 15:48:27 2011|debug [13565]: checks done, can return now > Sun Mar 20 15:48:27 2011|debug [13565]: Entering critical section : > reading the header file > Sun Mar 20 15:48:27 2011|debug [13565]: Exiting critical section > Sun Mar 20 15:48:27 2011|debug [13565]: Header sent: HTTP/1.1 302 Moved > Temporarily > Connection: Keep-Alive > Content-Length: 0 > Sun Mar 20 15:48:27 2011|debug [13565]: ready to send contents > of > /var/cache/apt-cacher/packages/de.archive.ubuntu.com_ubuntu_dists_maverick_main_i18n_Translation-en.bz2 > Sun Mar 20 15:48:27 2011|debug [13565]: read 924 bytes > Sun Mar 20 15:48:27 2011|debug [13565]: wrote 924 (sum: 924) bytes > Sun Mar 20 15:48:27 2011|debug [13565]: read 0 bytes > Sun Mar 20 15:48:27 2011|debug [13565]: fetcher released lock > Sun Mar 20 15:48:27 2011|debug [13565]: read 0 bytes > Sun Mar 20 15:48:27 2011|debug [13565]: Package sent > --- 8< ---------------------------------------------------- > > Specifically, the file to be downloaded does not exist but instead of > passing 404 to the client, apt-cacher returns 302 by, I think, reading > an invalid cached header. I am wondering how can the invalid header > exists in the very first place if the file never exists in the server.
I suspect it appeared as the CURLOPT_FOLLOWLOCATION was not set. So, can you delete /var/cache/apt-cacher/headers/archive.ubuntu.com_ubuntu_dists_maverick_main_i18n_Translation-en.bz2 and try again (with the patch) Mark -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
