2010/1/13 mog <[email protected]>: > 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.
Not a lot, but jogged my memory over what this may be. It has come up once, maybe twice before only and is in part why mod_wsgi was changed to generate a timeout like that. What was occurring in prior case, which was investigated a bit, was that the Apache server child process was getting a successful result for connecting to the listener socket of the daemon process and so started proxying the request, but on the daemon side it was never getting any indication at all that a connection had been received and hadn't even accepted a connection. Thus daemon process was just sitting there not doing anything yet the Apache server child process was waiting for a response. In the main case where this happened before it was only happening every so often and not every time as seems to be your case. There was suspicion over another case like yours where it happened every time but don't remember the outcome of that. It is possible they just gave up and went away without providing opportunity to debug it, or that they rebuilt lots of stuff and it went away, I just can't remember. One discussion about prior issue is: http://groups.google.com/group/trac-dev/browse_frm/thread/bcaedbbb7fe5b6c Unfortunately people don't always get back to me about whether issue indeed went away or what they worked out the problem was. In this case all I could do was to patch the code to make it more tolerant of unexpected behaviour. Give me a little while to think about this. I may put some more debugging in code and get you to compile up a version from head of subversion repository. Graham
-- 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.
