# setenforce 0 On Sun, Jan 21, 2018 at 6:34 AM, Friscia, Michael <michael.fris...@yale.edu> wrote:
> 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: > > eedd07f7aef45a5ed22f748a31724947.0000002528 > > to > > eedd07f7aef45a5ed22f748a31724947 > > > > This seems to happen on some pages and then continues to happen if I > browse that page but most pages are not affected. > > > > Has anyone seen this before? > > > > ___________________________________________ > > Michael Friscia > > Office of Communications > > Yale School of Medicine > > (203) 737-7932 - office > > (203) 544-3282 – mobile > > http://web.yale.edu > > > > _______________________________________________ > nginx mailing list > nginx@nginx.org > http://mailman.nginx.org/mailman/listinfo/nginx >
_______________________________________________ nginx mailing list nginx@nginx.org http://mailman.nginx.org/mailman/listinfo/nginx
