Lots of Virus detection after 6.6.1 Update

I think Weds. is ideal.  There's two days where development is available for early adopters, and you have some idea by the weekend on where the release stands.

For anyone run into the slowness issue after enabling AntiVirus in 6.6.1, here is a work-around before the beta or official firmware with the fix is available: 

1. Turn on SSH service through the Admin Page and SSH into ReadyNAS
2. Remove or comment out the lines starting with OnAccessExcludePath in file /etc/clamav/clamd.conf, save it.
3. Restart the clamav by running this command: systemctl restart clamav-daemon

Note that this clamd.conf configuration file will be overwritten again if re-enabling Anti-Virus, so above steps need to be re-done in that case. 

It was a hell of a FW version!

I hope the 6.7.0 would kill all the bugs!

This will be a quasi useless answer and I'll apologize up front for that but...

It's a Beta. There are always concerns with Beta releases. This is largely because the requisite testing is on going so there could be problems they simply don't know about yet. Beta testing is a more mature stage and accelerates the process because the user base can expand and randomize the parameters of the test by simply doing their normal thing. If your data is backed up and you can tolerate a loss of access to the main storage for a few hours of recovery then I'd say go for it. If you do not have backup copies of the contents of the NAS or have a user base that cannot tolerate a loss of access then don't do it.

I for one will not run the Beta. While I have several copies of the data it would cost my users and I dearly if they lost access to their files. It's a pain getting data in and out of my network environment. I can access all of my storage locations with out much trouble but providing every user with a similar path out of the local IPS would be a colossal pain. 

---

jtowntex wrote:

It's a Beta. There are always concerns with Beta releases.

---

That is certainly true, and many people do avoid them because they aren't fully tested.  Netgear always has some disclaimers in the beta release posts, and you should read them carefully.  

I agree that you need to weigh the risk of disruption to your users against the gains of the fixes and new features in the beta.

In this particular beta I haven't seen serious bugs reported, and since it does have AV fixes that many people want, I suspect a lot of folks are running it.  So it appears to be stable - "appears" being an important qualifier.  

Personally I usually do install them on a backup NAS, and (if that goes well) then put onto my other ReadyNAS.  I've begun that process, and have seen no issues so far.  But I haven't been running it very long.

Thank you.  Right now, with the AV off, it is working fine, so I will take your advice and wait for the FW release.

After the invervening updates some users have been able to re-enable it without much issue and with out a full OS upgrade. For my secondary NAS unit this has been true with out exception. For the main unit it has still been mildly buggy but nothing I couldn't deal with by simply rebooting before the rest of the staff comes in to work. I expect the difference between the two units is a function of user load. Very few people utilize the second unit and those that do usually open a single file at a time. Meanwhile the main unit sees roughly a dozen "users" reading and writing to and from several files each. Depending on where you are on this curve you may be fine to re-enable the AV now. 

None of this is particularly surprising since the core problem appears to be an issue with resource management where the AV simply takes up too much of the processing power and effectively crashes the system.

The glitch ofcourse is that you have to re-enable the AV first to update it. Also, the enable and disable function seems a bit buggy too. So if you need to disable again you might need to reboot and then immediately disable the AV. Elsewise, it might not actually disable. Then you still reboot again just to verify it is really off.

We have released an Anti-Virus hotfix last week, NAS units in the field running 6.6.1 should have already installed the hotfix, and the fix would be effective upon next reboot. If you haven't done a reboot since last week, you can manually reboot it therefore the antivirus hotfix will be applied properly. Thank you.

Switched on Anti-Virus again yesterday on my ReadyNAS 204, the message about the 30% is correct, the rest is odd:

Fri Feb 24 2017 8:07:11    
Volume: Less than 5% of volume media's capacity is free. Performance on volume media is degraded. To improve performance, you must add capacity.
Fri Feb 24 2017 8:00:10    
Volume: System volume root's usage is 85%. This condition should not occur in normal conditions. Contact technical support.
Fri Feb 24 2017 7:57:10    
Volume: Less than 30% of volume media's capacity is free. NETGEAR recommends that you add capacity to maintain current performance levels. Continuous protection snapshots will be deleted when volume free space is less than 5%.
Thu Feb 23 2017 19:57:33    
System: Antivirus scanner definition file was updated to 57.23116.
Thu Feb 23 2017 19:36:52    
System: ReadyNASOS background service started.

The "media" volume is for the external USB drive attached to the NAS, nothing to worry there, we'll not query external USB drive capacity for this report moving forward, to avoid the confusion. 

"Volume: Less than 5% of volume media's capacity is free. Performance on volume media is degraded. To improve performance, you must add capacity.
Fri Feb 24 2017 8:00:10"  

The system volume root can get full in rare cases. Can you SSH onto the box and run command "df -h" and post the output on your box? 
"Volume: System volume root's usage is 85%. This condition should not occur in normal conditions. Contact technical support.
Fri Feb 24 2017 7:57:10"

Just to provide some more feedback, I tried turning on the Anti-virus (AV) as I've had it switched off for the past month or so and the model 104 I've got is still difficult to manage and doing lots of disk activity with the AV on. The hotfix does not seem to have made much difference and the box is pretty hard to manage and use with AV on, so I've had to switch it off again. Like many here wish I had not updated to 6.6.1 so quickly!

Still, thanks for trying, every little data point adds to the knowledge base. As individuals these might be petty details but sometimes the sum of these details can be informative. I obviously cannot speak for Netgear but having a variety of competencies and a variety of environments tied to these experiences really helps pin down problems. 

Looking at it from a manufacturing point of view. If I had 2 users come back saying that their stack was a few nanometers too thick it wouldn't mean much but as I receive more feedback noting the same problem then it would be clear that one of my machines were out of calibration. Well two actually - the machine that made the error and the machine that failed to catch the error. blah blah blah

Another customer unhappy I've also turned virus checker off since update two days ago so many false virus alerts it's flooding my mail box.

For a issue that's been reported already I cannot believe this problem still exists.

For sure that issue is not handled very quickly!!

Thread created on 2017-01-18 04:26 PM today 2017-03-23 09:42 ZULU!!!!:(!

Any update?  When will this be fixed?  I'm stil getting constant false positives.