Thanks, Gary
On 7/11/2021 4:01 PM, Eric Broch wrote:
If the service is running, updates are happening, but if the clamav developers are doing away with freshclam daemon, which seems likely, option 2 seems to be the way to go.--------------------------------------------------------------------- To unsubscribe, e-mail: qmailtoaster-list-unsubscr...@qmailtoaster.com For additional commands, e-mail: qmailtoaster-list-h...@qmailtoaster.com
On 7/11/2021 1:55 PM, Gary Bowling wrote:
Thanks Eric.
So I kinda of like having the service show up in toaststat as it's an easy way to check things. Which would encourage me to take option 1.
However, is the "new" way of doing it, to do it in cron? If it is, then that's probably better as it makes my box more "standard."
I'm not sure having the service show up in toaststat really means anything anyway, it just says the service is running. Not that the db is actually getting updated.
Thanks, Gary
On 7/11/2021 2:51 PM, Eric Broch wrote:
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.--------------------------------------------------------------------- To unsubscribe, e-mail: qmailtoaster-list-unsubscr...@qmailtoaster.com For additional commands, e-mail: qmailtoaster-list-h...@qmailtoaster.com
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:
--------------------------------------------------------------------- To unsubscribe, e-mail: qmailtoaster-list-unsubscr...@qmailtoaster.com For additional commands, e-mail: qmailtoaster-list-h...@qmailtoaster.com
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: qmailtoaster-list-unsubscr...@qmailtoaster.com For additional commands, e-mail: qmailtoaster-list-h...@qmailtoaster.com
---------------------------------------------------------------------
To unsubscribe, e-mail: qmailtoaster-list-unsubscr...@qmailtoaster.com
For additional commands, e-mail: qmailtoaster-list-h...@qmailtoaster.com
---------------------------------------------------------------------
To unsubscribe, e-mail: qmailtoaster-list-unsubscr...@qmailtoaster.com
For additional commands, e-mail: qmailtoaster-list-h...@qmailtoaster.com
