[GH-ISSUE #2386] Mount failes in eu-central-1 #1171

Open
opened 2026-03-04 01:51:55 +03:00 by kerem · 4 comments
Owner

Originally created by @ptofevski on GitHub (Nov 29, 2023).
Original GitHub issue: https://github.com/s3fs-fuse/s3fs-fuse/issues/2386

Additional Information

Version of s3fs being used (s3fs --version)

Amazon Simple Storage Service File System V1.93 (commit:unknown) with OpenSSL
Copyright (C) 2010 Randy Rizun rrizun@gmail.com
License GPL2: GNU GPL version 2 https://gnu.org/licenses/gpl.html
This is free software: you are free to change and redistribute it.
There is NO WARRANTY, to the extent permitted by law.

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

2.9.9

Kernel information (uname -r)

6.2.0-1016-aws

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

PRETTY_NAME="Ubuntu 22.04.3 LTS"
NAME="Ubuntu"
VERSION_ID="22.04"
VERSION="22.04.3 LTS (Jammy Jellyfish)"
VERSION_CODENAME=jammy
ID=ubuntu
ID_LIKE=debian
HOME_URL="https://www.ubuntu.com/"
SUPPORT_URL="https://help.ubuntu.com/"
BUG_REPORT_URL="https://bugs.launchpad.net/ubuntu/"
PRIVACY_POLICY_URL="https://www.ubuntu.com/legal/terms-and-policies/privacy-policy"
UBUNTU_CODENAME=jammy

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

Nov 29 15:05:16 ****** s3fs[8318]: s3fs version 1.93(unknown) : s3fs -o passwd_file=.passwd-s3fs -o allow_other bucket /mount
Nov 29 15:05:16  s3fs[8318]: Loaded mime information from /etc/mime.types
Nov 29 15:05:16 s3fs[8320]: init v1.93(commit:unknown) with OpenSSL, credential-library(built-in)
Nov 29 15:05:17 s3fs[8320]: s3fs.cpp:s3fs_check_service(4473): Failed to connect region 'us-east-1'(default), so retry to connect region 'eu-central-1' for url(http(s)://s3-eu-central-1.amazonaws.com).
Nov 29 15:05:17 s3fs[8320]: s3fs.cpp:s3fs_check_service(4508): Failed to connect by sigv4, so retry to connect by signature version 2. But you should to review url and endpoint option.
Nov 29 15:05:17 s3fs[8320]: s3fs.cpp:s3fs_check_service(4520): Failed to check bucket and directory for mount point : Bad Request(host=https://s3-eu-central-1.amazonaws.com)
Nov 29 15:05:17 systemd[1]: adeva\x2dapp\x2dstorage.mount: Deactivated successfully.

Details about issue

I can not mount an S3 bucket.

Originally created by @ptofevski on GitHub (Nov 29, 2023). Original GitHub issue: https://github.com/s3fs-fuse/s3fs-fuse/issues/2386 ### Additional Information #### Version of s3fs being used (`s3fs --version`) Amazon Simple Storage Service File System V1.93 (commit:unknown) with OpenSSL Copyright (C) 2010 Randy Rizun <rrizun@gmail.com> License GPL2: GNU GPL version 2 <https://gnu.org/licenses/gpl.html> This is free software: you are free to change and redistribute it. There is NO WARRANTY, to the extent permitted by law. #### Version of fuse being used (`pkg-config --modversion fuse`, `rpm -qi fuse` or `dpkg -s fuse`) ``` 2.9.9 ``` #### Kernel information (`uname -r`) ``` 6.2.0-1016-aws ``` #### GNU/Linux Distribution, if applicable (`cat /etc/os-release`) ``` PRETTY_NAME="Ubuntu 22.04.3 LTS" NAME="Ubuntu" VERSION_ID="22.04" VERSION="22.04.3 LTS (Jammy Jellyfish)" VERSION_CODENAME=jammy ID=ubuntu ID_LIKE=debian HOME_URL="https://www.ubuntu.com/" SUPPORT_URL="https://help.ubuntu.com/" BUG_REPORT_URL="https://bugs.launchpad.net/ubuntu/" PRIVACY_POLICY_URL="https://www.ubuntu.com/legal/terms-and-policies/privacy-policy" UBUNTU_CODENAME=jammy ``` #### 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. --> ``` Nov 29 15:05:16 ****** s3fs[8318]: s3fs version 1.93(unknown) : s3fs -o passwd_file=.passwd-s3fs -o allow_other bucket /mount Nov 29 15:05:16 s3fs[8318]: Loaded mime information from /etc/mime.types Nov 29 15:05:16 s3fs[8320]: init v1.93(commit:unknown) with OpenSSL, credential-library(built-in) Nov 29 15:05:17 s3fs[8320]: s3fs.cpp:s3fs_check_service(4473): Failed to connect region 'us-east-1'(default), so retry to connect region 'eu-central-1' for url(http(s)://s3-eu-central-1.amazonaws.com). Nov 29 15:05:17 s3fs[8320]: s3fs.cpp:s3fs_check_service(4508): Failed to connect by sigv4, so retry to connect by signature version 2. But you should to review url and endpoint option. Nov 29 15:05:17 s3fs[8320]: s3fs.cpp:s3fs_check_service(4520): Failed to check bucket and directory for mount point : Bad Request(host=https://s3-eu-central-1.amazonaws.com) Nov 29 15:05:17 systemd[1]: adeva\x2dapp\x2dstorage.mount: Deactivated successfully. ``` ### Details about issue I can not mount an S3 bucket.
Author
Owner

@ggtakec commented on GitHub (Feb 12, 2024):

@ptofevski
Please tell us about the command line or fstab when starting s3fs.
Also, if possible, please specify the curldbg=dbg or curldbg option to collect detailed logs.
I think the logs will be helpful in resolving the issue.

<!-- gh-comment-id:1938264361 --> @ggtakec commented on GitHub (Feb 12, 2024): @ptofevski Please tell us about the command line or fstab when starting s3fs. Also, if possible, please specify the `curldbg=dbg` or `curldbg` option to collect detailed logs. I think the logs will be helpful in resolving the issue.
Author
Owner

@celesteking commented on GitHub (Aug 15, 2024):

Failed to connect by sigv4, so retry to connect by signature version 2

Maybe you should stop downgrading proto to sigv2 which is missing in new AWS regions.

<!-- gh-comment-id:2290113510 --> @celesteking commented on GitHub (Aug 15, 2024): > Failed to connect by sigv4, so retry to connect by signature version 2 Maybe you should stop downgrading proto to sigv2 which is missing in new AWS regions.
Author
Owner

@ggtakec commented on GitHub (Aug 17, 2024):

@celesteking
This may be a separate issue. (I think it should be treated as a separate issue and not discussed in this issue, so I will continue to consider it in #2513.)
Downgrading to sigv2 has been around since it was introduced when sigv4 was supported.
First, determine the need for this and how long it will be supported. (#2513)

<!-- gh-comment-id:2294533637 --> @ggtakec commented on GitHub (Aug 17, 2024): @celesteking This may be a separate issue. (I think it should be treated as a separate issue and not discussed in this issue, so I will continue to consider it in #2513.) Downgrading to sigv2 has been around since it was introduced when sigv4 was supported. First, determine the need for this and how long it will be supported. (#2513)
Author
Owner

@gaul commented on GitHub (Aug 24, 2024):

You can force v4-only via -o sigv4.

<!-- gh-comment-id:2308400447 --> @gaul commented on GitHub (Aug 24, 2024): You can force v4-only via `-o sigv4`.
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#1171
No description provided.