Page 1 of 1

cherrypy errors in Snow Leopard (mac os x 10.6)

Posted: March 25th, 2010, 6:30 am
by tantalus
Hi. Sorry to spam with another topic.  I tried to search out info, but was unsuccessful.

I'm getting cherrypy errors in my logs that look like this:


2010-03-25 03:37:10,500
ERROR:
[25/Mar/2010:03:37:10]  Traceback (most recent call last):
  File "cherrypy/_cpwsgi.pyc", line 79, in setapp
  File "cherrypy/_cpwsgi.pyc", line 219, in get_response
  File "cherrypy/_cprequest.pyc", line 579, in run
TimeoutError
2010-03-25 03:37:11,052
ERROR:
[25/Mar/2010:03:37:11]  Traceback (most recent call last):
  File "cherrypy/_cpwsgi.pyc", line 79, in setapp
  File "cherrypy/_cpwsgi.pyc", line 219, in get_response
  File "cherrypy/_cprequest.pyc", line 579, in run
TimeoutError
2010-03-25 03:37:14,393

etc...

The program seems to freeze up for an extended period before these show up in my log.

I'm on version 0.5.0 with the plush skin (installed as an app with the installer downloaded from sabnzbd.org) on ipv4
my OS is os x 10.6.2 (hackintosh install, but only minimally modified)
firewall software: little snitch is installed, but sabnzbd is greenlighted and I'm not getting any little snitch notifications.

I was trying to track down what version of cherrypy is expected in v0.5.0.  Maybe I'll have to manually change my cherrypy version?

Any help anyone can offer would be appreciated.
Thank you

Re: cherrypy errors in Snow Leopard (mac os x 10.6)

Posted: March 25th, 2010, 6:54 am
by shypike
No idea, looks that something goes wrong on your system.
The freezing would explain the timeouts.
No use replacing cherrypy, only the embedded version will work.

Re: cherrypy errors in Snow Leopard (mac os x 10.6)

Posted: April 1st, 2010, 3:29 am
by tantalus
For what it's worth, I've solved this problem by deleting all the preference files for sabnzbd (and consequently also emptying the queue) and starting fresh. Everything seems to be smooth sailing now. I'm guessing it was either a corrupted config file somewhere or maybe a malformed nzb file. I am re-adding the nzb files from the backup directory (more slowly this time.  I had another, likely related problem, of high memory usage with a large queue). If one of those nzb files throws another monkey wrench, I should be able to isolate it this time and maybe send it to you devs if you want to look at it.

Thanks for the support. You guys have made a terrific program.