[GH-ISSUE #758] S3 Bucket Connection Lost and Debug will not Complete #437

Closed
opened 2026-03-04 01:45:34 +03:00 by kerem · 2 comments
Owner

Originally created by @dkangel37 on GitHub (May 10, 2018).
Original GitHub issue: https://github.com/s3fs-fuse/s3fs-fuse/issues/758

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)

1.83

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

example: 2.9.4

System information (uname -r)

AWS RHEL 7

Distro (cat /etc/issue)

command result: cat /etc/issue

/etc/fstab entry (if applicable):

# /etc/fstab
# Created by anaconda on Wed Jan  3 17:52:46 2018
#
# Accessible filesystems, by reference, are maintained under '/dev/disk'
# See man pages fstab(5), findfs(8), mount(8) and/or blkid(8) for more info
#
UUID=3e11801e-5277-4d87-be4c-0a9a61fbc3da /                       xfs     defaults        0 0

s3fs#sarchive /opt/s3/coldbucket fuse retries=5,allow_other,url=https://s3.amazonaws.com 0 0
s3fs#sbucket /opt/s3/frozenbucket fuseretries=5,allow_other,url=https://s3.amazonaws.com 0 0

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

[CRT] s3fs.cpp:set_s3fs_log_level(271): change debug level from [CRT] to [INF]
[INF]     s3fs.cpp:set_mountpoint_attribute(4206): PROC(uid=0, gid=0) - MountPoint(uid=0, gid=0, mode=40755)
[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 https://s3.amazonaws.com/sbucket/
[INF]       curl.cpp:prepare_url(4285): URL changed is https://sbucket.s3.amazonaws.com/
[INF]       curl.cpp:insertV4Headers(2400): computing signature [GET] [/] [] []
[INF]       curl.cpp:url_to_host(101): url is https://s3.amazonaws.com
* About to connect() to sbucket.s3.amazonaws.com port 443 (#0)
*   Trying 54.231.41.75...
* Connected to sbucket.s3.amazonaws.com (54.231.41.75) port 443 (#0)
* Initializing NSS with certpath: sql:/etc/pki/nssdb
*   CAfile: /etc/pki/tls/certs/ca-bundle.crt
  CApath: none
* SSL connection using TLS_ECDHE_RSA_WITH_AES_128_GCM_SHA256
* Server certificate:
*       subject: CN=*.s3.amazonaws.com,O=Amazon.com Inc.,L=Seattle,ST=Washington,C=US
*       start date: Sep 22 00:00:00 2017 GMT
*       expire date: Jan 03 12:00:00 2019 GMT
*       common name: *.s3.amazonaws.com
*       issuer: CN=DigiCert Baltimore CA-2 G2,OU=www.digicert.com,O=DigiCert Inc,C=US
> GET / HTTP/1.1
User-Agent: s3fs/1.83 (commit hash e1dafe7; OpenSSL)
Accept: */*
Authorization: AWS4-HMAC-SHA256 Credential=xxxx/20180510/us-east-1/s3/aws4_request, SignedHeaders=host;x-amz-content-sha256;x-amz-date, Signature=9b9382ea0dab7e23d8aaf9bdbec61c300f757f926a828a8b2941f3074f7705b6
host: sbucket.s3.amazonaws.com
x-amz-content-sha256: e3b0c44298fc1c149afbf4c8996fb92427ae41e4649b934ca495991b7852b855
x-amz-date: 20180510T013000Z

< HTTP/1.1 200 OK
< x-amz-id-2: bkKLZ+K5HSnTY2r465wtVqcMc8uNpYDtAvCg8X/jaLGld/wXo1pj5+6l2MC+TtF6dANeh+wVkTw=
< x-amz-request-id: CE1BD6564FEC3E41
< Date: Thu, 10 May 2018 01:30:01 GMT
< x-amz-bucket-region: us-east-1
< Content-Type: application/xml
< Transfer-Encoding: chunked
< Server: AmazonS3
<
* Connection #0 to host sbucket.s3.amazonaws.com left intact
[INF]       curl.cpp:RequestPerform(2051): HTTP response code 200

Details about issue

The Mounts to the S3 buckets have disconnected and won't reconnect. A manual Mount does not work either. The debug will not complete and only hangs. A restart does not help either. Thoughts?

Originally created by @dkangel37 on GitHub (May 10, 2018). Original GitHub issue: https://github.com/s3fs-fuse/s3fs-fuse/issues/758 ### 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) 1.83 #### Version of fuse being used (pkg-config --modversion fuse) _example: 2.9.4_ #### System information (uname -r) AWS RHEL 7 #### Distro (cat /etc/issue) _command result: cat /etc/issue_ #### /etc/fstab entry (if applicable): ``` # /etc/fstab # Created by anaconda on Wed Jan 3 17:52:46 2018 # # Accessible filesystems, by reference, are maintained under '/dev/disk' # See man pages fstab(5), findfs(8), mount(8) and/or blkid(8) for more info # UUID=3e11801e-5277-4d87-be4c-0a9a61fbc3da / xfs defaults 0 0 s3fs#sarchive /opt/s3/coldbucket fuse retries=5,allow_other,url=https://s3.amazonaws.com 0 0 s3fs#sbucket /opt/s3/frozenbucket fuseretries=5,allow_other,url=https://s3.amazonaws.com 0 0 ``` #### s3fs syslog messages (grep s3fs /var/log/syslog, or s3fs outputs) ``` [CRT] s3fs.cpp:set_s3fs_log_level(271): change debug level from [CRT] to [INF] [INF] s3fs.cpp:set_mountpoint_attribute(4206): PROC(uid=0, gid=0) - MountPoint(uid=0, gid=0, mode=40755) [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 https://s3.amazonaws.com/sbucket/ [INF] curl.cpp:prepare_url(4285): URL changed is https://sbucket.s3.amazonaws.com/ [INF] curl.cpp:insertV4Headers(2400): computing signature [GET] [/] [] [] [INF] curl.cpp:url_to_host(101): url is https://s3.amazonaws.com * About to connect() to sbucket.s3.amazonaws.com port 443 (#0) * Trying 54.231.41.75... * Connected to sbucket.s3.amazonaws.com (54.231.41.75) port 443 (#0) * Initializing NSS with certpath: sql:/etc/pki/nssdb * CAfile: /etc/pki/tls/certs/ca-bundle.crt CApath: none * SSL connection using TLS_ECDHE_RSA_WITH_AES_128_GCM_SHA256 * Server certificate: * subject: CN=*.s3.amazonaws.com,O=Amazon.com Inc.,L=Seattle,ST=Washington,C=US * start date: Sep 22 00:00:00 2017 GMT * expire date: Jan 03 12:00:00 2019 GMT * common name: *.s3.amazonaws.com * issuer: CN=DigiCert Baltimore CA-2 G2,OU=www.digicert.com,O=DigiCert Inc,C=US > GET / HTTP/1.1 User-Agent: s3fs/1.83 (commit hash e1dafe7; OpenSSL) Accept: */* Authorization: AWS4-HMAC-SHA256 Credential=xxxx/20180510/us-east-1/s3/aws4_request, SignedHeaders=host;x-amz-content-sha256;x-amz-date, Signature=9b9382ea0dab7e23d8aaf9bdbec61c300f757f926a828a8b2941f3074f7705b6 host: sbucket.s3.amazonaws.com x-amz-content-sha256: e3b0c44298fc1c149afbf4c8996fb92427ae41e4649b934ca495991b7852b855 x-amz-date: 20180510T013000Z < HTTP/1.1 200 OK < x-amz-id-2: bkKLZ+K5HSnTY2r465wtVqcMc8uNpYDtAvCg8X/jaLGld/wXo1pj5+6l2MC+TtF6dANeh+wVkTw= < x-amz-request-id: CE1BD6564FEC3E41 < Date: Thu, 10 May 2018 01:30:01 GMT < x-amz-bucket-region: us-east-1 < Content-Type: application/xml < Transfer-Encoding: chunked < Server: AmazonS3 < * Connection #0 to host sbucket.s3.amazonaws.com left intact [INF] curl.cpp:RequestPerform(2051): HTTP response code 200 ``` ### Details about issue The Mounts to the S3 buckets have disconnected and won't reconnect. A manual Mount does not work either. The debug will not complete and only hangs. A restart does not help either. Thoughts?
kerem closed this issue 2026-03-04 01:45:35 +03:00
Author
Owner

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

Could you mount in the foreground with debug logging via -f -d?

<!-- gh-comment-id:473608312 --> @gaul commented on GitHub (Mar 17, 2019): Could you mount in the foreground with debug logging via `-f -d`?
Author
Owner

@gaul commented on GitHub (Jun 25, 2019):

Closing due to inactivity.

<!-- gh-comment-id:505610565 --> @gaul commented on GitHub (Jun 25, 2019): Closing due to inactivity.
Sign in to join this conversation.
No milestone
No project
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#437
No description provided.