Unable to connect to WSGI daemon process
Mads Kiilerich
mads at kiilerich.com
Sat Aug 1 20:49:41 UTC 2020
On 7/31/20 4:37 PM, Louis Bertrand wrote:
> There was a disconnect between Apache and the Kallithea WSGI daemon process. The WSGI daemon was unable to read the socket. The exact error message in Apache's logs/ssl-errors is
>
> [Thu Jul 30 17:52:34.396927 2020] [wsgi:error] [pid 10169] (13)Permission denied: [client 216.blahblah:58674] mod_wsgi (pid=10169): Unable to connect to WSGI daemon process 'kallithea' on '/var/run/apache2/wsgi.10110.0.1.sock' as user with uid=1003.
>
> where user 1003 is 'hg', the Linux Kallithea user.
>
> Solved by adding
> socket-user=hg
> on the WSGIDaemonProcess line in the Apache WSGI configuration and restarting Apache
This must be when using mod_wsgi. Is it configured pretty much like
outlined in the Kallithea documentation?
socket-user seems to be a recent addition, and this is might thus not be
a general solution.
What mod_wsgi version and which OS and version are you using?
To help us review and assess how general this is: What led to this
solution? Any external references?
/Mads
More information about the kallithea-general
mailing list