issues with MM3 / Apache mod_wsgi errors
Hello all,
Mark Sapiro helped me with some basic config issues earlier but now i'm stuck here; my web browser shows me:
"Service Unavailable
The server is temporarily unable to service your request due to maintenance downtime or capacity problems. Please try again later."
my server's apache postorius error log shows me:
[Tue Oct 06 15:52:34.961249 2015] [:error] [pid 11691] (13)Permission denied: [client <IP>:42590] mod_wsgi (pid=11691): Unable to connect to WSGI daemon process 'hyperkitty' on '/run/httpd/wsgi.11685.0.1.sock' after multiple attempts.
this occurs when i try to access: /hyperkitty/
if i try /postorius/, i see same browser result and similar apache log result:
[Tue Oct 06 15:58:53.355159 2015] [:error] [pid 11693] (13)Permission denied: [client <IP>:42654] mod_wsgi (pid=11693): Unable to connect to WSGI daemon process 'postorius' on '/run/httpd/wsgi.11685.0.2.sock' after multiple attempts.
MM3 components installed from hyperkitty-el.repo and using apache 2.4.6 on centos 7. python 2.7 and 3.4 installed.
What's missing here? Thanks all.
- Fabe S.
Are you sure the sockets exist? If they exist, what are their permissions? Do they belong to the same user as apache is using?
You might want to look at the wsgi logs as well to see if the python application is the culprit.
You can check out my deployment instructions 1 using nginx and uwsgi. It might help you with debugging the issue
Are you sure the sockets exist? If they exist, what are their permissions? Do they belong to the same user as apache is using?
You might want to look at the wsgi logs as well to see if the python application is the culprit.
You can check out my deployment instructions 1 using nginx and uwsgi. It might help you with debugging the issue
participants (3)
-
fsantiago＠deviltracks.net -
fsantiago＠garbage-juice.com -
Simon Hanna