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

classic Classic list List threaded Threaded
3 messages Options
Reply | Threaded
Open this post in threaded view
|

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

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:

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
[hidden email]
http://mailman.nginx.org/mailman/listinfo/nginx
Reply | Threaded
Open this post in threaded view
|

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

Francis Daly
On Sat, Jan 20, 2018 at 10:34:21PM +0000, Friscia, Michael wrote:

Hi there,

> 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.

Does the error cause any breakage in your nginx?

I suspect that the reason for the error is that an "uncommon" filesystem
may have more failure modes than a "common" one; and the best way to avoid
filesystem-related problems is to avoid using a network-based filesystem.

If what you have works well enough for you, then it might be simplest to
leave it as-is, and accept that your filesystem sometimes denies "rename"
permission and other times allows "rename" permission.

To investigate further, you may want to enable the debug log, and perhaps
check the full permissions of the files in question and their containing
directories, and see if there is anything that looks unusual.

"full permissions" may not just be "ls -l", depending on the
implementation or configuration details.

> Has anyone seen this before?

I've not; so this is just as much guess work as the previous one :-)

Good luck with it,

        f
--
Francis Daly        [hidden email]
_______________________________________________
nginx mailing list
[hidden email]
http://mailman.nginx.org/mailman/listinfo/nginx
Reply | Threaded
Open this post in threaded view
|

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

方坤
In reply to this post by Friscia, Michael
# setenforce 0

On Sun, Jan 21, 2018 at 6:34 AM, Friscia, Michael <[hidden email]> 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

<a href="tel:(203)%20737-7932" value="+12037377932" target="_blank">(203) 737-7932 - office

<a href="tel:(203)%20544-3282" value="+12035443282" target="_blank">(203) 544-3282 – mobile

http://web.yale.edu

 


_______________________________________________
nginx mailing list
[hidden email]
http://mailman.nginx.org/mailman/listinfo/nginx


_______________________________________________
nginx mailing list
[hidden email]
http://mailman.nginx.org/mailman/listinfo/nginx