Just a quick note to point out that the problem with clamd blocking and then clamav-milter spawning a ridiculous number of chils processes is still not fixed in the CVS snapshot from today. I see this in the logs:-
Dec 9 16:08:49 castor clamd[22701]: Self checking every 3600 seconds. Dec 9 16:08:49 castor clamd[22701]: Timeout set to 180 seconds. Dec 9 16:08:49 castor clamd[22701]: SelfCheck: Database status OK. Dec 9 17:09:25 castor clamd[22701]: SelfCheck: Database status OK. Dec 9 17:19:29 castor clamd[22701]: Session 3 stopped due to timeout. Dec 9 17:19:31 castor clamd[22701]: Session 0 stopped due to timeout. Dec 9 17:19:33 castor clamd[22701]: Session 2 stopped due to timeout. Dec 9 17:19:40 castor clamd[22701]: Session 4 stopped due to timeout. Dec 9 17:20:42 castor clamd[22701]: Session 1 stopped due to timeout. Dec 9 17:22:30 castor clamd[22701]: Session 3 stopped due to timeout. .... and more timeouts As soon as this starts happening, the number of milter processes starts growing, and I see this sort of thing on the logs:- ] Dec 9 17:15:28 castor clamav-milter[3524]: clamfi_connect: connection from ool-44c36dcc.dyn.optonline.net [68.195.109.204] Dec 9 17:15:28 castor clamav-milter[3528]: clamfi_connect: connection from guinness.omniscient.com [64.134.101.78] Dec 9 17:15:28 castor clamav-milter[3521]: hit max-children limit (5 >= 5): waiting for some to exit Dec 9 17:15:28 castor clamav-milter[3515]: hit max-children limit (5 >= 5): waiting for some to exit Dec 9 17:15:28 castor clamav-milter[3537]: clamfi_connect: connection from [61.41.146.218] [61.41.146.218] and so on, until:- Dec 9 17:29:09 castor clamav-milter[5684]: hit max-children limit (62 >= 5): waiting for some to exit Dec 9 17:29:16 castor clamav-milter[5692]: clamfi_connect: connection from sulafat.acu.ac.uk [194.81.120.141] Dec 9 17:29:16 castor clamav-milter[5692]: hit max-children limit (63 >= 5): waiting for some to exit At that point I notice, and kill it, and restart, and all works again until the next time. It fails like this regularly, lasting from a few hours to a few days. This behaviour has been going on ever since I first installed clamav - just over 2 1/2 months ago. Does anyone know what causes it, and is there any hope of a fix? Mike. ------------------------------------------------------- This SF.net email is sponsored by: IBM Linux Tutorials. Become an expert in LINUX or just sharpen your skills. Sign up for IBM's Free Linux Tutorials. Learn everything from the bash shell to sys admin. Click now! http://ads.osdn.com/?ad_id=1278&alloc_id=3371&op=click _______________________________________________ Clamav-users mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/clamav-users
