mirror of
https://github.com/s3fs-fuse/s3fs-fuse.git
synced 2026-04-25 13:26:00 +03:00
[GH-ISSUE #857] Can not connect to s3 after upgrading from 1.79 to 1.84: passwd_file option is ignored #498
Labels
No labels
bug
bug
dataloss
duplicate
enhancement
feature request
help wanted
invalid
need info
performance
pull-request
question
question
testing
No milestone
No project
No assignees
1 participant
Notifications
Due date
No due date set.
Dependencies
No dependencies set.
Reference
starred/s3fs-fuse#498
Loading…
Add table
Add a link
Reference in a new issue
No description provided.
Delete branch "%!s()"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
Originally created by @KES777 on GitHub (Nov 15, 2018).
Original GitHub issue: https://github.com/s3fs-fuse/s3fs-fuse/issues/857
Version of s3fs being used (s3fs --version)
V1.84(commit:91c16f8)
Version of fuse being used (pkg-config --modversion fuse, rpm -qi fuse, dpkg -s fuse)
Version: 2.9.4-1ubuntu3.1
Kernel information (uname -r)
4.13.0-26-generic
GNU/Linux Distribution, if applicable (cat /etc/os-release)
NAME="Linux Mint"
VERSION="18.3 (Sylvia)"
ID=linuxmint
ID_LIKE=ubuntu
PRETTY_NAME="Linux Mint 18.3"
VERSION_ID="18.3"
HOME_URL="http://www.linuxmint.com/"
SUPPORT_URL="http://forums.linuxmint.com/"
BUG_REPORT_URL="http://bugs.launchpad.net/linuxmint/"
VERSION_CODENAME=sylvia
UBUNTU_CODENAME=xenial
s3fs command line used, if applicable
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
Details about issue
After upgrading from 1.79 to this version s3fs can not connect to
s3I think problem is here:
But what to do next?
how to specify different version? Thank you.
@KES777 commented on GitHub (Nov 15, 2018):
probably related to #133
@KES777 commented on GitHub (Nov 15, 2018):
with 1.79 version:
@KES777 commented on GitHub (Nov 15, 2018):
found source of problem:
This was fixed by changing
${HOME}by real path:But still:
I notice next:
AKIAIKCHMTFSUOU6RTBQ, this key is from default AWS profile. Thus mypasswd_filejust ignored when run from command line.Thus I fix my
AWSconfiguration file and replacepasswd_filebyprofile