On my old server with Apache2.2 I use mod_wsgi without problems. On my new server with apache2.4 I cannot get mod_wsgi working properly in daemon mode.
In directory /var/logs the wsgi socket files are created normally, but there seems to be a problem reading those socket files. Running mod_wsgi in daemon mode gives errors like this:
mod_wsgi (pid=18561): Unable to connect to WSGI daemon process 'username' on '/var/run/apache/wsgi.18555.0.2.sock'.
On de mod_wsgi I have checked my configuration files, and everything seems to be ok. Anybody a hint of what can go wrong here? (like too strict security options)
Are there big change in apache2.2 --> apache2.4 what could cause this problems?
In directory /var/logs the wsgi socket files are created normally, but there seems to be a problem reading those socket files. Running mod_wsgi in daemon mode gives errors like this:
mod_wsgi (pid=18561): Unable to connect to WSGI daemon process 'username' on '/var/run/apache/wsgi.18555.0.2.sock'.
On de mod_wsgi I have checked my configuration files, and everything seems to be ok. Anybody a hint of what can go wrong here? (like too strict security options)
Are there big change in apache2.2 --> apache2.4 what could cause this problems?