Fri Aug 13 22:56:07 2021 -> SelfCheck: Database status OK.
Fri Aug 13 23:10:45 2021 -> SelfCheck: Database status OK.
Fri Aug 13 23:20:22 2021 -> instream(local): Win.Malware.Aa93a15d-6745814-0 FOUND
Fri Aug 13 23:20:45 2021 -> SelfCheck: Database status OK.
Fri Aug 13 23:30:47 2021 -> SelfCheck: Database status OK.
Fri Aug 13 23:40:47 2021 -> SelfCheck: Database status OK.
Comments
I can see issue #167 and pull #169 seem to be aimed at resolving this and predate the current release by someway but the issue still exists. I have turned off deleting for infected files found during background scan for the time being as this would result in files being deleted unnecessarily.
If I am not mistaken and pull #169 is included in the latest release could this be the result of some sort of concurrency issue?
Steps to reproduce
Expected behaviour
Only the uploaded known infected file should be detected as infected in logs.
Actual behaviour
The infected file and what I assume is the very next file scanned are both detected as infected.
Server configuration
Operating system: Alpine Linux 3.13 Arm64
Web server: Nginx 1.18.0
Database: PostgreSQL 13.3
PHP version: PHP 7.4.21
Nextcloud version: 20.0.12
Where did you install Nextcloud from: Alpine Linux Repositories
List of activated apps:
Nextcloud configuration:
Client configuration
Browser: Chrome Version 92.0.4515.131 (Official Build) (64-bit)
Operating system: Ubuntu 20.04.2 LTS
Logs
Nextcloud log (data/owncloud.log)
Clamav log
Comments
I can see issue #167 and pull #169 seem to be aimed at resolving this and predate the current release by someway but the issue still exists. I have turned off deleting for infected files found during background scan for the time being as this would result in files being deleted unnecessarily.
If I am not mistaken and pull #169 is included in the latest release could this be the result of some sort of concurrency issue?