[GH-ISSUE #1821] Files transferred with WinSCP to s3fs mount HTTP response code 404 was returned, returning ENOENT #935

New issue

Open

opened 2026-03-04 01:50:03 +03:00 by kerem · 0 comments

kerem commented

2026-03-04 01:50:03 +03:00

Owner

Originally created by @CESteinmetz on GitHub (Dec 22, 2021).
Original GitHub issue: https://github.com/s3fs-fuse/s3fs-fuse/issues/1821

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.
Keep in mind that the commands we provide to retrieve information are oriented to GNU/Linux Distributions, so you could need to use others if you use s3fs on macOS or BSD

Version of s3fs being used (s3fs --version)

Amazon Simple Storage Service File System V1.90 (commit:5de92e9) with OpenSSL

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

Name        : fuse
Version     : 2.9.4
Release     : 1.18.amzn1
Architecture: x86_64

Kernel information (uname -r)

4.14.252-131.483.amzn1.x86_64

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

NAME="Amazon Linux AMI"
VERSION="2018.03"
ID="amzn"
ID_LIKE="rhel fedora"
VERSION_ID="2018.03"
PRETTY_NAME="Amazon Linux AMI 2018.03"
ANSI_COLOR="0;33"
CPE_NAME="cpe:/o:amazon:linux:2018.03:ga"
HOME_URL="http://aws.amazon.com/amazon-linux-ami/"

s3fs command line used, if applicable

/etc/fstab entry, if applicable

mybucket:/prefix /my/mount/point fuse.s3fs _netdev,allow_other,endpoint=us-east-2,iam_role=auto,uid=559,gid=501,url=https://s3-us-east-2.amazonaws.com,dbglevel=info,curldbg 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

Dec 22 10:02:01 ip-10-10-21-199 s3fs[26040]: [path=/]
Dec 22 10:03:08 ip-10-10-21-199 s3fs[26040]: [path=/keyname.zip]
Dec 22 10:03:08 ip-10-10-21-199 s3fs[26040]: [path=/keyname.zip.filepart]
Dec 22 10:03:08 ip-10-10-21-199 s3fs[26040]:       [tpath=/keyname.zip.filepart]
Dec 22 10:03:08 ip-10-10-21-199 s3fs[26040]:       [tpath=/keyname.zip.filepart][bpath=][save=][sseckeypos=18446744073709551615]
Dec 22 10:03:08 ip-10-10-21-199 s3fs[26040]:       URL is https://s3-us-east-2.amazonaws.com/bucketname/prefix/keyname.zip.filepart
Dec 22 10:03:08 ip-10-10-21-199 s3fs[26040]:       URL changed is https://bucketname.s3-us-east-2.amazonaws.com/prefix/keyname.zip.filepart
Dec 22 10:03:08 ip-10-10-21-199 s3fs[26040]:       computing signature [HEAD] [/prefix/keyname.zip.filepart] [] []
Dec 22 10:03:08 ip-10-10-21-199 s3fs[26040]:       url is https://s3-us-east-2.amazonaws.com
Dec 22 10:03:08 ip-10-10-21-199 s3fs[26040]: * Connection 10 seems to be dead!
Dec 22 10:03:08 ip-10-10-21-199 s3fs[26040]: * Closing connection 10
Dec 22 10:03:08 ip-10-10-21-199 s3fs[26040]: * TLSv1.2 (OUT), TLS alert, close notify (256):
Dec 22 10:03:08 ip-10-10-21-199 s3fs[26040]: *   Trying 52.219.101.170...
Dec 22 10:03:08 ip-10-10-21-199 s3fs[26040]: * TCP_NODELAY set
Dec 22 10:03:08 ip-10-10-21-199 s3fs[26040]: * Connected to bucketname.s3-us-east-2.amazonaws.com (52.219.101.170) port 443 (#11)
Dec 22 10:03:08 ip-10-10-21-199 s3fs[26040]: * Cipher selection: ALL:!EXPORT:!EXPORT40:!EXPORT56:!aNULL:!LOW:!RC4:@STRENGTH
Dec 22 10:03:08 ip-10-10-21-199 s3fs[26040]: * successfully set certificate verify locations:
Dec 22 10:03:08 ip-10-10-21-199 s3fs[26040]: *   CAfile: /etc/pki/tls/certs/ca-bundle.crt#012  CApath: none
Dec 22 10:03:08 ip-10-10-21-199 s3fs[26040]: * SSL re-using session ID
Dec 22 10:03:08 ip-10-10-21-199 s3fs[26040]: * TLSv1.2 (OUT), TLS handshake, Client hello (1):
Dec 22 10:03:08 ip-10-10-21-199 s3fs[26040]: * TLSv1.2 (IN), TLS handshake, Server hello (2):
Dec 22 10:03:08 ip-10-10-21-199 s3fs[26040]: * TLSv1.2 (IN), TLS handshake, Certificate (11):
Dec 22 10:03:08 ip-10-10-21-199 s3fs[26040]: * TLSv1.2 (IN), TLS handshake, Server key exchange (12):
Dec 22 10:03:08 ip-10-10-21-199 s3fs[26040]: * TLSv1.2 (IN), TLS handshake, Server finished (14):
Dec 22 10:03:08 ip-10-10-21-199 s3fs[26040]: * TLSv1.2 (OUT), TLS handshake, Client key exchange (16):
Dec 22 10:03:08 ip-10-10-21-199 s3fs[26040]: * TLSv1.2 (OUT), TLS change cipher, Change cipher spec (1):
Dec 22 10:03:08 ip-10-10-21-199 s3fs[26040]: * TLSv1.2 (OUT), TLS handshake, Finished (20):
Dec 22 10:03:08 ip-10-10-21-199 s3fs[26040]: * TLSv1.2 (IN), TLS change cipher, Change cipher spec (1):
Dec 22 10:03:08 ip-10-10-21-199 s3fs[26040]: * TLSv1.2 (IN), TLS handshake, Finished (20):
Dec 22 10:03:08 ip-10-10-21-199 s3fs[26040]: * SSL connection using TLSv1.2 / ECDHE-RSA-AES128-GCM-SHA256
Dec 22 10:03:08 ip-10-10-21-199 s3fs[26040]: * old SSL session ID is stale, removing
Dec 22 10:03:08 ip-10-10-21-199 s3fs[26040]: * Server certificate:
Dec 22 10:03:08 ip-10-10-21-199 s3fs[26040]: *  subject: CN=*.s3.us-east-2.amazonaws.com
Dec 22 10:03:08 ip-10-10-21-199 s3fs[26040]: *  start date: Mar 24 00:00:00 2021 GMT
Dec 22 10:03:08 ip-10-10-21-199 s3fs[26040]: *  expire date: Mar 19 23:59:59 2022 GMT
Dec 22 10:03:08 ip-10-10-21-199 s3fs[26040]: *  subjectAltName: host "bucketname.s3-us-east-2.amazonaws.com" matched cert's "*.s3-us-east-2.amazonaws.com"
Dec 22 10:03:08 ip-10-10-21-199 s3fs[26040]: *  issuer: C=US; O=Amazon; OU=Server CA 1B; CN=Amazon
Dec 22 10:03:08 ip-10-10-21-199 s3fs[26040]: *  SSL certificate verify ok.
Dec 22 10:03:08 ip-10-10-21-199 s3fs[26040]: > HEAD /prefix/keyname.zip.filepart HTTP/1.1
Dec 22 10:03:08 ip-10-10-21-199 s3fs[26040]: > Host: bucketname.s3-us-east-2.amazonaws.com
Dec 22 10:03:08 ip-10-10-21-199 s3fs[26040]: > User-Agent: s3fs/1.90 (commit hash 5de92e9; OpenSSL)
Dec 22 10:03:08 ip-10-10-21-199 s3fs[26040]: > Accept: */*
Dec 22 10:03:08 ip-10-10-21-199 s3fs[26040]: > Authorization: AWS4-HMAC-SHA256 Credential=ASIAUIKCI7XFAO7ATIGL/20211222/us-east-2/s3/aws4_request, SignedHeaders=host;x-amz-content-sha256;x-amz-date;x-amz-security-token, Signature=1415c258522d027af915efb9dfb91bc303c359f9cf339d33924bb70a2e9c8480
Dec 22 10:03:08 ip-10-10-21-199 s3fs[26040]: > x-amz-content-sha256: e3b0c44298fc1c149afbf4c8996fb92427ae41e4649b934ca495991b7852b855
Dec 22 10:03:08 ip-10-10-21-199 s3fs[26040]: > x-amz-date: 20211222T100308Z
Dec 22 10:03:08 ip-10-10-21-199 s3fs[26040]: > x-amz-security-token: **security token***
Dec 22 10:03:08 ip-10-10-21-199 s3fs[26040]: >
Dec 22 10:03:08 ip-10-10-21-199 s3fs[26040]: < HTTP/1.1 404 Not Found
Dec 22 10:03:08 ip-10-10-21-199 s3fs[26040]: < x-amz-request-id: BYF613969MZJ2T4R
Dec 22 10:03:08 ip-10-10-21-199 s3fs[26040]: < x-amz-id-2: r0Dh6a86VVc6BSib5GJGLQPCO5z2gtCGRJ7pclNDOk7k84snOIGhBi6kGkgpLFw1eP4+AZwdZFg=
Dec 22 10:03:08 ip-10-10-21-199 s3fs[26040]: < Content-Type: application/xml
Dec 22 10:03:08 ip-10-10-21-199 s3fs[26040]: < Date: Wed, 22 Dec 2021 10:03:07 GMT
Dec 22 10:03:08 ip-10-10-21-199 s3fs[26040]: < Server: AmazonS3
Dec 22 10:03:08 ip-10-10-21-199 s3fs[26040]: <
Dec 22 10:03:08 ip-10-10-21-199 s3fs[26040]: * Connection #11 to host bucketname.s3-us-east-2.amazonaws.com left intact
Dec 22 10:03:08 ip-10-10-21-199 s3fs[26040]:       HTTP response code 404 was returned, returning ENOENT
Dec 22 10:03:08 ip-10-10-21-199 s3fs[26040]:       [tpath=/keyname.zip.filepart/]
Dec 22 10:03:08 ip-10-10-21-199 s3fs[26040]:       [tpath=/keyname.zip.filepart/][bpath=][save=][sseckeypos=18446744073709551615]
Dec 22 10:03:08 ip-10-10-21-199 s3fs[26040]:       URL is https://s3-us-east-2.amazonaws.com/bucketname/prefix/keyname.zip.filepart/
Dec 22 10:03:08 ip-10-10-21-199 s3fs[26040]:       URL changed is https://bucketname.s3-us-east-2.amazonaws.com/prefix/keyname.zip.filepart/
Dec 22 10:03:08 ip-10-10-21-199 s3fs[26040]:       computing signature [HEAD] [/prefix/keyname.zip.filepart/] [] []
Dec 22 10:03:08 ip-10-10-21-199 s3fs[26040]:       url is https://s3-us-east-2.amazonaws.com
Dec 22 10:03:08 ip-10-10-21-199 s3fs[26040]: * Found bundle for host bucketname.s3-us-east-2.amazonaws.com: 0x7f83ac009880 [can pipeline]
Dec 22 10:03:08 ip-10-10-21-199 s3fs[26040]: * Re-using existing connection! (#11) with host bucketname.s3-us-east-2.amazonaws.com
Dec 22 10:03:08 ip-10-10-21-199 s3fs[26040]: * Connected to bucketname.s3-us-east-2.amazonaws.com (52.219.101.170) port 443 (#11)
Dec 22 10:03:08 ip-10-10-21-199 s3fs[26040]: > HEAD /prefix/keyname.zip.filepart/ HTTP/1.1
Dec 22 10:03:08 ip-10-10-21-199 s3fs[26040]: > Host: bucketname.s3-us-east-2.amazonaws.com
Dec 22 10:03:08 ip-10-10-21-199 s3fs[26040]: > User-Agent: s3fs/1.90 (commit hash 5de92e9; OpenSSL)
Dec 22 10:03:08 ip-10-10-21-199 s3fs[26040]: > Accept: */*
Dec 22 10:03:08 ip-10-10-21-199 s3fs[26040]: > Authorization: AWS4-HMAC-SHA256 Credential=ASIAUIKCI7XFAO7ATIGL/20211222/us-east-2/s3/aws4_request, SignedHeaders=host;x-amz-content-sha256;x-amz-date;x-amz-security-token, Signature=b63371e9e71871bfdb6932b5e3ffbd22813a81c820ba875bcb95da947b016ec7
Dec 22 10:03:08 ip-10-10-21-199 s3fs[26040]: > x-amz-content-sha256: e3b0c44298fc1c149afbf4c8996fb92427ae41e4649b934ca495991b7852b855
Dec 22 10:03:08 ip-10-10-21-199 s3fs[26040]: > x-amz-date: 20211222T100308Z
Dec 22 10:03:08 ip-10-10-21-199 s3fs[26040]: > x-amz-security-token: ****
Dec 22 10:03:08 ip-10-10-21-199 s3fs[26040]: >
Dec 22 10:03:08 ip-10-10-21-199 s3fs[26040]: < HTTP/1.1 404 Not Found
Dec 22 10:03:08 ip-10-10-21-199 s3fs[26040]: < x-amz-request-id: BYF04JZ4CSBCYYK6
Dec 22 10:03:08 ip-10-10-21-199 s3fs[26040]: < x-amz-id-2: gy8EDtVlf09xIjIERTA8AWrZEmpQW7CHdCHif1S8rIbM7EzcHmCbiOR29fDJAxphgRQv/zfr81U=
Dec 22 10:03:08 ip-10-10-21-199 s3fs[26040]: < Content-Type: application/xml
Dec 22 10:03:08 ip-10-10-21-199 s3fs[26040]: < Date: Wed, 22 Dec 2021 10:03:07 GMT
Dec 22 10:03:08 ip-10-10-21-199 s3fs[26040]: < Server: AmazonS3
Dec 22 10:03:08 ip-10-10-21-199 s3fs[26040]: <
Dec 22 10:03:08 ip-10-10-21-199 s3fs[26040]: * Connection #11 to host bucketname.s3-us-east-2.amazonaws.com left intact
Dec 22 10:03:08 ip-10-10-21-199 s3fs[26040]:       HTTP response code 404 was returned, returning ENOENT
Dec 22 10:03:08 ip-10-10-21-199 s3fs[26040]:       [tpath=/keyname.zip.filepart_$folder$]
Dec 22 10:03:08 ip-10-10-21-199 s3fs[26040]:       [tpath=/keyname.zip.filepart_$folder$][bpath=][save=][sseckeypos=18446744073709551615]
Dec 22 10:03:08 ip-10-10-21-199 s3fs[26040]:       URL is https://s3-us-east-2.amazonaws.com/bucketname/prefix/keyname.zip.filepart_%24folder%24
Dec 22 10:03:08 ip-10-10-21-199 s3fs[26040]:       URL changed is https://bucketname.s3-us-east-2.amazonaws.com/prefix/keyname.zip.filepart_%24folder%24
Dec 22 10:03:08 ip-10-10-21-199 s3fs[26040]:       computing signature [HEAD] [/prefix/keyname.zip.filepart_$folder$] [] []
Dec 22 10:03:08 ip-10-10-21-199 s3fs[26040]:       url is https://s3-us-east-2.amazonaws.com
Dec 22 10:03:08 ip-10-10-21-199 s3fs[26040]: * Found bundle for host bucketname.s3-us-east-2.amazonaws.com: 0x7f83ac009880 [can pipeline]
Dec 22 10:03:08 ip-10-10-21-199 s3fs[26040]: * Re-using existing connection! (#11) with host bucketname.s3-us-east-2.amazonaws.com
Dec 22 10:03:08 ip-10-10-21-199 s3fs[26040]: * Connected to bucketname.s3-us-east-2.amazonaws.com (52.219.101.170) port 443 (#11)
Dec 22 10:03:08 ip-10-10-21-199 s3fs[26040]: > HEAD /prefix/keyname.zip.filepart_%24folder%24 HTTP/1.1
Dec 22 10:03:08 ip-10-10-21-199 s3fs[26040]: > Host: bucketname.s3-us-east-2.amazonaws.com
Dec 22 10:03:08 ip-10-10-21-199 s3fs[26040]: > User-Agent: s3fs/1.90 (commit hash 5de92e9; OpenSSL)
Dec 22 10:03:08 ip-10-10-21-199 s3fs[26040]: > Accept: */*
Dec 22 10:03:08 ip-10-10-21-199 s3fs[26040]: > Authorization: AWS4-HMAC-SHA256 Credential=ASIAUIKCI7XFAO7ATIGL/20211222/us-east-2/s3/aws4_request, SignedHeaders=host;x-amz-content-sha256;x-amz-date;x-amz-security-token, Signature=3e3030cb8393fbf23fda67564444bdc0ad8aa201c0d9c8af2c9a974eff232b2e
Dec 22 10:03:08 ip-10-10-21-199 s3fs[26040]: > x-amz-content-sha256: e3b0c44298fc1c149afbf4c8996fb92427ae41e4649b934ca495991b7852b855
Dec 22 10:03:08 ip-10-10-21-199 s3fs[26040]: > x-amz-date: 20211222T100308Z
Dec 22 10:03:08 ip-10-10-21-199 s3fs[26040]: > x-amz-security-token: ****
Dec 22 10:03:08 ip-10-10-21-199 s3fs[26040]: >
Dec 22 10:03:08 ip-10-10-21-199 s3fs[26040]: < HTTP/1.1 404 Not Found
Dec 22 10:03:08 ip-10-10-21-199 s3fs[26040]: < x-amz-request-id: BYF6E0KPRZ1GBG9M
Dec 22 10:03:08 ip-10-10-21-199 s3fs[26040]: < x-amz-id-2: vDbQogrhPbcmkx8UmpnjY4eeG6encUMswwnna/QnkVcc2veXIG+5VhMNqM/Bke6neBqjoc8GSIA=
Dec 22 10:03:08 ip-10-10-21-199 s3fs[26040]: < Content-Type: application/xml
Dec 22 10:03:08 ip-10-10-21-199 s3fs[26040]: < Date: Wed, 22 Dec 2021 10:03:07 GMT
Dec 22 10:03:08 ip-10-10-21-199 s3fs[26040]: < Server: AmazonS3
Dec 22 10:03:08 ip-10-10-21-199 s3fs[26040]: <
Dec 22 10:03:08 ip-10-10-21-199 s3fs[26040]: * Connection #11 to host bucketname.s3-us-east-2.amazonaws.com left intact
Dec 22 10:03:08 ip-10-10-21-199 s3fs[26040]:       HTTP response code 404 was returned, returning ENOENT
Dec 22 10:03:08 ip-10-10-21-199 s3fs[26040]:   [path=/keyname.zip.filepart]
Dec 22 10:03:08 ip-10-10-21-199 s3fs[26040]:       [tpath=/keyname.zip.filepart]
Dec 22 10:03:08 ip-10-10-21-199 s3fs[26040]:       URL is https://s3-us-east-2.amazonaws.com/bucketname?delimiter=/&max-keys=2&prefix=prefix/keyname.zip.filepart/
Dec 22 10:03:08 ip-10-10-21-199 s3fs[26040]:       URL changed is https://bucketname.s3-us-east-2.amazonaws.com?delimiter=/&max-keys=2&prefix=prefix/keyname.zip.filepart/
Dec 22 10:03:08 ip-10-10-21-199 s3fs[26040]:       computing signature [GET] [/] [delimiter=/&max-keys=2&prefix=prefix/keyname.zip.filepart/] []
Dec 22 10:03:08 ip-10-10-21-199 s3fs[26040]:       url is https://s3-us-east-2.amazonaws.com
Dec 22 10:03:08 ip-10-10-21-199 s3fs[26040]: * Rebuilt URL to: https://bucketname.s3-us-east-2.amazonaws.com/?delimiter=/&max-keys=2&prefix=prefix/keyname.zip.filepart/
Dec 22 10:03:08 ip-10-10-21-199 s3fs[26040]: * Found bundle for host bucketname.s3-us-east-2.amazonaws.com: 0x7f83ac009880 [can pipeline]
Dec 22 10:03:08 ip-10-10-21-199 s3fs[26040]: * Re-using existing connection! (#11) with host bucketname.s3-us-east-2.amazonaws.com
Dec 22 10:03:08 ip-10-10-21-199 s3fs[26040]: * Connected to bucketname.s3-us-east-2.amazonaws.com (52.219.101.170) port 443 (#11)
Dec 22 10:03:08 ip-10-10-21-199 s3fs[26040]: > GET /?delimiter=/&max-keys=2&prefix=prefix/keyname.zip.filepart/ HTTP/1.1
Dec 22 10:03:08 ip-10-10-21-199 s3fs[26040]: > Host: bucketname.s3-us-east-2.amazonaws.com
Dec 22 10:03:08 ip-10-10-21-199 s3fs[26040]: > User-Agent: s3fs/1.90 (commit hash 5de92e9; OpenSSL)
Dec 22 10:03:08 ip-10-10-21-199 s3fs[26040]: > Accept: */*
Dec 22 10:03:08 ip-10-10-21-199 s3fs[26040]: > Authorization: AWS4-HMAC-SHA256 Credential=ASIAUIKCI7XFAO7ATIGL/20211222/us-east-2/s3/aws4_request, SignedHeaders=host;x-amz-content-sha256;x-amz-date;x-amz-security-token, Signature=55861304dbeca55aaae47966e6a787bcf03e572ceaf59f1ae18b7b0f3c1aae61
Dec 22 10:03:08 ip-10-10-21-199 s3fs[26040]: > x-amz-content-sha256: e3b0c44298fc1c149afbf4c8996fb92427ae41e4649b934ca495991b7852b855
Dec 22 10:03:08 ip-10-10-21-199 s3fs[26040]: > x-amz-date: 20211222T100308Z
Dec 22 10:03:08 ip-10-10-21-199 s3fs[26040]: > x-amz-security-token: ****
Dec 22 10:03:08 ip-10-10-21-199 s3fs[26040]: >
Dec 22 10:03:08 ip-10-10-21-199 s3fs[26040]: < HTTP/1.1 200 OK
Dec 22 10:03:08 ip-10-10-21-199 s3fs[26040]: < x-amz-id-2: hrxqFPwjPjqQYLSXYNu0jAfGyCaqq6VZQ2APIaaHFVU2o1kYTSBNHGPq0s5oaKt861bOFFuXoQU=
Dec 22 10:03:08 ip-10-10-21-199 s3fs[26040]: < x-amz-request-id: BYF8P9ZP7MTVY1GK
Dec 22 10:03:08 ip-10-10-21-199 s3fs[26040]: < Date: Wed, 22 Dec 2021 10:03:09 GMT
Dec 22 10:03:08 ip-10-10-21-199 s3fs[26040]: < x-amz-bucket-region: us-east-2
Dec 22 10:03:08 ip-10-10-21-199 s3fs[26040]: < Content-Type: application/xml
Dec 22 10:03:08 ip-10-10-21-199 s3fs[26040]: < Transfer-Encoding: chunked
Dec 22 10:03:08 ip-10-10-21-199 s3fs[26040]: < Server: AmazonS3
Dec 22 10:03:08 ip-10-10-21-199 s3fs[26040]: <
Dec 22 10:03:08 ip-10-10-21-199 s3fs[26040]: * Connection #11 to host bucketname.s3-us-east-2.amazonaws.com left intact
Dec 22 10:03:08 ip-10-10-21-199 s3fs[26040]:       HTTP response code 200
Dec 22 10:03:11 ip-10-10-21-199 s3fs[26040]: [path=/keyname.zip.filepart]
Dec 22 10:03:11 ip-10-10-21-199 s3fs[26040]:       [tpath=/keyname.zip.filepart]
Dec 22 10:03:11 ip-10-10-21-199 s3fs[26040]:       [tpath=/keyname.zip.filepart][bpath=][save=][sseckeypos=18446744073709551615]
Dec 22 10:03:11 ip-10-10-21-199 s3fs[26040]:       URL is https://s3-us-east-2.amazonaws.com/bucketname/prefix/keyname.zip.filepart
Dec 22 10:03:11 ip-10-10-21-199 s3fs[26040]:       URL changed is https://bucketname.s3-us-east-2.amazonaws.com/prefix/keyname.zip.filepart
Dec 22 10:03:11 ip-10-10-21-199 s3fs[26040]:       computing signature [HEAD] [/prefix/keyname.zip.filepart] [] []
Dec 22 10:03:11 ip-10-10-21-199 s3fs[26040]:       url is https://s3-us-east-2.amazonaws.com
Dec 22 10:03:11 ip-10-10-21-199 s3fs[26040]: * Found bundle for host bucketname.s3-us-east-2.amazonaws.com: 0x7f83ac009880 [can pipeline]
Dec 22 10:03:11 ip-10-10-21-199 s3fs[26040]: * Re-using existing connection! (#11) with host bucketname.s3-us-east-2.amazonaws.com
Dec 22 10:03:11 ip-10-10-21-199 s3fs[26040]: * Connected to bucketname.s3-us-east-2.amazonaws.com (52.219.101.170) port 443 (#11)
Dec 22 10:03:11 ip-10-10-21-199 s3fs[26040]: > HEAD /prefix/keyname.zip.filepart HTTP/1.1
Dec 22 10:03:11 ip-10-10-21-199 s3fs[26040]: > Host: bucketname.s3-us-east-2.amazonaws.com
Dec 22 10:03:11 ip-10-10-21-199 s3fs[26040]: > User-Agent: s3fs/1.90 (commit hash 5de92e9; OpenSSL)
Dec 22 10:03:11 ip-10-10-21-199 s3fs[26040]: > Accept: */*
Dec 22 10:03:11 ip-10-10-21-199 s3fs[26040]: > Authorization: AWS4-HMAC-SHA256 Credential=ASIAUIKCI7XFAO7ATIGL/20211222/us-east-2/s3/aws4_request, SignedHeaders=host;x-amz-content-sha256;x-amz-date;x-amz-security-token, Signature=d56b0a452517cf32e8daa065327aaccc13ce75d914efce03a9ce6d1255eeaeb5
Dec 22 10:03:11 ip-10-10-21-199 s3fs[26040]: > x-amz-content-sha256: e3b0c44298fc1c149afbf4c8996fb92427ae41e4649b934ca495991b7852b855
Dec 22 10:03:11 ip-10-10-21-199 s3fs[26040]: > x-amz-date: 20211222T100311Z
Dec 22 10:03:11 ip-10-10-21-199 s3fs[26040]: > x-amz-security-token: *****
Dec 22 10:03:11 ip-10-10-21-199 s3fs[26040]: >
Dec 22 10:03:11 ip-10-10-21-199 s3fs[26040]: < HTTP/1.1 404 Not Found
Dec 22 10:03:11 ip-10-10-21-199 s3fs[26040]: < x-amz-request-id: HWH9T7D6394KY6RC
Dec 22 10:03:11 ip-10-10-21-199 s3fs[26040]: < x-amz-id-2: kwg8xXZnDbzZrlINnyugPyJi2tnaqeXthpWRawQjBiGpX6HNPY3Y9ttMMpvB71CupyWyDgrCZ/M=
Dec 22 10:03:11 ip-10-10-21-199 s3fs[26040]: < Content-Type: application/xml
Dec 22 10:03:11 ip-10-10-21-199 s3fs[26040]: < Date: Wed, 22 Dec 2021 10:03:10 GMT
Dec 22 10:03:11 ip-10-10-21-199 s3fs[26040]: < Server: AmazonS3
Dec 22 10:03:11 ip-10-10-21-199 s3fs[26040]: <
Dec 22 10:03:11 ip-10-10-21-199 s3fs[26040]: * Connection #11 to host bucketname.s3-us-east-2.amazonaws.com left intact
Dec 22 10:03:11 ip-10-10-21-199 s3fs[26040]:       HTTP response code 404 was returned, returning ENOENT
Dec 22 10:03:11 ip-10-10-21-199 s3fs[26040]:       [tpath=/keyname.zip.filepart/]
Dec 22 10:03:11 ip-10-10-21-199 s3fs[26040]:       [tpath=/keyname.zip.filepart/][bpath=][save=][sseckeypos=18446744073709551615]
Dec 22 10:03:11 ip-10-10-21-199 s3fs[26040]:       URL is https://s3-us-east-2.amazonaws.com/bucketname/prefix/keyname.zip.filepart/
Dec 22 10:03:11 ip-10-10-21-199 s3fs[26040]:       URL changed is https://bucketname.s3-us-east-2.amazonaws.com/prefix/keyname.zip.filepart/
Dec 22 10:03:11 ip-10-10-21-199 s3fs[26040]:       computing signature [HEAD] [/prefix/keyname.zip.filepart/] [] []
Dec 22 10:03:11 ip-10-10-21-199 s3fs[26040]:       url is https://s3-us-east-2.amazonaws.com
Dec 22 10:03:11 ip-10-10-21-199 s3fs[26040]: * Found bundle for host bucketname.s3-us-east-2.amazonaws.com: 0x7f83ac009880 [can pipeline]
Dec 22 10:03:11 ip-10-10-21-199 s3fs[26040]: * Re-using existing connection! (#11) with host bucketname.s3-us-east-2.amazonaws.com
Dec 22 10:03:11 ip-10-10-21-199 s3fs[26040]: * Connected to bucketname.s3-us-east-2.amazonaws.com (52.219.101.170) port 443 (#11)
Dec 22 10:03:11 ip-10-10-21-199 s3fs[26040]: > HEAD /prefix/keyname.zip.filepart/ HTTP/1.1
Dec 22 10:03:11 ip-10-10-21-199 s3fs[26040]: > Host: bucketname.s3-us-east-2.amazonaws.com
Dec 22 10:03:11 ip-10-10-21-199 s3fs[26040]: > User-Agent: s3fs/1.90 (commit hash 5de92e9; OpenSSL)
Dec 22 10:03:11 ip-10-10-21-199 s3fs[26040]: > Accept: */*
Dec 22 10:03:11 ip-10-10-21-199 s3fs[26040]: > Authorization: AWS4-HMAC-SHA256 Credential=ASIAUIKCI7XFAO7ATIGL/20211222/us-east-2/s3/aws4_request, SignedHeaders=host;x-amz-content-sha256;x-amz-date;x-amz-security-token, Signature=2ed9ea1ba990b004fc247cc8d7be8da6095029b994f9dc98c52b52bb384a9076
Dec 22 10:03:11 ip-10-10-21-199 s3fs[26040]: > x-amz-content-sha256: ****
Dec 22 10:03:11 ip-10-10-21-199 s3fs[26040]: > x-amz-date: 20211222T100311Z
Dec 22 10:03:11 ip-10-10-21-199 s3fs[26040]: > x-amz-security-token: ****
Dec 22 10:03:11 ip-10-10-21-199 s3fs[26040]: >
Dec 22 10:03:11 ip-10-10-21-199 s3fs[26040]: < HTTP/1.1 404 Not Found
Dec 22 10:03:11 ip-10-10-21-199 s3fs[26040]: < x-amz-request-id: HWH1HZWBE7WGF2ZY
Dec 22 10:03:11 ip-10-10-21-199 s3fs[26040]: < x-amz-id-2: iA+/RW2Wxs4Qf41sdoa5+aHcB9vGj9LMdo5BWhJHOtWM8EyYgpp7Sc+XPGDuAPIjDCrPBYd9IVA=
Dec 22 10:03:11 ip-10-10-21-199 s3fs[26040]: < Content-Type: application/xml
Dec 22 10:03:11 ip-10-10-21-199 s3fs[26040]: < Date: Wed, 22 Dec 2021 10:03:10 GMT
Dec 22 10:03:11 ip-10-10-21-199 s3fs[26040]: < Server: AmazonS3
Dec 22 10:03:11 ip-10-10-21-199 s3fs[26040]: <
Dec 22 10:03:11 ip-10-10-21-199 s3fs[26040]: * Connection #11 to host bucketname.s3-us-east-2.amazonaws.com left intact
Dec 22 10:03:11 ip-10-10-21-199 s3fs[26040]:       HTTP response code 404 was returned, returning ENOENT
Dec 22 10:03:11 ip-10-10-21-199 s3fs[26040]:       [tpath=/keyname.zip.filepart_$folder$]
Dec 22 10:03:11 ip-10-10-21-199 s3fs[26040]:       [tpath=/keyname.zip.filepart_$folder$][bpath=][save=][sseckeypos=18446744073709551615]
Dec 22 10:03:11 ip-10-10-21-199 s3fs[26040]:       URL is https://s3-us-east-2.amazonaws.com/bucketname/prefix/keyname.zip.filepart_%24folder%24
Dec 22 10:03:11 ip-10-10-21-199 s3fs[26040]:       URL changed is https://bucketname.s3-us-east-2.amazonaws.com/prefix/keyname.zip.filepart_%24folder%24
Dec 22 10:03:11 ip-10-10-21-199 s3fs[26040]:       computing signature [HEAD] [/prefix/keyname.zip.filepart_$folder$] [] []
Dec 22 10:03:11 ip-10-10-21-199 s3fs[26040]:       url is https://s3-us-east-2.amazonaws.com
Dec 22 10:03:11 ip-10-10-21-199 rsyslogd-2177: imuxsock begins to drop messages from pid 26040 due to rate-limiting

Details about issue

Whenever I upload a file to an s3fs mount using WinSCP the logs never seem to get to the PUT request. According to the logs, the process keeps sending HEAD requests that return 404 Not Found, returning ENOENT. It never seems to register the PUT uploading request (though the file is accessible in the bucket) I do not have this issue with other sftp clients, just WinSCP.

Originally created by @CESteinmetz on GitHub (Dec 22, 2021). Original GitHub issue: https://github.com/s3fs-fuse/s3fs-fuse/issues/1821 ### 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._ _Keep in mind that the commands we provide to retrieve information are oriented to GNU/Linux Distributions, so you could need to use others if you use s3fs on macOS or BSD_ #### Version of s3fs being used (s3fs --version) `Amazon Simple Storage Service File System V1.90 (commit:5de92e9) with OpenSSL` #### Version of fuse being used (pkg-config --modversion fuse, rpm -qi fuse, dpkg -s fuse) ``` Name : fuse Version : 2.9.4 Release : 1.18.amzn1 Architecture: x86_64 ``` #### Kernel information (uname -r) ``` 4.14.252-131.483.amzn1.x86_64 ``` #### GNU/Linux Distribution, if applicable (cat /etc/os-release) ``` NAME="Amazon Linux AMI" VERSION="2018.03" ID="amzn" ID_LIKE="rhel fedora" VERSION_ID="2018.03" PRETTY_NAME="Amazon Linux AMI 2018.03" ANSI_COLOR="0;33" CPE_NAME="cpe:/o:amazon:linux:2018.03:ga" HOME_URL="http://aws.amazon.com/amazon-linux-ami/" ``` #### s3fs command line used, if applicable ``` ``` #### /etc/fstab entry, if applicable ``` mybucket:/prefix /my/mount/point fuse.s3fs _netdev,allow_other,endpoint=us-east-2,iam_role=auto,uid=559,gid=501,url=https://s3-us-east-2.amazonaws.com,dbglevel=info,curldbg 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_ ``` Dec 22 10:02:01 ip-10-10-21-199 s3fs[26040]: [path=/] Dec 22 10:03:08 ip-10-10-21-199 s3fs[26040]: [path=/keyname.zip] Dec 22 10:03:08 ip-10-10-21-199 s3fs[26040]: [path=/keyname.zip.filepart] Dec 22 10:03:08 ip-10-10-21-199 s3fs[26040]: [tpath=/keyname.zip.filepart] Dec 22 10:03:08 ip-10-10-21-199 s3fs[26040]: [tpath=/keyname.zip.filepart][bpath=][save=][sseckeypos=18446744073709551615] Dec 22 10:03:08 ip-10-10-21-199 s3fs[26040]: URL is https://s3-us-east-2.amazonaws.com/bucketname/prefix/keyname.zip.filepart Dec 22 10:03:08 ip-10-10-21-199 s3fs[26040]: URL changed is https://bucketname.s3-us-east-2.amazonaws.com/prefix/keyname.zip.filepart Dec 22 10:03:08 ip-10-10-21-199 s3fs[26040]: computing signature [HEAD] [/prefix/keyname.zip.filepart] [] [] Dec 22 10:03:08 ip-10-10-21-199 s3fs[26040]: url is https://s3-us-east-2.amazonaws.com Dec 22 10:03:08 ip-10-10-21-199 s3fs[26040]: * Connection 10 seems to be dead! Dec 22 10:03:08 ip-10-10-21-199 s3fs[26040]: * Closing connection 10 Dec 22 10:03:08 ip-10-10-21-199 s3fs[26040]: * TLSv1.2 (OUT), TLS alert, close notify (256): Dec 22 10:03:08 ip-10-10-21-199 s3fs[26040]: * Trying 52.219.101.170... Dec 22 10:03:08 ip-10-10-21-199 s3fs[26040]: * TCP_NODELAY set Dec 22 10:03:08 ip-10-10-21-199 s3fs[26040]: * Connected to bucketname.s3-us-east-2.amazonaws.com (52.219.101.170) port 443 (#11) Dec 22 10:03:08 ip-10-10-21-199 s3fs[26040]: * Cipher selection: ALL:!EXPORT:!EXPORT40:!EXPORT56:!aNULL:!LOW:!RC4:@STRENGTH Dec 22 10:03:08 ip-10-10-21-199 s3fs[26040]: * successfully set certificate verify locations: Dec 22 10:03:08 ip-10-10-21-199 s3fs[26040]: * CAfile: /etc/pki/tls/certs/ca-bundle.crt#012 CApath: none Dec 22 10:03:08 ip-10-10-21-199 s3fs[26040]: * SSL re-using session ID Dec 22 10:03:08 ip-10-10-21-199 s3fs[26040]: * TLSv1.2 (OUT), TLS handshake, Client hello (1): Dec 22 10:03:08 ip-10-10-21-199 s3fs[26040]: * TLSv1.2 (IN), TLS handshake, Server hello (2): Dec 22 10:03:08 ip-10-10-21-199 s3fs[26040]: * TLSv1.2 (IN), TLS handshake, Certificate (11): Dec 22 10:03:08 ip-10-10-21-199 s3fs[26040]: * TLSv1.2 (IN), TLS handshake, Server key exchange (12): Dec 22 10:03:08 ip-10-10-21-199 s3fs[26040]: * TLSv1.2 (IN), TLS handshake, Server finished (14): Dec 22 10:03:08 ip-10-10-21-199 s3fs[26040]: * TLSv1.2 (OUT), TLS handshake, Client key exchange (16): Dec 22 10:03:08 ip-10-10-21-199 s3fs[26040]: * TLSv1.2 (OUT), TLS change cipher, Change cipher spec (1): Dec 22 10:03:08 ip-10-10-21-199 s3fs[26040]: * TLSv1.2 (OUT), TLS handshake, Finished (20): Dec 22 10:03:08 ip-10-10-21-199 s3fs[26040]: * TLSv1.2 (IN), TLS change cipher, Change cipher spec (1): Dec 22 10:03:08 ip-10-10-21-199 s3fs[26040]: * TLSv1.2 (IN), TLS handshake, Finished (20): Dec 22 10:03:08 ip-10-10-21-199 s3fs[26040]: * SSL connection using TLSv1.2 / ECDHE-RSA-AES128-GCM-SHA256 Dec 22 10:03:08 ip-10-10-21-199 s3fs[26040]: * old SSL session ID is stale, removing Dec 22 10:03:08 ip-10-10-21-199 s3fs[26040]: * Server certificate: Dec 22 10:03:08 ip-10-10-21-199 s3fs[26040]: * subject: CN=*.s3.us-east-2.amazonaws.com Dec 22 10:03:08 ip-10-10-21-199 s3fs[26040]: * start date: Mar 24 00:00:00 2021 GMT Dec 22 10:03:08 ip-10-10-21-199 s3fs[26040]: * expire date: Mar 19 23:59:59 2022 GMT Dec 22 10:03:08 ip-10-10-21-199 s3fs[26040]: * subjectAltName: host "bucketname.s3-us-east-2.amazonaws.com" matched cert's "*.s3-us-east-2.amazonaws.com" Dec 22 10:03:08 ip-10-10-21-199 s3fs[26040]: * issuer: C=US; O=Amazon; OU=Server CA 1B; CN=Amazon Dec 22 10:03:08 ip-10-10-21-199 s3fs[26040]: * SSL certificate verify ok. Dec 22 10:03:08 ip-10-10-21-199 s3fs[26040]: > HEAD /prefix/keyname.zip.filepart HTTP/1.1 Dec 22 10:03:08 ip-10-10-21-199 s3fs[26040]: > Host: bucketname.s3-us-east-2.amazonaws.com Dec 22 10:03:08 ip-10-10-21-199 s3fs[26040]: > User-Agent: s3fs/1.90 (commit hash 5de92e9; OpenSSL) Dec 22 10:03:08 ip-10-10-21-199 s3fs[26040]: > Accept: */* Dec 22 10:03:08 ip-10-10-21-199 s3fs[26040]: > Authorization: AWS4-HMAC-SHA256 Credential=ASIAUIKCI7XFAO7ATIGL/20211222/us-east-2/s3/aws4_request, SignedHeaders=host;x-amz-content-sha256;x-amz-date;x-amz-security-token, Signature=1415c258522d027af915efb9dfb91bc303c359f9cf339d33924bb70a2e9c8480 Dec 22 10:03:08 ip-10-10-21-199 s3fs[26040]: > x-amz-content-sha256: e3b0c44298fc1c149afbf4c8996fb92427ae41e4649b934ca495991b7852b855 Dec 22 10:03:08 ip-10-10-21-199 s3fs[26040]: > x-amz-date: 20211222T100308Z Dec 22 10:03:08 ip-10-10-21-199 s3fs[26040]: > x-amz-security-token: **security token*** Dec 22 10:03:08 ip-10-10-21-199 s3fs[26040]: > Dec 22 10:03:08 ip-10-10-21-199 s3fs[26040]: < HTTP/1.1 404 Not Found Dec 22 10:03:08 ip-10-10-21-199 s3fs[26040]: < x-amz-request-id: BYF613969MZJ2T4R Dec 22 10:03:08 ip-10-10-21-199 s3fs[26040]: < x-amz-id-2: r0Dh6a86VVc6BSib5GJGLQPCO5z2gtCGRJ7pclNDOk7k84snOIGhBi6kGkgpLFw1eP4+AZwdZFg= Dec 22 10:03:08 ip-10-10-21-199 s3fs[26040]: < Content-Type: application/xml Dec 22 10:03:08 ip-10-10-21-199 s3fs[26040]: < Date: Wed, 22 Dec 2021 10:03:07 GMT Dec 22 10:03:08 ip-10-10-21-199 s3fs[26040]: < Server: AmazonS3 Dec 22 10:03:08 ip-10-10-21-199 s3fs[26040]: < Dec 22 10:03:08 ip-10-10-21-199 s3fs[26040]: * Connection #11 to host bucketname.s3-us-east-2.amazonaws.com left intact Dec 22 10:03:08 ip-10-10-21-199 s3fs[26040]: HTTP response code 404 was returned, returning ENOENT Dec 22 10:03:08 ip-10-10-21-199 s3fs[26040]: [tpath=/keyname.zip.filepart/] Dec 22 10:03:08 ip-10-10-21-199 s3fs[26040]: [tpath=/keyname.zip.filepart/][bpath=][save=][sseckeypos=18446744073709551615] Dec 22 10:03:08 ip-10-10-21-199 s3fs[26040]: URL is https://s3-us-east-2.amazonaws.com/bucketname/prefix/keyname.zip.filepart/ Dec 22 10:03:08 ip-10-10-21-199 s3fs[26040]: URL changed is https://bucketname.s3-us-east-2.amazonaws.com/prefix/keyname.zip.filepart/ Dec 22 10:03:08 ip-10-10-21-199 s3fs[26040]: computing signature [HEAD] [/prefix/keyname.zip.filepart/] [] [] Dec 22 10:03:08 ip-10-10-21-199 s3fs[26040]: url is https://s3-us-east-2.amazonaws.com Dec 22 10:03:08 ip-10-10-21-199 s3fs[26040]: * Found bundle for host bucketname.s3-us-east-2.amazonaws.com: 0x7f83ac009880 [can pipeline] Dec 22 10:03:08 ip-10-10-21-199 s3fs[26040]: * Re-using existing connection! (#11) with host bucketname.s3-us-east-2.amazonaws.com Dec 22 10:03:08 ip-10-10-21-199 s3fs[26040]: * Connected to bucketname.s3-us-east-2.amazonaws.com (52.219.101.170) port 443 (#11) Dec 22 10:03:08 ip-10-10-21-199 s3fs[26040]: > HEAD /prefix/keyname.zip.filepart/ HTTP/1.1 Dec 22 10:03:08 ip-10-10-21-199 s3fs[26040]: > Host: bucketname.s3-us-east-2.amazonaws.com Dec 22 10:03:08 ip-10-10-21-199 s3fs[26040]: > User-Agent: s3fs/1.90 (commit hash 5de92e9; OpenSSL) Dec 22 10:03:08 ip-10-10-21-199 s3fs[26040]: > Accept: */* Dec 22 10:03:08 ip-10-10-21-199 s3fs[26040]: > Authorization: AWS4-HMAC-SHA256 Credential=ASIAUIKCI7XFAO7ATIGL/20211222/us-east-2/s3/aws4_request, SignedHeaders=host;x-amz-content-sha256;x-amz-date;x-amz-security-token, Signature=b63371e9e71871bfdb6932b5e3ffbd22813a81c820ba875bcb95da947b016ec7 Dec 22 10:03:08 ip-10-10-21-199 s3fs[26040]: > x-amz-content-sha256: e3b0c44298fc1c149afbf4c8996fb92427ae41e4649b934ca495991b7852b855 Dec 22 10:03:08 ip-10-10-21-199 s3fs[26040]: > x-amz-date: 20211222T100308Z Dec 22 10:03:08 ip-10-10-21-199 s3fs[26040]: > x-amz-security-token: **** Dec 22 10:03:08 ip-10-10-21-199 s3fs[26040]: > Dec 22 10:03:08 ip-10-10-21-199 s3fs[26040]: < HTTP/1.1 404 Not Found Dec 22 10:03:08 ip-10-10-21-199 s3fs[26040]: < x-amz-request-id: BYF04JZ4CSBCYYK6 Dec 22 10:03:08 ip-10-10-21-199 s3fs[26040]: < x-amz-id-2: gy8EDtVlf09xIjIERTA8AWrZEmpQW7CHdCHif1S8rIbM7EzcHmCbiOR29fDJAxphgRQv/zfr81U= Dec 22 10:03:08 ip-10-10-21-199 s3fs[26040]: < Content-Type: application/xml Dec 22 10:03:08 ip-10-10-21-199 s3fs[26040]: < Date: Wed, 22 Dec 2021 10:03:07 GMT Dec 22 10:03:08 ip-10-10-21-199 s3fs[26040]: < Server: AmazonS3 Dec 22 10:03:08 ip-10-10-21-199 s3fs[26040]: < Dec 22 10:03:08 ip-10-10-21-199 s3fs[26040]: * Connection #11 to host bucketname.s3-us-east-2.amazonaws.com left intact Dec 22 10:03:08 ip-10-10-21-199 s3fs[26040]: HTTP response code 404 was returned, returning ENOENT Dec 22 10:03:08 ip-10-10-21-199 s3fs[26040]: [tpath=/keyname.zip.filepart_$folder$] Dec 22 10:03:08 ip-10-10-21-199 s3fs[26040]: [tpath=/keyname.zip.filepart_$folder$][bpath=][save=][sseckeypos=18446744073709551615] Dec 22 10:03:08 ip-10-10-21-199 s3fs[26040]: URL is https://s3-us-east-2.amazonaws.com/bucketname/prefix/keyname.zip.filepart_%24folder%24 Dec 22 10:03:08 ip-10-10-21-199 s3fs[26040]: URL changed is https://bucketname.s3-us-east-2.amazonaws.com/prefix/keyname.zip.filepart_%24folder%24 Dec 22 10:03:08 ip-10-10-21-199 s3fs[26040]: computing signature [HEAD] [/prefix/keyname.zip.filepart_$folder$] [] [] Dec 22 10:03:08 ip-10-10-21-199 s3fs[26040]: url is https://s3-us-east-2.amazonaws.com Dec 22 10:03:08 ip-10-10-21-199 s3fs[26040]: * Found bundle for host bucketname.s3-us-east-2.amazonaws.com: 0x7f83ac009880 [can pipeline] Dec 22 10:03:08 ip-10-10-21-199 s3fs[26040]: * Re-using existing connection! (#11) with host bucketname.s3-us-east-2.amazonaws.com Dec 22 10:03:08 ip-10-10-21-199 s3fs[26040]: * Connected to bucketname.s3-us-east-2.amazonaws.com (52.219.101.170) port 443 (#11) Dec 22 10:03:08 ip-10-10-21-199 s3fs[26040]: > HEAD /prefix/keyname.zip.filepart_%24folder%24 HTTP/1.1 Dec 22 10:03:08 ip-10-10-21-199 s3fs[26040]: > Host: bucketname.s3-us-east-2.amazonaws.com Dec 22 10:03:08 ip-10-10-21-199 s3fs[26040]: > User-Agent: s3fs/1.90 (commit hash 5de92e9; OpenSSL) Dec 22 10:03:08 ip-10-10-21-199 s3fs[26040]: > Accept: */* Dec 22 10:03:08 ip-10-10-21-199 s3fs[26040]: > Authorization: AWS4-HMAC-SHA256 Credential=ASIAUIKCI7XFAO7ATIGL/20211222/us-east-2/s3/aws4_request, SignedHeaders=host;x-amz-content-sha256;x-amz-date;x-amz-security-token, Signature=3e3030cb8393fbf23fda67564444bdc0ad8aa201c0d9c8af2c9a974eff232b2e Dec 22 10:03:08 ip-10-10-21-199 s3fs[26040]: > x-amz-content-sha256: e3b0c44298fc1c149afbf4c8996fb92427ae41e4649b934ca495991b7852b855 Dec 22 10:03:08 ip-10-10-21-199 s3fs[26040]: > x-amz-date: 20211222T100308Z Dec 22 10:03:08 ip-10-10-21-199 s3fs[26040]: > x-amz-security-token: **** Dec 22 10:03:08 ip-10-10-21-199 s3fs[26040]: > Dec 22 10:03:08 ip-10-10-21-199 s3fs[26040]: < HTTP/1.1 404 Not Found Dec 22 10:03:08 ip-10-10-21-199 s3fs[26040]: < x-amz-request-id: BYF6E0KPRZ1GBG9M Dec 22 10:03:08 ip-10-10-21-199 s3fs[26040]: < x-amz-id-2: vDbQogrhPbcmkx8UmpnjY4eeG6encUMswwnna/QnkVcc2veXIG+5VhMNqM/Bke6neBqjoc8GSIA= Dec 22 10:03:08 ip-10-10-21-199 s3fs[26040]: < Content-Type: application/xml Dec 22 10:03:08 ip-10-10-21-199 s3fs[26040]: < Date: Wed, 22 Dec 2021 10:03:07 GMT Dec 22 10:03:08 ip-10-10-21-199 s3fs[26040]: < Server: AmazonS3 Dec 22 10:03:08 ip-10-10-21-199 s3fs[26040]: < Dec 22 10:03:08 ip-10-10-21-199 s3fs[26040]: * Connection #11 to host bucketname.s3-us-east-2.amazonaws.com left intact Dec 22 10:03:08 ip-10-10-21-199 s3fs[26040]: HTTP response code 404 was returned, returning ENOENT Dec 22 10:03:08 ip-10-10-21-199 s3fs[26040]: [path=/keyname.zip.filepart] Dec 22 10:03:08 ip-10-10-21-199 s3fs[26040]: [tpath=/keyname.zip.filepart] Dec 22 10:03:08 ip-10-10-21-199 s3fs[26040]: URL is https://s3-us-east-2.amazonaws.com/bucketname?delimiter=/&max-keys=2&prefix=prefix/keyname.zip.filepart/ Dec 22 10:03:08 ip-10-10-21-199 s3fs[26040]: URL changed is https://bucketname.s3-us-east-2.amazonaws.com?delimiter=/&max-keys=2&prefix=prefix/keyname.zip.filepart/ Dec 22 10:03:08 ip-10-10-21-199 s3fs[26040]: computing signature [GET] [/] [delimiter=/&max-keys=2&prefix=prefix/keyname.zip.filepart/] [] Dec 22 10:03:08 ip-10-10-21-199 s3fs[26040]: url is https://s3-us-east-2.amazonaws.com Dec 22 10:03:08 ip-10-10-21-199 s3fs[26040]: * Rebuilt URL to: https://bucketname.s3-us-east-2.amazonaws.com/?delimiter=/&max-keys=2&prefix=prefix/keyname.zip.filepart/ Dec 22 10:03:08 ip-10-10-21-199 s3fs[26040]: * Found bundle for host bucketname.s3-us-east-2.amazonaws.com: 0x7f83ac009880 [can pipeline] Dec 22 10:03:08 ip-10-10-21-199 s3fs[26040]: * Re-using existing connection! (#11) with host bucketname.s3-us-east-2.amazonaws.com Dec 22 10:03:08 ip-10-10-21-199 s3fs[26040]: * Connected to bucketname.s3-us-east-2.amazonaws.com (52.219.101.170) port 443 (#11) Dec 22 10:03:08 ip-10-10-21-199 s3fs[26040]: > GET /?delimiter=/&max-keys=2&prefix=prefix/keyname.zip.filepart/ HTTP/1.1 Dec 22 10:03:08 ip-10-10-21-199 s3fs[26040]: > Host: bucketname.s3-us-east-2.amazonaws.com Dec 22 10:03:08 ip-10-10-21-199 s3fs[26040]: > User-Agent: s3fs/1.90 (commit hash 5de92e9; OpenSSL) Dec 22 10:03:08 ip-10-10-21-199 s3fs[26040]: > Accept: */* Dec 22 10:03:08 ip-10-10-21-199 s3fs[26040]: > Authorization: AWS4-HMAC-SHA256 Credential=ASIAUIKCI7XFAO7ATIGL/20211222/us-east-2/s3/aws4_request, SignedHeaders=host;x-amz-content-sha256;x-amz-date;x-amz-security-token, Signature=55861304dbeca55aaae47966e6a787bcf03e572ceaf59f1ae18b7b0f3c1aae61 Dec 22 10:03:08 ip-10-10-21-199 s3fs[26040]: > x-amz-content-sha256: e3b0c44298fc1c149afbf4c8996fb92427ae41e4649b934ca495991b7852b855 Dec 22 10:03:08 ip-10-10-21-199 s3fs[26040]: > x-amz-date: 20211222T100308Z Dec 22 10:03:08 ip-10-10-21-199 s3fs[26040]: > x-amz-security-token: **** Dec 22 10:03:08 ip-10-10-21-199 s3fs[26040]: > Dec 22 10:03:08 ip-10-10-21-199 s3fs[26040]: < HTTP/1.1 200 OK Dec 22 10:03:08 ip-10-10-21-199 s3fs[26040]: < x-amz-id-2: hrxqFPwjPjqQYLSXYNu0jAfGyCaqq6VZQ2APIaaHFVU2o1kYTSBNHGPq0s5oaKt861bOFFuXoQU= Dec 22 10:03:08 ip-10-10-21-199 s3fs[26040]: < x-amz-request-id: BYF8P9ZP7MTVY1GK Dec 22 10:03:08 ip-10-10-21-199 s3fs[26040]: < Date: Wed, 22 Dec 2021 10:03:09 GMT Dec 22 10:03:08 ip-10-10-21-199 s3fs[26040]: < x-amz-bucket-region: us-east-2 Dec 22 10:03:08 ip-10-10-21-199 s3fs[26040]: < Content-Type: application/xml Dec 22 10:03:08 ip-10-10-21-199 s3fs[26040]: < Transfer-Encoding: chunked Dec 22 10:03:08 ip-10-10-21-199 s3fs[26040]: < Server: AmazonS3 Dec 22 10:03:08 ip-10-10-21-199 s3fs[26040]: < Dec 22 10:03:08 ip-10-10-21-199 s3fs[26040]: * Connection #11 to host bucketname.s3-us-east-2.amazonaws.com left intact Dec 22 10:03:08 ip-10-10-21-199 s3fs[26040]: HTTP response code 200 Dec 22 10:03:11 ip-10-10-21-199 s3fs[26040]: [path=/keyname.zip.filepart] Dec 22 10:03:11 ip-10-10-21-199 s3fs[26040]: [tpath=/keyname.zip.filepart] Dec 22 10:03:11 ip-10-10-21-199 s3fs[26040]: [tpath=/keyname.zip.filepart][bpath=][save=][sseckeypos=18446744073709551615] Dec 22 10:03:11 ip-10-10-21-199 s3fs[26040]: URL is https://s3-us-east-2.amazonaws.com/bucketname/prefix/keyname.zip.filepart Dec 22 10:03:11 ip-10-10-21-199 s3fs[26040]: URL changed is https://bucketname.s3-us-east-2.amazonaws.com/prefix/keyname.zip.filepart Dec 22 10:03:11 ip-10-10-21-199 s3fs[26040]: computing signature [HEAD] [/prefix/keyname.zip.filepart] [] [] Dec 22 10:03:11 ip-10-10-21-199 s3fs[26040]: url is https://s3-us-east-2.amazonaws.com Dec 22 10:03:11 ip-10-10-21-199 s3fs[26040]: * Found bundle for host bucketname.s3-us-east-2.amazonaws.com: 0x7f83ac009880 [can pipeline] Dec 22 10:03:11 ip-10-10-21-199 s3fs[26040]: * Re-using existing connection! (#11) with host bucketname.s3-us-east-2.amazonaws.com Dec 22 10:03:11 ip-10-10-21-199 s3fs[26040]: * Connected to bucketname.s3-us-east-2.amazonaws.com (52.219.101.170) port 443 (#11) Dec 22 10:03:11 ip-10-10-21-199 s3fs[26040]: > HEAD /prefix/keyname.zip.filepart HTTP/1.1 Dec 22 10:03:11 ip-10-10-21-199 s3fs[26040]: > Host: bucketname.s3-us-east-2.amazonaws.com Dec 22 10:03:11 ip-10-10-21-199 s3fs[26040]: > User-Agent: s3fs/1.90 (commit hash 5de92e9; OpenSSL) Dec 22 10:03:11 ip-10-10-21-199 s3fs[26040]: > Accept: */* Dec 22 10:03:11 ip-10-10-21-199 s3fs[26040]: > Authorization: AWS4-HMAC-SHA256 Credential=ASIAUIKCI7XFAO7ATIGL/20211222/us-east-2/s3/aws4_request, SignedHeaders=host;x-amz-content-sha256;x-amz-date;x-amz-security-token, Signature=d56b0a452517cf32e8daa065327aaccc13ce75d914efce03a9ce6d1255eeaeb5 Dec 22 10:03:11 ip-10-10-21-199 s3fs[26040]: > x-amz-content-sha256: e3b0c44298fc1c149afbf4c8996fb92427ae41e4649b934ca495991b7852b855 Dec 22 10:03:11 ip-10-10-21-199 s3fs[26040]: > x-amz-date: 20211222T100311Z Dec 22 10:03:11 ip-10-10-21-199 s3fs[26040]: > x-amz-security-token: ***** Dec 22 10:03:11 ip-10-10-21-199 s3fs[26040]: > Dec 22 10:03:11 ip-10-10-21-199 s3fs[26040]: < HTTP/1.1 404 Not Found Dec 22 10:03:11 ip-10-10-21-199 s3fs[26040]: < x-amz-request-id: HWH9T7D6394KY6RC Dec 22 10:03:11 ip-10-10-21-199 s3fs[26040]: < x-amz-id-2: kwg8xXZnDbzZrlINnyugPyJi2tnaqeXthpWRawQjBiGpX6HNPY3Y9ttMMpvB71CupyWyDgrCZ/M= Dec 22 10:03:11 ip-10-10-21-199 s3fs[26040]: < Content-Type: application/xml Dec 22 10:03:11 ip-10-10-21-199 s3fs[26040]: < Date: Wed, 22 Dec 2021 10:03:10 GMT Dec 22 10:03:11 ip-10-10-21-199 s3fs[26040]: < Server: AmazonS3 Dec 22 10:03:11 ip-10-10-21-199 s3fs[26040]: < Dec 22 10:03:11 ip-10-10-21-199 s3fs[26040]: * Connection #11 to host bucketname.s3-us-east-2.amazonaws.com left intact Dec 22 10:03:11 ip-10-10-21-199 s3fs[26040]: HTTP response code 404 was returned, returning ENOENT Dec 22 10:03:11 ip-10-10-21-199 s3fs[26040]: [tpath=/keyname.zip.filepart/] Dec 22 10:03:11 ip-10-10-21-199 s3fs[26040]: [tpath=/keyname.zip.filepart/][bpath=][save=][sseckeypos=18446744073709551615] Dec 22 10:03:11 ip-10-10-21-199 s3fs[26040]: URL is https://s3-us-east-2.amazonaws.com/bucketname/prefix/keyname.zip.filepart/ Dec 22 10:03:11 ip-10-10-21-199 s3fs[26040]: URL changed is https://bucketname.s3-us-east-2.amazonaws.com/prefix/keyname.zip.filepart/ Dec 22 10:03:11 ip-10-10-21-199 s3fs[26040]: computing signature [HEAD] [/prefix/keyname.zip.filepart/] [] [] Dec 22 10:03:11 ip-10-10-21-199 s3fs[26040]: url is https://s3-us-east-2.amazonaws.com Dec 22 10:03:11 ip-10-10-21-199 s3fs[26040]: * Found bundle for host bucketname.s3-us-east-2.amazonaws.com: 0x7f83ac009880 [can pipeline] Dec 22 10:03:11 ip-10-10-21-199 s3fs[26040]: * Re-using existing connection! (#11) with host bucketname.s3-us-east-2.amazonaws.com Dec 22 10:03:11 ip-10-10-21-199 s3fs[26040]: * Connected to bucketname.s3-us-east-2.amazonaws.com (52.219.101.170) port 443 (#11) Dec 22 10:03:11 ip-10-10-21-199 s3fs[26040]: > HEAD /prefix/keyname.zip.filepart/ HTTP/1.1 Dec 22 10:03:11 ip-10-10-21-199 s3fs[26040]: > Host: bucketname.s3-us-east-2.amazonaws.com Dec 22 10:03:11 ip-10-10-21-199 s3fs[26040]: > User-Agent: s3fs/1.90 (commit hash 5de92e9; OpenSSL) Dec 22 10:03:11 ip-10-10-21-199 s3fs[26040]: > Accept: */* Dec 22 10:03:11 ip-10-10-21-199 s3fs[26040]: > Authorization: AWS4-HMAC-SHA256 Credential=ASIAUIKCI7XFAO7ATIGL/20211222/us-east-2/s3/aws4_request, SignedHeaders=host;x-amz-content-sha256;x-amz-date;x-amz-security-token, Signature=2ed9ea1ba990b004fc247cc8d7be8da6095029b994f9dc98c52b52bb384a9076 Dec 22 10:03:11 ip-10-10-21-199 s3fs[26040]: > x-amz-content-sha256: **** Dec 22 10:03:11 ip-10-10-21-199 s3fs[26040]: > x-amz-date: 20211222T100311Z Dec 22 10:03:11 ip-10-10-21-199 s3fs[26040]: > x-amz-security-token: **** Dec 22 10:03:11 ip-10-10-21-199 s3fs[26040]: > Dec 22 10:03:11 ip-10-10-21-199 s3fs[26040]: < HTTP/1.1 404 Not Found Dec 22 10:03:11 ip-10-10-21-199 s3fs[26040]: < x-amz-request-id: HWH1HZWBE7WGF2ZY Dec 22 10:03:11 ip-10-10-21-199 s3fs[26040]: < x-amz-id-2: iA+/RW2Wxs4Qf41sdoa5+aHcB9vGj9LMdo5BWhJHOtWM8EyYgpp7Sc+XPGDuAPIjDCrPBYd9IVA= Dec 22 10:03:11 ip-10-10-21-199 s3fs[26040]: < Content-Type: application/xml Dec 22 10:03:11 ip-10-10-21-199 s3fs[26040]: < Date: Wed, 22 Dec 2021 10:03:10 GMT Dec 22 10:03:11 ip-10-10-21-199 s3fs[26040]: < Server: AmazonS3 Dec 22 10:03:11 ip-10-10-21-199 s3fs[26040]: < Dec 22 10:03:11 ip-10-10-21-199 s3fs[26040]: * Connection #11 to host bucketname.s3-us-east-2.amazonaws.com left intact Dec 22 10:03:11 ip-10-10-21-199 s3fs[26040]: HTTP response code 404 was returned, returning ENOENT Dec 22 10:03:11 ip-10-10-21-199 s3fs[26040]: [tpath=/keyname.zip.filepart_$folder$] Dec 22 10:03:11 ip-10-10-21-199 s3fs[26040]: [tpath=/keyname.zip.filepart_$folder$][bpath=][save=][sseckeypos=18446744073709551615] Dec 22 10:03:11 ip-10-10-21-199 s3fs[26040]: URL is https://s3-us-east-2.amazonaws.com/bucketname/prefix/keyname.zip.filepart_%24folder%24 Dec 22 10:03:11 ip-10-10-21-199 s3fs[26040]: URL changed is https://bucketname.s3-us-east-2.amazonaws.com/prefix/keyname.zip.filepart_%24folder%24 Dec 22 10:03:11 ip-10-10-21-199 s3fs[26040]: computing signature [HEAD] [/prefix/keyname.zip.filepart_$folder$] [] [] Dec 22 10:03:11 ip-10-10-21-199 s3fs[26040]: url is https://s3-us-east-2.amazonaws.com Dec 22 10:03:11 ip-10-10-21-199 rsyslogd-2177: imuxsock begins to drop messages from pid 26040 due to rate-limiting ``` ### Details about issue Whenever I upload a file to an s3fs mount using WinSCP the logs never seem to get to the `PUT` request. According to the logs, the process keeps sending HEAD requests that return 404 Not Found, returning ENOENT. It never seems to register the PUT uploading request (though the file is accessible in the bucket) I do not have this issue with other sftp clients, just WinSCP.