There is definitely some bug in today's ClamAV update. I have the same
problem on all servers running ClamAV (different distributions,
different versions).
There is a workaround that worked for me - stop ClamAV daemon, delete
all files in /var/lib/clamav, run freshclam manually, then start
Package: clamav-freshclam
Version: 0.101.1+dfsg-3
Followup-For: Bug #923867
Hi again,
I stopped the freshclam service and tried running the update from the
command line. The same story, 100% CPU usage, same info shown:
# freshclam update
Wed Mar 6 13:21:37 2019 -> ClamAV update process started
2 matches
Mail list logo
