NETGEAR is aware of a growing number of phone and online scams. To learn how to stay safe click here.
Forum Discussion
Solved
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...
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
I have a RN212 and a RN214 connected to the same network, and Im experiencing the same update issue on both devices. According to the log on the RN212 the problem/first error message started july 10. It did update update both on the 11'th and 12'th, but then got stuck at the 12'th of july. No updates since then, and I get the error message daily when it start-up in the morning.
According to the log on the RN214 the problem/first error message started july 12. However dispite a daily error message after start-up it continues to update the antivirus. From the 17'th the RN214 has updated without error messages.
So - the 214 had some 'hick-ups' but seems to be back on track, however the 212 did not, and is stuck at june 12'th update.
In the log of the 212 and the 214 the file "clamscan.log" do display the following error:
ERROR: Malformed database
on some of the entries....
Restarting the 212 do not fix the issue, and I'm clueless as what to do :-(
I don't think my ROOT-directory is an issue....,
=== df -h ===
Filesystem Size Used Avail Use% Mounted on
udev 10M 4.0K 10M 1% /dev
/dev/md0 3.7G 1.2G 2.3G 35% /
tmpfs 1009M 4.0K 1009M 1% /dev/shm
tmpfs 1009M 1.2M 1008M 1% /run
tmpfs 505M 12M 493M 3% /run/lock
tmpfs 1009M 0 1009M 0% /sys/fs/cgroup
/dev/md127 5.5T 1.2T 4.4T 21% /data
/dev/md127 5.5T 1.2T 4.4T 21% /home
/dev/md127 5.5T 1.2T 4.4T 21% /apps
=== df -i ===
Filesystem Inodes IUsed IFree IUse% Mounted on
udev 187927 228 187699 1% /dev
/dev/md0 1048576 13428 1035148 2% /
tmpfs 188818 2 188816 1% /dev/shm
tmpfs 188818 450 188368 1% /run
tmpfs 188818 30 188788 1% /run/lock
tmpfs 188818 9 188809 1% /sys/fs/cgroup
/dev/md127 0 0 0 - /data
/dev/md127 0 0 0 - /home
/dev/md127 0 0 0 - /apps
Sorry if this is a duplicate
I checked the volume.zip and there is plenty of space.
The problem continues, however.
Thanks
DW
dweinshel wrote:I checked the volume.zip and there is plenty of space.
The problem continues, however.
Did you try turning off AV and then turning it on again?
Also, you could also try changing your DNS to 8.8.8.8 in the NAS.
I have truned AV on and off.
Any downside to DNS 8.8.8.8 ?
NETGEAR Academy
Boost your skills with the Netgear Academy - Get trained, certified and stay ahead with the latest Netgear technology!
Join Us!
