On Wed, 14 Apr 2004, I wrote:

> On Fri, 9 Apr 2004, I wrote:
>
> > I have been running ClamAV version devel-20040405 for three days without
> > issue, until this morning.
>
> Actually, clamav-milter had been running for about 28 hours before the
> start of the errors.
>
> > Now, for each virus rejected, the following
> > entry appears in the syslog:
> >
> > /kernel: pid 72343 (clamav-milter), uid 3001: exited on signal 11
> >
> > These appear to be from children as the parent proccess continues to
> > run. All else appears normal.
> >
> > System info:
> > FreeBSD 4.9-RELEASE-p2
> > clamd / ClamAV version devel-20040405
> > ClamAV version devel-20040405, clamav-milter version 0.70g
> >
> > # ps ax | grep clam
> > 17139  ??  Is     0:00.07 /usr/local/bin/freshclam -d -c 13
> > 40560  ??  Ss     2:41.65 /usr/local/sbin/clamd
> > 40568  ??  Ss     0:13.25 /usr/local/sbin/clamav-milter -lonHP -m50
>
> This has happened again. After nearly four days of error free operation,
> clamav-milter children that find a virus exit sig 11. Also, I found one
> clamav-milter child stuck consuming 100% CPU.
>
> Please note:
> - Some amount of time passes from the start of the clamav-milter
>   parent process before problems with child processes begin.
> - ONLY clamav-milter children that report a virus exit sig 11
>     (or consume 100% cpu).
> - clamav-milter children that DO NOT report a virus exit cleanly.
> - Both clamd.log and maillog look normal. Only syslog has errors.
>   These are milters reporting a virus...
>
> Apr 13 10:03:12 copland /kernel: pid 33341 (clamav-milter), uid 3001:
> exited on signal 11

Shortly after sending the above I realized that in my environment the
only functional difference between a milter that reports a virus and one
that does not is the email notification. I looked through my logs and
found that when a clamav-milter process had reported a virus and exited
cleanly, the event was correctly logged in the syslog and the email
notification was sent, but when the clamav-milter processes began to sig
11, correct logging to the syslog continued, but email notifications
stopped.

I have since restarted clamav-milter with the "--quiet" option. Time
will tell if this is effective.

-- 
Michael Lambert
Systems Admin, IT Dept
JEOL USA Inc
http://www.jeol.com


-------------------------------------------------------
This SF.Net email is sponsored by: IBM Linux Tutorials
Free Linux tutorial presented by Daniel Robbins, President and CEO of
GenToo technologies. Learn everything from fundamentals to system
administration.http://ads.osdn.com/?ad_id=1470&alloc_id=3638&op=click
_______________________________________________
Clamav-users mailing list
[EMAIL PROTECTED]
https://lists.sourceforge.net/lists/listinfo/clamav-users

Reply via email to