Antivirus scanner definition file update failed

Well, it doesn't seem like anything is being done to resolve this problem, but I will add just one more update with my experiences.

As noted in my last post, the AV update worked again after a forced restart on my NAS.  The new information is that it only worked once before the error came back.  I had several more NAS lockups (caused by a bad eSATA drive connection, not something in the NAS), and after each forced restart, the AV updates worked either once or twice before the same error came back.  So I didn't want anyone thinking that simply restarting the NAS was any kind of a solution to this problem at all.

What's weird about this is that it only affects some folks.  I enabled AV on my RN202 shortly after this was reported, and I haven't had any errors updating the definitions.

I had to buy a replacement Nas. I got another readyNAS 212.

Same error occurs with both those boxes now.

I'm not surprised.

It appears these are no longer being supported by Netgear. 

all

Apologies for the late update.

Seems that the issue was with clamd process wherein it eats a lot of memory getting it terminted resulting to the update failing. This is being coordinated with Clam if correct. 

We will try to provide update ASAP.

HTH

dweinshel

You may want to try and get the latest update. Kindly connect your NAS to the Internet and reboot if possible then wait for a few minutes. A hotfix should be downloaded automatically. 

---

Marc_V wrote:

 

You may want to try and get the latest update. Kindly connect your NAS to the Internet and reboot if possible then wait for a few minutes. A hotfix should be downloaded automatically. 

 

 

---

Well that happened just as predicted.

If I get the dreaded definition file update failed message, I'll report back.

The hotfix was automatically applied to my ReadyNAS per the Logs view within the Unser Interface which will have as noted below
Lets hope this is now fixed
Log entry to look for:

Thank you, Netgear, since a happy event never comes late: 3 succesful anti virus updates since the hotfix.

---

TerryJColes wrote:

---

If I get the dreaded definition file update failed message, I'll report back.

---

I didn't.  Fingers crossed that this is the last time I will need to post here.

Hi all,

First of all it looks promising this hotfix, already 2 updates went well and without any issue.

On March 5th, I did saw in the system main-view it mentioned "Firmware : 6.10.4 hotfix 1 " , but checking the logs I had my doubts...

no entry in the log regarding the update to hotfix 1 and found also next message:
rn-update.sh[14483]: E: Sub-process /usr/bin/dpkg returned an error code (1)

first tried a reboot but still finding entries in logs which gives me indications the hotfix was NOT installed correctly

so I did a reinstall of the firmware with version 6.10.4 and immediately after finishing this reinstall I got an entry in the log stating
"A hotfix was applied to your system (6.10.4 Hotfix 1)."
And of course checking again the logs:
readynasd[2373]: A hotfix was applied to your system (6.10.4 Hotfix 1).

rgds

AV updates failing again - two days straight now. Firmware v6.10.4 Hotfix 1 was applied last month and seemed to work for a while. This is becoming tedious.

Tom

---

tewatson60 wrote:

AV updates failing again - two days straight now. Firmware v6.10.4 Hotfix 1 was applied last month and seemed to work for a while. This is becoming tedious.

 

Tom

 

---

tewatson60 

I rebooted my ReadyNAS with Hotfix 1 applied and did see one instance where AV Updates where not being applied.

I logged into my ReadyNAS via a command prompt with command SSH root@root@xxxxxReadyNAS (use your admin password when promted) and found after checking the freshclam service using the command below in bold and that it had failed with an error similar to

root@xxxxxReadyNAS:~# 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 Day 2021-mm-yy hh:mm:ss AEDT; xxh ago
  Process: 4507 ExecStart=/usr/bin/freshclam --quiet (code=exited, status=1/FAILURE)
 Main PID: 4507 (code=exited, status=1/FAILURE)

I then issued the command 

root@xxxxxReadyNAS:~# systemctl start clamav-freshclam.service

and the freshclam service started successfully and has been running without issue.   If you check the status again you will see something like

root@xxxxxReadyNAS:~# 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: inactive (dead) since Wed 2021-03-10 08:33:47 AEDT; 20h ago
  Process: 6711 ExecStart=/usr/bin/freshclam --quiet (code=exited, status=0/SUCCESS)
 Main PID: 6711 (code=exited, status=0/SUCCESS)

Mar 10 08:33:11 xxxxxReadyNAS systemd[1]: Starting ClamAV virus database updater...
Mar 10 08:33:12 xxxxxReadyNAS freshclam[6711]: ClamAV update process started at Wed Mar 10 08:33:12 2021
Mar 10 08:33:12 xxxxxReadyNAS freshclam[6711]: main.cld is up to date (version: 59, sigs: 4564902, f-level: 60, builder: sigmgr)
Mar 10 08:33:19 xxxxxReadyNAS freshclam[6711]: Downloading daily-26103.cdiff [100%]
Mar 10 08:33:25 xxxxxReadyNAS freshclam[6711]: daily.cld updated (version: 26103, sigs: 3958648, f-level: 63, builder: raynman)
Mar 10 08:33:31 xxxxxReadyNAS freshclam[6711]: Can't query daily.26103.93.1.0.6810DA54.ping.clamav.net
Mar 10 08:33:32 xxxxxReadyNAS freshclam[6711]: bytecode.cld is up to date (version: 333, sigs: 92, f-level: 63, builder: awillia2)
Mar 10 08:33:46 xxxxxReadyNAS freshclam[6711]: Database updated (8523642 signatures) from database.clamav.net (IP: 104.16.218.84)
Mar 10 08:33:46 xxxxxReadyNAS freshclam[6711]: Clamd successfully notified about the update.
Mar 10 08:33:47 xxxxxReadyNAS systemd[1]: Started ClamAV virus database updater.

My guess it may be failing for reasons unknown after a reboot and then without rebooting your NAS you start the Freshclam service it will continue to run.

My ReadyNAS has been running since the last reboot on Mar 5 without missing an AV Update

Thx for the insight. My concern is whether simply rebooting the device requires some sort of manual clam freshening intervention every time, which is kind of unacceptable.

Tom

---

tewatson60 wrote:

Thx for the insight. My concern is whether simply rebooting the device requires some sort of manual clam freshening intervention every time, which is kind of unacceptable.

 

Tom

 

---

Yes I suspect so

B_L & dingjs1421 - Your thoughts would be appreciated?

Netgear advised me (through PM) they identified the problem and will fix it in the next firmware release. 

Tom

Hi scrjs ,

I found the root cause of the issue that tewatson60 reported. The hotfix 1 stopped working if you configure any system services (for example, enable/disable NFS), or update share settings. I am working with engineering team to have it fixed asap.

You can enable the SDM and send the port number to me via a private message. I can apply a temporary fix for you.

---

B_L wrote:

Hi scrjs ,

 

I found the root cause of the issue that tewatson60 reported. The hotfix 1 stopped working if you configure any system services (for example, enable/disable NFS), or update share settings. I am working with engineering team to have it fixed asap.

 

You can enable the SDM and send the port number to me via a private message. I can apply a temporary fix for you.

---

Thanks B_L 

Thats good news!  Shame Hotfix 1 wasn't the end of this story.

Thank you for your kind offer of a temp fix,

I don't reboot my ReadyNAS often nor make changes like enable/disable NFS, or update share settings so I am happy to simply re-start freshclam via 

root@xxxxxReadyNAS:~# systemctl start clamav-freshclam.service

manually in the interim till the hotfix 2 is available (I am guessing that is what your temp fix is doing).

Please keep us in the loop when you have an ETA...

---

tewatson60 wrote:

My concern is whether simply rebooting the device requires some sort of manual clam freshening intervention every time, which is kind of unacceptable.

 

---

rebooting will start the service the same way scrjs did, so I think not.  So one workaround is to just reboot the NAS when you see this (or maybe just reboot the NAS daily or weekly by putting it on a power schedule).

It is possible to change the service config to automatically restart on failure.  There's an example here: https://ma.ttias.be/auto-restart-crashed-service-systemd/ That change might not survive firmware updates or OS reinstalls, so you would need to check it occasionally and (if needed) reapply it.

@  B_L NETGEAR Moderator 

any news regarding the new fix? Although it is still running fine, I am very interested when this bug is fixed

rgds Hans

RN528X and RN212 with hotfix1 will not update AV file past Jan 25 2021 even with full reboot, while RN314 happily updates to latest AV version. Not interested in SSH solutions, this should just work, at least after a reboot. 

I sent you a PM, no reply yet.

After several reboots and switching AV on and off still not able to get AV Defs

running 6.10.4 Hotfix 1

ReadyNAS 526X

AV updates broken again, for over a week now. Really don't understand why this is still unresolved after so long. Is ANYONE at Netgear working on it?

Tom

Running 6.10.4 Hotfix 1

We released 6.10.5 Beta 1 today. This issue was fixed in Beta 1 release.

https://community.netgear.com/t5/Using-your-ReadyNAS-in-Business/Antivirus-scanner-definition-file-update-failed/m-p/2084996/emcs_t/S2h8ZW1haWx8dG9waWNfc3Vic2NyaXB0aW9ufEtOSklKUjlPWFRPVUtafDIwODQ5OTZ8U1VCU0NSSVBUSU9OU3xoSw#M191586

JohnCM_S& B_L 

rgds

So, who's defs are the most out-of-date? I think I might be a contender.