starred/s3fs-fuse
1
0
Fork 0
mirror of https://github.com/s3fs-fuse/s3fs-fuse.git synced 2026-04-25 13:26:00 +03:00
Code Issues 305 Projects Releases 5 Packages Wiki Activity

[GH-ISSUE #708] Hangs at [INF] curl.cpp:RequestPerform(2051): HTTP response code 200 #400

New issue
Closed
opened 2026-03-04 01:45:12 +03:00 by kerem · 4 comments
kerem commented 2026-03-04 01:45:12 +03:00
Owner
Copy link

Originally created by @listedegarde on GitHub (Jan 19, 2018).
Original GitHub issue: https://github.com/s3fs-fuse/s3fs-fuse/issues/708

Additional Information

The following information is very important in order to help us to help you. Omission of the following details may delay your support request or receive no attention at all.

Version of s3fs being used (s3fs --version)

Amazon Simple Storage Service File System V1.83(commit:e1dafe7) with OpenSSL

Version of fuse being used (pkg-config --modversion fuse)

2.9.4

System information (uname -r)

4.4.0-103-generic

Distro (cat /etc/issue)

Ubuntu 16.04.3 LTS \n \l

s3fs command line used (if applicable)

s3fs cdn.example.com -o use_cache=/tmp -o allow_other -o uid=1000 -o mp_umask=002 -o multireq_max=5 /var/www/html/example.com/mount -o dbglevel=info -f -o curldbg
 -o passwd_file=/etc/passwd-s3fs -o use_path_request_style -o endpoint=us-west-2 -ourl=http://s3-us-web-2.amazonaws.com

/etc/fstab entry (if applicable):

LABEL=cloudimg-rootfs   /        ext4   defaults,discard        0 0

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

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

Jan 19 14:57:19 ip-172-31-46-148 s3fs[10143]: s3fs: could not determine how to establish security credentials.
Jan 19 14:57:57 ip-172-31-46-148 s3fs[10185]: init v1.83(commit:e1dafe7) with OpenSSL
Jan 19 14:57:57 ip-172-31-46-148 s3fs[10185]: s3fs.cpp:s3fs_check_service(3813): unable to connect(host=https://s3.amazonaws.com) - result of checking service.
Jan 19 14:58:35 ip-172-31-46-148 s3fs[10200]: init v1.83(commit:e1dafe7) with OpenSSL
Jan 19 14:58:36 ip-172-31-46-148 s3fs[10200]: s3fs.cpp:s3fs_check_service(3813): unable to connect(host=https://s3.amazonaws.com) - result of checking service.
Jan 19 15:02:44 ip-172-31-46-148 s3fs[10303]: s3fs: MOUNTPOINT directory /var/www/html/example.com/mount is not empty. if you are sure this is safe, can use the 'nonempty' mount option.
Jan 19 15:02:58 ip-172-31-46-148 s3fs[10315]: init v1.83(commit:e1dafe7) with OpenSSL
Jan 19 15:02:58 ip-172-31-46-148 s3fs[10315]: s3fs.cpp:s3fs_check_service(3813): unable to connect(host=https://s3.amazonaws.com) - result of checking service.
Jan 19 15:23:12 ip-172-31-46-148 s3fs[10475]: init v1.83(commit:e1dafe7) with OpenSSL
Jan 19 15:23:12 ip-172-31-46-148 s3fs[10475]: s3fs.cpp:s3fs_check_service(3813): unable to connect(host=https://s3.amazonaws.com) - result of checking service.
Jan 19 16:35:42 ip-172-31-46-148 s3fs[11421]: s3fs: specified unknown third optioni(dbglevel=info).
Jan 19 16:35:54 ip-172-31-46-148 s3fs[11426]: s3fs.cpp:set_s3fs_log_level(271): change debug level from [CRT] to [INF]
Jan 19 16:35:54 ip-172-31-46-148 s3fs[11426]:     PROC(uid=1000, gid=1000) - MountPoint(uid=1000, gid=1000, mode=40775)
Jan 19 16:35:54 ip-172-31-46-148 s3fs[11429]: init v1.83(commit:e1dafe7) with OpenSSL
Jan 19 16:35:54 ip-172-31-46-148 s3fs[11429]: check services.
Jan 19 16:35:54 ip-172-31-46-148 s3fs[11429]:       check a bucket.
Jan 19 16:35:54 ip-172-31-46-148 s3fs[11429]:       URL is https://s3.amazonaws.com/cdn.example.com/
Jan 19 16:35:54 ip-172-31-46-148 s3fs[11429]:       URL changed is https://cdn.example.com.s3.amazonaws.com/
Jan 19 16:35:54 ip-172-31-46-148 s3fs[11429]:       computing signature [GET] [/] [] []
Jan 19 16:35:54 ip-172-31-46-148 s3fs[11429]:       url is https://s3.amazonaws.com
Jan 19 16:35:54 ip-172-31-46-148 s3fs[11429]: curl.cpp:RequestPerform(2189): ###curlCode: 51  msg: SSL peer certificate or SSH remote key was not OK
Jan 19 16:35:54 ip-172-31-46-148 s3fs[11429]: curl.cpp:CheckBucket(3096): Check bucket failed, S3 response:
Jan 19 16:35:54 ip-172-31-46-148 s3fs[11429]: s3fs.cpp:s3fs_check_service(3813): unable to connect(host=https://s3.amazonaws.com) - result of checking service.
Jan 19 16:35:54 ip-172-31-46-148 s3fs[11429]: s3fs.cpp:s3fs_exit_fuseloop(3361): Exiting FUSE event loop due to errors
Jan 19 16:35:54 ip-172-31-46-148 s3fs[11429]: destroy
Jan 19 16:35:54 ip-172-31-46-148 s3fs[11429]: s3fs.cpp:s3fs_destroy(3438): Could not release curl library.
Jan 19 16:57:54 ip-172-31-46-148 s3fs[11847]: s3fs: missing MOUNTPOINT argument.

Details about issue

The output from the command is:

[CRT] s3fs.cpp:set_s3fs_log_level(271): change debug level from [CRT] to [INF] 
[INF]     s3fs.cpp:set_mountpoint_attribute(4206): PROC(uid=1000, gid=1000) - MountPoint(uid=1000, gid=1000, mode=40775)
[INF] s3fs.cpp:s3fs_init(3371): init v1.83(commit:e1dafe7) with OpenSSL
[INF] s3fs.cpp:s3fs_check_service(3747): check services.
[INF]       curl.cpp:CheckBucket(3068): check a bucket.
[INF]       curl.cpp:prepare_url(4253): URL is http://s3-us-west-2.amazonaws.com/cdn.example.com/
[INF]       curl.cpp:prepare_url(4285): URL changed is http://s3-us-west-2.amazonaws.com/cdn.example.com/
[INF]       curl.cpp:insertV4Headers(2400): computing signature [GET] [/] [] []
[INF]       curl.cpp:url_to_host(101): url is http://s3-us-west-2.amazonaws.com
*   Trying 52.218.144.64...
* Connected to s3-us-west-2.amazonaws.com (52.218.144.64) port 80 (#0)
> GET /cdn.example.com/ HTTP/1.1
host: s3-us-west-2.amazonaws.com
User-Agent: s3fs/1.83 (commit hash e1dafe7; OpenSSL)
Accept: */*
Authorization: AWS4-HMAC-SHA256 Credential=AKIAICSUFL22UWCVNHKA/20180119/us-west-2/s3/aws4_request, SignedHeaders=host;x-amz-content-sha256;x-amz-date, Signature=11fd2c0b4826a5739e4c57d631e5a2cf830d60e76f0352b2e3262e9f347118e7
x-amz-content-sha256: e3b0c44298fc1c149afbf4c8996fb92427ae41e4649b934ca495991b7852b855
x-amz-date: 20180119T164926Z

< HTTP/1.1 200 OK
< x-amz-id-2: 0bcyD6aN6tApuXjcw9lhytHaMXUqEVUryK2LDSHIILKxsqyZ0HPNO7V/Cjr3U7wxzxmgahugnr0=
< x-amz-request-id: 1202A399422BD0C2
< Date: Fri, 19 Jan 2018 16:49:28 GMT
< x-amz-bucket-region: us-west-2
< Content-Type: application/xml
< Transfer-Encoding: chunked
< Server: AmazonS3
< 
* Connection #0 to host s3-us-west-2.amazonaws.com left intact
[INF]       curl.cpp:RequestPerform(2051): HTTP response code 200

And it just hangs there. As far as I see, there is no error, but I cannot get beyond that point. I have changed my domain name for example.com

Edit: I just did an ls in the folder /var/www/html/example.com/mount and my index.html and imgs folders are there. But when I do an ls on the mount/imgs folder, it hangs. So perhaps it is just because I have so much stuff in there (multiple GBs) and I am just not waiting long enough?

Originally created by @listedegarde on GitHub (Jan 19, 2018). Original GitHub issue: https://github.com/s3fs-fuse/s3fs-fuse/issues/708 ### Additional Information _The following information is very important in order to help us to help you. Omission of the following details may delay your support request or receive no attention at all._ #### Version of s3fs being used (s3fs --version) _Amazon Simple Storage Service File System V1.83(commit:e1dafe7) with OpenSSL_ #### Version of fuse being used (pkg-config --modversion fuse) _2.9.4_ #### System information (uname -r) _4.4.0-103-generic_ #### Distro (cat /etc/issue) _Ubuntu 16.04.3 LTS \n \l_ #### s3fs command line used (if applicable) ``` s3fs cdn.example.com -o use_cache=/tmp -o allow_other -o uid=1000 -o mp_umask=002 -o multireq_max=5 /var/www/html/example.com/mount -o dbglevel=info -f -o curldbg -o passwd_file=/etc/passwd-s3fs -o use_path_request_style -o endpoint=us-west-2 -ourl=http://s3-us-web-2.amazonaws.com ``` #### /etc/fstab entry (if applicable): ``` LABEL=cloudimg-rootfs / ext4 defaults,discard 0 0 ``` #### s3fs syslog messages (grep s3fs /var/log/syslog, or s3fs outputs) _if you execute s3fs with dbglevel, curldbg option, you can get detail debug messages_ ``` Jan 19 14:57:19 ip-172-31-46-148 s3fs[10143]: s3fs: could not determine how to establish security credentials. Jan 19 14:57:57 ip-172-31-46-148 s3fs[10185]: init v1.83(commit:e1dafe7) with OpenSSL Jan 19 14:57:57 ip-172-31-46-148 s3fs[10185]: s3fs.cpp:s3fs_check_service(3813): unable to connect(host=https://s3.amazonaws.com) - result of checking service. Jan 19 14:58:35 ip-172-31-46-148 s3fs[10200]: init v1.83(commit:e1dafe7) with OpenSSL Jan 19 14:58:36 ip-172-31-46-148 s3fs[10200]: s3fs.cpp:s3fs_check_service(3813): unable to connect(host=https://s3.amazonaws.com) - result of checking service. Jan 19 15:02:44 ip-172-31-46-148 s3fs[10303]: s3fs: MOUNTPOINT directory /var/www/html/example.com/mount is not empty. if you are sure this is safe, can use the 'nonempty' mount option. Jan 19 15:02:58 ip-172-31-46-148 s3fs[10315]: init v1.83(commit:e1dafe7) with OpenSSL Jan 19 15:02:58 ip-172-31-46-148 s3fs[10315]: s3fs.cpp:s3fs_check_service(3813): unable to connect(host=https://s3.amazonaws.com) - result of checking service. Jan 19 15:23:12 ip-172-31-46-148 s3fs[10475]: init v1.83(commit:e1dafe7) with OpenSSL Jan 19 15:23:12 ip-172-31-46-148 s3fs[10475]: s3fs.cpp:s3fs_check_service(3813): unable to connect(host=https://s3.amazonaws.com) - result of checking service. Jan 19 16:35:42 ip-172-31-46-148 s3fs[11421]: s3fs: specified unknown third optioni(dbglevel=info). Jan 19 16:35:54 ip-172-31-46-148 s3fs[11426]: s3fs.cpp:set_s3fs_log_level(271): change debug level from [CRT] to [INF] Jan 19 16:35:54 ip-172-31-46-148 s3fs[11426]: PROC(uid=1000, gid=1000) - MountPoint(uid=1000, gid=1000, mode=40775) Jan 19 16:35:54 ip-172-31-46-148 s3fs[11429]: init v1.83(commit:e1dafe7) with OpenSSL Jan 19 16:35:54 ip-172-31-46-148 s3fs[11429]: check services. Jan 19 16:35:54 ip-172-31-46-148 s3fs[11429]: check a bucket. Jan 19 16:35:54 ip-172-31-46-148 s3fs[11429]: URL is https://s3.amazonaws.com/cdn.example.com/ Jan 19 16:35:54 ip-172-31-46-148 s3fs[11429]: URL changed is https://cdn.example.com.s3.amazonaws.com/ Jan 19 16:35:54 ip-172-31-46-148 s3fs[11429]: computing signature [GET] [/] [] [] Jan 19 16:35:54 ip-172-31-46-148 s3fs[11429]: url is https://s3.amazonaws.com Jan 19 16:35:54 ip-172-31-46-148 s3fs[11429]: curl.cpp:RequestPerform(2189): ###curlCode: 51 msg: SSL peer certificate or SSH remote key was not OK Jan 19 16:35:54 ip-172-31-46-148 s3fs[11429]: curl.cpp:CheckBucket(3096): Check bucket failed, S3 response: Jan 19 16:35:54 ip-172-31-46-148 s3fs[11429]: s3fs.cpp:s3fs_check_service(3813): unable to connect(host=https://s3.amazonaws.com) - result of checking service. Jan 19 16:35:54 ip-172-31-46-148 s3fs[11429]: s3fs.cpp:s3fs_exit_fuseloop(3361): Exiting FUSE event loop due to errors Jan 19 16:35:54 ip-172-31-46-148 s3fs[11429]: destroy Jan 19 16:35:54 ip-172-31-46-148 s3fs[11429]: s3fs.cpp:s3fs_destroy(3438): Could not release curl library. Jan 19 16:57:54 ip-172-31-46-148 s3fs[11847]: s3fs: missing MOUNTPOINT argument. ``` ### Details about issue The output from the command is: ``` [CRT] s3fs.cpp:set_s3fs_log_level(271): change debug level from [CRT] to [INF] [INF] s3fs.cpp:set_mountpoint_attribute(4206): PROC(uid=1000, gid=1000) - MountPoint(uid=1000, gid=1000, mode=40775) [INF] s3fs.cpp:s3fs_init(3371): init v1.83(commit:e1dafe7) with OpenSSL [INF] s3fs.cpp:s3fs_check_service(3747): check services. [INF] curl.cpp:CheckBucket(3068): check a bucket. [INF] curl.cpp:prepare_url(4253): URL is http://s3-us-west-2.amazonaws.com/cdn.example.com/ [INF] curl.cpp:prepare_url(4285): URL changed is http://s3-us-west-2.amazonaws.com/cdn.example.com/ [INF] curl.cpp:insertV4Headers(2400): computing signature [GET] [/] [] [] [INF] curl.cpp:url_to_host(101): url is http://s3-us-west-2.amazonaws.com * Trying 52.218.144.64... * Connected to s3-us-west-2.amazonaws.com (52.218.144.64) port 80 (#0) > GET /cdn.example.com/ HTTP/1.1 host: s3-us-west-2.amazonaws.com User-Agent: s3fs/1.83 (commit hash e1dafe7; OpenSSL) Accept: */* Authorization: AWS4-HMAC-SHA256 Credential=AKIAICSUFL22UWCVNHKA/20180119/us-west-2/s3/aws4_request, SignedHeaders=host;x-amz-content-sha256;x-amz-date, Signature=11fd2c0b4826a5739e4c57d631e5a2cf830d60e76f0352b2e3262e9f347118e7 x-amz-content-sha256: e3b0c44298fc1c149afbf4c8996fb92427ae41e4649b934ca495991b7852b855 x-amz-date: 20180119T164926Z < HTTP/1.1 200 OK < x-amz-id-2: 0bcyD6aN6tApuXjcw9lhytHaMXUqEVUryK2LDSHIILKxsqyZ0HPNO7V/Cjr3U7wxzxmgahugnr0= < x-amz-request-id: 1202A399422BD0C2 < Date: Fri, 19 Jan 2018 16:49:28 GMT < x-amz-bucket-region: us-west-2 < Content-Type: application/xml < Transfer-Encoding: chunked < Server: AmazonS3 < * Connection #0 to host s3-us-west-2.amazonaws.com left intact [INF] curl.cpp:RequestPerform(2051): HTTP response code 200 ``` ---- And it just hangs there. As far as I see, there is no error, but I cannot get beyond that point. I have changed my domain name for example.com **Edit:** I just did an `ls` in the folder /var/www/html/example.com/mount and my index.html and imgs folders are there. But when I do an `ls` on the mount/imgs folder, it hangs. So perhaps it is just because I have so much stuff in there (multiple GBs) and I am just not waiting long enough?
kerem closed this issue 2026-03-04 01:45:12 +03:00
kerem commented 2026-03-04 01:45:13 +03:00
Author
Owner
Copy link

@heldtogether commented on GitHub (Jan 21, 2018):

I'm seeing this issue too. However, I get a little bit more output and Killed when I try to ls the directory:

.
.
.
* Connection #0 to host {bucket}.ams3.digitaloceanspaces.com left intact
[INF]       curl.cpp:RequestPerform(2051): HTTP response code 200
* found 148 certificates in /etc/ssl/certs/ca-certificates.crt
* found 148 certificates in /etc/ssl/certs/ca-certificates.crt
* * found 148 certificates in /etc/ssl/certs/ca-certificates.crt
found 148 certificates in /etc/ssl/certs/ca-certificates.crt
* found 148 certificates in /etc/ssl/certs/ca-certificates.crt
* found 148 certificates in /etc/ssl/certs/ca-certificates.crt
* found 148 certificates in /etc/ssl/certs/ca-certificates.crt
* found 148 certificates in /etc/ssl/certs/ca-certificates.crt
* found 148 certificates in /etc/ssl/certs/ca-certificates.crt
* found 148 certificates in /etc/ssl/certs/ca-certificates.crt
* found 148 certificates in /etc/ssl/certs/ca-certificates.crt
* found 148 certificates in /etc/ssl/certs/ca-certificates.crt
* found 148 certificates in /etc/ssl/certs/ca-certificates.crt
* found 148 certificates in /etc/ssl/certs/ca-certificates.crt
* found 148 certificates in /etc/ssl/certs/ca-certificates.crt
* found 148 certificates in /etc/ssl/certs/ca-certificates.crt
* found 148 certificates in /etc/ssl/certs/ca-certificates.crt
Killed

I have the same version of s3fs, fuse, distro and system info as @listedegarde

<!-- gh-comment-id:359232361 --> @heldtogether commented on GitHub (Jan 21, 2018): I'm seeing this issue too. However, I get a little bit more output and `Killed` when I try to `ls` the directory: ``` . . . * Connection #0 to host {bucket}.ams3.digitaloceanspaces.com left intact [INF] curl.cpp:RequestPerform(2051): HTTP response code 200 * found 148 certificates in /etc/ssl/certs/ca-certificates.crt * found 148 certificates in /etc/ssl/certs/ca-certificates.crt * * found 148 certificates in /etc/ssl/certs/ca-certificates.crt found 148 certificates in /etc/ssl/certs/ca-certificates.crt * found 148 certificates in /etc/ssl/certs/ca-certificates.crt * found 148 certificates in /etc/ssl/certs/ca-certificates.crt * found 148 certificates in /etc/ssl/certs/ca-certificates.crt * found 148 certificates in /etc/ssl/certs/ca-certificates.crt * found 148 certificates in /etc/ssl/certs/ca-certificates.crt * found 148 certificates in /etc/ssl/certs/ca-certificates.crt * found 148 certificates in /etc/ssl/certs/ca-certificates.crt * found 148 certificates in /etc/ssl/certs/ca-certificates.crt * found 148 certificates in /etc/ssl/certs/ca-certificates.crt * found 148 certificates in /etc/ssl/certs/ca-certificates.crt * found 148 certificates in /etc/ssl/certs/ca-certificates.crt * found 148 certificates in /etc/ssl/certs/ca-certificates.crt * found 148 certificates in /etc/ssl/certs/ca-certificates.crt Killed ``` I have the same version of s3fs, fuse, distro and system info as @listedegarde
kerem commented 2026-03-04 01:45:13 +03:00
Author
Owner
Copy link

@manuelsotoma commented on GitHub (Sep 28, 2018):

Same issue

<!-- gh-comment-id:425519824 --> @manuelsotoma commented on GitHub (Sep 28, 2018): Same issue
kerem commented 2026-03-04 01:45:13 +03:00
Author
Owner
Copy link

@gaul commented on GitHub (Feb 2, 2019):

Could you try mounting with -o use_path_request_style? The periods in your bucket name may give SSL errors otherwise.

<!-- gh-comment-id:459930816 --> @gaul commented on GitHub (Feb 2, 2019): Could you try mounting with `-o use_path_request_style`? The periods in your bucket name may give SSL errors otherwise.
kerem commented 2026-03-04 01:45:13 +03:00
Author
Owner
Copy link

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

Closing due to inactivity. Please reopen if symptoms persist.

<!-- gh-comment-id:481185252 --> @gaul commented on GitHub (Apr 9, 2019): Closing due to inactivity. Please reopen if symptoms persist.
Sign in to join this conversation.
No Branch/Tag specified
Branches Tags
master
v1.97
v1.96
v1.95
v1.94
v1.93
v1.92
v1.91
v1.90
v1.89
v1.88
v1.87
v1.86
v1.85
v1.84
v1.83
v1.82
v1.81
v1.80
v1.79
v1.78
Pre-v1.78
v1.77
v1.76
v1.75
v1.74
Labels
Clear labels   
bug

   
bug

   
dataloss

   
duplicate

   
enhancement

   
feature request

   
help wanted

   
invalid

   
need info

   
performance

   
pull-request

Mirrored from GitHub Pull Request

  
question

   
question

   
testing
No labels
bug
bug
dataloss
duplicate
enhancement
feature request
help wanted
invalid
need info
performance
pull-request
question
question
testing
Milestone
Clear milestone
No items
No milestone
Projects
Clear projects
No items
No project
Assignees
Clear assignees
No assignees
1 participant
Notifications
Due date
The due date is invalid or out of range. Please use the format "yyyy-mm-dd".

No due date set.

Dependencies

No dependencies set.

Reference
starred/s3fs-fuse#400
No description provided.