Tag Info

New answers tagged

0

I ran into the same issue. According to this thread, Alias always superseed WSGIScriptAlias. However, according to modwsgi documentation, it could be replaced by a standard Alias directive. Solution to your issue would be something like below. Note that /stuff is defined before / Alias /stuff /foo/foo/wsgi.py WSGIPythonPath /foo <Directory ...


0

To anyone else having this issue, read the following: https://code.google.com/p/modwsgi/wiki/ConfigurationIssues I resolved my issues by appending the following in my httpd.conf: WSGISocketPrefix /var/run/wsgi


1

You are trying to use a version of lxml compiled against one installation of Python against a different Python installation. The two Python installations are not the same. Specifically the one lxml was compiled against had 16 bit Unicode character width specified when Python itself was compiled. The Python run time being used though was compiled for 32 but ...


-1

In apache, stablish the path to the python executable using the directive WSGIPythonHome: WSGIPythonHome /home/jenkins/local/bin/


0

Managed to solve the problem by installing all with 64 bits version.


2

Use preloading to force load the application when the process starts up rather than relying on the default of lazy loading on first request for the application. If using a sufficiently new enough version of mod_wsgi, instead of using: WSGIDaemonProcess xxx WSGIProcessGroup xxx WSGIApplicationGroup %{GLOBAL} WSGIScriptAlias / /some/path/wsgi.py Use: ...



Top 50 recent answers are included