On 13/01/2010 02:15, Graham Dumpleton wrote:
2010/1/13 mog<[email protected]>:
Just trying to do these things, but it doesn't like the WSGIVerboseLogging
directive. No matter where I put it, Apache complains about it being there
and wont start up.
Should I proceed with the test without it? Or?
Sorry, should be WSGIVerboseDebugging.
You do need mod_wsgi 3.0+ however.
No worries, both log levels are set.
Here goes... *waits for it to time out*
This is from the main Apache httpd-error log file:
[Wed Jan 13 02:16:28 2010] [notice] Apache/2.2.14 (FreeBSD)
mod_ssl/2.2.14 OpenSSL/0.9.8e DAV/2 mod_wsgi/3.1 Python/2.6.4 PHP/5.2.12
with Suhosin-Patch configured -- resuming normal operations
[Wed Jan 13 02:16:28 2010] [info] Server built: Jan 8 2010 14:09:05
[Wed Jan 13 02:16:28 2010] [debug] prefork.c(1013): AcceptMutex: flock
(default: flock)
[Wed Jan 13 02:16:28 2010] [info] mod_wsgi (pid=93063): Initializing Python.
[Wed Jan 13 02:16:28 2010] [info] mod_wsgi (pid=93064): Initializing Python.
[Wed Jan 13 02:16:28 2010] [info] mod_wsgi (pid=93062): Initializing Python.
[Wed Jan 13 02:16:28 2010] [info] mod_wsgi (pid=93065): Initializing Python.
[Wed Jan 13 02:16:28 2010] [info] mod_wsgi (pid=93061): Attach
interpreter ''.
[Wed Jan 13 02:16:28 2010] [info] mod_wsgi (pid=93065): Attach
interpreter ''.
[Wed Jan 13 02:16:28 2010] [info] mod_wsgi (pid=93063): Attach
interpreter ''.
[Wed Jan 13 02:16:28 2010] [info] mod_wsgi (pid=93064): Attach
interpreter ''.
[Wed Jan 13 02:16:28 2010] [info] mod_wsgi (pid=93062): Attach
interpreter ''.
<Apache start-up was complete at this point>
[Wed Jan 13 02:18:31 2010] [debug] mod_wsgi.c(11882): mod_wsgi
(pid=93061): Request server was 'test.elasticmind.net|0'.
[Wed Jan 13 02:18:31 2010] [info] mod_wsgi (pid=93071): Initializing Python.
[Wed Jan 13 02:18:31 2010] [info] mod_wsgi (pid=93071): Attach
interpreter ''.
<The above is what happened when I made the request>
[Wed Jan 13 02:23:31 2010] [debug] mod_wsgi.c(11882): mod_wsgi
(pid=93064): Request server was 'test.elasticmind.net|0'.
<The above is the result from the request timing out I think>
This is all the virtual host log-file said in the time period:
[Wed Jan 13 02:23:31 2010] [error] Script timed out before returning
headers: saweb.wsgi
Sorry this doesn't seem very useful at all to me, but it's literally all
there is :(
I am, however, building a jail so I've got a completely clean testing
environment to work with. I will set Apache and mod_wsgi up in there and
see what happens. If it's just an environmental thing it should work in
that.
With thanks,
mog
--
You received this message because you are subscribed to the Google Groups
"modwsgi" 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/modwsgi?hl=en.
