Thanks for your reply, we already checked /var/log/messages and dmesg, found nothing. Now, We are trying to use stap to trace SIGKILL source. There is another problem confused me. We plan to upgrade clamav to 0.98.6. When testing the performance of new version clamd by sending the same email continuously, the average time of each email handled by clamd is about 40ms same as 0.97.4. But about every 30 emails, the process time will surge to more than 100ms. Old version act normally. Thanks for any help!
> Date: Wed, 18 Mar 2015 10:06:59 -0400 > From: [email protected] > To: [email protected] > Subject: Re: [clamav-users] clamd exit frequently > > fannnvirusss wrote: > > Hi all, We are running ClamAV-0.97.4 on RHEL 5.4 for a long time, but > > recently clamd process exit quietly and frequently, about four times one > > day. Log file has nothing useful information. When I use gdb attach clamd, > > finally gdb say something like this: Program terminated with signal > > SIGKILL, killed. The program no longer exists. > > Until now, I have no idea why clamd be killed! Why exit so > > frequently! Thanks for hints! > > I don't think I've ever seen clamd just roll over and die on its own. > > Wild guess, based on "Program terminated with signal SIGKILL, killed": > Check /var/log/messages for "OOM" - clamd is a bit of a memory hog and > if you're running it on a low-memory VPS, clamd may be getting killed by > the kernel to free up memory for something else. > > -kgd > _______________________________________________ > Help us build a comprehensive ClamAV guide: > https://github.com/vrtadmin/clamav-faq > > http://www.clamav.net/contact.html#ml _______________________________________________ Help us build a comprehensive ClamAV guide: https://github.com/vrtadmin/clamav-faq http://www.clamav.net/contact.html#ml
