uninstalled clamv, system reports trying to enable it
Posted: Sun Oct 29, 2017 10:49 am
I have already uninstalled clamv and spamassassin according to :
viewtopic.php?f=12&t=11279#p43123
my /usr/local/vesta/conf/vesta.conf :
my etc/exim/exim.conf :
However in the message log, I see the system repeatedly failing to enable clamd scanner:
what should I do?
viewtopic.php?f=12&t=11279#p43123
my /usr/local/vesta/conf/vesta.conf :
Code: Select all
ANTIVIRUS_SYSTEM=''
ANTISPAM_SYSTEM=''
Code: Select all
SPAMASSASSIN = no
SPAM_SCORE = 50
CLAMD = no
Code: Select all
Oct 29 03:09:13 server systemd: Starting clamd scanner (clamd) daemon...
Oct 29 03:09:13 server systemd: Started clamd scanner (clamd) daemon.
Oct 29 03:09:13 server systemd: Failed at step EXEC spawning /usr/sbin/clamd: No such file or directory
Oct 29 03:09:13 server systemd: clamd.service: main process exited, code=exited, status=203/EXEC
Oct 29 03:09:13 server systemd: Unit clamd.service entered failed state.
Oct 29 03:09:13 server systemd: clamd.service failed.
Oct 29 03:09:13 server systemd: clamd.service holdoff time over, scheduling restart.
Oct 29 03:09:13 server systemd: Starting clamd scanner (clamd) daemon...
Oct 29 03:09:13 server systemd: Started clamd scanner (clamd) daemon.
Oct 29 03:09:13 server systemd: Failed at step EXEC spawning /usr/sbin/clamd: No such file or directory
Oct 29 03:09:13 server systemd: clamd.service: main process exited, code=exited, status=203/EXEC
Oct 29 03:09:13 server systemd: Unit clamd.service entered failed state.
Oct 29 03:09:13 server systemd: clamd.service failed.
Oct 29 03:09:14 server systemd: clamd.service holdoff time over, scheduling restart.
.
.
.