[ClamAV] clamd on server is currently down, fresh install

Wanabo

Wanabo

Verified User
Joined
Jan 19, 2013
Messages
339
Just installed ClamAV with:
./build clamav

Code: 
Installation jibberish....
Restarting freshclam.
Restarting clamd.
Restarting exim.
Done ClamAV.

All seemed well, but shortly after install I received a DA message by mail:
A new message or response with subject:
The service 'clamd' on server host.abc.nl is currently down
has arrived for you to view.
Click to expand...

Code: 
[root@host custombuild]# service clamd status
Redirecting to /bin/systemctl status  clamd.service
 clamd.service - Generic clamav scanner daemon
   Loaded: loaded (/etc/systemd/system/clamd.service; enabled; vendor preset: disabled)
   Active: failed (Result: start-limit) since Wed 2016-05-04 16:25:03 CEST; 12s ago
  Process: 14041 ExecStart=/usr/local/sbin/clamd --nofork=yes (code=exited, status=1/FAILURE)
  Process: 14039 ExecStartPre=/usr/bin/chown -R clamav:clamav /var/run/clamd (code=exited, status=0/SUCCESS)
  Process: 14036 ExecStartPre=/usr/bin/mkdir -p /var/run/clamd (code=exited, status=0/SUCCESS)
 Main PID: 14041 (code=exited, status=1/FAILURE)

May 04 16:25:02 host.abc.nl systemd[1]: Unit clamd.service entered failed state.
May 04 16:25:02 host.abc.nl systemd[1]: clamd.service failed.
May 04 16:25:03 host.abc.nl systemd[1]: clamd.service holdoff time over, scheduling restart.
May 04 16:25:03 host.abc.nl systemd[1]: start request repeated too quickly for clamd.service
May 04 16:25:03 host.abc.nl systemd[1]: Failed to start Generic clamav scanner daemon.
May 04 16:25:03 host.abc.nl systemd[1]: Unit clamd.service entered failed state.
May 04 16:25:03 host.abc.nl systemd[1]: clamd.service failed.
May 04 16:25:06 host.abc.nl systemd[1]: start request repeated too quickly for clamd.service
May 04 16:25:06 host.abc.nl systemd[1]: Failed to start Generic clamav scanner daemon.
May 04 16:25:06 host.abc.nl systemd[1]: clamd.service failed.

I found some info on the internet that clamd is waiting to be called by another process.
All of the other answers for some reason seem to assume that clamd actually scans your system automatically. In reality, clamd does not scan your system on its own. All it does is wait for another process to ask it to scan the system, and thus doesn't do much more then speed up the "clamscan" procedure (since it doesn't have to reload virus definitions on each scan).
Click to expand...

Is this correct? clamd should not be active all the time?

I'm concerned ClamAV isn't working correctly. Found this thread http://forum.directadmin.com/showthread.php?t=50807&highlight=clamav and tested with netstat -ant | grep 3310 but there was no output.

Also tried ./build exim_conf to see if that improves things, but no.
 
You must log in or register to reply here.
Back
Top