How can I fix the error: [Anti-virus Signature - freshclam] service could not be started?

On Centos/AlmaLinux/RHEL 8 the Anti-virus signature service (freshclam) fails to start after rebooting the server. This is caused by an incorrect PID location in the freshclam config file.

To fix the problem from within the Warden extension interface:

Go to Warden -> Settings -> Signature Updates and change the PID file option from /run/clamav-freshclam/freshclam.pid to /run/freshclam.pid . Then restart the Anti-virus Signature Service on the Dashboard. This will fix the issue.

To fix the problem from the command line:

Edit the file /etc/freshclam.conf and change the PidFile option

From:

PidFile /run/clamav-freshclam/freshclam.pid

To:

PidFile /run/freshclam.pid

Enable Freshclam:

systemctl enable clamav-freshclam

Restart Freshclam:

systemctl restart clamav-freshclam
  • signatures, freshclam
  • 0 Users Found This Useful
Was this answer helpful?

Related Articles

How can I fix the error: Host '127.0.0.1' is not allowed to connect to this MariaDB server?

When looking at the server mail log you see this: Apr 4 11:01:15 alma amavis[3540852]:...

ClamAV will not start. How can I fix the ClamAV error: daily.{c[vl]d,inc} was not met?

ClamAV refuses to start and when viewing the status you see...

How can I fix any statistics generation problems?

Missing the Warden Crontab Entry There is a crontab entry that will update Warden statistics...

How can I fix the error: "milter-reject: END-OF-MESSAGE from..." in the log and found the AV in error (cannot read /etc/clam.d/scan.conf).

Cloudlinux / Imunify360 added their own version of ClamAV to their repo which accidentally...

How can I fix the error: Can't connect to TCP port 10024 on 127.0.0.0 [Address already in use] when trying to start Amavis?

When trying to start Amavis you see this in the mail log: Oct 02 03:20:15 condor3648 systemd[1]:...