Downloads Fail, OK with other client?

[b93419]

I've recently installed SABNZBD V0.6.5 on my QNAP TS-412 (ARM). At first it seemed to work OK, but lately all downloads fail with "not enough repair blocks". However, using the same NZB with the same provider with a different client (AltBinz) on my PC works perfectly. Is this a problem with the QNAP install or something else? Any ideas?

EDIT: It seems that SAB is not picking up all the articles - just looked at the one of the NZBs, it's missing half the RAR files. Again, no issues when using AltBinz

[shypike]

Due to trickery people use to disguise posts, older versions of SABnzbd will fail sometimes.
You should upgrade.

[MrX4000]

OK I am having a very similar problem. They fail in Sab ... but use the same server, same computer, same NZB, and they will download in Neewslecher np. Am I missing something? I do not get messages that they fail or will fail, If I expand them in the que they are red in color and are not downloading. Any ideas?

Running WHS 2011 computer
Astraweb provider


I should add that some NZBs will download without problem so its not like Sab is completely broken for me. Just certain ones?

OK .. Just found this http://forums.sabnzbd.org/viewtopic.php?f=2&t=15959 ... might be whats going on. I will check those settings and let you know if it makes any differenece.

[MrX4000]

Nope ... still can't explain why some fail .. but work on another program

[shypike]

Not downloading doesn't sound very likely.
Missed repairs due to bad naming that SABnzbd doesn't understand, that could be possible.
Are you using the latest release?
NL doesn't have to take the behaviour on non-Windows systems into account.
Do you have an example of an NZB that "doesn't download" with SABnzbd but does with NL?

[MrX4000]

Yes running he latest release. No it's definitely not downloading, the speed drops to about 3k if you expand the nzb ( plus sign ) they all slowly appear read in color. I've had some not repair and they download and in the bottom of the screen it will tell me that repair failed. This is different, I will check which ones that do it for sure and get you an example of it. Where should I upload the NZB?

[shypike]

. Where should I upload the NZB?

Email to bugs@sabnzbd.org and please add the URL of this message.

[0402robbie]

Hello, I am also having this problem. Been using this program for about 2 years now with little to no problems, for about the last 3 - 4 weeks 90% of my downloads fail with missing blocks or a crc file errors. Latest Version: 0.7.16 — Released: 02-SEP-2013 is the version i'm running on a windows 7 Ultimate i5 system. Any help would be appreciated.

[shypike]

Hello, I am also having this problem. Been using this program for about 2 years now with little to no problems, for about the last 3 - 4 weeks 90% of my downloads fail with missing blocks or a crc file errors. Latest Version: 0.7.16 — Released: 02-SEP-2013 is the version i'm running on a windows 7 Ultimate i5 system. Any help would be appreciated.

You only have the same problem when another client will download
successfully from the same Usenet server.

[Thom-]

Hi shypike,

I think I have the same troubles lately. Almost every download failes currently with sabnzbd:



I'm not sure if the censoring is stupid, but I thought it doesn't harm.

I waited now a few weeks, but the problem is still there (at first I thought about DCMA takedowns or something like that).
Today I tried it with a different client (Alt.binz) and voilá it worked :\
I took then the same nzb file (normally I'm using sickbeard) and tried it again with sabnzbd - but the problem stayed the same.

I'm using version 0.7.16 with python 2.7.5 (default, May 30 2013, 21:53:45) [GCC 4.2.1] on a Synology DS412j NAS.

You can see the log of sabnzbd here: http://tny.cz/2013bbcb
And the log of alt.binz (maybe you can see a difference somehow?) here: http://tny.cz/e769afc8

All files are very current, and I even tried some a few days later (in sickbeard I got a new nzb file two days later and so on).

It's really strange, it worked fine until a couple of weeks. The last day which was kind of normal was 2013-10-13 but I'm trying to find out what changed. I know that there has been an update of sabnzbd some day, but I think it was longer ago.
Any idea what could be wrong?

[shypike]

I hate to repeat myself, but it's only a real SABnzbd issue
when SABnzbd cannot complete the download while other clients can.
There also the possibility that a weird naming scheme is used that
makes SABnzbd confused about the repair process.
In any case, please email the NZB file to bugs@sabnzbd.org
(Please add the URL of this post.)

[Thom-]

Thanks for the quick reply

I hate to repeat myself, but it's only a real SABnzbd issue
when SABnzbd cannot complete the download while other clients can.

This is in fact the issue here. Works with alt.binz but not in SABnzbd :/ (Same nzb file)
I tried it with the Synology Download Station client and it worked too (so on the same system as sabnzbd)
You can check the logfile of that download here: http://tny.cz/9135874a

I'll send you the file, thank you for your support and thanks for checking out the problem

[0402robbie]

You only have the same problem when another client will download
successfully from the same Usenet server.

I have Successfully download the same files from an older version of Sab on a virtual machine I had, also works on my synology box where I have sab installed.

Is this sufficient evidence I have the same problem or do you require screen caps and system logs?

[shypike]

An NZB and a debug log would be great.
You can email to bugs@sabnzbd.org
(Please add the URL of this post.)

[0402robbie]

I resolved my issue, I completely uninstalled 0.7.16 from my PC, Then re installed 0.7.16. This has fixed the issue. I have successfully downloaded the same files that failed several time before the reinstall. So a quick fix if you need it.

I used revo uninstaller and removed everything from the system. Had to add back all settings. Don't know if this was necessary but I didn't want to do it twice. Lol Good luck.