Hi, Following up my previous mail about this, I've finally got round to running clamav-daemon in debug mode, and catching some more output. Hopefully it'll be useful.
I started clamav-daemon, clamav-milter, and sendmail at 10:10:00:- Feb 11 10:09:56 castor clamav-milter[16265]: ClamAV version 'clamd / ClamAV version devel-20040205', clamav-milter version '0.66k' Feb 11 10:10:00 castor sendmail[16276]: starting daemon (8.12.10): [EMAIL PROTECTED]:30:00 At 10:48, it fell over, producing the following messages in the log:- Feb 11 10:48:20 castor clamav-milter[21948]: i1BAmJMu021946: clean message from <[EMAIL PROTECTED]> Feb 11 10:48:20 castor sendmail[21951]: i1BAmJMu021946: to=<[EMAIL PROTECTED]>, delay=00:00:01, xdelay=00:00:00, mailer=esmtp, pri=30725, relay=mail9.messagelabs.com. [194.205.110.133], dsn= 2.0.0, stat=Sent (ok 1076496521 qp 6128) Feb 11 10:49:26 castor clamav-milter[21980]: hit max-children limit (5 >= 5): waiting for some to exit Feb 11 10:49:31 castor sendmail[20559]: i1B7QqAv027441: to=<[EMAIL PROTECTED]>, delay=03:22:39, xdelay=00:03:09, mailer=esmtp, pri=579227, relay=yapost.com. [203.176.150.62], dsn=4.0.0, stat=Deferred: Connec tion timed out with yapost.com. Feb 11 10:49:36 castor sendmail[21978]: i1BAnQMu021978: Milter (ClamAVFilter): timeout before data read Feb 11 10:49:36 castor sendmail[21978]: i1BAnQMu021978: Milter (ClamAVFilter): to error state This log excerpt shows the last correctly scanned mail for this run, followed by the first problem message. About 90 seconds after that, I start getting clamd sesion timeout errors:- Feb 11 10:51:00 castor clamd[16260]: Session 0 stopped due to timeout. When I started clamd for this run, I had "Forground" and "Daemon" in clamd.conf, and clamd was busily logging messages. This logging stopped completely when the error first ocurred - I have full debug logging for the last message that clamav-milter reported as clean, and nothing after that - last few lines of the log are:- LibClamAV debug: blobSetFilename: textportion LibClamAV debug: Saving main message, encoded with scheme 0 LibClamAV debug: Saving attachment in /tmp/ff6427eb2752244a/textportion LibClamAV debug: Attachment saved as /tmp/ff6427eb2752244a/textportionCcDW3c (98 bytes long) LibClamAV debug: blobDestroy LibClamAV debug: parseEmailBody() returning 1 LibClamAV debug: cli_mbox returning 0 LibClamAV debug: Scanning /tmp/ff6427eb2752244a/textportionCcDW3c These all refer to the last good message, and LibClamAV debug logging stops dead at this point. This problem has grown more severe with newer versions of clamd. With 0.60, when I first started using it, it would go into an error state about once every 3-4 days. With the current version I'm running (CVS snapshot 20040204), it lasts a maximum of about two hours. Is this a result of the thread management issues I've read about? ANy idea when there might be a fix? Mike. ------------------------------------------------------- SF.Net is sponsored by: Speed Start Your Linux Apps Now. Build and deploy apps & Web services for Linux with a free DVD software kit from IBM. Click Now! http://ads.osdn.com/?ad_id=1356&alloc_id=3438&op=click _______________________________________________ Clamav-users mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/clamav-users
