I think I found the reason of this issue: The unfsd service manual tells in the nfs3 bug section that all the path needs to be in exec rights for the user, and that the server executes the requests with the same uid, gid as the client (except for root if not autorised - which is not my case). http://linux.die.net/man/8/unfsd My client running Nginx is running in root for the master and in aby MPtiBot - Other discussion
Thank you for your quick answer itpp2012! I retain your proposition, but I am currently not able to add any component to the server. However, I found something which looks to work and might be related to NFS: If I add the x right to the full path of the logs for all users (even if the server is executed as root). I have no error and everything is logged. NFS would needs the x right to procesby MPtiBot - Other discussion
Good morning, I am facing a very annoying issue with Nginx access and error logs. For a reason I cannot mention, I absolutely need to write my nginx logs on a NFS partition mounted on the server. For this, I mentionned the path to the error and access logs files (each one on a different nfs partition). The file is properly created bu the Nginx master but only a few logs are written (most oby MPtiBot - Other discussion