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
HansRL
Feb 03, 2021Apprentice
Netgear, Justin (@dingjs1421), came back to me and told me they have a solution for this issue..... Netgear did an adjustment to my virusscan-software via "secure diagnostic modus" and I have asked what they did:
the service:freshclam is used to download AV pattern db , after succeeded to download it tries to load all db files
(several houndreds MB) into memory to test. Due to limited memory resources on ReadyNAS RN21x,
it might run into the issue: can't allocate enough memory to test DB.
So we just disable the option: TestDatabases for freshclam. Thanks Justin
So I looked what was changed and found out it was file freshclam.conv ; file is located in etc/clamav;
This is my freshclam now:
DatabaseOwner root
LogSyslog true
LogFacility LOG_LOCAL6
Debug false
MaxAttempts 5
DatabaseDirectory /var/lib/clamav
DNSDatabaseInfo current.cvd.clamav.net
ConnectTimeout 120
ReceiveTimeout 120
TestDatabases false
ScriptedUpdates true
CompressLocalDatabase false
Bytecode true
NotifyClamd /etc/clamav/clamd.conf
OnErrorExecute /usr/bin/clamav_event -s 1
OnUpdateExecute /usr/bin/clamav_event -s 0
Checks 2
DatabaseMirror database.clamav.net
DatabaseMirror db.cn.clamav.net
DatabaseMirror db.tw.clamav.net
The first normal update did work, will keep checking the next couple of days...
rgds Hans
HansRL
Feb 03, 2021Apprentice
oeps a type-o.... freshclam.conv
must be
freshclam.conf
- Matteo73Feb 03, 2021Aspirant
Thx for your quickly support.
I saw by ssh that the problem was not enought memory on my Readynas HW.
Btw on older readynas 102xx with the lastest fw, netgear disabled antivirus option, so I think they are adopting on next update the same solution :-(At the moment I'll try what you suggest.
Best regards
Matteo
- StephenBFeb 03, 2021Guru - Experienced User
Matteo73 wrote:
Btw on older readynas 102xx with the lastest fw, netgear disabled antivirus option, so I think they are adopting on next update the same solution :-(I don't think they will do that, as there are other desktop models that also have 2 GB of RAM. Plus they have a simple solution. They should have pushed a hot-fix for it months ago - no idea why they didn't.
The RN100 series only had 512 GB, which turned out not to be enough to run all the services as time went on.
HansRL: thanks for posting what they changed.
- HansRLFeb 05, 2021Apprentice
Unfortunately I have to say the solution advised by NETGEAR did not solve it....
the first time wrong (second time the normal update-proces ran) I got next messages in the log:
feb 04, 2021 15:17:14 Systeem: ReadyNASOS-achtergrondservice is gestart.feb 04, 2021 15:17:07 Systeem: ReadyNASOS-service of -proces (readynasd) is opnieuw gestart.
feb 04, 2021 15:15:53 Systeem: ReadyNASOS-service of -proces (enclosure_monit) is opnieuw gestart.
the following normal update i got the well know message:
feb 05, 2021 15:16:04 Systeem: Bijwerken van definitiebestand van antivirusscanner is mislukt door een fout bij het downloaden. Controleer uw internetverbinding..
rgds Hans
Related Content
NETGEAR Academy

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