goofys icon indicating copy to clipboard operation
goofys copied to clipboard

main.ERROR Unable to access '<bucket_name>': permission denied

Open NohYeongHun opened this issue 6 months ago • 3 comments

Currently, the situation I have confirmed is as follows:

  1. Register aws credentials in the ~/.aws/credentials file
[default]
aws_access_key_id= <aws_access_key_id>
aws_secret_access_key=<aws_secret_access_key>


2. Check whether the mount folder has been properly created on the current server and s3 bucket.


nevertheless
When using goofys, an error called Permission denied occurs.
Is there anything else I need to check?

## Log
---[ REQUEST POST-SIGN ]-----------------------------
HEAD /<bucket_name>/<folder_name>/4hub3iuzc22q0x83tiskzq1g7san68fo HTTP/1.1
Host: s3.ap-northeast-2.amazonaws.com
User-Agent: aws-sdk-go/1.8.25 (go1.9.2; linux; amd64)
Authorization: AWS4-HMAC-SHA256 Credential=<Credential>
SignedHeaders=host;x-amz-content-sha256;x-amz-date, 
Signature=<Signature>
X-Amz-Content-Sha256: ...
X-Amz-Date: 20231227T082901Z


-----------------------------------------------------
2023/12/27 17:29:01.866202 s3.DEBUG DEBUG: Response s3/HeadObject Details:
---[ RESPONSE ]--------------------------------------
HTTP/1.1 403 Forbidden
Connection: close
Content-Type: application/xml
Date: Wed, 27 Dec 2023 08:29:01 GMT
Server: AmazonS3
X-Amz-Id-2: ...
X-Amz-Request-Id: ...


### error
-----------------------------------------------------
2023/12/27 17:29:01.866276 s3.DEBUG DEBUG: Validate Response s3/HeadObject failed, not retrying, error Forbidden: Forbidden
        status code: 403, request id: <request_id>, host id: <host_id>
2023/12/27 17:29:01.866309 main.ERROR Unable to access '<bucket_name>': permission denied
2023/12/27 17:29:01.866328 main.FATAL Mounting file system: Mount: initialization failed

NohYeongHun avatar Dec 27 '23 08:12 NohYeongHun

Same problem for me

antoniofarina avatar Jan 10 '24 12:01 antoniofarina

@NohYeongHun I have further investigated and, in my case, I discovered the ntp service crashed on my server. Restarting the ntp solved the issue.

antoniofarina avatar Jan 10 '24 14:01 antoniofarina