ConfigServer Community Forum

Hi

We follow the suggestion about changing MailScanner virus scanner to clamd, but have the following problems:

Frist, clamd starts using about 32Mb, but sometimes, don't know why, rises up to 150mb ... and suddenly stops working.

Cpanel doesn't monitor clamd unless clamvconnect is intalled, which breaks MailScanner. We installed one of the routines that comes with ClamAV to monitor clamd, but seems that doesn't always works. Sometimes it does restart clamd, others doesn't.

We installed clamdmon, and set the cron job every 5 min to monitor clamd. In about half of the times we detect clamd was not working, this directive doesn't work either.

/usr/local/sbin/clamdmon.sh -p /tmp/clamd.socket

We run this command about 2 or 3 times from console and clamd restarts.....

Do you have a better method to monitor clamd and restart it in case clamd stop working?

also, it's normal that clamd uses so much memory? (We happily switch to clamd because of the promise of use less memory, but 150mb it's to much)


Thanks in advance

We have seen this memory usage increase in clamd on some servers but have not seen the problem that chkservd does not restart clamd. In Service Manager are both boxes ticked for clamd?

If clamd is not providing improved performance or decreased memory use on your server then we would recommend reverting to clamavmodule. Instructions can be found in this FAQ:
http://www.configserver.com/techfaq/index.php?faqid=64

Hi Sarah

Thanks for your answer.

Regarding the chkservd, it's not possible, at least, we can't see clamd at Service Manager unless Clamavconnector is installed.

The increase of memory doesn't bothers much, but we imagine it what hung clamd. So if we can monitor clamd, imagine everything will be fine for us.....

On the other hand, from reading at the link you provide, we should go back to clamavmodule, it's more reliable

Thanks again.

Are you using our MailScanner Front-End? If so, did you upgrade ClamAV by clicking the button in the WHM MSFE? If not, you may not have done all the necessary steps to add clamav to the Service Manager.