Readynas 104 - Very slow, almost unusable

rn_enthusiast
Virtuoso
Mar 30, 2021
Hi Richard-P

Thanks for the logs.

Your unit is running into an "out of memory" condition over and over, every 10-20 mins. This is obviously a problem. The odd thing is, that this seems related to clam-av (the antivirus service), which was disabled on the RN100 series a while back.
Mar 28 12:50:34 ReadyNAS kernel: Out of memory: Kill process 4975 (clamd) score 1411 or sacrifice child Mar 28 12:50:34 ReadyNAS kernel: Killed process 4975 (clamd) total-vm:691048kB, anon-rss:210748kB, file-rss:436kB Mar 28 13:07:08 ReadyNAS kernel: enclosure_monit invoked oom-killer: gfp_mask=0x24201ca, order=0, oom_score_adj=-1000 Mar 28 13:07:09 ReadyNAS kernel: enclosure_monit cpuset=/ mems_allowed=0 Mar 28 13:07:09 ReadyNAS kernel: CPU: 0 PID: 2524 Comm: enclosure_monit Tainted: P O 4.4.190.armada.1 #1 Mar 28 13:07:09 ReadyNAS kernel: Hardware name: Marvell Armada 370/XP (Device Tree) Mar 28 13:07:09 ReadyNAS kernel: [<c0015270>] (unwind_backtrace) from [<c001173c>] (show_stack+0x10/0x18) Mar 28 13:07:09 ReadyNAS kernel: [<c001173c>] (show_stack) from [<c03849d0>] (dump_stack+0x78/0x9c) Mar 28 13:07:09 ReadyNAS kernel: [<c03849d0>] (dump_stack) from [<c00d5e20>] (dump_header+0x4c/0x1b4) Mar 28 13:07:09 ReadyNAS kernel: [<c00d5e20>] (dump_header) from [<c00a09a0>] (oom_kill_process+0xd0/0x45c) Mar 28 13:07:09 ReadyNAS kernel: [<c00a09a0>] (oom_kill_process) from [<c00a10b0>] (out_of_memory+0x310/0x374) Mar 28 13:07:09 ReadyNAS kernel: [<c00a10b0>] (out_of_memory) from [<c00a49d4>] (__alloc_pages_nodemask+0x6e0/0x7dc) Mar 28 13:07:09 ReadyNAS kernel: [<c00a49d4>] (__alloc_pages_nodemask) from [<c009faa4>] (filemap_fault+0x344/0x464) Mar 28 13:07:09 ReadyNAS kernel: [<c009faa4>] (filemap_fault) from [<c01548a0>] (ext4_filemap_fault+0x2c/0x44) Mar 28 13:07:09 ReadyNAS kernel: [<c01548a0>] (ext4_filemap_fault) from [<c00ba4c4>] (__do_fault+0x60/0xdc) Mar 28 13:07:09 ReadyNAS kernel: [<c00ba4c4>] (__do_fault) from [<c00bd1a0>] (handle_mm_fault+0x4e0/0xc04) Mar 28 13:07:09 ReadyNAS kernel: [<c00bd1a0>] (handle_mm_fault) from [<c0017cb8>] (do_page_fault+0x134/0x2b0) Mar 28 13:07:09 ReadyNAS kernel: [<c0017cb8>] (do_page_fault) from [<c0009368>] (do_PrefetchAbort+0x34/0x9c) Mar 28 13:07:09 ReadyNAS kernel: [<c0009368>] (do_PrefetchAbort) from [<c00125dc>] (ret_from_exception+0x0/0x24) Mar 28 13:07:09 ReadyNAS kernel: Exception stack(0xdb277fb0 to 0xdb277ff8)

This service shouldn't even appear in the processes list, but it does.
S root 3471 1 3471 0 1 80 0 8 2601 pipe_w 04:17 ? 00:00:14 /usr/bin/freshclam --quiet D root 3477 3471 3477 2 1 80 0 64756 175427 wait_o 04:18 ? 00:08:42 /usr/bin/freshclam --quiet R root 8502 1 8502 14 1 98 18 230996 158682 - 11:16 ? 00:02:26 /usr/sbin/clamd --foreground=true --config-file=/etc/clamav/clamd.conf
It is enabled on your NAS, in the default services list:
ANTIVIRUS=1 ANTIVIRUS_SCHE_SCAN=0

Something is amiss with this. I don't get how the clam daemon is running at this point, unless you started it yourself? Do you use SSH and command line (CLI) on this NAS? You are on 6.10.4 and have been updating regularly:
[2019/07/13 15:10:30 UTC] Updated from ReadyNASOS 6.10.0 (ReadyNASOS) to 6.10.1 (ReadyNASOS). [2020/03/07 09:06:53 UTC] Updated from ReadyNASOS 6.10.1 (ReadyNASOS) to 6.10.2 (ReadyNASOS). [2020/03/18 08:02:56 UTC] Updated from ReadyNASOS 6.10.2 (ReadyNASOS) to 6.10.3 (ReadyNASOS). [2020/12/19 09:37:52 UTC] Updated from ReadyNASOS 6.10.3 (ReadyNASOS) to 6.10.4 (ReadyNASOS). [2021/01/03 14:22:58 UTC] Updated from ReadyNASOS 6.10.4 (ReadyNASOS) to 6.10.4 (ReadyNASOS). [2021/03/27 09:26:47 UTC] Updated from ReadyNASOS 6.10.4 (ReadyNASOS) to 6.10.4 (ReadyNASOS).
Netgear disabled the AV service on the RN100 series NAS, due to resource and performance issues and I think that happened around 6.10.0. So... how your AV service is running, I don't know :) But that is your performance problem right there. You need to disable that AV service. You can do it from the CLI:
systemctl stop clamav-daemon
Check it is stopped:
systemctl status clamav-daemon
You also need to turn it off in the /etc/default/services file (set it to "0"), so that it will not start again upon next NAS reboot.

Do you know how to access the NAS CLI over SSH, in order to fix this?

Cheers
- Richard-P
  Aspirant
  Mar 30, 2021
  Hi rn Enthusiast,
  
  Thanks SO much for all this. I really appreciate your time and advice.
  
  I have no idea why the anti virus would still be running if it should have been disabled. I definitely haven't enabled it (not on purpose anyway).
  I've had a look around on the admin page and can't see where/how I disable it. How on earth do I do it? :-)
  
  Thanks again, you're a star!
  
  Kind regards,
  RIchard
  - rn_enthusiast
    Virtuoso
    Mar 30, 2021
    Hi again,
    
    Yes, you won't find the AV option in the GUI because they removed that, which is why it is super strange that you have the service running on the NAS in the first place :)
    
    Anyhow, the ReadyNAS is built on a Linux backend, so it is "just" a Linux computer essentially. In order to fix this AV problem, we need to use SSH to get to the Linux command line (CLI) of the NAS. From here, we can run then a few commands.
    
    To get to the CLI, first you need to enable that Service. Go to the Web Admin Page: System > Settings > Services > Click on SSH. Here you want to enable SSH and Enable password authentication. So, tick both boxes and hit Apply.
    
    You can thereafter use the command prompt in Windows, to access the NAS over SSH. Very easy. Click on the start menu and search for "cmd". Once you find the command prompt application, open it and you will see a black box.
    
    Here you type:
    
    ssh root@192.168.1.1
    NOTE: You need to substitute the IP address above (192.168.1.1) with the actual IP of your NAS. You can find the IP by accessing the admin web page and look at the address bar in the browser. It will show the IP address of your NAS.
    
    Hit Enter and you will be asked "Are you sure you want to continue connecting". Type yes and hit Enter.
    Now, you will be prompted for the NAS password. It is the same password as you use for the admin web page.
    
    Once you enter you password (and hit Enter), you are in.
    
    Now, you can type commands into the CLI. Please do these two commands for me, in order:
    
    systemctl stop clamav-daemon systemctl status clamav-daemon
    
    Show me the output of the last command, please. This will confirm if the service is stopped. You can copy paste output from the command prompt window by using your mouse to Highlight text (as normal) and then hit Enter, which will copy that text into your clipboard.
    
    Just paste the output of the last command for me, please. It SHOULD look something like mine here:
    
    root@Databak:~# systemctl status clamav-daemon ● clamav-daemon.service - Clam AntiVirus userspace daemon Loaded: loaded (/lib/systemd/system/clamav-daemon.service; disabled; vendor preset: disabled) Active: inactive (dead)
    
    Cheers!
- mdgm
  Virtuoso
  Apr 22, 2021
  rn_enthusiast wrote:
  But that is your performance problem right there. You need to disable that AV service. You can do it from the CLI:
  systemctl stop clamav-daemon
  That command only stops the instance for the current boot
  rn_enthusiast wrote:
  You also need to turn it off in the /etc/default/services file (set it to "0"), so that it will not start again upon next NAS reboot.
  That file might be used for the status in the GUI or other things in the backend but to disable it from starting automatically on boot you actually need to use another systemctl command
  systemctl disable clamav-daemon
  Or if you know where the symlink is stored (or are doing it from tech support mode where you don't have easy access to use systemctl commands) you can remove the symlink using rm (does pretty much the same thing as the disable command above without requiring systemd to be running). I think this should do the trick:
  rm /etc/systemd/system/multi-user.target.wants/clamav-daemon.service
  NETGEAR really should put something in the firmware upgrade script for ARM devices to do some of these things if they don't already.
  
  If there are any other clam services running you probably want to disable those as well.
  
  You definitely should change the /etc/default/services file so that hopefully the system doesn't think it needs to re-enable anti-virus (not sure if it would do that). If the services file reverts back to the old anti-virus setting it could be because the setting is stored in the management service database and the system has "repaired" the config.
  
  StephenB wrote:
  You could also just uninstall clamav, instead of disabling it.
  That shouldn't be necessary
  - StephenB
    Guru - Experienced User
    Apr 22, 2021
    mdgm wrote:
    StephenB wrote:
    
    You could also just uninstall clamav, instead of disabling it.
    
    That shouldn't be necessary
    
    Might be easier, and it should have been uninstalled when the firmware was upgraded (it is not installed on my RN102).

Forum Discussion

Readynas 104 - Very slow, almost unusable

Related Content

R7000P 5Ghz Unusable

render wlan unusable

MR80: Satellites become unusable after time while main router is fine?

ReadyCLOUD mac desktop app still unusable

OS 6.4.1 slow ... to the point of unusable

NETGEAR Academy

ProSupport for Business