IOError
Posted: November 23rd, 2016, 1:01 am
v 1.1.0 in a Docker container
When trying to download a links from an RSS feed I'm presented with the following error:
The RSS feed imports correctly, all other integrations, downloads and post-processing is working fine. If I grab the NZB file from the link in the RSS feed manually and then manually add it to sabnzbd it downloads the content without issue.
I'd welcome suggestions as to where to start troubleshooting further.
When trying to download a links from an RSS feed I'm presented with the following error:
Code: Select all
500 Internal Server Error
The server encountered an unexpected condition which prevented it from fulfilling the request.
Traceback (most recent call last):
File "/usr/share/sabnzbdplus/cherrypy/_cprequest.py", line 670, in respond
response.body = self.handler()
File "/usr/share/sabnzbdplus/cherrypy/lib/encoding.py", line 220, in __call__
self.body = self.oldhandler(*args, **kwargs)
File "/usr/share/sabnzbdplus/cherrypy/_cpdispatch.py", line 60, in __call__
return self.callable(*self.args, **self.kwargs)
File "/usr/share/sabnzbdplus/sabnzbd/interface.py", line 2227, in download
sabnzbd.add_url(url, pp, script, cat, prio, nzbname)
File "/usr/share/sabnzbdplus/sabnzbd/__init__.py", line 507, in add_url
future_nzo = NzbQueue.do.generate_future(msg, pp, script, cat, url=url, priority=priority, nzbname=nzbname)
File "/usr/share/sabnzbdplus/sabnzbd/decorators.py", line 32, in newFunction
return f(*args, **kw)
File "/usr/share/sabnzbdplus/sabnzbd/nzbqueue.py", line 282, in generate_future
self.add(future_nzo)
File "/usr/share/sabnzbdplus/sabnzbd/decorators.py", line 32, in newFunction
return f(*args, **kw)
File "/usr/share/sabnzbdplus/sabnzbd/nzbqueue.py", line 391, in add
nzo.nzo_id = sabnzbd.get_new_id('nzo', nzo.workpath, self.__nzo_table)
File "/usr/share/sabnzbdplus/sabnzbd/decorators.py", line 32, in newFunction
return f(*args, **kw)
File "/usr/share/sabnzbdplus/sabnzbd/__init__.py", line 842, in get_new_id
raise IOError
IOErrorI'd welcome suggestions as to where to start troubleshooting further.