Hi,
I'm analysing a mail failure featuring a redhat based system using
clamav, amavis-ng, and qmail. The reported symptom of the failure
was that inbound mail was not being received. After finding the
following error in the amavis-ng log (every inbound mail produced
similar log entries) I found a defunct clamd process and the missing
mail quarantined in /var/spool/amavis-ng/problems/.
/var/log/amavis-ng/amavis.log:
...
amavis[8207]: AMAVIS::AV::CLAMD: Unknown virus scanner output: Session(0): Time
out ERROR
amavis[8207]: Error while scanning for viruses with AMAVIS::AV::CLAMD:
amavis[8207]: AMAVIS::MTA::Qmail: Freezing message
amavis[8207]: Quarantining infected message to
/var/spool/amavis-ng/problems/43c40089-200f
Restarting clamd, supervised by daemontools, restored mail delivery.
I've searched the various clamav resources but haven't found any
evidence that there are known issues/versions where clamd dies. The
clamav package is old (clamav-0.65-6), however before I upgrade I'm
hoping this community can help tell me if
a) this is a known issue in older releases (can I be reasonably
assured that upgrading will prevent this from happening again?)
b) until I understand the various components involved and test
upgrades on a staging system, is there anything I can do to mitigate
the chances of this failure happening again?
c) can I expect an upgrade to be any more complex than
- removing clamav-libs (/usr/lib/libclamav.so.1 from install of
clamav-0.88-1.0.rh7.rf conflicts with file from package
clamav-libs-0.65-6)
- install/upgrade clamav-db and clamav
Thanks for your time,
Paul
_______________________________________________
http://lurker.clamav.net/list/clamav-users.html
