I restarted clamd and the run file was created. I un-commented the code in exim.conf and everything started working again.
The only thing I can think of is that the updated of clamd-data may have installed stale data which was then replaced with the freshclam CRON job.
Either way, we're all working again.
On Wednesday 04 May 2016 16:40:48 Gary Stainburn wrote:
I have just run a 'yum update' on a Centos 7.2 server which updated several hundred RPMs.
The update worked fine with no errors or warnings
I then rebooted the server and now my EXIM is rejecting emails because the clamd service isn't running.
So I tried:
[root@ollie2 ~]# systemctl restart clamd.exim Failed to restart clamd.exim.service: Unit clamd.exim.service failed to load: No such file or directory. [root@ollie2 ~]# systemctl list-unit-files --type=service|grep -i exim exim.service enabled [root@ollie2 ~]# systemctl list-unit-files --type=service|grep -i clam clamd.service enabled clamd@.service static [root@ollie2 ~]# systemctl restart clamd [root@ollie2 ~]# systemctl status clamd ● clamd.service - Home brewed module for the Clam Antivirus scanner Loaded: loaded (/usr/lib/systemd/system/clamd.service; enabled; vendor preset: disabled) Active: failed (Result: start-limit) since Wed 2016-05-04 16:34:16 BST; 5s ago Process: 14405 ExecStart=/root/bin/clamd.start (code=exited, status=1/FAILURE) Main PID: 14405 (code=exited, status=1/FAILURE)
May 04 16:34:16 ollie2.ringways.co.uk systemd[1]: Unit clamd.service entered failed state. May 04 16:34:16 ollie2.ringways.co.uk systemd[1]: clamd.service failed. May 04 16:34:16 ollie2.ringways.co.uk systemd[1]: clamd.service holdoff time over, scheduling restart. May 04 16:34:16 ollie2.ringways.co.uk systemd[1]: start request repeated too quickly for clamd.service May 04 16:34:16 ollie2.ringways.co.uk systemd[1]: Failed to start Home brewed module for the Clam Antivirus scanner. May 04 16:34:16 ollie2.ringways.co.uk systemd[1]: Unit clamd.service entered failed state. May 04 16:34:16 ollie2.ringways.co.uk systemd[1]: clamd.service failed. [root@ollie2 ~]#
Can anyone tell me what happened to clamd.exim, and what I need to do to get it working again. For now I've had to comment out:
# Deny if the message contains a virus. Before enabling this check, you # must install a virus scanner and set the av_scanner option above. # deny set acl_m0 = clamd:/var/run/clamd.exim/clamd.sock malware = * set acl_c_SPAM = 1 message = A virus has been detected ($malware_name).
CentOS mailing list CentOS@centos.org https://lists.centos.org/mailman/listinfo/centos