[AMaViS-user] ClamAV failing (Exceeded allowed time) w/ Amavisd 2.6.1

[Don Brearley]

Hello Everyone,

I am running Amavisd-new 2.6.1 and ClamAV 0.93.3.

Mail delivery is working fine, then after a little while (sometimes
5 minutes, other times two hours), I start seeing the following:

ALL VIRUS SCANNERS FAILED: ClamAV-clamd av-scanner FAILED: run_av error:
ask_daemon_internal: Exceeded allowed time at (eval 99) line 307.

Then mail delivery basically ceases until I restart the system again.

I have upped the maximum open files on the system significantly. I see
in the
2.6.1 changelog that this bug was supposedly fixed, yet I continue to
have it.
I am not using Mail::ClamAV, I am using clamd, although Mail::ClamAV is
installed on the system.

Any clues? Thanks!

- Don

-------------------------------------------------------------------------
This SF.Net email is sponsored by the Moblin Your Move Developer's challenge
Build the coolest Linux based applications with Moblin SDK & win great prizes
Grand prize is a trip for two to an Open Source event anywhere in the world
http://moblin-contest.org/redirect.php?banner_id=100&url=/
_______________________________________________
AMaViS-user mailing list
AMaVi...@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/amavis-user
AMaViS-FAQ:http://www.amavis.org/amavis-faq.php3
AMaViS-HowTos:http://www.amavis.org/howto/

[Mark Martinec]

Don,

> I am running Amavisd-new 2.6.1 and ClamAV 0.93.3.
>
> Mail delivery is working fine, then after a little while (sometimes
> 5 minutes, other times two hours), I start seeing the following:
>
> ALL VIRUS SCANNERS FAILED: ClamAV-clamd av-scanner FAILED: run_av error:
> ask_daemon_internal: Exceeded allowed time at (eval 99) line 307.
>
> Then mail delivery basically ceases until I restart the system again.
>
> I have upped the maximum open files on the system significantly. I see
> in the 2.6.1 changelog that this bug was supposedly fixed, yet I continue
> to have it. I am not using Mail::ClamAV, I am using clamd, although
> Mail::ClamAV is installed on the system.

That bug (fixed in 2.6.1) was specific to runnning a virus scanner
in a forked perl subprocess (like Mail::ClamAV). Most other virus
scanners, including clamd, were not affected by the bug.

So what you are seeing must be something else. Check timing in the
log (TIMING report at log level 2, or just examine syslog timestamps
around a call to clamd) - I guess the diagnostic was genuine,
i.e. that clamd really took long time to respond.

Mark

[Michael Scheidell]

I see same thing on freebsd 5.5

If you are running freebsd 5.5, know that someone (clamav) broke threaded
processes in 93.x. Freebsd no longer supports 5.5, so only option is to
upgrade to 6.x or 7.x

To test this, cd to some directory, look for a small file.
Do 'clamdscan {filename}'.

It should timeout.

/usr/local/etc/rc.d/clamav-clamd.sh stop
(won't). You will need killall -9 clamd.

--
Michael Scheidell, CTO
>|SECNAP Network Security
Winner 2008 Network Products Guide Hot Companies
FreeBSD SpamAssassin Ports maintainer

_________________________________________________________________________
This email has been scanned and certified safe by SpammerTrap(r).
For Information please see http://www.spammertrap.com
_________________________________________________________________________