RSS Fetched NZBs

[b0x]

I've had several rss fetched items get stuck in the queue. In previous versions such nzbs would have been marked invalid or unobtainable and knocked to the history. In .70 it now leaves them in the queue to retry over and over. I see no setting to change this or to at least set the number of retries. It has caused me to exceed the limit of the rss feed and its locked me out now.

[shypike]

There's no pleasing everyone.
Several indexers tend to have issues over long periods.
Most people don't like having SABnzbd give up trying.
Which indexer are you having problems with?

[b0x]

nzbsrus is where I hit the limit. If we could have a way to at least set the number of retries I think it'd help prevent such in the future. In the past I would retry the ones that fell to the history on my own either way.

[b0x]

btw all the links were valid. also working with nzbsrus on the issue on their end.

Thank you for the help

[Battle_707]

If I understand it correctly, SAB keeps trying to re-download the file if the original was empty. However, even though the new downloads work just fine, it does not seem to overwrite the old (empty) NZB and thus keeps repeating itself, causing the user's download counter to run out.

Apparently this also happens when an NZB is deleted, but is still in the RSS stream (it's cache based). Our site should actually delete entries from the RSS as well when a post is being deleted from the site, but I will have to recheck our code to be sure this is happening properly. Either way, the download link will throw an error when a file has been deleted and is no longer available.

[shypike]

Either way, the download link will throw an error when a file has been deleted and is no longer available.

The problem we have is that some/many sites show bizarre behaviour when having problems.
If you can tell us which error code(s) should be treated as "not recoverable" (as in don't try again), I'll be happy to implement that.

[b0x]

Here's a snip of the logs.

2012-06-25 14:44:08,530::INFO::[urlgrabber:117] Grabbing URL https://www.nzbsrus.com/nzbdownload_rss ... xxx/xxxxx/
2012-06-25 14:44:09,937::INFO::[nzbstuff:638] Replacing spaces with underscores in Trued.Blud
2012-06-25 14:44:09,937::INFO::[misc:768] Creating directories: Z:\Hidden\Trued.Blud
2012-06-25 14:44:09,953::WARNING::[nzbstuff:702] Empty NZB file nzb [https://www.nzbsrus.com/nzbdownload_rss ... xxx/xxxxx/]
2012-06-25 14:44:09,953::INFO::[urlgrabber:208] Unknown error fetching NZB, retry after 2 min https://www.nzbsrus.com/nzbdownload_rss ... xxx/xxxxx/
2012-06-25 14:44:14,953::INFO::[urlgrabber:117] Grabbing URL https://www.nzbsrus.com/nzbdownload_rss ... xxx/xxxxx/
2012-06-25 14:44:16,342::INFO::[nzbstuff:638] Replacing spaces with underscores in Trued.Blud
2012-06-25 14:44:16,342::INFO::[misc:768] Creating directories: Z:\Hidden\Trued.Blud

[s0ck3t]

I have asked some of the other nzbsrus members who are also having issues to pm me some of logs they have so we can see if it is the same error, I am 99% sure it will be but want to just make sure.


s0ck3t
Admin
Nzbsrus.com

[Battle_707]

There is actually a variety of error codes that the download script can through. Varying from invalid request to download restriction due to the post being nuked. Most of the error codes are not as much error codes as they are messages (strings of text in a die() command), as the RSS feed was not setup to be used as an API substitute. But I'm hoping to work on our API design in a week or two, and by the looks of it I will be running it over the same script, so I will have to update the error codes so they can be parsed more easily.

Please let me know if you have specific error code outlines. Since I haven't done them yet, I might as well adhere to something that works for you... x). Otherwise, I think they'll be something like 'SERVICE_DOWN_RETRY' and 'DELETED_NORETRY'.

[shypike]

If you can give the error strings, that's enough for now.
I'm in a bit of a hurry because release 0.7.1 will be this week.

[Battle_707]

RSS offline [RETRY]:
'Service temporarily offline'

Invalid link [NO RETRY]:
'Invalid Link: #1'

User verification incorrect [NO RETRY]:
'Invalid Link: #3'

NZB deleted [NO RETRY]:
'NZB DELETED'

NZB has been disabled due to nuke [NO RETRY]:
'Post has been nuked: <string_reason>'

NZB file not available [NO RETRY]:
'Invalid link: #8'

The error codes obviously appear without the quotes. Like I said, these will change as I will build the API. Let me know if you have any questions.

[exussum]

I get Invalid link #1 and #8 mostly when my sab fails