Hi,
FWIW, I'm testing a (private) backport of 0.7.14-1 on a Wheezy system
to try and confirm if it fixes the problem for me.
Eduard: if it indeed does fix the issue, would you consider
maintaining an official backport of apt-cacher-ng for wheezy?
Cheers,
--
intrigeri
| GnuPG key @
Hallo,
* intrigeri [Wed, Jul 24 2013, 03:49:51PM]:
FWIW, I'm testing a (private) backport of 0.7.14-1 on a Wheezy system
to try and confirm if it fixes the problem for me.
Thanks.
Eduard: if it indeed does fix the issue, would you consider
maintaining an official backport of apt-cacher-ng
Hello guys,
if you have still means to reproduce the mentioned behavior, I have a
test version (unofficial 0.7.14pre1) which should avoid such loops for
sure. It also eliminates a couple of possible scenarios that may have
caused the looping itself... and if the reason is still there, it will
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
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
Hi,
Alexander Muthmann wrote (13 May 2013 07:00:38 GMT) :
I can confirm this bug on my wheezy system.
Each morning my apt-cacher-ng system starts some processing and CPU usage
goes up to ~30%. The process lasts at least 2 days ( i killed it
afterwards).
I observe the same behaviour
Hi Eduard,
the problem remains with the version installed, but strace gives other
information:
[pid 3992] select(1, [], NULL, NULL, {0, 1}) = 0 (Timeout)
[pid 3992] clock_gettime(CLOCK_REALTIME, {1368782750, 214815908}) = 0
[pid 3992] futex(0x80d83c4, FUTEX_WAKE_PRIVATE, 1) = 0
[pid 3992]
Hi,
I have the same problem here, 'top' always shows:
PID USER PR NI VIRT RES SHR S %CPU %MEMTIME+ COMMAND
2581 apt-cach 20 0 50348 4844 1360 S 17.6 0.1 100:26.85 apt-cacher-ng
[...]
It would be great if this could be fixed for the wheezy point relase.
Please let me
Hallo,
* Alexander Muthmann [Mon, May 13 2013, 09:00:38AM]:
I can confirm this bug on my wheezy system.
Each morning my apt-cacher-ng system starts some processing and CPU usage
goes up to ~30%. The process lasts at least 2 days ( i killed it
afterwards).
As the system is monitored, i can
Done...
I will report if the problem remains.
root@internal-services:~# dpkg -i apt-cacher-ng_0.7.12-1_i386.deb
(Reading database ... 34645 files and directories currently installed.)
Preparing to replace apt-cacher-ng 0.7.11-1 (using
apt-cacher-ng_0.7.12-1_i386.deb) ...
[ ok ] Stopping
I can confirm this bug on my wheezy system.
Each morning my apt-cacher-ng system starts some processing and CPU usage
goes up to ~30%. The process lasts at least 2 days ( i killed it
afterwards).
As the system is monitored, i can tell some things:
There is no increase of Disk IO but the number
Hi!
acng isn't eating 100% CPU on me right now, but it is eating about 10% CPU.
I've attached an strace as suggested -- I let it run for a couple of seconds
and it generated a very large log which doesn't (at first glance) look
interesting at all.
I also increased the verbosity but nothing is
Package: apt-cacher-ng
Version: 0.7.11-1
Severity: important
Hi,
on a few Wheezy systems I run, apt-cacher-ng from sid often starts
eating 100% of the CPU and seems to never stop, unless I restart it.
I've no idea what triggered this, but at least the CPU eating goes on
even if there is no
Hallo,
* intrig...@debian.org [Sun, Mar 17 2013, 07:46:57PM]:
on a few Wheezy systems I run, apt-cacher-ng from sid often starts
eating 100% of the CPU and seems to never stop, unless I restart it.
I've no idea what triggered this, but at least the CPU eating goes on
even if there is no
14 matches
Mail list logo
