On Nov 19, 12:30 am, Nakedsteve <[email protected]> wrote:
> Alright, so I'm now trying to get it to work with mod_wsgi (still with
> no luck, might I add)
>
> Here's my sites-available config:
>
> WSGIScriptAlias /test /var/www/webpy/testapp/main.py/
The web.py documentation is wrong. There should be no trailing slash
on last argument.
> AddType text/html .py
> <Directory /var/www/webpy/testapp/>
> Order deny,allow
> Allow from all
> </Directory>
>
> And this gives me another 500 error, putting the following into
> error.log
>
> [Wed Nov 18 13:27:34 2009] [warn] mod_wsgi: Compiled for Python/2.6.2.
> [Wed Nov 18 13:27:34 2009] [warn] mod_wsgi: Runtime using Python/
> 2.6.4rc2.
Difference normally doesn't matter. Read the documentation about it:
http://code.google.com/p/modwsgi/wiki/InstallationIssues
> [Wed Nov 18 13:27:34 2009] [warn] mod_wsgi: Python module path '/usr/
> lib/python2.6/:/usr/lib/python2.6/plat-linux2:/usr/lib/python2.6/lib-
> tk:/usr/lib/python2.6/lib-old:/usr/lib/python2.6/lib-dynload'.
> [Wed Nov 18 13:27:34 2009] [notice] Apache/2.2.12 (Ubuntu) PHP/
> 5.2.10-2ubuntu6 with Suhosin-Patch mod_wsgi/2.5 Python/2.6.4rc2
> configured -- resuming normal operations
> [Wed Nov 18 13:27:36 2009] [error] [client 168.170.197.90] Premature
> end of script headers: main.py
Because your script is not being executed by mod_wsgi but still as a
CGI script.
You likely have a conflicting cgi-script definition for .py extension.
Use a .wsgi extension for WSGI script files and likely you would have
had no problems.
I would really suggest that if you want to use mod_wsgi you follow
exactly the mod_wsgi documentation on the mod_wsgi site to get a
simple hello world example working independent of any framework. See:
http://code.google.com/p/modwsgi/wiki/QuickConfigurationGuide
Graham
> So the warnings are telling me that the python version that wsgi was
> compiled for is older than the current runtime, could that be causing
> the problem?
>
> On Nov 16, 9:25 pm, Graham Dumpleton <[email protected]>
> wrote:
>
>
>
> > On Nov 15, 9:18 am, vlatko <[email protected]> wrote:
>
> > > try this line
>
> > > WSGIScriptAlias /test "/var/www/webpy/testapp/"
> > > AddType text/html .py
>
> > > change ScriptAlias with WSGIScript
> > > and test
>
> > There has been no indication that he is using mod_wsgi so that will
> > not help.
>
> > That WSGIScriptAlias line is wrong anyway. If the final argument is a
> > directory and you are intending all script files in the directory to
> > be interpreted as being for mod_wsgi, it should be:
>
> > WSGIScriptAlias /test/ /var/www/webpy/testapp/
>
> > If the final argument is a WSGI script file, it should be:
>
> > WSGIScriptAlias /test /var/www/webpy/testapp
>
> > You should not have a trailing slash on final argument if its is a
> > script file. If it is required for some reason, then web.py is not
> > honouring WSGI request variables properly or is otherwise broken in
> > respect of handling trailing slash redirects.
>
> > I have pointed out before that web.py wiki documentation on mod_wsgi
> > is wrong in this respect.
>
> > Anyway, as mentioned above, he is not trying to use mod_wsgi and is
> > instead using CGI as was confirmed from a prior test.
>
> > The stack trace originally provided suggests that FASTCGI code in
> > web.py is being triggered instead of CGI code.
>
> > Graham
--~--~---------~--~----~------------~-------~--~----~
You received this message because you are subscribed to the Google Groups
"web.py" 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/webpy?hl=en
-~----------~----~----~----~------~----~------~--~---
