Same here, root cause is the optional installation of nethserver-httpd-admin which provides the httpd-admin.service which is still a Requisite to run Scan now. Update the database has the same issue.
Do not think so, the cron invokes /sbin/e-smith/nethserver-clamscan directly:
cat /etc/cron.d/clamscan
# ================= DO NOT MODIFY THIS FILE =================
#
# Manual changes will be lost when this file is regenerated.
#
# Please read the developer's guide, which is available
# at NethServer official site: https://www.nethserver.org
#
#
# nethserver-clamscan filesystem scan
34 17 * * * root /sbin/e-smith/nethserver-clamscan
My error
I interpreted the âHourâ setting for the daily scan as being the exact hourâŠ
Looking at the cron file made me realise that I was wrongâŠ
When I wait long enough (I helped it a bit by not complying to the first line in the file) for the time that it is started, it does run.
However, the result is (from clamscan.log):
Thu Feb 18 16:50:01 2021
Scanned Folder: /ERROR: Can't open file or directory
Is there a way to run it more verbose so it will tell what folder cannot be opened?
Did âhackedâ this test setup to get the buttons working so maybe it is because I was able to (manual)update the database and run an initial (manual)scan
I ran the command. clamav-unofficial-sigs.sh is in /usr/sbin, so ran it from there.
The funny thing is, I canât really see any real difference in the logs of this run of the db update and previous ones (apart from âx hours have not yet elapsedâ). But⊠now the scan did run completely (made my laptop sound like it was ready for lift off). Result:
------------------------------------
Thu Feb 18 17:26:01 2021
Scanned Folder: //var/lib/nethserver/nextcloud/9268A0AC-3256-4608-8EB9-A38276518976/files/eicar_com.zip: Win.Test.EICAR_HDB-1 FOUND
/var/lib/clamav-unofficial-sigs/dbs-lmd/sigpack.tgz: Php.Exploit.C99-27 FOUND
----------- SCAN SUMMARY -----------
Known viruses: 8571332
Engine version: 0.103.0
Scanned directories: 17386
Scanned files: 101404
Infected files: 2
Data scanned: 6344.86 MB
Data read: 4235.92 MB (ratio 1.50:1)
Time: 1034.680 sec (17 m 14 s)
Start Date: 2021:02:18 17:26:01
End Date: 2021:02:18 17:43:16
So, updating the database from the command line seems to have done somethingâŠ