nginx permission denied for upstream unix socket

[Edwin]

Le 2014-08-25 09:51, Tim a écrit :
> Am 2014-08-25 15:46, schrieb Valentin V. Bartenev:
>> On Monday 25 August 2014 15:21:44 Tim wrote:
>>> Hi,
>>> 
>>> I'm running nginx under CentOS 7 as a local proxy for a puppetmaster. 
>>> I
>>> get the following error for every agent trying to connect to the 
>>> master:
>>> 
>>> "[crit] 8543#0: *13 connect() to
>>> unix:/var/run/puppet/puppetmaster_puma.sock failed (13: Permission
>>> denied) while connecting to upstream, client: 192.168.122.189, 
>>> server: ,
>>> request: "PUT /production/report/master.puppet.local HTTP/1.1",
>>> upstream:
>>> 
>> "http://unix:/var/run/puppet/puppetmaster_puma.sock:/production/report/master.puppet.local",
>>> host: "master.puppet.local:8140""
>>> 
>>> 
>>> But:
>>> srwxrwxrwx. 1 puppet puppet 0 25. Aug 10:35
>>> /var/run/puppet/puppetmaster_puma.sock
>>> 
>>> The socket seems to be read/write able for everyone on the system? 
>>> Why
>>> throws nginx a "permission denied" massage?
>>> 
>> [..]
>> 
>> What about the /var/run/puppet/ directory?
> 
> seems to be fine:
> 
> drwxr-xr-x.  2 puppet   puppet    100 25. Aug 10:35 /var/run/puppet
> 
> (the nginx user is in the puppet group btw). Even setting the
> permissions to 777 didn't fix the issue.
> 
>> 
>>   wbr, Valentin V. Bartenev
>> 
>> _______________________________________________
>> nginx mailing list
>> nginx at nginx.org
>> http://mailman.nginx.org/mailman/listinfo/nginx
> 
> _______________________________________________
> nginx mailing list
> nginx at nginx.org
> http://mailman.nginx.org/mailman/listinfo/nginx

Hi,

Have you checked your SELinux permissions? According to your "ls -l", 
you would have SELinux enabled on those files/sockets (the "." in the 
output). I would check SELinux settings to allow access from nginx to 
the socket.

Sincerely,
---
Edwin