Package: apt-cacher-ng Version: 0.2.6-1 Severity: important I regularly use apt-cacher-ng quite happily. Today I noticed excesive usage of one of cpu cores. I noticed it was apt-cacher-ng to blame ,so I went to the error log and I saw log full with this message:
Tue Aug 12 07:43:28 2008|Error resolving ftp.de.debian.org: 503 No address associated with hostname Tue Aug 12 07:43:28 2008|Error resolving ftp.de.debian.org: 503 No address associated with hostname Tue Aug 12 07:43:28 2008|Error resolving ftp.de.debian.org: 503 No address associated with hostname Tue Aug 12 07:43:28 2008|Error resolving ftp.de.debian.org: 503 No address associated with hostname Tue Aug 12 07:43:28 2008|Error resolving ftp.de.debian.org: 503 No address associated with hostname Tue Aug 12 07:43:28 2008|Error resolving ftp.de.debian.org: 503 No address associated with hostname Tue Aug 12 07:43:28 2008|Error resolving ftp.de.debian.org: 503 No address associated with hostname Tue Aug 12 07:43:28 2008|Error resolving ftp.de.debian.org: 503 No address associated with hostnam [...] Tue Sep 2 18:20:49 2008|Error resolving debrep: 503 No address associated with hostname Tue Sep 2 18:20:49 2008|Error resolving debrep: 503 No address associated with hostname Tue Sep 2 18:20:49 2008|Error resolving debrep: 503 No address associated with hostname Tue Sep 2 18:20:49 2008|Error resolving debrep: 503 No address associated with hostname Tue Sep 2 18:20:49 2008|Error resolving debrep: 503 No address associated with hostname But worst than these is the following command result: ls -lh /var/log/apt-cacher-ng total 653M -rw-r--r-- 1 apt-cacher-ng apt-cacher-ng 652M sep 2 18:20 apt-cacher.err -rw-r--r-- 1 apt-cacher-ng apt-cacher-ng 484K sep 1 21:42 apt-cacher.log -rw-r--r-- 1 apt-cacher-ng apt-cacher-ng 54K sep 1 07:36 maint_1220247306.log -rw-r--r-- 1 apt-cacher-ng apt-cacher-ng 2,3K sep 2 07:35 maint_1220333705.log Having a 650M+ log is no good, this could lead to grave system impact, for example starving your /var partition. I qualify this bug as important because I didn't dare to use the critical or severe tags, but I think using one of those tags should be considered. I have to add that I was connected to internet yesteday evening/night using my regular wifi connection, I left computer on all night and this morning I hibernated it by 8:15 or so. You can notice that errors start before that. I resumed/hibernated several times along the day and I finally noticed the apt-cacher-ng misbehaviour. I'm available to provide whatever info could be required and perform any test that would help to clear this issue out. Regards, Raúl -- System Information: Debian Release: lenny/sid APT prefers unstable APT policy: (900, 'unstable'), (500, 'testing'), (100, 'experimental') Architecture: amd64 (x86_64) Kernel: Linux 2.6.26.3-toi3-rc7 (SMP w/2 CPU cores; PREEMPT) Locale: LANG=es_ES.UTF-8, LC_CTYPE=es_ES.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Versions of packages apt-cacher-ng depends on: ii adduser 3.110 add and remove users and groups ii libbz2-1.0 1.0.5-1 high-quality block-sorting file co ii libc6 2.7-13 GNU C Library: Shared libraries ii libfuse2 2.7.3-5 Filesystem in USErspace library ii libgcc1 1:4.3.1-9 GCC support library ii libstdc++6 4.3.1-9 The GNU Standard C++ Library v3 ii zlib1g 1:1.2.3.3.dfsg-12 compression library - runtime apt-cacher-ng recommends no packages. apt-cacher-ng suggests no packages. -- no debconf information -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
