Hi there, On Tue, 28 Jan 2020, Stefan Malte Schumacher via clamav-users wrote:
we are using Clamav as On-Access-Scanner on a Debian Server Landscape currently containing Debian 8 (to be migrated until the official EOL), Debian 9 and 10. Now I have a new VM which refuses to do an On-Access-Scan despite all the settings being correct. ...
As long as you think in that way, you will make it more difficult to find your mistake. The settings are clearly NOT all correct, or it would work. Computers are like that, and ClamAV is *very* like that.
Why does the problem only appear on that specific machine and not on all VMs with Debian 10?
Because of differences between the configuration on that machine and the configuration on the others which you have not yet found.
How can I fix it?
Find your mistake. If you try to give us more information, for example about fanotify configuration, you will probably find your mistake in the process. If you keep all the configuration in /etc then a recursive diff between that directory on the problematic host and the same directory on one of the others might be informative but there are probably easier ways. -- 73, Ged. _______________________________________________ clamav-users mailing list clamav-users@lists.clamav.net https://lists.clamav.net/mailman/listinfo/clamav-users Help us build a comprehensive ClamAV guide: https://github.com/vrtadmin/clamav-faq http://www.clamav.net/contact.html#ml
