SABnzbd Forums

I'm using sabnzbd v. 0.7.7 and have a problem where sabnzbd reports the following warnings when retrieving a NZB from a RSS feed:

WARNING: Empty NZB file [file-name].nzb [http://[site]/download/[file-name].nzb]

I have many many of these...

The problem is, sabnzbd keeps pinging the tracker every some interval for the same NZB without stop. This eventually fills up my queue with many requests that "can't" be retrieved.

I've confirmed why this is occurring. After retrieving one of the NZB files from the URL using a browser, it turns out that the NZB file is NOT EMPTY. It is a fully valid NZB file, but it contains ONLY PAR FILES. Sabnzbd considers these files "invalid / empty" and keeps pinging the tracker every now and then to try and get a "valid" nzb.

This is bad for 2 reasons:

1. It generates unnecessary traffic to the tracker.

2. It fills up the download queue with entries that never go away unless I manually delete them.

I would classify this as a bug in sabnzbd.

My suggestion would be to simply discard these "invalid" NZB files while issuing the warning, or at least provide an option somewhere where the user can choose what behavior should be taken when invalid NZB files are returned from the tracker.

Thanks,

Are you sure that SABnzbd actually gets content?
Tracker APIs can be unreliable.
An NZB with just par2 files will not give an empty file warning.
What does SABnzbd do when you upload the NZB manually?

Yes, I have traced the request via Fiddler 2 (http://www.fiddler2.com/fiddler2/) and WireShark.

Sabnzbd does retrieve the nzb file. The tracker returns valid data every time.

When adding said NZB file to the watch folder the same warning is issued and the NZB file is never picked up.

I don't see how this can be anything else but a sabnzbd issue.

cloud5 wrote: I don't see how this can be anything else but a sabnzbd issue.

Well, I haven't been able to reproduce the problem.
Can you email an example to bugs@sabnzbd.org ?
(Please add the URL of this post.)

Sure.

I've reproduced the issue one more time and have attached a NZB file that creates the problem to the email.

Just to anyone else having the same problem in the future, we've determined that this was caused by the switch Ignore Samples being set to Do not download. Switching it to Off resolves the retry issue.

Is this a confirmed issue now? I'm seeing the same issue (using 0.7.1 as a Synology package) and I've confirmed that the switch Ignore Samples is set to Do Not Downloads.

I'm getting repeated messages of the following format:

WAIT: XX SECS : Trying to fetch NZB from http://nzb-matrix.eu/getnzb/abab015dec0 ... 9e21ab4858

Checking the log shows:

2013-01-04 23:52:36,136 WARNING: Empty NZB file Person.of.Interest.S02E11.720p.HDTV.X264-DIMENSION.nzb [http://nzb-matrix.eu/getnzb/abab015dec0 ... e21ab48580]

Manually downloading the NZB in question is possible, but manually uploading the file shows the same issue. NZB in question is shown below. ANy assistance would be gratefully received!

Edit to my post : a shut down /restart of Synology box didn't solve it, but an update to SABNZBD v0.7.7 did.

No idea as to the root cause, but I wonder if it's to do with a switch over to a New Year? Last year was a leap year....

Quite a few bugs were solved between 0.7.1 and 0.7.7.
The particular issue of cloud5 is solved in 0.7.8.