NETGEAR is aware of a growing number of phone and online scams. To learn how to stay safe click here.
Forum Discussion
Solved
Antivirus stopped updating
The antivirus stopped updating a couple of weeks ago. I tried updating os to 6.9.5 but i stilldo not update.
Tried running host -t txt current.cvd.clamav.net which returned a long string of numbers. Then I tried running
freshclam which returned ERROR: Can't open/parse the config file /etc/clamav/freshclam.conf. Anyone have an idea what to do?
Note that starting with 6.10.x, netgear is dropping antivirus on the RN100 series. See item 19 here: https://community.netgear.com/t5/ReadyNAS-Beta/ReadyNASOS-6-10-0-RC2/m-p/1651396#M10285
11 Replies
Replies have been turned off for this discussion
Realised that freshclam must be run by root. Now got the following :
root@ReadyNAS:~# freshclam
ClamAV update process started at Thu Mar 14 22:01:06 2019
WARNING: Your ClamAV installation is OUTDATED!
WARNING: Local version: 0.100.2 Recommended version: 0.101.1
DON'T PANIC! Read https://www.clamav.net/documents/upgrading-clamav
main.cld is up to date (version: 58, sigs: 4566249, f-level: 60, builder: sigmgr)
Downloading daily-25380.cdiff [100%]
Then nothing happened. The freshclam-process took 95% of CPU so i terminated it after 35 minutes.
Which ReadyNAS unit are you using?
Hey OOM-9
I will add my two cents to this. I checked on my unit here: RN422 running 6.9.5.
AV did update the definitions.
root@Datastore:~# tail -n1 /var/log/frontview/status.log [19/03/15 22:12:56 WET] notice:system:LOGMSG_ANTIVIRUS_DEF_UPDATE Antivirus scanner definition file was updated to 58.25389.
The AV version itself is outdated though, same as siggek
root@Datastore:~# freshclam ClamAV update process started at Fri Mar 15 22:53:38 2019 WARNING: Your ClamAV installation is OUTDATED! WARNING: Local version: 0.100.2 Recommended version: 0.101.1 DON'T PANIC! Read https://www.clamav.net/documents/upgrading-clamav main.cvd is up to date (version: 58, sigs: 4566249, f-level: 60, builder: sigmgr) daily.cvd is up to date (version: 25389, sigs: 1518483, f-level: 63, builder: raynman) bytecode.cvd is up to date (version: 328, sigs: 94, f-level: 63, builder: neo)
When doing verbose status it seems that the AV engine tries to update via: current.cvd.clamav.net
root@Datastore:~# freshclam -v Current working dir is /var/lib/clamav Max retries == 5 ClamAV update process started at Fri Mar 15 22:54:36 2019 Using IPv6 aware code Querying current.cvd.clamav.net TTL: 1183 Software version from DNS: 0.101.1 WARNING: Your ClamAV installation is OUTDATED! WARNING: Local version: 0.100.2 Recommended version: 0.101.1 DON'T PANIC! Read https://www.clamav.net/documents/upgrading-clamav main.cvd version from DNS: 58 main.cvd is up to date (version: 58, sigs: 4566249, f-level: 60, builder: sigmgr) daily.cvd version from DNS: 25389 daily.cvd is up to date (version: 25389, sigs: 1518483, f-level: 63, builder: raynman) bytecode.cvd version from DNS: 328 bytecode.cvd is up to date (version: 328, sigs: 94, f-level: 63, builder: neo)
If I try to resolve that address, even with Google DNS, it does not resolve.
root@Datastore:~# nslookup current.cvd.clamav.net 8.8.8.8 Server: 8.8.8.8 Address 1: 8.8.8.8 google-public-dns-a.google.com nslookup: can't resolve 'current.cvd.clamav.net'
I am not sure how the updates are done exactly and if the problem is that unresolvable address? I can see that freshclam accessed the mirrors successfully when it updated the definitions though.
root@Datastore:~# freshclam --list-mirrors Mirror #1 IP: 104.16.218.84 Successes: 2 Failures: 0 Last access: Fri Mar 15 22:12:21 2019 Ignore: No
Cheers
NETGEAR Academy
Boost your skills with the Netgear Academy - Get trained, certified and stay ahead with the latest Netgear technology!
Join Us!
