Vesta Control Panel - Forum

Turns out that somewhen VestaCP changed clamav-daemon name to clamd, but system doesn'tknow about it. That's why we have lots of problems to start and stop or monitor Clamd service from VestaCP control Panel. Here is the fix: systemctl stop clamav-daemon systemctl disable clamav.daemon mv /lib/syste...

Seems like deleting old *.cld clamd base files and updating them with new *.cvd fixed the problem.

Did you found the answer?

About a month ago I've started receiving messages in exim4 paniclog that mailserver can't connect to /var/run/clamav/clamd.ctl socket file. Sending and receiving mail stopped! Socket and pid files were at the place, clamd daemon started and working. Looking at freshclam.log I've found last string th...