[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
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. 2ff7e9595c
コメント