Dennis Peterson wrote: > > Jon R. Kibler wrote: > > Hello, > > > > Upgraded to clamav 0.88.2 on Sunday. We use clamdwatch to monitor clamd. > > Ever > > since the upgrade, clamdwatch reports that clamd has hung about 8 to 10 > > times > > a day -- sometimes more. (Our supporting shell script then restarts clamd.) > > We run clamdwatch once a minute. > > > > How do we go about debugging this? > > Possibly you've hit a limit on threads or other configurable. You might > have your clamdwatch run ps -elLf |grep clam >>/tmp/clamdwatch.log just > before it kills the patient, for example. Review your configuration file > to see if any limits are getting in the way. > > Modify the script so that it retries a couple times before pulling the > trigger.
Dennis: Well, Murphy must hate me. I added a system call at the beginning of clamdwatch to capture ps as you suggested. With that change, everything now seems to be working. Weird. I will keep it running like that for a while and see if it again appears to break. For what I see from ps, have plenty of all resources needed, so I do not think it is a resource starvation issue. But, we'll see. THANKS! Jon Kibler -- Jon R. Kibler Chief Technical Officer A.S.E.T., Inc. Charleston, SC USA (843) 849-8214 ================================================== Filtered by: TRUSTEM.COM's Email Filtering Service http://www.trustem.com/ No Spam. No Viruses. Just Good Clean Email.
_______________________________________________ http://lurker.clamav.net/list/clamav-users.html
