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've been following this thread for a while because I have had this issue intermittently for several months. However, I have what may be a variation on the issue which could prove helpful to unravelling the cause/solution. I have two nearly identical RN214 on the same network with identical setups, including all network settings. One is experiencing the issue, the other is not. The only difference is that the one that is currently not updating the antivirus definitions is 4x6TB while the other is 4x3TB. They are both assigned static IP addresses, which are reserved for them in the router (a Netgear Nighthawk RAX 80) outside the range of addresses available for DHCP. For some reason, the router occasionally assigns the "problem" NAS another address by DHCP. Despite that, all other network-dependent functions (RAIDair, admin page, share access, time sync, rsync backups) appear normal. The "extra" address doesn't persist in the router. In addition, occasionally I have gotten the download to succeed by turning off AV, restarting the NAS and then re-enabling AV. That solution doesn't work every time, however.
Just an "update" to my prior post. After I made the statement that my RN214 were configured identically (other than the specific static address, of course), I looked a bit further to make sure there wasn't an app or service running on one that wasn't installed or running on the other. It turns out that there was: the "trouble" NAS was running ReadyNAS Replicate (which I don't recall having activated, and definitely never used). When I deregistered the NAS and turned off the service, the virus scanner definition updated successfully within minutes. The "good" NAS has never run any cloud services that I can detect.
I have 10 ReadyNAS in our enterprise and they are all configured the same. Only one of my NAS' is having the virus update problem. I am updating daily with freshclam -v
The fact that not all NAS are equally affected is, I expect, one of the (if not the only) things that is causing resolution to take so long. It must be difficult to even duplicate the condition.
It's now been several days since I've had a failure to update. I don't want to assume that the problem is solved, but I did want to report that turning off ReadyNAS Replicate seems to have addressed the issue. At any rate, both of my RN214s are consistently behaving identically.
ReadyNAS Replicate could not be the cause of the update failure on my site, because it was not active on my configuration...
I noticed when the manual upgrade via FRESHCLAM has no new files to install and later on the regular update of the virusscanner is running, I received no error message but the update failed.
While checking the normal LOG I saw these messages:System: ReadyNASOS background service started. System: ReadyNASOS service or process (readynasd) was restarted. System: ReadyNASOS service or process (continuous_snap) was restarted
but nothing about the failed update of the virusscanner
and checking the SYSTEM.LOG I saw just before the above messages, the regular update of the virusscanner went wrong and a message regarding "Malformed database".In order to be sure your virusscanner is updated, you must see almost a daily entry in your log: "System: Antivirus scanner definition file was updated to 59.%%%%%"
NETGEAR Academy
Boost your skills with the Netgear Academy - Get trained, certified and stay ahead with the latest Netgear technology!
Join Us!
