The service 'freshclam' on server is currently down

bobsthename

Verified User
Joined
Sep 23, 2009
Messages
66
Location
NZ
Hello,
I am getting this message from directadmin every hour on 2 Debian servers, but unsure why its happening and how to stop it.
The service 'freshclam' on server is currently down.
Thanks
 
Hello,

Either start freshclamd

Code:
/etc/init.d/freshclam start

(btw what do you see if you try to start it manually?)

or remove freshclam from monitoring:

Code:
./build set_service freshclam OFF
 
Thanks, I get this error

/etc/init.d/freshclam start
-bash: /etc/init.d/freshclam: No such file or directory
 
I see, I've missed you on Debian 8. Try then

Code:
systemctl start freshclam
systemctl status freshclam
 
Ran into same issue, would appear the lock directory is not created correctly, causing the daemon to have some weird failed state all the time:

Code:
killall freshclam
mkdir -p /var/run/clamd
chown root:clamav /var/run/clamd
chmod -R 775 /var/run/clamd
systemctl start freshclam

After this the status command should show it as running correctly.
 
Just noticed - this issue appears again after reboot, apparently something is wrong with the startup scripts fundamentally. That makes this an issue for the DA team to resolve.
 
I was under the impression that the binary itself was called and ran as a script rather than a running service. I believe it can be done either way.
 
If you installed custombuild2 with clamav, you can copy there init.d script.

Code:
cp -a /usr/local/directadmin/custombuild/freshclam_debian /etc/init.d/freshclam
chmod 755 /etc/init.d/freshclam
ln -s /usr/local/bin/freshclam /usr/bin/freshclam
 
Back
Top