[Date Prev][Date Next] [Thread Prev][Thread Next] [Date Index] [Thread Index]

Bug#281697: marked as done (apt-cacher: Works slowly (if at all) with apache2 and litters zombies)



Your message dated Sun, 27 Jul 2008 17:29:12 +0200 (CEST)
with message-id <Pine.LNX.4.64.0807271728050.10762@eru.sfritsch.de>
and subject line apt-cacher: Works slowly (if at all) with apache2 and litters zombies
has caused the Debian Bug report #274274,
regarding apt-cacher: Works slowly (if at all) with apache2 and litters zombies
to be marked as done.

This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.

(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact owner@bugs.debian.org
immediately.)


-- 
274274: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=274274
Debian Bug Tracking System
Contact owner@bugs.debian.org with problems
--- Begin Message ---
Package: apt-cacher
Version: 0.8-4
Severity: important



NOTE: Another user has also reported this problem on debian-isp:
http://www.mail-archive.com/debian-isp@lists.debian.org/msg13260.html

The apt-cacher package works incredibly slow on my system, times
out a lot, and leaves zombie processes adrift in the process table.

Playing with this a bit, during an apt-get update, the first file
usually downloads quickly, then subsequent files will show a download
bandwidth, as they get 10-20 bytes or so of data from the webserver, 
but then will hang for a very long time before completing.  If all apt-cacher
processes are killed (killall -9 /usr/bin/perl, assuming that is safe on
the system) after the bandwidth counter disappears, then the file will
download almost immediately thereafter -- and the next file will encounter
the same problem.

After an apt-get update, the process table still shows a large number of
processes as such:

www-data 11054  0.0  2.4  4704 3080 ?        S    19:52   0:00 /usr/bin/perl /usr/share/apt-cacher/apt-cacher.pl
www-data 11055  0.0  0.0     0    0 ?        Z    19:52   0:00 [wget] <defunct>
www-data 11059  0.0  2.4  4704 3076 ?        S    19:54   0:00 /usr/bin/perl /usr/share/apt-cacher/apt-cacher.pl
www-data 11060  0.0  0.0     0    0 ?        Z    19:54   0:00 [wget] <defunct>
www-data 11063  0.0  2.4  4704 3084 ?        S    19:56   0:00 /usr/bin/perl /usr/share/apt-cacher/apt-cacher.pl
www-data 11064  0.2  0.0     0    0 ?        Z    19:56   0:00 [wget] <defunct>
[...]


copy of /etc/apache2/conf.d/apt-cacher (private ip's X'd out):

Alias /apt-cacher /usr/share/apt-cacher/apt-cacher.pl

<DirectoryMatch /usr/share/apt-cacher/>
	Options ExecCGI
	AddHandler cgi-script .pl
	AllowOverride None
	order allow,deny
        allow from X.X.X.0/24
        allow from 127.0.0.1/32
</DirectoryMatch>

copy of /etc/apt-cacher/apt-cacher.conf (comments deleted):


cache_dir=/var/cache/apt-cacher

admin_email=root@localhost

allowed_hosts=X.X.X.1-X.X.X.254

generate_reports=1

clean_cache=1

logdir=/var/log/apt-cacher

expire_hours=36

http_proxy=proxy.example.com:8080

use_proxy=0

limit=0

debug=1


CGI apache2 support module is loaded and the apt-cacher
config snippet is properly linked in apache2's conf.d

I don't know why the below show "not found" for some
packages.  They were installed via dpkg.


-- System Information:
Debian Release: 3.1
  APT prefers unstable
  APT policy: (500, 'unstable')
Architecture: i386 (i586)
Kernel: Linux 2.6.7godsmack
Locale: LANG=C, LC_CTYPE=C (charmap=ANSI_X3.4-1968)

Versions of packages apt-cacher depends on:
pn  apache | apache-ssl | apache2            Not found.
ii  bzip2                         1.0.2-1    A high-quality block-sorting file 
pn  perl                                     Not found.
pn  wget                                     Not found.

-- no debconf information


--- End Message ---
--- Begin Message --- There are no reports that this is still a problem with 2.2.x. Closing the bug.


--- End Message ---

Reply to: