mirror of
https://github.com/s3fs-fuse/s3fs-fuse.git
synced 2026-04-25 13:26:00 +03:00
[GH-ISSUE #1140] Nothing happens after mounting #600
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#600
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 @perfectlegato on GitHub (Sep 3, 2019).
Original GitHub issue: https://github.com/s3fs-fuse/s3fs-fuse/issues/1140
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)
V1.85
Version of fuse being used (pkg-config --modversion fuse, rpm -qi fuse, dpkg -s fuse)
2.9.4
Kernel information (uname -r)
4.4.0-1084-aws
GNU/Linux Distribution, if applicable (cat /etc/os-release)
16.04.5 LTS (Xenial Xerus)
s3fs command line used, if applicable
sudo s3fs aispeak-seoul-lg -o use_cache=/tmp -o allow_other -o uid=1000 -o mp_umask=002 -o multireq_max=5 /audiodata
/etc/fstab entry, if applicable
s3fs#aispeak-seoul-lg /audiodata fuse allow_other 0 0
s3fs syslog messages (grep s3fs /var/log/syslog, journalctl | grep s3fs, or s3fs outputs)
Sep 3 10:16:10 ip-172-31-43-206 s3fs[28866]: init v1.85(commit:ae4bcd4) with OpenSSL
Sep 3 10:16:11 ip-172-31-43-206 s3fs[28866]: s3fs.cpp:s3fs_check_service(3864): Failed to connect by sigv4, so retry to connect by signature version 2.
Sep 3 10:16:11 ip-172-31-43-206 s3fs[28866]: s3fs.cpp:s3fs_check_service(3879): invalid credentials(host=https://s3.amazonaws.com) - result of checking service.
Details about issue
I accidentally deleted my security credentials on AWS and tried to hook up the original bucket to the original directory but it didn't work. So I decided to create a new bucket with new policy, and a new directory but now it's returning invalid credentials even though the security credentials are correct.
@lxknvlk commented on GitHub (Sep 3, 2019):
You probably have to create new AMI credentials and use them
@perfectlegato commented on GitHub (Sep 3, 2019):
Hey Alex. Yeah I did create a new set of credentials and double checked if
it's the right policy I'm using
On Tue, Sep 3, 2019, 22:37 Alex notifications@github.com wrote:
@lxknvlk commented on GitHub (Sep 3, 2019):
have you set new credentials in $ aws-configure ?
@perfectlegato commented on GitHub (Sep 3, 2019):
I did it in aws console.
Tried to do a brand new set of credential/bucket/ clean installation too
On Tue, Sep 3, 2019, 23:09 Alex notifications@github.com wrote:
@lxknvlk commented on GitHub (Sep 4, 2019):
I see that your fuse line does not have _netdev option, maybe try adding it.
@gaul commented on GitHub (Feb 3, 2020):
Did you find a workaround? This looks like a credential mismatch.
@gaul commented on GitHub (Apr 22, 2020):
Please reopen if symptoms persist.