SABnzbd Forums

Hi,

I get a lot of those messages lately. Usually when I see something > 100% I assume a bug. Not sure this time.

Does anyone know where this comes from?



Cu

Version: 1.2.1 [d32cf57]
Uptime: 23h
Config File: /config/sabnzbd.ini
Used cache: Cached 0 articles (0 B)
Parameters: /usr/bin/sabnzbdplus --config-file /config --server 0.0.0.0:8080
Python Version: 2.7.12 (default, Nov 19 2016, 06:48:10) [GCC 5.4.0 20160609] [UTF-8]
OpenSSL: OpenSSL 1.0.2g 1 Mar 2016 [TLS v1.2, TLS v1.1, TLS v1]

That means you have no par2 files, which is risky.

Anyway: You could try setting req_completion_rate to something lower than 100.2, for example 99

see http://localhost:8080/sabnzbd/config/sp ... etion_rate

Usually means at least 1 article was missing, so the download can never be completed fully because either doesn't have par2.

sander wrote:That means you have no par2 files, which is risky. Anyway: You could try setting req_completion_rate to something lower than 100.2, for example 99

The message is from the pre-download completion check. No par2 files is the most likely situation here, but this result is also possible whenever damage and par2 availability for a particular job are a (very close) match. It's the latter case that makes sab want that 0.2% margin, as usenet articles and par2 blocks don't necessarily stack up nicely. Which is also why it says "might fail" in that message for jobs in the 100.0-100.2 range... not "will fail".

That said, the lowest sensible value for the completion rate setting is exactly 100% as anything below that will always fail regardless. For jobs without par2 files 100% is also the highest they could ever score (and the only chance of a successful download). So if you come across such jobs regularly you know what to do.