NETGEAR is aware of a growing number of phone and online scams. To learn how to stay safe click here.
Forum Discussion
HansRL
Jul 10, 2020Apprentice
Antivirus scanner definition file update failed
ReadyNAS 212 OSversion 6.10.3 Since a couple of days (starting July 5th) my virus definition file update failes.. stating check internet-connection ; my internet connection is fine because the rea...
- Dec 23, 2020
I kept getting errors while executing command: 'systemctl status clamav-freshclam.service' ; see below
root@Geldrop:~# systemctl status clamav-freshclam.service
● clamav-freshclam.service - ClamAV virus database updater
Loaded: loaded (/lib/systemd/system/clamav-freshclam.service; static; vendor preset: disabled)
Active: failed (Result: exit-code) since Wed 2020-12-23 14:33:45 CET; 15s ago
Process: 6263 ExecStart=/usr/bin/freshclam --quiet (code=exited, status=1/FAILURE)
Main PID: 6263 (code=exited, status=1/FAILURE)Dec 23 14:33:45 Geldrop systemd[1]: Starting ClamAV virus database updater...
Dec 23 14:33:45 Geldrop freshclam[6263]: ClamAV update process started at Wed Dec 23 14:33:45 2020
Dec 23 14:33:45 Geldrop freshclam[6263]: main.cvd is up to date (version: 59, sigs: 4564902, f-level: 60, builder: sigmgr)
Dec 23 14:33:45 Geldrop freshclam[6263]: daily.cld is up to date (version: 26026, sigs: 4328586, f-level: 63, builder: raynman)
Dec 23 14:33:45 Geldrop freshclam[6263]: bytecode.cvd is up to date (version: 331, sigs: 94, f-level: 63, builder: anvilleg)
Dec 23 14:33:45 Geldrop systemd[1]: clamav-freshclam.service: Main process exited, code=exited, status=1/FAILURE
Dec 23 14:33:45 Geldrop systemd[1]: Failed to start ClamAV virus database updater.
Dec 23 14:33:45 Geldrop systemd[1]: clamav-freshclam.service: Unit entered failed state.
Dec 23 14:33:45 Geldrop systemd[1]: clamav-freshclam.service: Failed with result 'exit-code'.The following I did after reading the following web-page (https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=972974):
stopping clamav: 'systemctl stop clamav-daemon'stopping clamav freshclam: 'systemctl stop clamav-freshclam'
adjusting member 'usr.bin.freshclam' in dir: /etc/apparmor.d ; adding 'capability dac_override,' and 'capability chown,'
capability setgid,
capability setuid,
capability dac_override,
capability chown,removing all file from dir: '/var/lib/clamav' (bytecode ; daily ; main ; mirrors ; antivir)
starting clamav : 'systemctl start clamav-daemon'
starting clamav freshclam: 'systemctl start clamav-freshclam'
starting 'clamav freshclam' takes a while (about 2 minutes, I guess) and afterwards it looks like the normal databased-updater is working again.... lets see what happens the coming days...
regards
chrhei
Sep 20, 2020Luminary
ReadyNAS 202, Firmware 6.10.3, 2x 1TB
Hello. I will just say again since I run a daily CRON job my issue is resolved for me. Lets call it a workaround:
- login to your NAS as root via ssh
- 'crontab -e'
- e.g. add: '0 4 * * * /usr/bin/freshclam' - this will execute freshclam daily at 4 a.m.
RBRoberts115
Oct 02, 2020Aspirant
chrhei wrote:ReadyNAS 202, Firmware 6.10.3, 2x 1TB
Hello. I will just say again since I run a daily CRON job my issue is resolved for me. Lets call it a workaround:
- login to your NAS as root via ssh
- 'crontab -e'
- e.g. add: '0 4 * * * /usr/bin/freshclam' - this will execute freshclam daily at 4 a.m.
This suggestion worked for me and got my updates running again. At least for the past 48 hours. I have not had a problem. We'll see how long it lasts.
Related Content
NETGEAR Academy

Boost your skills with the Netgear Academy - Get trained, certified and stay ahead with the latest Netgear technology!
Join Us!