Commit d952ddbe authored by Harsh Chouraria's avatar Harsh Chouraria Committed by Evan Read

Docs: Gitaly RPC PermissionDenied error troubleshooting

parent 6a9d4a7d
...@@ -626,11 +626,30 @@ unset http_proxy ...@@ -626,11 +626,30 @@ unset http_proxy
unset https_proxy unset https_proxy
``` ```
### Permission denied errors appearing in Gitaly logs when accessing repositories from a standalone Gitaly server ### Permission denied errors appearing in Gitaly or Praefect logs when accessing repositories
If this error occurs even though file permissions are correct, it's likely that You might see the following in Gitaly and Praefect logs:
the Gitaly server is experiencing
```shell
{
...
"error":"rpc error: code = PermissionDenied desc = permission denied",
"grpc.code":"PermissionDenied",
"grpc.meta.client_name":"gitlab-web",
"grpc.request.fullMethod":"/gitaly.ServerService/ServerInfo",
"level":"warning",
"msg":"finished unary call with code PermissionDenied",
...
}
```
This is a GRPC call
[error response code](https://grpc.github.io/grpc/core/md_doc_statuscodes.html).
If this error occurs, even though
[the Gitaly auth tokens are correctly setup](../gitaly/praefect.md#debugging-praefect),
it's likely that the Gitaly servers are experiencing
[clock drift](https://en.wikipedia.org/wiki/Clock_drift). [clock drift](https://en.wikipedia.org/wiki/Clock_drift).
Ensure the Gitaly clients and servers are synchronized, and use an NTP time Ensure the Gitaly clients and servers are synchronized, and use an NTP time
server to keep them synchronized, if possible. server to keep them synchronized.
Markdown is supported
0%
or
You are about to add 0 people to the discussion. Proceed with caution.
Finish editing this message first!
Please register or to comment