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.
LadFromWales wrote:I am confused as to which option I should be enabling
"Abort jobs that cannot be completed"
"Check before download"
I have several configured servers. Both options appear to inform me of missing articles, the former does so much sooner, but from what I understand, fails the download if 1% is deemed to be unavailable? What about PAR's?
Use "check before" only when you want to waste as little data as possible, but don't care about the time it costs extra.
"abort" saves time, but may waste data.
The "check before" option is for people on a quota who don't want to be confronted with downloads that are almost complete,
but unrepairable. "Check" requires 100.5% of the (normally) 110% available (110% = 100% data + 10% par2)
Dabront wrote:I've used Frugal as my main server and always had a problem with pre-download check. Even with 0.7.9 I find the same issue. Sometimes SAB with just get stuck checking and this will continue until I turn off checking and delete the NZB. A restart will not fix the problem, the NZB must be deleted. There is something between Frugal and SAB that doesn't play well together with checking turned on.
Some servers are slow at answering when an article is not present.
This is especially a problem when you have set the timeout a bit short, SABnzbd will retry too soon.
Checking will check ALL articles, while normal download will skip the par2 files that are not needed.
