failed (13: Permission denied) while reading upstream on rename()

2018-01-20 Thread Friscia, Michael
Earlier today I solved a chmod() problem in the cache and now I’m faced with this one which happens much less frequently. I don’t think permission is the problem, I think it’s an Nginx configuration I failed to set correctly. In the error I see that the rename() failure was to change: eedd07f7ae

Re: Operation not permitted) while reading upstream - error log is filled with tons of these

2018-01-20 Thread Friscia, Michael
I tried appling the noperm flag on my test environment, but once I applied the other fix of adding gid/uid to the cifs mount, the chmod() error went away. Now I face a new error that happens infrequently which is rename() fails. I’m guessing the real problem is that without a lot of additional c

Re: Nginx rewrites URL

2018-01-20 Thread Francis Daly
On Thu, Jan 18, 2018 at 01:01:44PM -0500, P lva wrote: Hi there, > I'm trying to get nginx server configured as a reverse proxy serving > requests to few application servers upstream. > > Server { > server_name app1.company.domain.com; > listen 80; > > location / { > proxy_pass http://appse

Re: Operation not permitted) while reading upstream - error log is filled with tons of these

2018-01-20 Thread Francis Daly
On Sat, Jan 20, 2018 at 12:47:29PM +, Friscia, Michael wrote: Hi there, > 2018/01/20 07:37:44 [crit] 122598#122598: *91 chmod() > "/etc/nginx/cache/nginx2/main/a5/d8/e0/72677057b97aef4eee8e619c49e0d8a5.13" > failed (1: Operation not permitted) while reading upstream, client: > 35.2

Re: Operation not permitted) while reading upstream - error log is filled with tons of these

2018-01-20 Thread Friscia, Michael
Ok, found it. It was a permission issue. I did not have the uid and gid in the fstab, I set that the the www-data user that nginx is running as and the errors went away. I’m just not sure I understand how it made the cache files/directories in the first place. But clearly this is a problem when

Re: Operation not permitted) while reading upstream - error log is filled with tons of these

2018-01-20 Thread Aziz Rozyev
As usual, try disabling selinux if it’s active. If that helps, investigate audit log.. br, Aziz. > On 20 Jan 2018, at 15:47, Friscia, Michael wrote: > > I’m stumped and have exhausted pretty much every google search I could come > up with on this. I have NGINX setup for caching. I’m using

Operation not permitted) while reading upstream - error log is filled with tons of these

2018-01-20 Thread Friscia, Michael
I’m stumped and have exhausted pretty much every google search I could come up with on this. I have NGINX setup for caching. I’m using Ubuntu 17.10 and Nginx 1.12.1. Everything appears to be working just fine by the error log is getting filled with errors like this 2018/01/20 07:37:44 [crit] 12