0.4.5 RSS Feed Warnings

[clobber]

Hey, - Using 0.4.5 I'm having a minor problem with RSS Feeds. Everything works correctly until I get warnings that the RSS feed could not be retrieved. I've attached a part of the log below. If I just go to the RSS config tab and click on preview or download, everything starts working properly again.


2008-12-07 18:38:01,671::INFO::[sabnzbd] Saving data for rss_data.sab in D:\Files\SABNZBD\CACHE\rss_data.sab
2008-12-07 19:06:19,140::WARNING::[RSS] Failed to retrieve RSS from http://tvbinz.net/rss_new.php
2008-12-07 19:08:19,140::INFO::[sabnzbd] Saving data for rss_data.sab in D:\Files\SABNZBD\CACHE\rss_data.sab
2008-12-07 19:36:18,828::WARNING::[RSS] Failed to retrieve RSS from http://tvbinz.net/rss_new.php
2008-12-07 19:38:18,875::INFO::[sabnzbd] Saving data for rss_data.sab in D:\Files\SABNZBD\CACHE\rss_data.sab
2008-12-07 20:06:19,171::WARNING::[RSS] Failed to retrieve RSS from http://tvbinz.net/rss_new.php
2008-12-07 20:08:19,171::INFO::[sabnzbd] Saving data for rss_data.sab in D:\Files\SABNZBD\CACHE\rss_data.sab
2008-12-07 20:36:18,983::WARNING::[RSS] Failed to retrieve RSS from http://tvbinz.net/rss_new.php
2008-12-07 20:38:19,062::INFO::[sabnzbd] Saving data for rss_data.sab in D:\Files\SABNZBD\CACHE\rss_data.sab

[shypike]

Do all scheduled scans go wrong or just some (or sometimes)?

[clobber]

Shypike - not sure what you mean by all scheduled scans? I only have one RSS Feed set up, so I guess it is the only scheduled scan. The problem seems to just happen "after a while" but ususally something like once a day.

[shypike]

I just wanted to know if every attempt to contact the feed failed
or just occasionally.
It looks like occasionally the feed doesn't want talk with SABnzbd (overload of server?).

This is to be expected, however the dilemma for us is: should we report any
failed attempt to the user?
If not, you may never know that it stopped working.
If we do, you get worried about something which may not really be a problem.

[clobber]

I see the problem. I think I would prefer to have any and every warning....

But do you think there is a bug here? As soon as I manually kick it off again, sabnzbd can once again talk to the RSS feed. My observation is that sometimes sabnzbd "thinks" it can't talk to the RSS feed when it really can?

[shypike]

It would be rather odd bug if sometimes it connects and sometimes not.
The Internet isn't exactly reliable.
You must have seen often that connecting to a website fails and a retry will solve it?
The most we can do is retry a few times.
But given the periodic nature of the RSS feed scan, we might as well wait for the next scan.
(And not tell you about the "problem".)

[clobber]

Agree with that.

However, you'll notice from my log snippet that the RSS feed was checked every 20 minutes (like it is configured). However, it kept failing for 5 hours. Right after it failed (maybe 2 seconds), I forced it to check the feed by pressing "preview" and "download." That caused everything to work properly. Hmmm....

[shypike]

I'm not denying something strange happened.

The problem is that the exact same code is used for scheduled scans and preview.
There's no explanation why it fails when scheduled but not with manual control.
It doesn't help that we get hardly any info from the RSS-library we use about why things failed.
This makes it next to impossible to diagnose.

We'll see what we can do about improving logging of RSS problems.

BTW, do you have multiple feeds defined?

[crushinat0r]

Hey,

I'm having a similar issue with the same logging errors.  If I take the RSS feed and put it in a browser directly it works fine and I see search results.  However, when it's in the RSS area in SABnzbd+ I consistently get the error and no files download.  Hitting preview or download show blank results.  Again, the urls seem valid, because I can enter them directly in a browser and they work. I've tried with many RSS feeds and with a single one (to isolate the issue), it makes no difference.

This used to work for me but stopped about 3 weeks ago, not sure why.

[clobber]

Nope, I only have one feed defined. The fix is certainly not a priority and I appreciate your help.

[shypike]

I'm having a similar issue with the same logging errors.  If I take the RSS feed and put it in a browser directly it works fine and I see search results.  However, when it's in the RSS area in SABnzbd+ I consistently get the error and no files download.  Hitting preview or download show blank results.  Again, the urls seem valid, because I can enter them directly in a browser and they work. I've tried with many RSS feeds and with a single one (to isolate the issue), it makes no difference.

Using the browser and  SABnzbd are two different things.
With the browser you're usually logged in to the site (or the authorization cookie is still there) and then use the RSS URL.
SABnzbd needs to have the authorization embedded in the URL.
For some sites the authorization part expires after some time and you need to use the browser to get a fresh RSS URL.

[crushinat0r]

Using the browser and  SABnzbd are two different things.
With the browser you're usually logged in to the site (or the authorization cookie is still there) and then use the RSS URL.
SABnzbd needs to have the authorization embedded in the URL.
For some sites the authorization part expires after some time and you need to use the browser to get a fresh RSS URL.

Ah ok.  I'm using Newzbin and have my login settings setup through SABnzbd.  I've tried using the "bookmark" option to download things directly from newzbin (set a bookmark, and SAB pulls the nzb and downloads automatically) just to see if my connection to newzbin is set up properly, and it works. But yeah, the RSS feeds don't seem to work.  I can grab fresh URLs from newzbin and see if that makes a difference.

[shypike]

Unlike the other newzbin functions, the RSS feed doesn't have a nice API.
That's the reason that SABnzbd cannot actually use the username and password for RSS.
It really requires a full URL including the encoded authorisation string.

[crushinat0r]

FYI, I reloaded all 25+ feeds I have with fresh URLs and it seems to be working again.  I'm not sure why reloading them fixed the problem, but thanks!