Hallo,
* Eric [Mon, Jul 01 2013, 01:17:29PM]:
> I am having the exact same problem with apt-cacher-ng eating 25% of
> the CPU as the original reporter. I am running Debian Wheezy.
>
> The runaway cpu usage starts after the the daily cron job is
> launched if apt-cacher-ng has been running for multiple hours.
>
>
> Here is an strace I get when its looping..
>
> [pid 5628] select(1, [], NULL, NULL, {0, 1}) = 0 (Timeout)
> [pid 5628] time(NULL) = 1372610725
> [pid 5628] time(NULL) = 1372610725
> [pid 5628] time(NULL) = 1372610725
> [pid 5628] time(NULL) = 1372610725
> [pid 5628] time(NULL) = 1372610725
I know where it is (background cleanup task) but not exactly what
triggers it, I will add more debugging code in the next version. I
cannot reproduce it with your Release URL either, it must be something
very subtle.
In the meantime, could you run:
killall -SIGUSR2 apt-cacher-ng
killall -SIGUSR1 apt-cacher-ng
That's an undocumented way to print some information about active
download items to apt-cacher.err log file. And then please send me the
relevant list.
> apt-cache 5594 apt-cacher-ng 25w REG 8,33
> 1347 5245206
> /bigvideo/apt-cacher-ng/dl.google.com/linux/chrome/deb/dists/stable/Release
> ----- Error logs for google urls during maintance
>
> Mon Jul 1 08:00:58 2013|Download started, storeHeader for
> dl.google.com/linux/deb/dists/stable/Release, current status: 1
> Mon Jul 1 08:00:58 2013|Download started, storeHeader for
> dl.google.com/linux/deb/dists/stable/Release, current status: 32
> Mon Jul 1 08:00:58 2013|Error: item finished and idle, refusing download
> start
That could be caused by the issue above.
Thanks.
Regards,
Eduard.
--
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
