× NETGEAR will be terminating ReadyCLOUD service by July 1st, 2023. For more details click here.
Orbi WiFi 7 RBE973
Reply

Re: ReadyNASOS 6.10.6 Beta

dingjs1421
NETGEAR Expert

ReadyNASOS 6.10.6 Beta

• ARM

  • Supported devices: RN102 / RN104 / RN202 / RN204 / RN212 / RN214 / RN2120

• x86_64

  • Supported devices: RN312 / RN314 / RN316 / RN422 / RN424 / RN426 / RN516 / RN524X / RN526X / RN528X /  RN626X / RN628X / RN716X / RR2304 / RN3130 / RN3138 / RN3220 / RN4220 / RR3312 / RR4312X / RR4312S / RR4360X / RR4360S

 

To install: Click on appropriate link above for your system to download firmware image.
Then upload that image from the management UI's System->Settings->Update->Install Firmware section.

 

 

Enhancements

Antivirus ClamAV is upgraded to version 0.103.2+dfsg.

 

Bug Fixes

This firmware addresses the following bug:

Email alert fails when multiple contacts are added with certain email services


Warnings:

 

  • Unless you are advised by NETGEAR Support in a support case to update to beta software, NETGEAR Support may deny support if you are running beta software. You can seek help here on the NETGEAR Community for issues encountered on the beta.
  • Devices updated with 6.10.6 firmware should not be downgraded to firmware versions before 6.10.0.
  • ReadyNAS 102, 104, and 2120 systems must not be updated directly to 6.10.x from 6.3.x or older firmware. They must first be updated to either 6.2.5 or 6.3.5 then to 6.5.2 and then to 6.10.x.
  • ReadyNAS 202, 204, 212 and 212 systems must not be updated directly to 6.10.x from 6.3.x. They must first be updated to 6.3.5 then 6.5.2 and then to 6.10.x.
Message 1 of 24
HansRL
Apprentice

Re: ReadyNASOS 6.10.6 Beta

@ dingjs1421

 

Great to hear CLAMAV has been upgraded to a newer version, only a pitty it is not the latest version so the log still complaining CLAMAV is outdated.
Maybe this beta-firmware can get another update before it becomes general available so CLAMAV can be update from version 0.103.2 to recommended version: 0.103.3

 

rgds Hans

Message 2 of 24
dingjs1421
NETGEAR Expert

Re: ReadyNASOS 6.10.6 Beta

Hi Hans

 

Thank you for your attention on ClamAV upgrade on ReadyNAS. Basically we are following Debian's step to upgrade ClamAV, current version on Debain 10 is Clamav-0.103.2 too. Besides it's a challenage to upgrade from old 0.100 to 0.103 on ReadyNAS.

 

Message 3 of 24
Sandshark
Sensei

Re: ReadyNASOS 6.10.6 Beta

Does this also address the issue 6.10.5 Hotfix 1 fixed?  Still zero attention to the rsync backup job problem?

Message 4 of 24
StephenB
Guru

Re: ReadyNASOS 6.10.6 Beta


@Sandshark wrote:

Still zero attention to the rsync backup job problem?


Actually, @dingjs1421 posted something on this back in September: "please enable multiple file systems on rsync backup option, which will back up the whole data volume to destination."

 

This option is on the "advanced" tab of the backup job - not sure when it was added. I haven't gotten around to trying this yet (I don't normally use push backups)..

Message 5 of 24
HansRL
Apprentice

Re: ReadyNASOS 6.10.6 Beta

@dingjs1421,

 

just today I was checking my LOGS, especially 'Systemd-Journal.LOG', and I found a lot of following messages:
Oct 29 14:49:18 Geldrop clamonacc[29735]: ERROR: ClamFanotif: internal error (readlink() failed), 6, Bad file descriptor
Oct 29 14:49:18 Geldrop clamonacc[29735]: ClamWorker: fd already closed ... recovering ...
Oct 29 14:49:18 Geldrop clamonacc[29735]: ERROR: ClamFanotif: internal error (readlink() failed), 6, Bad file descriptor
Oct 29 14:49:18 Geldrop clamonacc[29735]: ClamWorker: fd already closed ... recovering ...
Oct 29 14:49:18 Geldrop clamonacc[29735]: ERROR: ClamFanotif: internal error (readlink() failed), 6, Bad file descriptor
Oct 29 14:49:18 Geldrop clamonacc[29735]: ClamWorker: fd already closed ... recovering ...
Oct 29 14:49:18 Geldrop clamonacc[29735]: ERROR: ClamFanotif: internal error (readlink() failed), 6, Bad file descriptor
Oct 29 14:49:18 Geldrop clamonacc[29735]: ClamWorker: fd already closed ... recovering ...
Oct 29 14:49:18 Geldrop clamonacc[29735]: ERROR: ClamFanotif: internal error (readlink() failed), 6, Bad file descriptor
Oct 29 14:49:18 Geldrop clamonacc[29735]: ClamWorker: fd already closed ... recovering ...
Oct 29 14:49:18 Geldrop clamonacc[29735]: ERROR: ClamFanotif: internal error (readlink() failed), 6, Bad file descriptor
Oct 29 14:49:18 Geldrop clamonacc[29735]: ClamWorker: fd already closed ... recovering ...
Oct 29 14:49:18 Geldrop clamonacc[29735]: ERROR: ClamFanotif: internal error (readlink() failed), 6, Bad file descriptor
Oct 29 14:49:18 Geldrop clamonacc[29735]: ClamWorker: fd already closed ... recovering ...
Oct 29 14:49:18 Geldrop clamonacc[29735]: ERROR: ClamFanotif: internal error (readlink() failed), 6, Bad file descriptor
Oct 29 14:49:18 Geldrop clamonacc[29735]: ClamWorker: fd already closed ... recovering ...
Oct 29 14:49:18 Geldrop clamonacc[29735]: ERROR: ClamFanotif: internal error (readlink() failed), 6, Bad file descriptor
Oct 29 14:49:18 Geldrop clamonacc[29735]: ClamWorker: fd already closed ... recovering ...
Oct 29 14:49:18 Geldrop clamonacc[29735]: ERROR: ClamFanotif: internal error (readlink() failed), 6, Bad file descriptor
Oct 29 14:49:18 Geldrop clamonacc[29735]: ClamWorker: fd already closed ... recovering ...

Although I am experiences no issues with my NAS, I thought it was worth to mentioned 🙂
So this has something to do with the new ClamAV-version.

 

Oeps almost forgotten...
when I download all the LOG-file at least the System.LOG and the Systemd-Journal.LOG has only entries from the time-stamp I requested the download.

 

regards Hans

 

Message 6 of 24
StephenB
Guru

Re: ReadyNASOS 6.10.6 Beta


@HansRL wrote:

 

Oeps almost forgotten...
when I download all the LOG-file at least the System.LOG and the Systemd-Journal.LOG has only entries from the time-stamp I requested the download.

 


Are those two logs flooded with the ClamAV errors?  If so, they might just be rotating very quickly.

Message 7 of 24
HansRL
Apprentice

Re: ReadyNASOS 6.10.6 Beta

@ Stephan,

 

For the Systemd-Journal.LOG should that be a plausible cause, but not for System.LOG because this file does not report the ClamAV errors.

 

created the download of all LOG-files at 10:49:51:
The first line in System.LOG (size:2841):
-- Logs begin at Sat 2021-10-30 10:08:18 CEST, end at Sat 2021-10-30 10:49:48 CEST. --
Oct 30 10:11:29 Geldrop dbus[1934]: [system] Activating service name='org.opensuse.Snapper' (using servicehelper)
Oct 30 10:11:29 Geldrop dbus[1934]: [system] Successfully activated service 'org.opensuse.Snapper'

 

The first lines in Systemd-Journal.LOG (size:535073):

-- Logs begin at Sat 2021-10-30 10:08:18 CEST, end at Sat 2021-10-30 10:49:48 CEST. --
Oct 30 10:47:47 Geldrop clamonacc[29735]: ClamWorker: fd already closed ... recovering ...
Oct 30 10:47:47 Geldrop clamonacc[29735]: ERROR: ClamFanotif: internal error (readlink() failed), 6, Bad file descriptor

Message 8 of 24
StephenB
Guru

Re: ReadyNASOS 6.10.6 Beta


@HansRL wrote:

 

For the Systemd-Journal.LOG should that be a plausible cause, but not for System.LOG because this file does not report the ClamAV errors.

 


Most of the logs are extracted from the systemd journal when you ask for the log zip (i.e., there is no system.log file in the OS partition).

 

So as the systemd journal rotates, the retention in the extracted logs is also affected.

Message 9 of 24
ChrisKing
Guide

Re: ReadyNASOS 6.10.6 Beta

I also just started getting with the ClamAV not updating, it started a few days ago, and it keeps complaining the ReadyNas is not connected to the internet, which it is and has been tested and confirmed. I have tried the usual things (switching off AV rebooting and then switching on again), in effect trying all sorts of things to no success. 

 

I could use this new Beta, but need to know if this will fix my Clam AV or make the problem worse? 

 

Chris

 

Model: RN214|4 BAY Desktop ReadyNAS Storage
Message 10 of 24
StephenB
Guru

Re: ReadyNASOS 6.10.6 Beta


@ChrisKing wrote:

 

I could use this new Beta, but need to know if this will fix my Clam AV or make the problem worse? 


I think the only way to tell is to try it.  

 

You can downgrade back to any 6.10.x release if it doesn't help.

Message 11 of 24
HansRL
Apprentice

Re: ReadyNASOS 6.10.6 Beta

@dingjs1421
@StephenB 

@ dingjs1421 & @ Stephan,

 

checked the log this morning and saw this in the Systemd-Journal.LOG:
Nov 01 10:16:40 Geldrop clamonacc[5223]: ERROR: ClamFanotif: internal error (readlink() failed), 7, Bad file descriptor
Nov 01 10:16:40 Geldrop clamonacc[5223]: ClamWorker: fd already closed ... recovering ...
Nov 01 10:16:40 Geldrop clamonacc[5223]: ERROR: ClamFanotif: internal error (readlink() failed), 7, Bad file descriptor
Nov 01 10:16:40 Geldrop clamonacc[5223]: ClamWorker: fd already closed ... recovering ...
Nov 01 10:17:01 Geldrop CRON[18245]: pam_unix(cron:session): session opened for user root by (uid=0)
Nov 01 10:17:01 Geldrop CRON[18246]: (root) CMD ( cd / && run-parts --report /etc/cron.hourly)
Nov 01 10:17:02 Geldrop CRON[18245]: pam_unix(cron:session): session closed for user root
Nov 01 10:18:07 Geldrop systemd[1]: clamav-daemon.service: State 'stop-sigterm' timed out. Killing.
Nov 01 10:18:07 Geldrop systemd[1]: clamav-daemon.service: Main process exited, code=killed, status=9/KILL
Nov 01 10:18:07 Geldrop systemd[1]: Stopped Clam AntiVirus userspace daemon.
Nov 01 10:18:07 Geldrop systemd[1]: clamav-daemon.service: Unit entered failed state.
Nov 01 10:18:07 Geldrop systemd[1]: clamav-daemon.service: Failed with result 'signal'.
Nov 01 10:18:08 Geldrop systemd[1]: Started Clam AntiVirus userspace daemon.
Nov 01 10:18:08 Geldrop systemd[1]: Starting ClamAV On-Access Scanner...
Nov 01 10:18:08 Geldrop clamd[18249]: Received 0 file descriptor(s) from systemd.
Nov 01 10:18:08 Geldrop clamd[18249]: clamd daemon 0.103.2 (OS: linux-gnueabi, ARCH: arm, CPU: arm)
Nov 01 10:18:08 Geldrop clamd[18249]: Log file size limited to 1048576 bytes.
Nov 01 10:18:08 Geldrop clamd[18249]: Reading databases from /var/lib/clamav
Nov 01 10:18:08 Geldrop clamd[18249]: Not loading PUA signatures.
Nov 01 10:18:08 Geldrop clamd[18249]: Only loading official signatures.
Nov 01 10:18:08 Geldrop clamd[18249]: Bytecode: Security mode set to "TrustSigned".
Nov 01 10:19:08 Geldrop clamd[18249]: Loaded 8573202 signatures.
Nov 01 10:19:19 Geldrop clamd[18249]: LOCAL: Unix socket file /var/run/clamav/clamd.ctl
Nov 01 10:19:19 Geldrop clamd[18249]: LOCAL: Setting connection queue length to 30
Nov 01 10:19:19 Geldrop clamd[18249]: Limits: Global time limit set to 120000 milliseconds.
Nov 01 10:19:19 Geldrop clamd[18249]: Limits: Global size limit set to 104857600 bytes.
Nov 01 10:19:19 Geldrop clamd[18249]: Limits: File size limit set to 52428800 bytes.
Nov 01 10:19:19 Geldrop clamd[18249]: Limits: Recursion level limit set to 16.
Nov 01 10:19:19 Geldrop clamd[18249]: Limits: Files limit set to 10000.
Nov 01 10:19:19 Geldrop clamd[18249]: Limits: MaxEmbeddedPE limit set to 10485760 bytes.
Nov 01 10:19:19 Geldrop clamd[18249]: Limits: MaxHTMLNormalize limit set to 10485760 bytes.
Nov 01 10:19:19 Geldrop clamd[18249]: Limits: MaxHTMLNoTags limit set to 2097152 bytes.
Nov 01 10:19:19 Geldrop clamd[18249]: Limits: MaxScriptNormalize limit set to 5242880 bytes.
Nov 01 10:19:19 Geldrop clamd[18249]: Limits: MaxZipTypeRcg limit set to 1048576 bytes.
Nov 01 10:19:19 Geldrop clamd[18249]: Limits: MaxPartitions limit set to 50.
Nov 01 10:19:19 Geldrop clamd[18249]: Limits: MaxIconsPE limit set to 100.
Nov 01 10:19:19 Geldrop clamd[18249]: Limits: MaxRecHWP3 limit set to 16.
Nov 01 10:19:19 Geldrop clamd[18249]: Limits: PCREMatchLimit limit set to 100000.
Nov 01 10:19:19 Geldrop clamd[18249]: Limits: PCRERecMatchLimit limit set to 2000.
Nov 01 10:19:19 Geldrop clamd[18249]: Limits: PCREMaxFileSize limit set to 26214400.
Nov 01 10:19:19 Geldrop clamd[18249]: Archive support enabled.
Nov 01 10:19:19 Geldrop clamd[18249]: AlertExceedsMax heuristic detection disabled.
Nov 01 10:19:19 Geldrop clamd[18249]: Heuristic alerts enabled.
Nov 01 10:19:19 Geldrop clamd[18249]: Portable Executable support enabled.
Nov 01 10:19:19 Geldrop clamd[18249]: ELF support enabled.
Nov 01 10:19:19 Geldrop clamd[18249]: Alerting on broken executables enabled.
Nov 01 10:19:19 Geldrop clamd[18249]: Mail files support enabled.
Nov 01 10:19:19 Geldrop clamd[18249]: OLE2 support enabled.
Nov 01 10:19:19 Geldrop clamd[18249]: PDF support enabled.
Nov 01 10:19:19 Geldrop clamd[18249]: SWF support enabled.
Nov 01 10:19:19 Geldrop clamd[18249]: HTML support enabled.
Nov 01 10:19:19 Geldrop clamd[18249]: XMLDOCS support enabled.
Nov 01 10:19:19 Geldrop clamd[18249]: HWP3 support enabled.
Nov 01 10:19:19 Geldrop clamd[18249]: Self checking every 600 seconds.
Nov 01 10:19:19 Geldrop clamd[18249]: Limits: Global time limit set to 120000 milliseconds.
Nov 01 10:19:19 Geldrop clamd[18249]: Limits: Global size limit set to 104857600 bytes.
Nov 01 10:19:19 Geldrop clamd[18249]: Limits: File size limit set to 52428800 bytes.
Nov 01 10:19:19 Geldrop clamd[18249]: Limits: Recursion level limit set to 16.
Nov 01 10:19:19 Geldrop clamd[18249]: Limits: Files limit set to 10000.
Nov 01 10:19:19 Geldrop clamd[18249]: Limits: MaxEmbeddedPE limit set to 10485760 bytes.
Nov 01 10:19:19 Geldrop clamd[18249]: Limits: MaxHTMLNormalize limit set to 10485760 bytes.
Nov 01 10:19:19 Geldrop clamd[18249]: Limits: MaxHTMLNoTags limit set to 2097152 bytes.
Nov 01 10:19:19 Geldrop clamd[18249]: Limits: MaxScriptNormalize limit set to 5242880 bytes.
Nov 01 10:19:19 Geldrop clamd[18249]: Limits: MaxZipTypeRcg limit set to 1048576 bytes.
Nov 01 10:19:19 Geldrop clamd[18249]: Limits: MaxPartitions limit set to 50.
Nov 01 10:19:19 Geldrop clamd[18249]: Limits: MaxIconsPE limit set to 100.
Nov 01 10:19:19 Geldrop clamd[18249]: Limits: MaxRecHWP3 limit set to 16.
Nov 01 10:19:19 Geldrop clamd[18249]: Limits: PCREMatchLimit limit set to 100000.
Nov 01 10:19:19 Geldrop systemd[1]: Started ClamAV On-Access Scanner.
Nov 01 10:19:19 Geldrop clamd[18249]: Limits: PCRERecMatchLimit limit set to 2000.
Nov 01 10:19:19 Geldrop clamd[18249]: Limits: PCREMaxFileSize limit set to 26214400.
Nov 01 10:19:19 Geldrop clamd[18249]: Archive support enabled.
Nov 01 10:19:19 Geldrop clamd[18249]: AlertExceedsMax heuristic detection disabled.
Nov 01 10:19:19 Geldrop clamd[18249]: Heuristic alerts enabled.
Nov 01 10:19:19 Geldrop clamd[18249]: Portable Executable support enabled.
Nov 01 10:19:19 Geldrop clamd[18249]: ELF support enabled.
Nov 01 10:19:19 Geldrop clamd[18249]: Alerting on broken executables enabled.
Nov 01 10:19:19 Geldrop clamd[18249]: Mail files support enabled.
Nov 01 10:19:19 Geldrop clamd[18249]: OLE2 support enabled.
Nov 01 10:19:19 Geldrop clamd[18249]: PDF support enabled.
Nov 01 10:19:19 Geldrop clamd[18249]: SWF support enabled.
Nov 01 10:19:19 Geldrop clamd[18249]: HTML support enabled.
Nov 01 10:19:19 Geldrop clamd[18249]: XMLDOCS support enabled.
Nov 01 10:19:19 Geldrop clamd[18249]: HWP3 support enabled.
Nov 01 10:19:19 Geldrop clamd[18249]: Self checking every 600 seconds.
Nov 01 10:20:43 Geldrop connmand[2047]: ntp: adjust (slew): -0.000093 sec
Nov 01 10:29:23 Geldrop clamd[18249]: SelfCheck: Database status OK.
Nov 01 10:29:23 Geldrop clamd[18249]: SelfCheck: Database status OK.
Nov 01 10:37:47 Geldrop connmand[2047]: ntp: adjust (slew): -0.000684 sec
Nov 01 10:39:41 Geldrop clamd[18249]: SelfCheck: Database status OK.
Nov 01 10:39:41 Geldrop clamd[18249]: SelfCheck: Database status OK.
Nov 01 10:49:58 Geldrop clamd[18249]: SelfCheck: Database status OK.
Nov 01 10:49:58 Geldrop clamd[18249]: SelfCheck: Database status OK.
Nov 01 10:55:04 Geldrop connmand[2047]: ntp: adjust (slew): -0.001147 sec
Nov 01 10:57:09 Geldrop dbus[1904]: [system] Activating service name='org.opensuse.Snapper' (using servicehelper)
Nov 01 10:57:09 Geldrop dbus[1904]: [system] Successfully activated service 'org.opensuse.Snapper'
Nov 01 10:59:59 Geldrop clamd[18249]: SelfCheck: Database status OK.
Nov 01 10:59:59 Geldrop clamd[18249]: SelfCheck: Database status OK.
Nov 01 11:10:00 Geldrop clamd[18249]: SelfCheck: Database status OK.
Nov 01 11:10:00 Geldrop clamd[18249]: SelfCheck: Database status OK.
Nov 01 11:12:08 Geldrop connmand[2047]: ntp: adjust (slew): -0.016510 sec
Nov 01 11:16:17 Geldrop systemd-journald[982]: Suppressed 225225 messages from /system.slice/clamav-clamonacc.service
Nov 01 11:16:17 Geldrop clamonacc[18330]: *** buffer overflow detected ***: /usr/sbin/clamonacc terminated
Nov 01 11:16:17 Geldrop systemd[1]: clamav-clamonacc.service: Main process exited, code=killed, status=6/ABRT
Nov 01 11:16:17 Geldrop systemd[1]: clamav-clamonacc.service: Unit entered failed state.
Nov 01 11:16:17 Geldrop systemd[1]: clamav-clamonacc.service: Failed with result 'signal'.
Nov 01 11:16:17 Geldrop systemd[1]: clamav-clamonacc.service: Service hold-off time over, scheduling restart.
Nov 01 11:16:17 Geldrop systemd[1]: systemd-journald-audit.socket: Cannot add dependency job, ignoring: Unit systemd-journald-audit.socket is masked.
Nov 01 11:16:17 Geldrop systemd[1]: Stopped ClamAV On-Access Scanner.
Nov 01 11:16:17 Geldrop systemd[1]: Starting ClamAV On-Access Scanner...
Nov 01 11:16:17 Geldrop systemd[1]: Started ClamAV On-Access Scanner.
Nov 01 11:16:55 Geldrop clamonacc[18880]: ScanOnAccess: Internal error (close(6) failed)
Nov 01 11:16:55 Geldrop systemd[1]: clamav-clamonacc.service: Service hold-off time over, scheduling restart.
Nov 01 11:16:55 Geldrop systemd[1]: systemd-journald-audit.socket: Cannot add dependency job, ignoring: Unit systemd-journald-audit.socket is masked.
Nov 01 11:16:55 Geldrop systemd[1]: Stopped ClamAV On-Access Scanner.
Nov 01 11:16:55 Geldrop systemd[1]: Starting ClamAV On-Access Scanner...
Nov 01 11:16:55 Geldrop systemd[1]: Started ClamAV On-Access Scanner.
Nov 01 11:17:01 Geldrop CRON[18904]: pam_unix(cron:session): session opened for user root by (uid=0)
Nov 01 11:17:01 Geldrop CRON[18905]: (root) CMD ( cd / && run-parts --report /etc/cron.hourly)
Nov 01 11:17:01 Geldrop CRON[18904]: pam_unix(cron:session): session closed for user root
Nov 01 11:20:04 Geldrop clamd[18249]: SelfCheck: Database status OK.
Nov 01 11:20:04 Geldrop clamd[18249]: SelfCheck: Database status OK.

hope this will help to determine what goes wrong.

Message 12 of 24
StephenB
Guru

Re: ReadyNASOS 6.10.6 Beta


@HansRL wrote:

@ dingjs1421 & Stephan,

 

checked the log this morning and saw this in the Systemd-Journal.LOG:

What NAS model are you seeing this on?

 

@dingjs1421 :  repeating the tag, as it looks misformatted in the previous post.

Message 13 of 24
HansRL
Apprentice

Re: ReadyNASOS 6.10.6 Beta

Readynas RN212

Message 14 of 24
ChrisKing
Guide

Re: ReadyNASOS 6.10.6 Beta

Thanks StephenB

 

I have updated to that version, and will respond back here in this thread if the issue persists etc. 

 

Chris

Model: RN214|4 BAY Desktop ReadyNAS Storage
Message 15 of 24
ChrisKing
Guide

Re: ReadyNASOS 6.10.6 Beta

Thanks Stephen B

 

Updated to the new RC and if finally updated to reflect AV for 01/11/2021, will monitor to ensure it updates ok on the next day

 

Its a shame the interface (web) doesnt allow a simple AV update file and ClamAV dont allow the latest definition to be downloaded from their site manually, so that way it can be manually updated in case of issues like this. 

 

Chris

 

Model: RN214|4 BAY Desktop ReadyNAS Storage
Message 16 of 24
dingjs1421
NETGEAR Expert

Re: ReadyNASOS 6.10.6 Beta

ClamAV blocks the old version(0.100.2) from downloading virus database,  ClamAV is upgraded from 0.100.2 to 0.103.2 on the comming 6.10.6. It's confirmed ClamAV 0.103.2 succeeds to download virus database from ClamAV download center.

Message 17 of 24
TerryJColes
Luminary

Re: ReadyNASOS 6.10.6 Beta


@dingjs1421 wrote:

ClamAV blocks the old version(0.100.2) from downloading virus database,  ClamAV is upgraded from 0.100.2 to 0.103.2 on the comming 6.10.6. It's confirmed ClamAV 0.103.2 succeeds to download virus database from ClamAV download center.


Is there any prediction on when this Beta will become the official release?  I have the dreaded 'failed due to download failure' error every day, but can lve with it if the official release is reasonably imminent. 

Message 18 of 24
BVUser
Aspirant

Re: ReadyNASOS 6.10.6 Beta

I too am having the dreaded "antivirus scanner definition file failed due to download failure check your internet connection" error. (My internet connection is fine.) I am running 6.10.5 Hotfix 1. I don't like to run Beta software and can wait a bit for this to go live but it would be very helpful if we could get an update when the fix for this error will be pushed to a live (non-beta) update. Any chance of getting information on that?

 

Thanks.

Model: RN3138|ReadyNAS 3138 Series 4- Bay (Diskless)
Message 19 of 24
kohdee
NETGEAR Expert

Re: ReadyNASOS 6.10.6 Beta

Good thing we released 6.10.6 officially 🙂

https://www.netgear.com/support/product/ReadyNAS_OS_6.aspx

 

Message 20 of 24
HansRL
Apprentice

Re: ReadyNASOS 6.10.6 Beta

Still receiving some issues with the new CLAMAV version:

Nov 05 11:35:22 Geldrop clamonacc[3598]: *** buffer overflow detected ***: /usr/sbin/clamonacc terminated
Nov 05 11:35:23 Geldrop systemd[1]: clamav-clamonacc.service: Main process exited, code=killed, status=6/ABRT
Nov 05 11:35:23 Geldrop systemd[1]: clamav-clamonacc.service: Unit entered failed state.
Nov 05 11:35:23 Geldrop systemd[1]: clamav-clamonacc.service: Failed with result 'signal'.
Nov 05 11:35:23 Geldrop systemd[1]: clamav-clamonacc.service: Service hold-off time over, scheduling restart.
Nov 05 11:35:23 Geldrop systemd[1]: systemd-journald-audit.socket: Cannot add dependency job, ignoring: Unit systemd-journald-audit.socket is masked.
Nov 05 11:35:23 Geldrop systemd[1]: Stopped ClamAV On-Access Scanner.
Nov 05 11:35:23 Geldrop systemd[1]: Starting ClamAV On-Access Scanner...
Nov 05 11:35:23 Geldrop systemd[1]: Started ClamAV On-Access Scanner.

Message 21 of 24
HansRL
Apprentice

Re: ReadyNASOS 6.10.6 Beta

@dingjs1421 @Dingjs1421,

 

any new regarding a solution for my issues with CLAMAV? still getting:

Nov 08 12:16:43 Geldrop clamonacc[14918]: ClamWorker: fd already closed ... recovering ...
Nov 08 12:16:43 Geldrop clamonacc[14918]: ERROR: ClamFanotif: internal error (readlink() failed), 7, Bad file descriptor

or
Nov 08 12:18:09 Geldrop systemd[1]: clamav-daemon.service: State 'stop-sigterm' timed out. Killing.
Nov 08 12:18:09 Geldrop systemd[1]: clamav-daemon.service: Main process exited, code=killed, status=9/KILL
Nov 08 12:18:09 Geldrop systemd[1]: Stopped Clam AntiVirus userspace daemon.
Nov 08 12:18:09 Geldrop systemd[1]: clamav-daemon.service: Unit entered failed state.
Nov 08 12:18:09 Geldrop systemd[1]: clamav-daemon.service: Failed with result 'signal'.
Nov 08 12:18:10 Geldrop systemd[1]: Started Clam AntiVirus userspace daemon.
Nov 08 12:18:10 Geldrop systemd[1]: Starting ClamAV On-Access Scanner...
Nov 08 12:18:10 Geldrop clamd[16404]: Received 0 file descriptor(s) from systemd.

Message 22 of 24
John245
Tutor

Re: ReadyNASOS 6.10.6 Beta

@kohdee 

I'm on 6.10.5 hotfix 1 and if I check for updates it will indicate that I'm on the latest version

Model: RN2120v2|Readynas 2120v2 1U 4-Bay Diskless
Message 23 of 24
StephenB
Guru

Re: ReadyNASOS 6.10.6 Beta


@John245 wrote:

I'm on 6.10.5 hotfix 1 and if I check for updates it will indicate that I'm on the latest version


6.10.6 is released - so you shouldn't install the beta/release candidate. Also, if you did install the beta, then you should update it to the production version.

 

Netgear always releases their ReadyNAS firmware updates for manual installation first.  Then they add it to their upgrade servers after a week or so.  So "check for updates" won't show it for a while after release. 

 

If you are in a hurry to get the AV fix installed, then I recommend going ahead with the manual install now.  Otherwise, it's fine to wait until you see it show up in "check for updates". You can manually install it from here: https://kb.netgear.com/000064345/ReadyNAS-OS-6-Software-Version-6-10-6

 

 

Message 24 of 24
Discussion stats
  • 23 replies
  • 6744 views
  • 1 kudo
  • 9 in conversation
Announcements