search

suganoo / s3fs

Automatically exported from code.google.com/p/s3fs
0 stars 0 forks source link

could not determine how to establish security credentials #126

Closed GoogleCodeExporter closed 8 years ago

GoogleCodeExporter commented 8 years ago 
Hi, I have s3fs (v 1-16) and it gives me this error "could not determine how to 
establish security credentials" when I try and use it. I'm using a .passwd-s3fs 
file in my home directory. Permissions on this file are 600. It can see this 
file because if I change the permissions so it's e.g. readable by others then 
it gives a different error.

Been driving me crazy! any ideas? thanks!

Original issue reported on code.google.com by rtg...@gmail.com on 24 Nov 2010 at 1:14

GoogleCodeExporter commented 8 years ago 
ok I fixed it...the passwd file should NOT specify the name of the bucket. then 
it works. :-)

Original comment by rtg...@gmail.com on 24 Nov 2010 at 1:29

GoogleCodeExporter commented 8 years ago 
This might still be a bug.  What was the format of your password file?

Either of these two formats will work:

AccessKeyId:SecretAccessKey

BucketName:AccessKeyId:SecretAccessKey

This allows for multiple credentials. If you only have one set of credentials 
then you should use the first style. However, the second style should work too. 
 At the very least this should lead to a better error message.

Original comment by dmoore4...@gmail.com on 24 Nov 2010 at 1:43

GoogleCodeExporter commented 8 years ago 
I can verify either work. I had [bucketname:] and not bucketname: as specified 
in the instructions (i.e. with the square brackets). When I removed all 
references to the bucket it started working, and having added bucketname (no 
brackets) it works too.

Sorry for the trouble. :-) And thanks for a great utility!

Original comment by rtg...@gmail.com on 24 Nov 2010 at 1:47

GoogleCodeExporter commented 8 years ago 
Hee, hee,  typically square brackets in usage examples indicate something that 
is optional.  I'll put in a couple of changes to ensure this doesn't happen 
again.  Thanks for the feedback, most of the credit goes to the original author 
though.

Original comment by dmoore4...@gmail.com on 24 Nov 2010 at 1:55

GoogleCodeExporter commented 8 years ago 
This issue was closed by revision r263.

Original comment by dmoore4...@gmail.com on 24 Nov 2010 at 2:44

GoogleCodeExporter commented 8 years ago 
[deleted comment]
GoogleCodeExporter commented 8 years ago 
I had a bucket with a capital letter that wouldn't mount. I created another 
bucket with all lowercase and it worked instantly. Basically, even though S3 
will allow a bucketname with a capital letter, s3fs can't see it.

Original comment by allella....@gmail.com on 1 Apr 2011 at 1:39

GoogleCodeExporter commented 8 years ago 
See issue #98

What version of s3fs are you using?

Since r203 a error message should show that buckets with upper case characters 
are not allowed.

Original comment by dmoore4...@gmail.com on 1 Apr 2011 at 2:16

GoogleCodeExporter commented 8 years ago 
You are correct. I'm using version 1.40 and it warned me about uppercase. 
However, since Amazon technically allows uppercase, I interpreted the warning 
as meaning I could pass in a lower case name like `s3fs test-bucket /mnt` and 
it would find my Test-bucket.

An obvious oversight on my end, since S3 said "s3fs: BUCKET Test-Bucket, upper 
case characters are not supported". However, the warning might be enhanced if 
it said, "s3fs does not support buckets with capital letters, even though S3 
allows them" 

I see that lower case bucket names are a best practice 
http://aws.amazon.com/articles/1904?_encoding=UTF8&jiveRedirect=1 , so I should 
have RTFD to start.

Thanks

Original comment by allella....@gmail.com on 1 Apr 2011 at 1:28

GoogleCodeExporter commented 8 years ago 
On my Linux Mint Debian, s3fs version 1.57 doesn't work with local home 
.passwd-s3fs but works using /etc/passwd-s3fs file

Great works!
Thanks

Original comment by etna...@gmail.com on 19 Jul 2011 at 9:51