2011-03-14, 12:15
compcentral Wrote:anyone?What exactly are you trying to post? Links often will be recognized as such. In Tracking-Systems Links are normally treated as SPAM.
acribb Wrote:Great app.Retention? How old are the files on nzb.su and what is your retention-setting in CP?
It's looking for the 1080p version. When you look directly at the nzb.su api url that CouchPotato is searching, you can clearly see several 1080p versions, one a director's cut, the other the original cut.
Why does CouchPotato not find it?
krestim Wrote:No, it will not. It runs separately from your browser.This is a rather interesting problem. I know the behaviour from Unix-System whereas Sickbeard (subsequently the cherrypy-Webserver) has to run with root-priviliges in order to fire up the webserver. Did you try run the executable as Administrator?
I've got the same issue that a few other posters have had earlier in this thread, but can't seem to figure it out:
Code:16:41:13 ERROR [ ENGINE] Shutting down due to error in start listener:
Traceback (most recent call last):
File "..\build\pyi.win32\CouchPotato\outPYZ1.pyz/cherrypy.process.wspbus", line 213, in start
File "..\build\pyi.win32\CouchPotato\outPYZ1.pyz/cherrypy.process.wspbus", line 193, in publish
ChannelFailures: IOError("Port 5000 not free on '0.0.0.0'",)
I have ran netstat -a -b and there is nothing running on port 5000. I've tried numerous other ports with no change in results. I've tried inputting "localhost" as well as the server's actual IP "192.168.1.50" with no change either.
The interesting thing is that going back through the logs, this isn't the first time its happened, and the next try, CP would start again. That doesn't seem to be the case anymore. A similar issue exists for me with Sickbeard, as if I upgrade to the newest version, it won't start because it thinks something is already running on port 8082. If I roll back to Sickbeard 478, there is no issues.
I am running SABNzbd (8080), Sickbeard (8082) and Couchpotato (5000) on WHS 2003. Any suggestions are appreciated
I am pretty sure this has to do with framework-change in either the cherrypy or the cheetahtemplates...
Another possibility for you would try running it from the source. You would have to install the Python-Runtime and subsequent dependencies (like cherrypy and cheetahtemplates), but you should be able to run it via a command-line then (that is what I do... I never had problems similiar to yours)