At 05:46 AM 4/11/2007, jacusy wrote:
>Hello,
>
>this night my clamd-process terminated with an error. The reason was
>that freshclam took too long to do its update, so that clamd could not
>lock the database. So clamd exited. But this behaviour is very fatal
>because the mail system (postfix with amavis) relys on clamd, so if it
>is down, the whole mail traffic is blocked!! Caused of an error while
>updating......
>
>What to do against?
Make sure your amavisd.conf defines clamscan as a secondary
scanner. If clamd is unavailable then amavsid-new will continue to
process mail using clamscan to check for viruses. When using
clamscan, system load will increase and throughput will decrease, but
mail will still be processed. If clamscan fails too, no mail will
pass through, which is good. It is possible to configure
amavisd-new to pass mail unscanned if that's what you want, but that
is not recommended.
Use some sort of monitor to check if clamd (and other critical
processes) are running, and restart them if necessary. I like monit
because it's simple and flexible, but there are lots of other choices.
Here, monit restarted clamd a couple times on several servers last
night because of the update problems. Everything was running
smoothly when I arrived this morning.
Yes, clamd and the whole clamav structure should be more resistant to
failure. Your choices are to either work with it as is, or wait
until clamav is more mature.
--
Noel Jones
_______________________________________________
Help us build a comprehensive ClamAV guide: visit http://wiki.clamav.net
http://lurker.clamav.net/list/clamav-users.html
(text/plain)