Graham Dumpleton

Impossible to tell from the information you have provided. What do you mean by "but request never dies and waiting for response"? Do you mean never returns a response and...

As explained in that document I pointed you at, add: ``` WSGIApplicationGroup %{GLOBAL} ``` It is always recommended to use this and combats problems with third party Python packages that...

Did you run `configure` first? You should be using: ``` ./configure make install ``` Only the `make` command would need `sudo` if indeed root access was need to copy Apache...

What operating system vendor/version is this? It appears their Python distribution is compiled in a way that prohibits embedding.

Can't really help too much. Obviously something about that custom kernel blocks standard loadable shared objects from being loaded. Likely you would need to build mod_wsgi from source code and...

Run it with the ``--help`` option and you will see all the options you can pass, including ``--request-timeout``. Also watch: * https://www.youtube.com/watch?v=CPz0s1CQsTE

Maybe. As noted in that video the default request timeout is 60 seconds, although it isn't as simple as that when using multithreaded daemon process. Be aware that unless you...

The stack trace to me suggests that the application is blocking on reading request content from the client. This could be because the client has not sent as much data...

Read: * https://modwsgi.readthedocs.io/en/master/user-guides/application-issues.html#access-rights-of-apache-user * https://modwsgi.readthedocs.io/en/master/user-guides/application-issues.html#application-working-directory Permissions access is usually going to be due to one of those issues.

The `pip` method is the correct method. The docs is old and needs to be corrected as it referred to an installation method that was stopped being used some time...