Freshclam doesn't start because databases are now updated by cron job '/etc/cron.d/clamav-update' in 'freshclam.service' file. If cron job file exists freshclam daemon is not necessary.

Pick one of two options:

1)

vi /usr/lib/systemd/system/clamav-freshclam.service

replace

ConditionPathExists=!/etc/cron.d/clamav-update

with

#ConditionPathExists=!/etc/cron.d/clamav-update

vi /etc/cron.d/clamav-update

replace

0  */3 * * * root /usr/share/clamav/freshclam-sleep > /dev/null

with

#0  */3 * * * root /usr/share/clamav/freshclam-sleep > /dev/null

or

2)

vi /usr/bin/toaststat

replace

for sv in clamd@scan clamav-freshclam spamassassin ... ... ...

with

for sv in clamd@scan spamassassin ... ... ...
On 7/11/2021 11:11 AM, Gary Bowling wrote:


I see where Chandran had this same issue a few weeks ago. What did you do to resolve it?


Thanks, Gary



On 7/11/2021 1:03 PM, Gary Bowling wrote:

Running a toaster on CentOS 7, with everything updated every couple of months. Just did an update on my server. The update took me from

clamav-update-0.103.2-1.el7.x86_64   > clamav-update-0.103.2-2.el7.x86_64

All the other clamav packages are also updated from/to the same version, clamav, clamav-lib, clamav-filesystem.

After a reboot, toastat gives me

systemd service:         clamav-freshclam:       [  FAILED  ]


Then I took a look at.

systemctl status clamav-freshclam
â clamav-freshclam.service - ClamAV virus database updater
   Loaded: loaded (/usr/lib/systemd/system/clamav-freshclam.service; enabled; vendor preset: disabled)
   Active: inactive (dead)
Condition: start condition failed at Sun 2021-07-11 12:48:21 EDT; 7min ago
           ConditionPathExists=!/etc/cron.d/clamav-update was not met
     Docs: man:freshclam(1)
           man:freshclam.conf(5)
https://www.clamav.net/documents


The /var/log/clamav/freshclam.log just has this one line.

Sun Jul 11 12:29:07 2021 -> Update process terminated


Any suggestions as to how to resolve this?


Thanks, Gary

--------------------------------------------------------------------- To unsubscribe, e-mail: [email protected] For additional commands, e-mail: [email protected]
--------------------------------------------------------------------- To unsubscribe, e-mail: [email protected] For additional commands, e-mail: [email protected]

---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]

Reply via email to