CentOS7 Systemd

[root@centos7 system]# systemctl enable clamd.service[root@centos7 system]# systemctl enable clamd@scan.service[root@centos7 system]# systemctl start clamd.service[root@centos7 system]# systemctl start clamd@scan.service

CentOS7 systemd

Download: https://www.google.com/url?q=https%3A%2F%2Fgohhs.com%2F2u8kJc&sa=D&sntz=1&usg=AOvVaw1RpJ_cO4Atlezzle8GKUtX

I suspect the problem is rooted in doing both starts as directed in the article: [root@centos7 system]# systemctl start clamd.service [root@centos7 system]# systemctl start clamd@scan.serviceIf so, that makes the explicit `start` of the `clamd@scan.service` superfluous.

Feb 14 21:52:10 centos72.testdomain.com systemd[1]: Unit clamd.service entered failed state.Feb 14 21:52:10 centos72.testdomain.com systemd[1]: clamd.service failed.Feb 14 21:52:10 centos72.testdomain.com systemd[1]: clamd.service holdoff time over, scheduling restart.Feb 14 21:52:10 centos72.testdomain.com systemd[1]: start request repeated too quickly for clamd.serviceFeb 14 21:52:10 centos72.rope-parkstad.nl systemd[1]: Failed to start clamd scanner daemon.Feb 14 21:52:10 centos72.rope-parkstad.nl systemd[1]: Unit clamd.service entered failed state.Feb 14 21:52:10 centos72.rope-parkstad.nl systemd[1]: clamd.service failed.