SABnzbd Forums

Everytime I click on the RSS feed settings from the config menu I get the following menu.  I reinstalled the software and it worked fine until I re-uploaded my settings file to the App Data folder.  I would just re-do the settings but I had 3 feeds and one had about 50 filters on it and I can't remember all of what I had to get it running smoothly.  Does anyone have any ideas on how to get the RSS feed working again without starting over from scratch?


500 Internal Server Error

The server encountered an unexpected condition which prevented it from fulfilling the request.

Traceback (most recent call last):
  File "cherrypy\_cprequest.pyo", line 618, in respond
  File "cherrypy\_cpdispatch.pyo", line 25, in __call__
  File "sabnzbd\interface.pyo", line 1985, in index
  File "_Program_Files_SABnzbd_interfaces_Plush_templates_config_rss_tmpl.py", line 636, in respond
IndexError: list index out of range

Stop SABnzbd.
Find the file rss_data.sab in the "cache" folder.
(To find that folder, it's in the same folder as sabnzbd.ini. See: http://wiki.sabnzbd.org/configure-v2 )
Start SABnzbd.

Alright... I found the file and didn't know what to do with it.  I tried deleting the file and restarting sabnzbd.  I still get the same "Internal Server Error"  Is there something in particular I need to do with that cache file?

Sorry, my fault. I was typing too hurried.
The idea was indeed to remove the file.

Of course this is a problem that "should not happen".
The alternative is to check the sabnzbd.ini file for irregularities.
Look for the [[rss]] section.
Each feed definition is started like this:
[name=of-feed]
The filters are numbered from filter0 to filter9 (example).
They should start with filter0 and be continuously numbered.

As a last resort, make a copy of sabnzbd.ini,
remove all passwords and send it to bugs at sabnzbd.org

No biggie.  This forced me to newer and better offerings.  I've now set up my system with Sick Beard and CouchPotato.  All seems to be going smoothly.  I'm starting to think it was a good thing I had this issue