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
[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
[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
[pid 5628] select(1, [], NULL, NULL, {0, 1}) = 0 (Timeout)
[pid 5628] time(NULL) = 1372610725
[pid 5628] time(NULL) = 1372610725
I have performed an lsof on apt-cacher-ng while it was eating cpu.
During which apt-cacher-ng has a file open on all it's threads that should
be closed. The file has a timestamp of when the daily cron job has been
executed. Every time this bug occurs this bug occurs its always leaving
the release file for the google chrome repository open.
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
apt-cache 5594 5627 apt-cacher-ng 25w REG 8,33 1347
5245206
/bigvideo/apt-cacher-ng/dl.google.com/linux/chrome/deb/dists/stable/Release
apt-cache 5594 5628 apt-cacher-ng 25w REG 8,33 1347
5245206
/bigvideo/apt-cacher-ng/dl.google.com/linux/chrome/deb/dists/stable/Release
apt-cache 5594 6859 apt-cacher-ng 25w REG 8,33 1347
5245206
/bigvideo/apt-cacher-ng/dl.google.com/linux/chrome/deb/dists/stable/Release
apt-cache 5594 6860 apt-cacher-ng 25w REG 8,33 1347
5245206
/bigvideo/apt-cacher-ng/dl.google.com/linux/chrome/deb/dists/stable/Release
apt-cache 5594 6861 apt-cacher-ng 25w REG 8,33 1347
5245206
/bigvideo/apt-cacher-ng/dl.google.com/linux/chrome/deb/dists/stable/Release
apt-cache 5594 8086 apt-cacher-ng 25w REG 8,33 1347
5245206
/bigvideo/apt-cacher-ng/dl.google.com/linux/chrome/deb/dists/stable/Release
----- Maintance Logs for google urls.
Checking/Updating dl.google.com/linux/chrome/deb/dists/stable/Release... (1KiB)
Checking/Updating dl.google.com/linux/deb/dists/stable/Release... (1KiB)
Checking/Updating dl.google.com/linux/earth/deb/dists/stable/Release... (1KiB)
----- 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
Mon Jul 1 08:00:58 2013|Download started, storeHeader for
dl.google.com/linux/earth/deb/dists/stable/Release, current status: 1
Mon Jul 1 08:00:58 2013|Download started, storeHeader for
dl.google.com/linux/earth/deb/dists/stable/Release, current status: 32
Mon Jul 1 08:00:58 2013|Error: item finished and idle, refusing download start
I don't know if there is something unique about the google-chrome
repository that is causing apt-cacher to hog cpu. Everytime apt-cacher-ng
has hung, it has been always leaving a google-chrome repository file open
and the file descriptor has always been #25.
----
bige1...@sdf.org
SDF Public Access UNIX System - http://sdf.org
--
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
