On Sat, Apr 12, 2008 at 03:32:07PM +0200, Eduard Bloch wrote: > #include <hallo.h> > * xavier renaut [Fri, Apr 11 2008, 03:25:23PM]: > > Package: apt-cacher-ng > > Version: 0.1.12-2 > > Severity: normal > > > > > > when accessing the apt-cacher-ng from multiple machines at the same > > time, apt-cacher-ng answer "503 Server overload, try later" > > Generic message. Maximum number of threads reached, system out of > memory, out of filehandles, ... >
how could I know what is the real error ? my debug value is already 3, and i dont have that many logs... thanks here is my conf : CacheDir: /data/apt-cacher-ng LogDir: /var/log/apt-cacher-ng Port:3142 Remap-debrep: file:deb_mirror*.gz /debian ; file:backends_debian Remap-uburep: file:ubuntu_mirrors /ubuntu ; file:backends_ubuntu VerboseLog: 1 ReportPage: acng-report.html Debug:3 ExTreshold: 30 > > we are using it as proxy to deb http://http.us.debian.org/debian. > > > > and the server does not recover from this state. > > hours later, i come to do a apt-get update on only one box, > > and i got "503 Server overload, try later". i then restart > > the server and it's working again. > > Server as in "server machine" or "server process"? server process, that is invoke-rc.d apt-cacher-ng restart -- xavier renaut, 514 906 1212 x315 -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
