Forum Discussion

Aspirant

Jan 13, 2017

Solved

sabnzbd causes high system load

Hi all, Is it normal that sabnzbd drives the sysload up to 143? (as reported in the top right corner of the web interface) I see three recently finished downloads (with "busy" spinners) in t...

Performance

twc
Jan 23, 2017
I think the NAS runs fine until sabnzbd begins repairing one of the downloads. So, I'll switch that function off (per the last post here). And then hopefully I'll be able to see which downloads need intervention, and run those repairs manually from my Mac.

However, now sabnzbd isn't able to start up. Are you able to take a look please?

twc

Aspirant

Jan 13, 2017

Will do thanks

twc

Aspirant

Jan 13, 2017

Does TOP give any clues?

Tasks: 413 total,   5 running, 408 sleeping,   0 stopped,   0 zombie
%Cpu(s): 59.1 us, 28.5 sy,  0.0 ni,  0.0 id,  0.0 wa,  0.0 hi, 12.3 si,  0.0 st
KiB Mem:    508720 total,   391488 used,   117232 free,      428 buffers
KiB Swap:  1047420 total,   326248 used,   721172 free.    21276 cached Mem

  PID USER      PR  NI    VIRT    RES    SHR S %CPU %MEM     TIME+ COMMAND                        
 2756 admin     20   0  644432  80764   3144 S 33.0 15.9 305:14.18 sabnzbd                        
 2669 root      20   0  246188  10628   1284 S 32.7  2.1   1329:56 lite_mv                        
22335 admin     20   0   22164  17852    276 R 13.5  3.5 191:38.58 par2                           
  404 root      20   0       0      0      0 S 10.7  0.0  92:22.97 kswapd0                        
 1095 root      20   0       0      0      0 S  3.9  0.0 146:20.98 md127_raid5                    
13338 tony      20   0    5784   1768   1160 R  2.5  0.3   0:00.52 top                            
10203 root      20   0       0      0      0 S  1.9  0.0   0:18.38 kworker/u2:4                   
    3 root      20   0       0      0      0 R  1.1  0.0 119:16.63 ksoftirqd/0                    
 9821 root      20   0       0      0      0 S  0.8  0.0   0:19.37 kworker/u2:0                   
  981 root       0 -20       0      0      0 S  0.3  0.0  15:20.16 kworker/0:1H                   
 2376 root      20   0   23596   1308   1112 S  0.3  0.3   2:56.19 minidlnad                      
 7837 root      39  19   10404    916    844 D  0.3  0.2   0:00.84 archive_mrg_mv                 
12502 root      20   0       0      0      0 S  0.3  0.0   0:02.41 kworker/u2:5                   
29327 root      39  19   10404    892    820 D  0.3  0.2   0:03.34 archive_mrg_mv                 
31729 root      39  19   10404   1032    960 D  0.3  0.2   0:02.94 archive_mrg_mv                 
    1 root      20   0   26648    536    292 S  0.0  0.1   0:27.05 systemd                        
    2 root      20   0       0      0      0 S  0.0  0.0   0:00.19 kthreadd                       
    5 root       0 -20       0      0      0 S  0.0  0.0   0:00.00 kworker/0:0H                   
    7 root      20   0       0      0      0 R  0.0  0.0   4:59.89 rcu_sched                      
    8 root      20   0       0      0      0 S  0.0  0.0   0:00.00 rcu_bh                         
    9 root      rt   0       0      0      0 S  0.0  0.0   0:00.00 migration/0                    
   10 root      rt   0       0      0      0 S  0.0  0.0   0:02.60 watchdog/0                     
   11 root       0 -20       0      0      0 S  0.0  0.0   0:00.00 khelper                        
   12 root      20   0       0      0      0 S  0.0  0.0   0:00.00 kdevtmpfs                      
   13 root       0 -20       0      0      0 S  0.0  0.0   0:00.00 netns                          
  273 root      20   0       0      0      0 S  0.0  0.0   0:00.17 khungtaskd                     
  274 root       0 -20       0      0      0 S  0.0  0.0   0:00.00 writeback                      
  276 root       0 -20       0      0      0 S  0.0  0.0   0:00.00 crypto                         
  277 root       0 -20       0      0      0 S  0.0  0.0   0:00.00 bioset

I've also noticed about 200 processes like this:

/apps/surveillance/bin/archive_mrg_mv autobackup

FramerV
NETGEAR Employee Retired
Jan 15, 2017
Hi twc,

Where you able to get in touch with sabnzbd if this is normal for their app? I could have you case be checked but I need to now if the app is working as it should be.

Regards,
- twc
  Aspirant
  Jan 15, 2017
  Hi Framer, this is what we're up to over on the SAB forum:
  
  Repairing takes a lot of CPU power. That is what you experience. ...
  Your ReadyNAS 10400 is a low-spec machine, so you'll never get the same speed as on a
  PC with an Intel Core CPU. ... Your sysload values are so insanely high and your top
  output does not match that, that 1) something else must be going on (like disk IO problems)
  or 2) there is a bug in your OS / Python / SABnzbd reporting
  Are you able to help diagnose?
  
  Is he talking about par2? Is there a known issue with that perhaps, on the 10400?
  - FramerV
    NETGEAR Employee Retired
    Jan 16, 2017
    Hi twc,
    
    The support from SAB is actually trying to point out 3 possibilities I think.
    
    1. The ReadyNAS is under powered and it taking most of its resources when a repair is happening.
    
    2. An HDD failure.
    
    3. A possible issue with our OS.
    
    For the 2nd concern, we can check that via the system logs.
    
    How do I send all logs to ReadyNAS Community moderators?
    
    For the 3rd concern, updating to our latest firmware would be our way to go.
    
    ReadyNAS OS 6 Software Version 6.6.1
    
    Once we check these and see that everything is okay. We can say that the ReadyNAS is just that not powerful enough to handle the repair with ease.
    
    Regards,