thanks for the update, Chris, and for your notes... On Tue, Sep 8, 2009 at 9:08 PM, Chris S <[email protected]> wrote:
> > Well I uninstalled, reinstalled and still no go. > > I finally uninstalled Python 2.6 and downloaded 2.5.4 and the mod_wsgi > listed in the manual. Didn't change my Apache config files at all and > bingo everything started right up. I get the Apache page with http:// > and the Web2py page with https://. > > So I guess that does it for me, I'll just reinstall the modules I need > for python and I should be set, as long as it wasn't one of those > modules that broke 2.6.2 in the first place. Gee I kind of wish I > haden't said that now... > > As a side note. Now that I do have it running I can verify. The > manual says on the windows install to use server.key for the SSL key. > However, Apache doesn't support encrypted keys on windows so the > server.pem must be used. Additionally you need to go into the /conf/ > extra folder and comment out the "SSLPassPhraseDialog builtin" line > in httpd-ssl.conf file. > > Add those two small additions, and using Python 2.5.4 on windows with > Apache and WSGI couldn't have been easier. It was just finding my way > through the SSL and this python version thing thats taken some time. > > On Sep 8, 7:31 pm, Yarko Tymciurak <[email protected]> wrote: > > On Tue, Sep 8, 2009 at 7:25 PM, Chris S <[email protected]> wrote: > > > > > "You should reinstall your Python installation. This time use latest > > > version of Python 2.6 available and ensure that you install it for > > > all > > > users and not just yourself. That should resolve the issue. " > > > > > Hu, I just downloaded the Python 2.6.2 install on this machine > > > yesterday. I can't imagine it's not the newest version. I'll remove > > > and reinstall to verify with certainty that it's installed for all > > > users though I'm sure that's how I installed it. Hopefully, that's > > > all it is. I'll do a reinstall and see if that helps. Meanwhile I'm > > > open to suggestions as I'm skeptical that it's the python install. > > > > > Unless I've got to update a module in the Python 2.6.2 install > > > manually possibly? > > > > ... no, it's more likely what Graham said.... > > > > or if you installed more than one python version, I forget how it is on > > Windows - I think it updates the registry to the last one installed (that > > is, if you installed 2.5 after, it would be the default - you were > pulling > > in something from 2.5 - so either installation order, or not for all > users - > > either of those would make sense). > > > > > > > > > > > > > On Sep 8, 6:36 pm, Yarko Tymciurak <[email protected]> wrote: > > > > ....development and testing.... and there's no setup needed (which is > the > > > > real benefit; just run...) > > > > > > On Tue, Sep 8, 2009 at 6:35 PM, Yarko Tymciurak <[email protected]> > > > wrote: > > > > > cerrypy is fine for development... www.web2py.pyIbelieve uses the > > > > > builtin cherrypy. > > > > > For handling volumes of requests you may want to go with > alternatives. > > > > > > > On Tue, Sep 8, 2009 at 6:06 PM, Chris S <[email protected]> > > > wrote: > > > > > > >> I'm using 2.6.2 as my actual Python install. I'm guessing the > > > > >> mod_wsgi is compiled for python 2.6.1. Are you saying finding a > new > > > > >> mod_wsgi would allow me to run with python 2.6.2? > > > > > > >> I can look at the cherrypy but every step of the way the > instructions > > > > >> indicate over and over that Apache would be better, so I didn't > see a > > > > >> reason to try and setup with just cherrypy. When does the > crossover > > > > >> between needing to run with Apache and being ok with Cherrypy > occure? > > > > > > >> If Python is the issue I guess I can consider downgrading to 2.5.4 > and > > > > >> reinstalling all of my modules for 2.5. I was just sure someone > would > > > > >> have a way to make these work together. I've been looking for a > way > > > > >> to just make Apache use the Python 2.5 so my PATH can still use > the > > > > >> 2.6 but I'm not getting anywhere with that either. > > > > > > >> On Sep 8, 5:47 pm, Yarko Tymciurak <[email protected]> wrote: > > > > >> > Python 2.6.1 had errors; you need to use at least 2.6.2; > > > > > > >> > Anyway, web2py has cherrypy built in, so you should be able to > serve > > > > >> just by > > > > >> > running (for example): > > > > > > >> > python2.6 web2py.py -a 'my_admin_password' > > > > > > >> > python web2py.py -h > > > > > > >> > will list other command line options (port 8000 is default, for > > > > >> example). > > > > > > >> > - Yarko > > > > > > >> > On Tue, Sep 8, 2009 at 4:26 PM, Chris S < > [email protected]> > > > > >> wrote: > > > > > > >> > > So I'm afraid I know my answer but I'll check just to see. > I'm > > > > >> > > running Windows XP, and Python 2.6 and wanted to try Web2py as > I > > > just > > > > >> > > recently found it. I've been following the instruction > document > > > to > > > > >> > > set up Apache 2.2 and Web2py together. > > > > > > >> > > Currently, the Apache server starts and my config file is > what's > > > > >> > > litsed in the instruction manual (with the exception of using > > > > >> > > server.pem instead of server.key which I think is an error in > the > > > > >> > > instructions). I can see the "It Worked" webpage from Apache > but > > > if I > > > > >> > > use https:// to access the computer I get a 500 Internal > server > > > > >> error. > > > > > > >> > > Looking into the Apache log I find: > > > > > > >> > > [Tue Sep 08 16:01:13 2009] [warn] mod_wsgi: Compiled for > Python/ > > > > >> 2.6.1. > > > > >> > > [Tue Sep 08 16:01:13 2009] [warn] mod_wsgi: Runtime using > Python/ > > > > >> > > 2.6.2. > > > > >> > > [Tue Sep 08 16:01:13 2009] [warn] mod_wsgi: Python module path > > > 'C:\ > > > > >> > > > \WINDOWS\\system32\\python26.zip;C:\\Python26\\Lib;C:\\Python26\ > > > > >> > > \DLLs;C:\\Python26\\Lib\\lib-tk;;C:\\Program Files\\Apache > > > Software > > > > >> > > Foundation\\Apache2.2\\bin'. > > > > >> > > [Tue Sep 08 16:01:13 2009] [notice] Child 2380: Child process > is > > > > >> > > running > > > > >> > > [Tue Sep 08 16:01:13 2009] [notice] Child 2380: Acquired the > start > > > > >> > > mutex. > > > > >> > > [Tue Sep 08 16:01:13 2009] [notice] Child 2380: Starting 64 > worker > > > > >> > > threads. > > > > >> > > [Tue Sep 08 16:01:13 2009] [notice] Child 2380: Starting > thread to > > > > >> > > listen on port 443. > > > > >> > > [Tue Sep 08 16:01:13 2009] [notice] Child 2380: Starting > thread to > > > > >> > > listen on port 80. > > > > >> > > [Tue Sep 08 16:01:17 2009] [error] [client 192.168.1.1] > mod_wsgi > > > > >> > > (pid=2380): Target WSGI script 'C:/web2py/wsgihandler.py' > cannot > > > be > > > > >> > > loaded as Python module. > > > > >> > > [Tue Sep 08 16:01:17 2009] [error] [client 192.168.1.1] > mod_wsgi > > > > >> > > (pid=2380): Exception occurred processing WSGI script > 'C:/web2py/ > > > > >> > > wsgihandler.py'. > > > > >> > > [Tue Sep 08 16:01:17 2009] [error] [client 192.168.1.1] > Traceback > > > > >> > > (most recent call last): > > > > >> > > [Tue Sep 08 16:01:17 2009] [error] [client 192.168.1.1] File > > > "C:/ > > > > >> > > web2py/wsgihandler.py", line 24, in <module> > > > > >> > > [Tue Sep 08 16:01:17 2009] [error] [client 192.168.1.1] > import > > > > >> > > gluon.main > > > > >> > > [Tue Sep 08 16:01:17 2009] [error] [client 192.168.1.1] File > > > "gluon\ > > > > >> > > \main.py", line 15, in <module> > > > > >> > > [Tue Sep 08 16:01:17 2009] [error] [client 192.168.1.1] > import > > > cgi > > > > >> > > [Tue Sep 08 16:01:17 2009] [error] [client 192.168.1.1] File > > > "C:\ > > > > >> > > \Python26\\Lib\\cgi.py", line 40, in <module> > > > > >> > > [Tue Sep 08 16:01:17 2009] [error] [client 192.168.1.1] > import > > > > >> > > urllib > > > > >> > > [Tue Sep 08 16:01:17 2009] [error] [client 192.168.1.1] File > > > "C:\ > > > > >> > > \Python26\\Lib\\urllib.py", line 26, in <module> > > > > >> > > [Tue Sep 08 16:01:17 2009] [error] [client 192.168.1.1] > import > > > > >> > > socket > > > > >> > > [Tue Sep 08 16:01:17 2009] [error] [client 192.168.1.1] File > > > "C:\ > > > > >> > > \Python26\\Lib\\socket.py", line 46, in <module> > > > > >> > > [Tue Sep 08 16:01:17 2009] [error] [client 192.168.1.1] > import > > > > >> > > _socket > > > > >> > > [Tue Sep 08 16:01:17 2009] [error] [client 192.168.1.1] > > > ImportError: > > > > >> > > Module use of python25.dll conflicts with this version of > Python. > > > > > > >> > > More looking around I've verified that my mod_wsgi.so is > complied > > > for > > > > >> > > Python2.6 (if I use the 3.0 or 2.5 versions Apache doesn't > start). > > > So > > > > >> > > I'm fairly sure that's ok. The manual does say it is assumed > you > > > are > > > > >> > > using Python 2.5, but I'm already running 2.6 and the front > page > > > says > > > > >> > > it runs on 2.6. Is there an exception for running Apache with > > > WSGI > > > > >> > > which requires I run version 2.5 of python? > > > > > > >> > > If so can I keep my 2.6 install for scripts I'm already > running > > > > >> > > (unrelated to web2py) or do I have to reinstall everything for > > > python > > > > >> > > 2.5 in order to run with web2py/apache/WSGI/windows? > > > > > > >> > > I've been searching for hours so I've finally just decided to > ask. > > > --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "web2py-users" group. To post to this group, send email to [email protected] To unsubscribe from this group, send email to [email protected] For more options, visit this group at http://groups.google.com/group/web2py?hl=en -~----------~----~----~----~------~----~------~--~---
