Your message dated Sat, 28 Aug 2010 13:32:08 +0000 with message-id <e1oplvw-0004rd...@franck.debian.org> and subject line Bug#593356: fixed in apt-cacher-ng 0.5.1-2 has caused the Debian Bug report #593356, regarding apt-cacher-ng: memory leak in Lenny backport of 0.5.1 with "MaxStandbyConThreads: 2" enabled 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 ow...@bugs.debian.org immediately.) -- 593356: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=593356 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
--- Begin Message ---Package: apt-cacher-ng Severity: normal G'day. We use apt-cacher-ng in the office to reduce the cost of updates, for which it works great. However, after moving from an Etch machine to a Lenny machine running apt-cacher-ng we hit trouble with memory exhaustion. In an effort to improve this, and since it looks like there have been a whole lot of improvements, I backported (eg: compiled) the 0.5.1 package from testing on Lenny and deployed that. Sadly, our problem continued: we were filling 2GB of memory inside six hours, with about thirty systems updating through the cache. It turns out that the troublesome setting is: MaxStandbyConThreads: 2 With that enabled, memory leak, with it commented out, nothing. I had adjusted that because we use a container solution for the proxy host, and I was happy to pay the cost of slower response while threads spool up in return for potentially reclaiming some memory for other containers. Anyway, so far the system looks to be stable with that disabled, and with it enabled we see a huge leak from "while :; do aptitude update; done" on a system with the Debian Lenny core, backports, and volatile enabled. I can supply more details if you were interested, but figured that given the backport and all you might not be interested in this report. Let me know what, if anything, I can do to help further. Finally, thanks again for this package: it is a world better than the other cache alternatives we have tested, and makes my life vastly more pleasant by, generally, just working. :) Regards, Daniel -- System Information: Debian Release: squeeze/sid APT prefers unstable APT policy: (500, 'unstable'), (101, 'experimental') Architecture: amd64 (x86_64) Kernel: Linux 2.6.32-5-openvz-amd64 (SMP w/2 CPU cores) Locale: LANG=en_AU.UTF-8, LC_CTYPE=en_AU.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/bash -- ✣ Daniel Pittman ✉ dan...@rimspace.net ☎ +61 401 155 707 ♽ made with 100 percent post-consumer electrons
--- End Message ---
--- Begin Message ---Source: apt-cacher-ng Source-Version: 0.5.1-2 We believe that the bug you reported is fixed in the latest version of apt-cacher-ng, which is due to be installed in the Debian FTP archive: apt-cacher-ng_0.5.1-2.diff.gz to main/a/apt-cacher-ng/apt-cacher-ng_0.5.1-2.diff.gz apt-cacher-ng_0.5.1-2.dsc to main/a/apt-cacher-ng/apt-cacher-ng_0.5.1-2.dsc apt-cacher-ng_0.5.1-2_amd64.deb to main/a/apt-cacher-ng/apt-cacher-ng_0.5.1-2_amd64.deb A summary of the changes between this version and the previous one is attached. Thank you for reporting the bug, which will now be closed. If you have further comments please address them to 593...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Eduard Bloch <bl...@debian.org> (supplier of updated apt-cacher-ng package) (This message was generated automatically at their request; if you believe that there is a problem with it please contact the archive administrators by mailing ftpmas...@debian.org) -----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Format: 1.8 Date: Fri, 27 Aug 2010 22:12:30 +0200 Source: apt-cacher-ng Binary: apt-cacher-ng Architecture: source amd64 Version: 0.5.1-2 Distribution: unstable Urgency: high Maintainer: Eduard Bloch <bl...@debian.org> Changed-By: Eduard Bloch <bl...@debian.org> Description: apt-cacher-ng - caching proxy server for software repositories Closes: 546790 590291 593356 Changes: apt-cacher-ng (0.5.1-2) unstable; urgency=high . * Backporting fixes from newer upstream versions + conserver.cc: fix passing of detached parameter during thread creation, stops the leak of thread local memory on loaded systems (closes:#593356) + meta.h: avoid potential infite loop in downloader awakening + expiration.cc: prevent destruction of some .head files which most likely causes loss of information about original source mirror (closes: #546790) + maintenance.h: include sockio.h here to make MSG_MORE macro available in sources of all subclasses (Debian/kfreebsd FTBFS fix) + filereader.h: include sockio.h to make sys/stat.h included in related source files (closes: #590291) + job.cc: bounce attempted Chunked-Transfers with non-HTTP/1.1 clients and not correct ones (programing mistake) + job.cc: when using pass-through mode, avoid conflicts between file descriptor of the incoming connection and the dummy file object Checksums-Sha1: b348f42f34a86df7069500c011a20c3bb4a3797d 1032 apt-cacher-ng_0.5.1-2.dsc 6ad2ed04e42d613ed583f1d5f9540e902407eda9 25386 apt-cacher-ng_0.5.1-2.diff.gz 480530a57d8289d571d5dce7a44c7c7626e7e930 342228 apt-cacher-ng_0.5.1-2_amd64.deb Checksums-Sha256: 8f0003988674f55bc0864cf3d2e05547a2089ba6c3e629c00854d339b961e838 1032 apt-cacher-ng_0.5.1-2.dsc c97f0898ea4cd8e9e21bba18ec9aecf8734cba26c4c944be4ce0afa54cc70551 25386 apt-cacher-ng_0.5.1-2.diff.gz 61285b01bcb679da83ca0956e457374483f705a262b27aa7ef4d371578b230f6 342228 apt-cacher-ng_0.5.1-2_amd64.deb Files: 44789220a1c68fd80a2cfe2b3d7b1a8e 1032 net optional apt-cacher-ng_0.5.1-2.dsc 0be92a531651849e2486e7b4a6a97560 25386 net optional apt-cacher-ng_0.5.1-2.diff.gz 92441d9dc1158b5d1bc88dbebb135c38 342228 net optional apt-cacher-ng_0.5.1-2_amd64.deb -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.10 (GNU/Linux) iD8DBQFMeQh04QZIHu3wCMURAkw1AJ9RNHaTVLzyP64hncckVApE2z0ZeACfZjUN 4PBYC5y8l1rKyahvMUccfvI= =AthI -----END PGP SIGNATURE-----
--- End Message ---
