Hi there,
I'm new to SAB and it's installed on a ReadyNAS 10400. It seems to work fine until a download finishes and it enters the next stage. At that point, my ReadyNAS grinds to a halt and SAB reports increasingly big sysloads (in the top right corner of the web interface)
I see three recently finished downloads (with "busy" spinners) in the History section, and one says "repairing 79%". There's also one active download in the queue.
This causes my system to go offline for several days, and I had to flick the power switch last time.
Can I tell it to behave better during this stage of the download process?
Thanks,
Tony
Sysload: 228.37 | 214.94 | 207.68 | V=640M R=97M (ReadyNAS)
Forum rules
Help us help you:
Help us help you:
- Are you using the latest stable version of SABnzbd? Downloads page.
- Tell us what system you run SABnzbd on.
- Adhere to the forum rules.
- Do you experience problems during downloading?
Check your connection in Status and Interface settings window.
Use Test Server in Config > Servers.
We will probably ask you to do a test using only basic settings. - Do you experience problems during repair or unpacking?
Enable +Debug logging in the Status and Interface settings window and share the relevant parts of the log here using [ code ] sections.
Re: Sysload: 228.37 | 214.94 | 207.68 | V=640M R=97M (ReadyN
A "Sysload: 228.37 | 214.94 | 207.68" is very bad. A normal value is something below 1, and an acceptable max value is the same as the number of CPU cores you have (so 2 or 4).
So there is something wrong with your system. Can you get an overview of processes on your ReadyNAS, for example by logging in onto the command line and running "top"? I expect run-away processes. Or there is a problem with your disk setup (see man page snippet below).
From the 'uptime' man page about the sys load numbers:
So there is something wrong with your system. Can you get an overview of processes on your ReadyNAS, for example by logging in onto the command line and running "top"? I expect run-away processes. Or there is a problem with your disk setup (see man page snippet below).
From the 'uptime' man page about the sys load numbers:
System load averages is the average number of processes that are either in a runnable or uninterruptable state. A process in a
runnable state is either using the CPU or waiting to use the CPU. A process in uninterruptable state is waiting for some I/O
access, eg waiting for disk. The averages are taken over the three time intervals. Load averages are not normalized for the number
of CPUs in a system, so a load average of 1 means a single CPU system is loaded all the time while on a 4 CPU system it means it was
idle 75% of the time.
Re: Sysload: 228.37 | 214.94 | 207.68 | V=640M R=97M (ReadyN
now (and repair at 92%)
Code: Select all
Sysload: 276.55 | 272.81 | 267.20 | V=645M R=52M
Re: Sysload: 228.37 | 214.94 | 207.68 | V=640M R=97M (ReadyN
it's being caused by SAB. didn't have any problems before i installed it recently.
Code: Select all
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
Re: Sysload: 228.37 | 214.94 | 207.68 | V=640M R=97M (ReadyN
A few remarks:
Repairing takes a lot of CPU power. That is what you experience. So, find a post that does not need any repair (most post don't need a repair). Can you try that?
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
Repairing takes a lot of CPU power. That is what you experience. So, find a post that does not need any repair (most post don't need a repair). Can you try that?
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
Re: Sysload: 228.37 | 214.94 | 207.68 | V=640M R=97M (ReadyN
Thanks Sander. It seems like SAB is having to repair most posts. How would I go about telling it to find better posts? (via couchpotato)
Or... can I modify the "repair" call somehow, so it runs with a better nice value? I don't care if the repair takes twice as long.
Or... can I modify the "repair" call somehow, so it runs with a better nice value? I don't care if the repair takes twice as long.
Re: Sysload: 228.37 | 214.94 | 207.68 | V=640M R=97M (ReadyN
EDIT:
Get this NZB: http://www.filedropper.com/bigbuckbunny ... 2016-12-06
... put it into SABnzbd. It has no par2 files, so repair will not happen ...
Report back the speed and responsiveness of your system.
Get this NZB: http://www.filedropper.com/bigbuckbunny ... 2016-12-06
... put it into SABnzbd. It has no par2 files, so repair will not happen ...
Report back the speed and responsiveness of your system.
Re: Sysload: 228.37 | 214.94 | 207.68 | V=640M R=97M (ReadyN
Hi Sander. The SABnzbd web interface isn't responding, so I'm not sure how to have it download that file?
Here's some data from earlier downloads though, if that helps?
While system was overloaded...
Another...
Another one...
Another one (this might've been while system was not overloaded?)...
Here's some data from earlier downloads though, if that helps?
While system was overloaded...
Code: Select all
SABnzbd has downloaded "a post"
Finished at 2017-01-14 02:57:04
Downloaded 7.2 GB
Results of the job:
Stage Download
Downloaded in 1 hour 51 minutes 50 seconds at an average of 1.1 MB/s
70 articles were missing
Stage Source
a post.nzb
Stage Unpack
Unpacked 1 files/folders in 15 minutes 54 seconds
Stage Repair
[130047-0] Repaired in 0 seconds
[130047-1] Repaired in 5 hours 28 minutes 2 seconds
Code: Select all
SABnzbd has downloaded "a post"
Finished at 2017-01-13 18:33:08
Downloaded 7.1 GB
Results of the job:
Stage Download
Downloaded in 1 hour 10 minutes 8 seconds at an average of 1.7 MB/s
162 articles were missing
Stage Source
a post.nzb
Stage Unpack
[a post] Unpacked 2 files/folders in 27 minutes 18 seconds
Stage Repair
[a post] Repaired in 15 hours 29 minutes 45 seconds
Code: Select all
SABnzbd has downloaded "a post"
Finished at 2017-01-02 08:06:48
Downloaded 11.0 GB
Results of the job:
Stage Download
Downloaded in 3 hours 3 minutes 25 seconds at an average of 1.0 MB/s
Stage Source
a post.nzb
Stage Unpack
[...] Unpacked 1 files/folders in 17 minutes 24 seconds
Stage Repair
[...] Quick Check OK
Code: Select all
Hi,
SABnzbd has downloaded "a post"
Finished at 2016-12-17 08:32:31
Downloaded 13.3 GB
Results of the job:
Stage Download
Downloaded in 2 hours 32 minutes 9 seconds at an average of 1.5 MB/s
10 articles were missing
Stage Source
a post.nzb
Stage Unpack
[...] Unpacked 2 files/folders in 33 minutes 39 seconds
Stage Repair
[...] Repaired in 2 hours 47 minutes 37 seconds
Re: Sysload: 228.37 | 214.94 | 207.68 | V=640M R=97M (ReadyN
No. Sorry.Here's some data from earlier downloads though, if that helps?
BTW: which version of SABnzbd are you using?
I don't think this thread is leading anywhere if we continue this way. You're overloading your underpowed NAS with too big files. Troubleshooting in such a situation is too difficult.The SABnzbd web interface isn't responding, so I'm not sure how to have it download that file?
Last try: install SABnzbd on your PC. That will work fast. You will get to know SABnzbd. If you understand SABnzd, you can consider using it on your NAS
Re: Sysload: 228.37 | 214.94 | 207.68 | V=640M R=97M (ReadyN
Hi Sander. I'm doing my best to help you help me, but you're ignoring my questions. And now you seem to be suggesting that I shouldn't be using SAB (or asking for help) if I'm a newbie?
Anyway... I don't own a PC and can't buy another server just for this function. I'd like to use my NAS, even though I appreciate it's not really suitable. SAB is offered for my NAS, so I'd just like to optimise it as best I can, if you don't mind?
So if you're willing to help...
1) How would I go about telling it to find better posts? (or is this a question for a couchpotato forum, which is the only way I'm sending nzb's over to SAB)
2) Can I modify the "repair" call somehow, so it runs with a better nice value? (eg. "mv par2 par2.old" and then replace par2 with a 1 line script to call par2.old with a nice value?)
Ps. Unfortunately, I can't access my NAS at the moment, in order to tell you which version I'm running. However, it's whatever shows up on the "available apps" page of the ReadyNAS
Anyway... I don't own a PC and can't buy another server just for this function. I'd like to use my NAS, even though I appreciate it's not really suitable. SAB is offered for my NAS, so I'd just like to optimise it as best I can, if you don't mind?
So if you're willing to help...
1) How would I go about telling it to find better posts? (or is this a question for a couchpotato forum, which is the only way I'm sending nzb's over to SAB)
2) Can I modify the "repair" call somehow, so it runs with a better nice value? (eg. "mv par2 par2.old" and then replace par2 with a 1 line script to call par2.old with a nice value?)
Ps. Unfortunately, I can't access my NAS at the moment, in order to tell you which version I'm running. However, it's whatever shows up on the "available apps" page of the ReadyNAS
Re: Sysload: 228.37 | 214.94 | 207.68 | V=640M R=97M (ReadyN
I think what Sander is trying to make clear is that your NAS is not just a bit slow, but inadequate to do downloading on its own. Usenet downloading is very CPU intensive, and repair even more.
That the package is technically available doesn't mean it's meant to run well, it's probably meant for devices of the same manufacturer with more power.
The times you report (5 hours for repair) are just way way too long.
When writing PC, we mean any computer, like a laptop, Mac, anything. You must have one of those?
That the package is technically available doesn't mean it's meant to run well, it's probably meant for devices of the same manufacturer with more power.
The times you report (5 hours for repair) are just way way too long.
When writing PC, we mean any computer, like a laptop, Mac, anything. You must have one of those?
If you like our support, check our special newsserver deal or donate at: https://sabnzbd.org/donate
Re: Sysload: 228.37 | 214.94 | 207.68 | V=640M R=97M (ReadyN
Hi Safihre. I was drawn to the concept of SAB (on NAS) because I could queue things up and forget about it. The NAS is tucked away and remains on. If I'm to run it on my mac now, it means I need to think about what's in the queue and make a decision each day about whether to leave it on or turn it off. That's the reason I bought a NAS in the first place. Set and forget.
So... if we're saying it's the repair process that overloads the NAS, is there no way to address just that particular limitation? (refer my questions above, please)
So... if we're saying it's the repair process that overloads the NAS, is there no way to address just that particular limitation? (refer my questions above, please)
Re: Sysload: 228.37 | 214.94 | 207.68 | V=640M R=97M (ReadyN
Well we do have the 'never_repair' special setting (Config > Specials).
This way successful downloads will nicely unpack, but if they need par2 repair then all par2 files will be downloaded so you can run the repair on your Mac:
https://sabnzbd.org/wiki/configuration/1.2/special
"Only perform QuickCheck and par2-verify, but never par2-repair. Use this when your low-performance system has trouble running repairs. All available par2 files will be downloaded, so you can let another system do the repair. If the download verifies OK, post-processing will be done as usual."
This way successful downloads will nicely unpack, but if they need par2 repair then all par2 files will be downloaded so you can run the repair on your Mac:
https://sabnzbd.org/wiki/configuration/1.2/special
"Only perform QuickCheck and par2-verify, but never par2-repair. Use this when your low-performance system has trouble running repairs. All available par2 files will be downloaded, so you can let another system do the repair. If the download verifies OK, post-processing will be done as usual."
If you like our support, check our special newsserver deal or donate at: https://sabnzbd.org/donate
Re: Sysload: 228.37 | 214.94 | 207.68 | V=640M R=97M (ReadyN
Thanks safihre, and sorry for the slow reply. That switch looks like the perfect solution! If I can't set that from within the web interface (?), then can you give me the path to the config file that I'll need to edit please?
And what command (or set of commands) should I run from my (more powerful) Mac, when a download needs repair? And how will I know that the download needs my intervention? Is this visible in the web interface?
Finally, do you know what sander meant by "find a post that does not need any repair"? Can I tell couchpotato to do that?
Thank you!
And what command (or set of commands) should I run from my (more powerful) Mac, when a download needs repair? And how will I know that the download needs my intervention? Is this visible in the web interface?
Finally, do you know what sander meant by "find a post that does not need any repair"? Can I tell couchpotato to do that?
Thank you!
Re: Sysload: 228.37 | 214.94 | 207.68 | V=640M R=97M (ReadyN
In Config > Specials you can set the switch. No need to edit the config.
You can use a program like https://gp.home.xs4all.nl/Site/MacPAR_deLuxe.html, that can open the par2 files and has an interface to do the repair.
No you can't tell couchpotato that. It was just meant for testing the power of your device!
You can use a program like https://gp.home.xs4all.nl/Site/MacPAR_deLuxe.html, that can open the par2 files and has an interface to do the repair.
No you can't tell couchpotato that. It was just meant for testing the power of your device!
If you like our support, check our special newsserver deal or donate at: https://sabnzbd.org/donate