Back again.... Had to replace a main drive and I am in the middle of reinstalling Moviegrabber. When launched I am getting a cherrypy error below. Any idea on what is going on?
Mini:moviegrabber roontoon$ python moviegrabber.py
[13/Jan/2012:20:13:09] ENGINE Listening for SIGHUP.
[13/Jan/2012:20:13:09] ENGINE Listening for SIGTERM.
[13/Jan/2012:20:13:09] ENGINE Listening for SIGUSR1.
[13/Jan/2012:20:13:09] ENGINE Bus STARTING
[13/Jan/2012:20:13:09] ENGINE Started monitor thread '_TimeoutMonitor'.
[13/Jan/2012:20:13:09] ENGINE Started monitor thread 'Monitor'.
[13/Jan/2012:20:13:10] ENGINE Error in HTTP server: shutting down
Traceback (most recent call last):
File "/Library/WebServer/Documents/moviegrabber/lib/site-packages/cherrypy/process/servers.py", line 187, in _start_http_thread
self.httpserver.start()
File "/Library/WebServer/Documents/moviegrabber/lib/site-packages/cherrypy/wsgiserver/wsgiserver2.py", line 1824, in start
raise socket.error(msg)
error: No socket could be created
[13/Jan/2012:20:13:10] ENGINE Bus STOPPING
[13/Jan/2012:20:13:10] ENGINE HTTP Server cherrypy._cpwsgi_server.CPWSGIServer(('192.168.0.6', 9191)) already shut down
[13/Jan/2012:20:13:10] ENGINE Stopped thread '_TimeoutMonitor'.
[13/Jan/2012:20:13:10] ENGINE Stopped thread 'Monitor'.
[13/Jan/2012:20:13:10] ENGINE Bus STOPPED
[13/Jan/2012:20:13:10] ENGINE Bus EXITING
[13/Jan/2012:20:13:10] ENGINE Bus EXITED
hi roontoon, this is the crutial part of the traceback:-
error: No socket could be created
the issue is due to a invalid or incorrectly set ip address, are you sure you have the ip address 192.168.0.6 set for your nic?, i would of thought you would of used the more usual 192.168.1.x where x is your specified host ip. if you have set it incorrectly then you will need to go into the "configs" folder and open webconfig.ini with your favorite text editor and modify the following line:-
server.socket_host = "192.168.0.6"
just change the ip address to the ip address you have set for your nic, save and it should then work.
one other thing to note, you may be using dhcp on your machine, this is going to cause issues with moviegrabber as your ip address could change and thus cherrypy may error again, best to set it to a static ip if its not already done.
binhex wrote:hi roontoon, this is the crutial part of the traceback:-
error: No socket could be created
the issue is due to a invalid or incorrectly set ip address, are you sure you have the ip address 192.168.0.6 set for your nic?, i would of thought you would of used the more usual 192.168.1.x where x is your specified host ip. if you have set it incorrectly then you will need to go into the "configs" folder and open webconfig.ini with your favorite text editor and modify the following line:-
server.socket_host = "192.168.0.6"
just change the ip address to the ip address you have set for your nic, save and it should then work.
one other thing to note, you may be using dhcp on your machine, this is going to cause issues with moviegrabber as your ip address could change and thus cherrypy may error again, best to set it to a static ip if its not already done.
Thanks got this fixed. Had the wrong IP address in the config file. BUT I am still getting the error referenced here
I had "thought" I had fixed it but the problem I was having with my machine may have fooled me. This is a TOTALLY clean install of Lion. All other apps (Sabnzdb, SickBeard, CouchPotato v2, and v1, Headphones) are currently running without the exception error. I will get the exception error every single time I try to launch MovieGrabber. The little bit of research that I have done leads me to believe that it is something in your includes library that has been compiled with a 32bit version of the compiler. Lion and I think python on lion is totally 64bit. But that is far as I can guess. But with out a doubt in my mind there is a problem somewhere in MovieGrabber. I would be more that willing to test anything that you come up with but anything in terms of the code I am out of my depth there.
hi roontoon, you sure this isnt the same issue you had previously of having two different versions of python on the machine?, i have done a quick google and somebody else has a very similar issue which was related to having python 2.7.1 and 2.7.2 on the machine at the same time.
binhex wrote:hi roontoon, you sure this isnt the same issue you had previously of having two different versions of python on the machine?, i have done a quick google and somebody else has a very similar issue which was related to having python 2.7.1 and 2.7.2 on the machine at the same time.
its possible that python 2.6.x (which CP, SB, and HP uses i believe) isnt as sensitive to this as python 2.7.x.
let me know if this fixes it.
Positive. The link you sent me is from me trying to figure out what my problem was on my mini before I did the clean install. Small world. I had an older version of the OS on the mini before which had 2.5 on it. On a mac you have the "apple" installed version of python and then you have any other version of python the the user installed. So you could have 2.5, 2.6, 2.7 all on the same machine with aliases pointing to the current version. But if you explicitly called python 2.6 as in python2.6 moviegrabber.py so you could test on different versions of python. That is why I emphasized the fact that this was a clean install. But just in case I will have a look see at the machine tonight when I get home. Also will do some more research on the exception error. Generally an exception error of this sort is referring to a compiled part of any program. But I am pretty sure at this point it has to do with a compiled library.
From the traceback, it appears that there is a problem with Python's
_scproxy module; that's an internal helper C module that provides an
interface to the OS X System Configuration framework to access Internet
proxy configurations for the urllib module. You should open an issue
for this at bugs.python.org. Please include the original crash report
traceback.
First off I have to say Amazing job on this program. I'm using it with no errors as far as I can tell. I have my settings pretty high so it downloads movies occasionaly. I'm pretty sure I all ready know the answer but I'll ask anyway.
Is there any way to have it search the entire nzb matrix site instead of just new posts. I have like 2000 movies and I dont remember every movie I have so its a pain to look thru the files before I download a movie. thats why I love moviegrabber.
hi compz, glad your enjoying moviegrabber :-), im afraid the answer right now is no backfill searching, the reasoning behind this is to stop undue load on the index sites, obviously searching an entire index site will put quite a strain and will take an extensive amount of time, the other concern is the number of potential nzb files downloaded which may exceed the permitted amount in 24 hours.
i may revisit this once i have finished re-coding the download module as this will then link to the nzb file as opposed to downloading (for queued items) and thus wont count towards your daily downloaded limit.
Loving this program since i installed a few months back. Appreciate all the work that you have put into it binhex.
Upgraded to the latest version a week or so ago and now the checking for already downloaded movies seems to be broken. Alot of movies that I allready have are being requeued.
All my movies are on 2 network shares that have been mapped to drives on this machine and are all in separate folders using IMDB name + year.
I have reinstalled python and MG and still can't get it to work again.
I have the following set in my config. Any idea what could be wrong?
hi boundo, quick question for you firstly, when you say "and are all in separate folders using IMDB name + year" do you literally mean The Movie 2009
if so then the issue is your missing round brackets for the year, just to confirm a matching title should be:-
hi boundo, ok just done some quick testing and this looks to be a bug, looks like i forgot to escape the brackets when having append year to title, my bad :-(, will have this fixed in 2.1.4 which should be out by mid to end of this week.
It seems that I also have the problem with python crashing unexpectedly. It seems that if I restart MovieGrabber a few times (randomly) then the first time i hit "run now" it works - but every subsequent time it will crash python.
It worked about two times over a total of ~20 restarts of the program. It seems I more or less have the same errors as the ones posted above (from the warning logs it's stating im running with -p, when I'm not, and also receiving "28/01/2012 01:25:40 Warning Poster Download, the _imaging C module is not installed" as an error.
Not exactly sure where to head from here, but that's just the basic information I figure I need to provide.
