[GH-ISSUE #740] s3fs: Failed to access bucket. #422

New issue

Closed

opened 2026-03-04 01:45:25 +03:00 by kerem · 3 comments

kerem commented

2026-03-04 01:45:25 +03:00

Owner

Originally created by @sreekanth0325 on GitHub (Mar 30, 2018).
Original GitHub issue: https://github.com/s3fs-fuse/s3fs-fuse/issues/740

#/usr/bin/s3fs dxtestb1 /dx_b1 -ouse_cache=/tmp/cache -ouse_sse=/etc/passwd-s3fs -ourl=http://s3.cn-north-1.amazonaws.com.cn -d -d -f -o curldbg

set_moutpoint_attribute(3293): PROC(uid=0, gid=0) - MountPoint(uid=0, gid=0, mode=40755)
FUSE library version: 2.9.2
nullpath_ok: 0
nopath: 0
utime_omit_ok: 0
unique: 1, opcode: INIT (26), nodeid: 0, insize: 56, pid: 0
INIT: 7.22
flags=0x0000f7fb
max_readahead=0x00020000
s3fs_init(2597): init
s3fs_check_service(2896): check services.
    CheckBucket(2244): check a bucket.
    RequestPerform(1478): connecting to URL http://dxtestb1.s3.cn-north-1.amazonaws.com.cn/
* Hostname was NOT found in DNS cache
*   Trying 54.222.48.6...
* Connected to dxtestb1.s3.cn-north-1.amazonaws.com.cn (54.222.48.6) port 80 (#0)
> GET / HTTP/1.1
Host: dxtestb1.s3.cn-north-1.amazonaws.com.cn
Accept: */*
Authorization: AWS AKIAOGMNRXLSVHO7S7QQ:D9upMmladMSq10o1hB4ahqW0fOM=
Date: Fri, 30 Mar 2018 08:11:26 GMT

* The requested URL returned error: 400 Bad Request
* Closing connection 0
RequestPerform(1611): ### CURLE_HTTP_RETURNED_ERROR
RequestPerform(1616): HTTP response code =400
s3fs: Failed to access bucket.

Please suggest

Originally created by @sreekanth0325 on GitHub (Mar 30, 2018). Original GitHub issue: https://github.com/s3fs-fuse/s3fs-fuse/issues/740 ``` #/usr/bin/s3fs dxtestb1 /dx_b1 -ouse_cache=/tmp/cache -ouse_sse=/etc/passwd-s3fs -ourl=http://s3.cn-north-1.amazonaws.com.cn -d -d -f -o curldbg set_moutpoint_attribute(3293): PROC(uid=0, gid=0) - MountPoint(uid=0, gid=0, mode=40755) FUSE library version: 2.9.2 nullpath_ok: 0 nopath: 0 utime_omit_ok: 0 unique: 1, opcode: INIT (26), nodeid: 0, insize: 56, pid: 0 INIT: 7.22 flags=0x0000f7fb max_readahead=0x00020000 s3fs_init(2597): init s3fs_check_service(2896): check services. CheckBucket(2244): check a bucket. RequestPerform(1478): connecting to URL http://dxtestb1.s3.cn-north-1.amazonaws.com.cn/ * Hostname was NOT found in DNS cache * Trying 54.222.48.6... * Connected to dxtestb1.s3.cn-north-1.amazonaws.com.cn (54.222.48.6) port 80 (#0) > GET / HTTP/1.1 Host: dxtestb1.s3.cn-north-1.amazonaws.com.cn Accept: */* Authorization: AWS AKIAOGMNRXLSVHO7S7QQ:D9upMmladMSq10o1hB4ahqW0fOM= Date: Fri, 30 Mar 2018 08:11:26 GMT * The requested URL returned error: 400 Bad Request * Closing connection 0 RequestPerform(1611): ### CURLE_HTTP_RETURNED_ERROR RequestPerform(1616): HTTP response code =400 s3fs: Failed to access bucket. ``` Please suggest

kerem closed this issue

2026-03-04 01:45:26 +03:00

kerem commented

2026-03-04 01:45:27 +03:00

Author

Owner

@jonathanvdmerwe commented on GitHub (Apr 13, 2018):

add this to your password file... bucketName:accessKeyId:secretAccessKey

@jonathanvdmerwe commented on GitHub (Apr 13, 2018): add this to your password file... bucketName:accessKeyId:secretAccessKey

kerem commented

2026-03-04 01:45:27 +03:00

Author

Owner

@gaul commented on GitHub (Mar 17, 2019):

It appears that your options are malformed:

-ouse_sse=/etc/passwd-s3fs

Did you intend to specify:

-o use_sse -o passwd_file=/etc/passwd-s3fs

@gaul commented on GitHub (Mar 17, 2019): It appears that your options are malformed: ``` -ouse_sse=/etc/passwd-s3fs ``` Did you intend to specify: ``` -o use_sse -o passwd_file=/etc/passwd-s3fs ```

kerem commented

2026-03-04 01:45:27 +03:00

Author

Owner

@gaul commented on GitHub (Apr 9, 2019):

Marking as resolved; please reopen if problems persist.

@gaul commented on GitHub (Apr 9, 2019): Marking as resolved; please reopen if problems persist.

kerem referenced this issue

2026-03-04 01:54:16 +03:00

[PR #422] [MERGED] Fixes for iam_role=auto #1501