SABnzbd++

Hello,

I've had SabNzbd working on my ReadyNAS Pro since last week.
It is great but crashes very frequently on SSL errors.

See here for an example from the error.log:

Exception in thread CP WSGIServer Thread-13:
Traceback (most recent call last):
File "/usr/lib/python2.4/threading.py", line 442, in __bootstrap
self.run()
File "/usr/share/sabnzbdplus/cherrypy/wsgiserver/__init__.py", line 1280, in run
conn.communicate()
File "/usr/share/sabnzbdplus/cherrypy/wsgiserver/__init__.py", line 1204, in communicate
format_exc())
File "/usr/share/sabnzbdplus/cherrypy/wsgiserver/__init__.py", line 601, in simple_response
self.wfile.sendall("".join(buf))
File "/usr/share/sabnzbdplus/cherrypy/wsgiserver/__init__.py", line 1114, in sendall
return self._safe_call(False, super(SSL_fileobject, self).sendall, *args, **kwargs)
File "/usr/share/sabnzbdplus/cherrypy/wsgiserver/__init__.py", line 1066, in _safe_call
return call(*args, **kwargs)
File "/usr/share/sabnzbdplus/cherrypy/wsgiserver/__init__.py", line 914, in sendall
bytes_sent = self.send(data)
File "/usr/share/sabnzbdplus/cherrypy/wsgiserver/__init__.py", line 1117, in send
return self._safe_call(False, super(SSL_fileobject, self).send, *args, **kwargs)
File "/usr/share/sabnzbdplus/cherrypy/wsgiserver/__init__.py", line 1096, in _safe_call
raise FatalSSLAlert(*e.args)
FatalSSLAlert: [('SSL routines', 'SSL3_GET_MESSAGE', 'excessive message size')]


Does it ring a bell?
Please? Anybody?

Thanks

Will look into it. Doesn't ring a bell instantly, though.

-Stefan

WhoCares? wrote:
Will look into it. Doesn't ring a bell instantly, though. -Stefan

Thank you for your time. Note that I am using the latest versions of everything.

Manually installed?

-Stefan

WhoCares? wrote:
Manually installed? -Stefan

If by manually you mean first installing Python then the Sabnzbd bin from the ReadyNas Pro admin web page then yes.

No, I meant whether you tried to install Python and SABnzbd on your own. Anyway, this behavior seems to be caused by a bug in OpenSSL as you can read here.
Unfortunately there isn't much I can do about this other than installing a replacement openssl library with SABnzbd/Python. Since openssl is a crucial part of the system I'm quite reluctant to do so but rather would think a fix (if any is deemed necessary) has to come by way of a firmware update from Netgear. Now I'm fully aware that fixing problems with a third party add-on probably isn't on top of the todo list so my best advice for now is to restart SABnzbd frequently. I could also add a cron job to do just that to future releases if that would be ok as a workaround.

-Stefan

WhoCares? wrote:

No, I meant whether you tried to install Python and SABnzbd on your own. Anyway, this behavior seems to be caused by a bug in OpenSSL as you can read here. Unfortunately there isn't much I can do about this other than installing a replacement openssl library with SABnzbd/Python. Since openssl is a crucial part of the system I'm quite reluctant to do so but rather would think a fix (if any is deemed necessary) has to come by way of a firmware update from Netgear. Now I'm fully aware that fixing problems with a third party add-on probably isn't on top of the todo list so my best advice for now is to restart SABnzbd frequently. I could also add a cron job to do just that to future releases if that would be ok as a workaround. -Stefan

Too bad. I kinda liked the idea of running all my downloads straight from the NAS.
Anyway, I will go back to running it from my HTPC and wait for another more stable version.
Thanks for your support.

WhoCares? wrote:

No, I meant whether you tried to install Python and SABnzbd on your own. Anyway, this behavior seems to be caused by a bug in OpenSSL as you can read here. Unfortunately there isn't much I can do about this other than installing a replacement openssl library with SABnzbd/Python. Since openssl is a crucial part of the system I'm quite reluctant to do so but rather would think a fix (if any is deemed necessary) has to come by way of a firmware update from Netgear. Now I'm fully aware that fixing problems with a third party add-on probably isn't on top of the todo list so my best advice for now is to restart SABnzbd frequently. I could also add a cron job to do just that to future releases if that would be ok as a workaround. -Stefan

You know, when I reverted back to the HTPC i also had some weird behavior involving SSL. It disappeared only after i deleted all my old Sabnzbd certificates from IE8 and Firefox.
I am wondering if.....
P.S: What about the new issue of SabNzbd v.0.5.5?

Well, you know, a day has just 24 hours and even if I'd add the night ... in short: when time permits ;)

-Stefan

WhoCares? wrote:
Well, you know, a day has just 24 hours and even if I'd add the night ... in short: when time permits ;) -Stefan

Of course. But what do you think about SSL?
Maybe I should try again and this time i will clean up certificates.
But before I go through all the procedure, do you think that a bad certificate on a browser accessing the NAS could crash the Sabnzbd daemon on the NAS?