Bug#524942: [FTR] Re: Bug#524942: apt-get update gets stuck when apt-cacher-ng is running behind nginx

[Olaf Meeuwissen]

On  Tue, 21 Apr 2009 09:58:40 +0200, Eduard Bloch e...@gmx.de wrote:
 Alexander Inyukhin shur...@sectorb.msk.ru wrote:
  When apt-cacher-ng is used behind nginx (0.6.32) apt-get gets stuck on 
  update.

I got something similar when running acng (through the corporate F/W)
behind an Apache reverse proxy.  That is:

 apt-get  --  apache  --  acng  --  F/W  --  repository

Apache and acng run on the same hardware.

The apt-get/aptitude client hangs until it gives up on updates for files
that do not exist in the repositories.  Particularly, I'm experiencing
this with the package diff-indices and the translation files.  Files
that do exist are not a problem at all.

See also: http://lists.debian.org/debian-user/2009/07/msg00152.html.

 [snip]

 The nginx-Issue has been known for some weeks and is already fixed in
 the current testing version. Please test that if possible.

 I am sorry about your patch but it's unlikely to be accepted in Debian
 Stable because of the usual rules. However, I plan to put a recent 0.3.x
 version into Debian Backports archive RSN.

# It's now three months later with no package in sight :-|
# Running the version from squeeze is not an option for me.

I've rebuilt the package from lenny with Alexander's patch in the hope
that that would fix things, but no such luck.

Hope this helps,
-- 
Olaf Meeuwissen, LPIC-2   FLOSS Engineer -- AVASYS Corporation
FSF Associate Member #1962   Help support software freedom
 http://www.fsf.org/jf?referrer=1962



-- 
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org

Bug#524942: apt-get update gets stuck when apt-cacher-ng is running behind nginx

[Alexander Inyukhin]

Package: apt-cacher-ng
Version: 0.2.2-2
Severity: normal
Tags: patch

When apt-cacher-ng is used behind nginx (0.6.32) apt-get gets stuck on update.

After some investigation I discover that stuck happens when acng returns
answer without body (e.g. error 404) in Connection: close mode.
Neither acng nor nginx close this connection and stuck is happened.

I do not know acng or nginx should be blamed for that,
but I found acng is easier to fix.

-- System Information:
Debian Release: 5.0.1
  APT prefers stable
  APT policy: (500, 'stable'), (1, 'experimental')
Architecture: i386 (i686)

Kernel: Linux 2.6.29.1-avi (SMP w/2 CPU cores; PREEMPT)
Locale: LANG=ru_RU.UTF-8, LC_CTYPE=ru_RU.UTF-8 (charmap=UTF-8) (ignored: LC_ALL 
set to ru_RU.UTF-8)
Shell: /bin/sh linked to /bin/bash
commit 63bb20719770e8509a03eb3fd908d5c98f595083
Author: Alexander Inyukhin shur...@sectorb.msk.ru
Date:   Tue Apr 21 04:16:30 2009 +0400

Close connections

diff --git a/source/job.cc b/source/job.cc
index 5646cf2..78a3a79 100644
--- a/source/job.cc
+++ b/source/job.cc
@@ -689,7 +689,7 @@ eJobResult job::SendData(int confd)

 
case(STATE_ALLDONE):
-   return R_DONE;
+   return m_bCloseCon ? R_DISCON : R_DONE;

case(STATE_NOWAYOUT):
default: