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
StephenB
Nov 01, 2021Guru - Experienced User
TerryJColes wrote: As I see it the problem must be at the Netgear end.
It could just as easily be the ClamAV servers (and perhaps linked to the old version of ClamAV that the NAS is running).
FWIW, the AV updates don't go through the Netgear servers.
TerryJColes wrote:
I would prefer not to install a Beta version unless the problem has definitely been identified and is in fact in the firmware and not the server side.
Up to you of course.
TerryJColes
Nov 01, 2021Luminary
StephenB wrote:FWIW, the AV updates don't go through the Netgear servers.
Fair enough, but as I recall the last time this occured I believe Netgear were in discussion with the ClamAV team about this issue and there was some talk about ClamAV needing to do something.
If that is the case, it may well be that the problem is at the 'server end', but ClamAV's server, not Netgear's.
As you say it's up to me and for the moment at least I'd prefer not to expend a lot of thime on this (as I did last time). Hopefully, since the problem has oscurred before, it shouldn't be quite so hard for Netgear / ClamAV to put it right.
- StephenBNov 01, 2021Guru - Experienced User
TerryJColes wrote:
If that is the case, it may well be that the problem is at the 'server end', but ClamAV's server, not Netgear's.
You might also want to double-check that you don't have a full OS partition.
- TerryJColesNov 01, 2021Luminary
StephenB wrote:
You might also want to double-check that you don't have a full OS partition.Anything is possible of course, but it seems a bit spooky that two other people have experienced the same problem at the same time.
I've checked the logs and there is nothing in there apart from the two alerts about ClamAV not updating.
- jhoweNov 01, 2021Aspirant
TerryJColes wrote:
StephenB wrote:
You might also want to double-check that you don't have a full OS partition.Anything is possible of course, but it seems a bit spooky that two other people have experienced the same problem at the same time.
I've checked the logs and there is nothing in there apart from the two alerts about ClamAV not updating.
ReadyNAS OS must be running version 0.100 of ClamAV. Another thread noted that this version went end-of-life on 10/29/21 (as indicated in https://docs.clamav.net/faq/faq-eol.html#version-support-matrix).
- Blaine_Nov 01, 2021Aspirant
It does seem to be using 0.100. This is what my "freshclam -v" claims as it refuses to run:
Software version from DNS: 0.103.3
WARNING: Your ClamAV installation is OUTDATED!
WARNING: Local version: 0.100.2 Recommended version: 0.103.3
- StephenBNov 01, 2021Guru - Experienced User
Blaine_ wrote:
Software version from DNS: 0.103.3
WARNING: Your ClamAV installation is OUTDATED!
WARNING: Local version: 0.100.2 Recommended version: 0.103.3
https://community.netgear.com/t5/ReadyNAS-Beta/ReadyNASOS-6-10-6-Beta/m-p/2151119#M10972
- swehjoNov 01, 2021Guide
And I am obviously using 0.100.2.... I read the link, https://docs.clamav.net/faq/faq-upgrade.html, which I actually don't understand... Do I really have to update this manually, isn't that taken care of by the update feature of the ReadyNAS?!
- StephenBNov 01, 2021Guru - Experienced User
swehjo wrote:
Do I really have to update this manually, isn't that taken care of by the update feature of the ReadyNAS?!
For some reason setting "check for updates" to "Beta" doesn't find it. So you will need to install it manually.
That isn't difficult - unzip the relevant package in the beta announcement, and use the "install firmware" button on the system->settings->update page.
- swehjoNov 01, 2021Guide
Ah... Ok, that seems rather straight forward. A bit reluctant to install beta versions though. Any idea when a stable release solving this matter will come?
- jhoweNov 01, 2021Aspirant
StephenB wrote:https://community.netgear.com/t5/ReadyNAS-Beta/ReadyNASOS-6-10-6-Beta/m-p/2151119#M10972
The Beta announcement doesn't list the RN428 as a supported system. Is that just an oversight and the x86_64 version actually does support the RN428?
- StephenBNov 01, 2021Guru - Experienced User
jhowe wrote:
StephenB wrote:
https://community.netgear.com/t5/ReadyNAS-Beta/ReadyNASOS-6-10-6-Beta/m-p/2151119#M10972
The Beta announcement doesn't list the RN428 as a supported system. Is that just an oversight and the x86_64 version actually does support the RN428?
I suspect just an oversight. It'll run on other platforms (legacy Pro and Ultra systems converted to OS-6). There isn't much platform-specific code.
Related Content
NETGEAR Academy
Boost your skills with the Netgear Academy - Get trained, certified and stay ahead with the latest Netgear technology!
Join Us!