#include <hallo.h>
* xavier renaut [Mon, Apr 21 2008, 05:41:25PM]:
> On Mon, Apr 21, 2008 at 11:05:46PM +0200, Eduard Bloch wrote:
> > #include <hallo.h>
> > * xavier renaut [Mon, Apr 21 2008, 01:31:25PM]:
> > > Package: apt-cacher-ng
> > > Followup-For: Bug #475583
> > >
> > >
> > > Hello,
> > >
> > > this time I had some error logs when the overload is stuck:
> > >
> > > *** ./apt-cacher.log ***
> > > 2008.04.21
> > > 07:35:01|O|131|::ffff:192.168.142.64|debrep/dists/testing/Release.gpg
> > > 2008.04.21
> > > 07:35:02|O|131|::ffff:192.168.142.64|debrep/dists/testing/Release
> > > 2008.04.21
> > > 07:35:02|O|131|::ffff:192.168.142.64|debrep/dists/testing/main/binary-i386/Packages.bz2
> >
> > It is not stuck, it just cannot create new threads. How much memory does
> > the system have?
>
>
> 2 G.
>
> cat /proc/sys/kernel/threads-max
> 32744
>From looking again at your other mail, I have the impression that some
download agents do not terminate when they are supposed to, thus
blocking the resources until the internal thread pool is full. However I
could not identify the code path leading to this condition yet and my
resources (spare time) are limited.
> what could i do ?
There is a way to gather more information but it's ugly.
apt-get build-dep apt-cacher-ng
apt-get source apt-cacher-ng
cd apt-cacher-ng*
make acng DEBUG=1
/etc/init.d/apt-cacher-ng stop
cp -a build/apt-cacher-ng /usr/sbin/apt-cacher-ng
/etc/init.d/apt-cacher-ng start
Then let it run unless you run into this broken state... and make sure
your log directory has enough free space.
Regards,
Eduard.
--
Naja, Garbage Collector eben. Holt den Müll sogar vom Himmel.
(Heise Trollforum über Java in der Flugzeugsteuerung)
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
