mod_wsgi unresponsive

[Demetrio Girardi]

I have a django project which is running fine on apache 2.2 with
python 2.6 and mod_wsgi.

I need to upgrade to python 2.7. I made a separate installation of
apache, python and mod_wsgi for this purpose. mod_wsgi is unresponsive
- requests are not served and eventually timeout, as if python was
freezing. Apache's access log is empty. The error log follows. I don't
know if there is some other log file I can look to get more clues?


[Thu Feb 09 08:54:46 2012] [warn] mod_wsgi: Compiled for Python/2.7.
[Thu Feb 09 08:54:46 2012] [warn] mod_wsgi: Runtime using Python/
2.7.2.
[Thu Feb 09 08:54:46 2012] [notice] Apache/2.2.22 (Win32) mod_wsgi/3.3
Python/2.7.2 configured -- resuming normal operations
[Thu Feb 09 08:54:46 2012] [notice] Server built: Jan 28 2012 11:16:39
[Thu Feb 09 08:54:46 2012] [notice] Parent: Created child process 7540
[Thu Feb 09 08:54:46 2012] [debug] mpm_winnt.c(477): Parent: Sent the
scoreboard to the child
[Thu Feb 09 08:54:46 2012] [warn] mod_wsgi: Compiled for Python/2.7.
[Thu Feb 09 08:54:46 2012] [warn] mod_wsgi: Runtime using Python/
2.7.2.
[Thu Feb 09 08:54:46 2012] [notice] Child 7540: Child process is
running
[Thu Feb 09 08:54:46 2012] [info] mod_wsgi (pid=7540): Initializing
Python.
[Thu Feb 09 08:54:46 2012] [info] mod_wsgi (pid=7540): Attach
interpreter ''.
[Thu Feb 09 08:54:46 2012] [info] Parent: Duplicating socket 252 and
sending it to child process 7540
[Thu Feb 09 08:54:46 2012] [debug] mpm_winnt.c(398): Child 7540:
Retrieved our scoreboard from the parent.
[Thu Feb 09 08:54:46 2012] [debug] mpm_winnt.c(595): Parent: Sent 1
listeners to child 7540
[Thu Feb 09 08:54:46 2012] [debug] mpm_winnt.c(554): Child 7540:
retrieved 1 listeners from parent
[Thu Feb 09 08:54:46 2012] [notice] Child 7540: Acquired the start
mutex.
[Thu Feb 09 08:54:46 2012] [notice] Child 7540: Starting 64 worker
threads.
[Thu Feb 09 08:54:46 2012] [notice] Child 7540: Starting thread to
listen on port 8080.
[Thu Feb 09 08:55:04 2012] [info] mod_wsgi (pid=7540): Create
interpreter 's-thema2.themaoptical.local:8080|'.
[Thu Feb 09 08:55:04 2012] [info] [client 127.0.0.1] mod_wsgi
(pid=7540, process='', application='s-thema2.themaoptical.local:
8080|'): Loading WSGI script 'C:/Documents and Settings/Administrator/
workspace/thema/thema/apache/django.wsgi'.

[Graham Dumpleton]

Have you tried with a WSGI hello world program rather than with Django
to work out whether a mod_wsgi issues or an issue in Django somehow?

Graham

> --
> You received this message because you are subscribed to the Google Groups "modwsgi" group.
> To post to this group, send email to mod...@googlegroups.com.
> To unsubscribe from this group, send email to modwsgi+u...@googlegroups.com.
> For more options, visit this group at http://groups.google.com/group/modwsgi?hl=en.
>

[Demetrio Girardi]

hello world works, but so does django's development server, hence why I think the culprit is mod_wsgi.

the working installation ships with a ton of DLLs (I assume visual c++ runtimes) both in mod_wsgi's and python2.6's paths. If I remove those, forcing use of system DLLs I presume, the installation behaves like the non-working installation.

Graham Dumpleton <graham.d...@gmail.com> wrote:

>Have you tried with a WSGI hello world program rather than with Django
>to work out whether a mod_wsgi issues or an issue in Django somehow?
>

--
Sent from my Android phone with K-9 Mail. Please excuse my brevity.

[Graham Dumpleton]

If you are only running the one WSGI application, try adding:

WSGIApplicationGroup %{GLOBAL}

It is a magic incantation which gets around problems in third party C
extension modules for Python which are written so as to only work in
main interpreter. If not run in main interpreter they will dead lock
the request thread.

Graham