Quoting Cyril Brulebois (kibi@debian.org): > Cyril Brulebois <kibi@debian.org> (2013-09-30): > > Yes; debian-i18n membership ping. > > > > Can't see the page on alioth due to: > > Permission denied. This project's administrator will have to grant you permission to view this page. > > > > so can't request it myself. You should be able to add me from your end > > though. > > Nevermind, that probably should go through rt.d.o (and it did). > > Anyway, running the script against "unstable", with the first patch > attached for debugging purposes, shows the package before 3depict is > 0ad-data, which leads to an exec of "xd" which allocates a lot of > memory. I suspect memory issue handling is poor, and leads to the nasty > side effect we saw: an unrelated package gets blamed. The second (quick > and dirty) patch seems to work around that, and the script is still > running for now. > > I guess fixing error handling and maybe getting some more memory should > be enough to get that part to work reliably. > > top - 05:12:13 up 30 days, 16:06, 2 users, load average: 0,06, 0,15, 0,19 Tasks: 103 total, 1 running, 102 sleeping, 0 stopped, 0 zombie %Cpu(s): 0,0 us, 1,7 sy, 0,0 ni, 98,3 id, 0,0 wa, 0,0 hi, 0,0 si, 0,0 st KiB Mem: 2061292 total, 1950408 used, 110884 free, 286504 buffers KiB Swap: 524284 total, 66436 used, 457848 free, 890868 cached PID USER PR NI VIRT RES SHR S %CPU %MEM TIME+ COMMAND 2508 clamav 20 0 398m 330m 5436 S 0,0 16,4 414:12.81 clamd So, it seems that: - the virtual machine doesn't have that much memory (2GB) - it doesnt have much swap - clamd is eating a lot of memory clamd seems to be running for 17 days, about a week after we started to have some issues with statistics. If I had root access to this machine, I would: - restart clamd - add more swap - eventually add more memory Anyway, I applied your patch and we'll see what happens
Attachment:
signature.asc
Description: Digital signature