[GH-ISSUE #1201] HTTP response 200 but not mounted #636

New issue

Closed

opened 2026-03-04 01:47:24 +03:00 by kerem · 1 comment

kerem commented

2026-03-04 01:47:24 +03:00

Owner

Originally created by @mateosantosdev on GitHub (Nov 20, 2019).
Original GitHub issue: https://github.com/s3fs-fuse/s3fs-fuse/issues/1201

Version of s3fs being used (s3fs --version)

1.85

Version of fuse being used (pkg-config --modversion fuse, rpm -qi fuse, dpkg -s fuse)

2.9.7

Kernel information (uname -r)

4.15.0-1054-aws

GNU/Linux Distribution, if applicable (cat /etc/os-release)

Ubuntu 18.04.3 LTS

s3fs command line used, if applicable

sudo s3fs myBucket /home/ubuntu/s3docker/  -o passwd_file=/home/ubuntu/.passwd-s3fs -o endpoint=eu-central-1 -o url=https://s3-eu-central-1.amazonaws.com -o dbglevel=info -d -f -o f2 -o curldbg

/etc/fstab entry, if applicable

LABEL=cloudimg-rootfs	/	 ext4	defaults,discard	0 0
/swapfile none swap sw 0 0

s3fs syslog messages (grep s3fs /var/log/syslog, journalctl | grep s3fs, or s3fs outputs)

if you execute s3fs with dbglevel, curldbg option, you can get detail debug messages

[CRT] s3fs.cpp:set_s3fs_log_level(297): change debug level from [CRT] to [INF]
[CRT] s3fs.cpp:set_s3fs_log_level(297): change debug level from [INF] to [DBG]
[INF]     s3fs.cpp:set_mountpoint_attribute(4384): PROC(uid=0, gid=0) - MountPoint(uid=0, gid=0, mode=40700)
FUSE library version: 2.9.7
nullpath_ok: 0
nopath: 0
utime_omit_ok: 0
unique: 1, opcode: INIT (26), nodeid: 0, insize: 56, pid: 0
INIT: 7.26
flags=0x001ffffb
max_readahead=0x00020000
[INF] s3fs.cpp:s3fs_init(3476): init v1.85(commit:cc4a307) with OpenSSL
[INF] s3fs.cpp:s3fs_check_service(3811): check services.
[INF]       curl.cpp:CheckBucket(3397): check a bucket.
[DBG] curl.cpp:GetHandler(289): Get handler from pool: rest = 31
[INF]       curl.cpp:prepare_url(4685): URL is https://s3-eu-central-1.amazonaws.com/myBucket/
[INF]       curl.cpp:prepare_url(4718): URL changed is https://myBucket.s3-eu-central-1.amazonaws.com/
[DBG] curl.cpp:RequestPerform(2379): connecting to URL https://myBucket.s3-eu-central-1.amazonaws.com/
[INF]       curl.cpp:insertV4Headers(2745): computing signature [GET] [/] [] []
[INF]       curl.cpp:url_to_host(99): url is https://s3-eu-central-1.amazonaws.com
*   Trying 52.219.73.132...
* TCP_NODELAY set
* Connected to myBucket.s3-eu-central-1.amazonaws.com (52.219.73.132) port 443 (#0)
* found 133 certificates in /etc/ssl/certs/ca-certificates.crt
* found 399 certificates in /etc/ssl/certs
* SSL connection using TLS1.2 / ECDHE_RSA_AES_128_GCM_SHA256
* 	 server certificate verification OK
* 	 server certificate status verification SKIPPED
* 	 common name: *.s3.eu-central-1.amazonaws.com (matched)
* 	 server certificate expiration date OK
* 	 server certificate activation date OK
* 	 certificate public key: RSA
* 	 certificate version: #3
* 	 subject: C=US,ST=Washington,L=Seattle,O=Amazon.com\, Inc.,CN=*.s3.eu-central-1.amazonaws.com
* 	 start date: Sat, 09 Nov 2019 00:00:00 GMT
* 	 expire date: Thu, 10 Dec 2020 12:00:00 GMT
* 	 issuer: C=US,O=DigiCert Inc,OU=www.digicert.com,CN=DigiCert Baltimore CA-2 G2
* 	 compression: NULL
> GET / HTTP/1.1
host: myBucket.s3-eu-central-1.amazonaws.com
User-Agent: s3fs/1.85 (commit hash cc4a307; OpenSSL)
Accept: */*
Authorization: AWS4-HMAC-SHA256 Credential=myAWSKey/20191120/eu-central-1/s3/aws4_request, SignedHeaders=host;x-amz-content-sha256;x-amz-date, Signature=XXX
x-amz-content-sha256: XXX
x-amz-date: 20191120T081104Z

< HTTP/1.1 200 OK
< x-amz-id-2: XXX
< x-amz-request-id: 7DCC4B0914038816
< Date: Wed, 20 Nov 2019 08:11:05 GMT
< x-amz-bucket-region: eu-central-1
< Content-Type: application/xml
< Transfer-Encoding: chunked
< Server: AmazonS3
<
* Connection #0 to host myBucket.s3-eu-central-1.amazonaws.com left intact
[INF]       curl.cpp:RequestPerform(2408): HTTP response code 200
[DBG] curl.cpp:ReturnHandler(311): Return handler to pool
[INF] curl.cpp:ReturnHandler(318): Pool full: destroy the oldest handler
   INIT: 7.19
   flags=0x00000039
   max_readahead=0x00020000
   max_write=0x00020000
   max_background=0
   congestion_threshold=0
   unique: 1, success, outsize: 40

Details about issue

I don't receive any error but the bucket is not mounting in my system.

Originally created by @mateosantosdev on GitHub (Nov 20, 2019). Original GitHub issue: https://github.com/s3fs-fuse/s3fs-fuse/issues/1201 #### Version of s3fs being used (s3fs --version) _1.85_ #### Version of fuse being used (pkg-config --modversion fuse, rpm -qi fuse, dpkg -s fuse) _2.9.7_ #### Kernel information (uname -r) _4.15.0-1054-aws_ #### GNU/Linux Distribution, if applicable (cat /etc/os-release) _Ubuntu 18.04.3 LTS_ #### s3fs command line used, if applicable ``` sudo s3fs myBucket /home/ubuntu/s3docker/ -o passwd_file=/home/ubuntu/.passwd-s3fs -o endpoint=eu-central-1 -o url=https://s3-eu-central-1.amazonaws.com -o dbglevel=info -d -f -o f2 -o curldbg ``` #### /etc/fstab entry, if applicable ``` LABEL=cloudimg-rootfs / ext4 defaults,discard 0 0 /swapfile none swap sw 0 0 ``` #### s3fs syslog messages (grep s3fs /var/log/syslog, journalctl | grep s3fs, or s3fs outputs) _if you execute s3fs with dbglevel, curldbg option, you can get detail debug messages_ ``` [CRT] s3fs.cpp:set_s3fs_log_level(297): change debug level from [CRT] to [INF] [CRT] s3fs.cpp:set_s3fs_log_level(297): change debug level from [INF] to [DBG] [INF] s3fs.cpp:set_mountpoint_attribute(4384): PROC(uid=0, gid=0) - MountPoint(uid=0, gid=0, mode=40700) FUSE library version: 2.9.7 nullpath_ok: 0 nopath: 0 utime_omit_ok: 0 unique: 1, opcode: INIT (26), nodeid: 0, insize: 56, pid: 0 INIT: 7.26 flags=0x001ffffb max_readahead=0x00020000 [INF] s3fs.cpp:s3fs_init(3476): init v1.85(commit:cc4a307) with OpenSSL [INF] s3fs.cpp:s3fs_check_service(3811): check services. [INF] curl.cpp:CheckBucket(3397): check a bucket. [DBG] curl.cpp:GetHandler(289): Get handler from pool: rest = 31 [INF] curl.cpp:prepare_url(4685): URL is https://s3-eu-central-1.amazonaws.com/myBucket/ [INF] curl.cpp:prepare_url(4718): URL changed is https://myBucket.s3-eu-central-1.amazonaws.com/ [DBG] curl.cpp:RequestPerform(2379): connecting to URL https://myBucket.s3-eu-central-1.amazonaws.com/ [INF] curl.cpp:insertV4Headers(2745): computing signature [GET] [/] [] [] [INF] curl.cpp:url_to_host(99): url is https://s3-eu-central-1.amazonaws.com * Trying 52.219.73.132... * TCP_NODELAY set * Connected to myBucket.s3-eu-central-1.amazonaws.com (52.219.73.132) port 443 (#0) * found 133 certificates in /etc/ssl/certs/ca-certificates.crt * found 399 certificates in /etc/ssl/certs * SSL connection using TLS1.2 / ECDHE_RSA_AES_128_GCM_SHA256 * server certificate verification OK * server certificate status verification SKIPPED * common name: *.s3.eu-central-1.amazonaws.com (matched) * server certificate expiration date OK * server certificate activation date OK * certificate public key: RSA * certificate version: #3 * subject: C=US,ST=Washington,L=Seattle,O=Amazon.com\, Inc.,CN=*.s3.eu-central-1.amazonaws.com * start date: Sat, 09 Nov 2019 00:00:00 GMT * expire date: Thu, 10 Dec 2020 12:00:00 GMT * issuer: C=US,O=DigiCert Inc,OU=www.digicert.com,CN=DigiCert Baltimore CA-2 G2 * compression: NULL > GET / HTTP/1.1 host: myBucket.s3-eu-central-1.amazonaws.com User-Agent: s3fs/1.85 (commit hash cc4a307; OpenSSL) Accept: */* Authorization: AWS4-HMAC-SHA256 Credential=myAWSKey/20191120/eu-central-1/s3/aws4_request, SignedHeaders=host;x-amz-content-sha256;x-amz-date, Signature=XXX x-amz-content-sha256: XXX x-amz-date: 20191120T081104Z < HTTP/1.1 200 OK < x-amz-id-2: XXX < x-amz-request-id: 7DCC4B0914038816 < Date: Wed, 20 Nov 2019 08:11:05 GMT < x-amz-bucket-region: eu-central-1 < Content-Type: application/xml < Transfer-Encoding: chunked < Server: AmazonS3 < * Connection #0 to host myBucket.s3-eu-central-1.amazonaws.com left intact [INF] curl.cpp:RequestPerform(2408): HTTP response code 200 [DBG] curl.cpp:ReturnHandler(311): Return handler to pool [INF] curl.cpp:ReturnHandler(318): Pool full: destroy the oldest handler INIT: 7.19 flags=0x00000039 max_readahead=0x00020000 max_write=0x00020000 max_background=0 congestion_threshold=0 unique: 1, success, outsize: 40 ``` ### Details about issue I don't receive any error but the bucket is not mounting in my system.