mirror of
https://github.com/s3fs-fuse/s3fs-fuse.git
synced 2026-04-25 13:26:00 +03:00
[GH-ISSUE #105] s3fs on Amazon VPC - transport endpoint not connected #63
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#63
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 @ai6pg on GitHub (Jan 19, 2015).
Original GitHub issue: https://github.com/s3fs-fuse/s3fs-fuse/issues/105
ubuntu@hostname:/etc$ fuse --version
The Free Unix Spectrum Emulator (Fuse) version 1.1.1.
fstab has:
s3fs#bucketname /mnt/s3 fuse rw,allow_other,_netdev,nosuid,nodev,uid=1000,gid=1000,use_cache=/home/ubuntu/cache 0 2
/etc/passwd-s3fs has key&passphrase
I'be been about to mount my bucket key.name
but not my bucket name2
cd: /mnt/s3: Transport endpoint is not connected
Any suggestions?
73 de AI6PG aka Peter
http://petergraceonline.com
@jb-1980 commented on GitHub (Jan 20, 2015):
I was having a similar issue. It turned out that I needed to ensure that my IAM user associated with the key:secret pair in the passwd-s3fs file had the correct permissions to access S3. It may be different for your case since you mention that you have been able to mount your bucket key.name, but I thought I would share what helped me solve that error when I was seeing it.
@ggtakec commented on GitHub (Mar 4, 2015):
Hi, I'm sorry fo replying late.
I got same problem in other issue, which is about "Transport endpoint is not connected".
But I could not solve that problem.
If you can, please run s3fs manually(command line), and run with "-f" and "-d" option.
Probably s3fs puts many logs and it helps us for splving this issue.
Thanks in advance for your assistance.
@wrstone commented on GitHub (Mar 30, 2015):
I have a similar issue. Specifically:
We have a number of Ubuntu 14.04 instances in GovCloud that are correctly mounting S3 buckets. However, I'm setting up a new instances and cannot connect to the bucket.
I've done a couple of command-line attempts to do this so that I can see error messages. First I tried it with our usual options:
[TEXTURAAWSGOV\bill.stone@govseesbuat01 ~]$ sudo s3fs -f -d -o url=http://s3-us-gov-west-1.amazonaws.com -o allow_other uat.project.files /java_data/s3projects
set_moutpoint_attribute(3530): PROC(uid=0, gid=0) - MountPoint(uid=0, gid=0, mode=40755)
s3fs_init(2713): init
s3fs_check_service(3070): check services.
CheckBucket(2538): check a bucket.
RequestPerform(1584): connecting to URL http://uat.project.files.s3-us-gov-west-1.amazonaws.com/
RequestPerform(1600): HTTP response code 400
RequestPerform(1614): HTTP response code 400 was returned, returing EIO.
CheckBucket(2590): Check bucket failed, S3 response:
AuthorizationHeaderMalformedThe authorization header is malformed; the region 'us-east-1' is wrong; expecting 'us-gov-west-1'us-gov-west-1D3F8A1498AE08C938Z26XMSpj9XY4HjoNke+l9nK/Q03DHeHBFeYLPmZZ8hoME5dYMW9S2SKzc41jNcms3fs_check_service(3103): Could not connect wrong region us-east-1, so retry to connect region us-gov-west-1.
CheckBucket(2538): check a bucket.
RequestPerform(1584): connecting to URL http://uat.project.files.s3-us-gov-west-1.amazonaws.com/
RequestPerform(1600): HTTP response code 404
RequestPerform(1624): HTTP response code 404 was returned, returning ENOENT
CheckBucket(2590): Check bucket failed, S3 response:
NoSuchBucketThe specified bucket does not existuat.project.files.s3.amazonaws.comD254DDFD35F0374BOW6J6Bs0eUn/zMXo+44vDMTGAyOOBuqbykWKEgjQtBrp9eGZ+qYbUHZkjim5WqVIs3fs: bucket not found
So it's telling me that the URL is wrong, even though I sent it the same URL for GovCloud S3 buckets that our other servers are correctly mounting. Consequently, I tried adding an explicit endpoint:
[TEXTURAAWSGOV\bill.stone@govseesbuat01 ~]$ sudo s3fs -f -d -o url=http://s3-us-gov-west-1.amazonaws.com -o allow_other -o endpoint=us-gov-west-1 -o passwd_file=/etc/passwd-s3fs prd.project.files /java_data/s3projects
set_moutpoint_attribute(3530): PROC(uid=0, gid=0) - MountPoint(uid=0, gid=0, mode=40755)
s3fs_init(2713): init
s3fs_check_service(3070): check services.
CheckBucket(2538): check a bucket.
RequestPerform(1584): connecting to URL http://prd.project.files.s3-us-gov-west-1.amazonaws.com/
RequestPerform(1600): HTTP response code 404
RequestPerform(1624): HTTP response code 404 was returned, returning ENOENT
CheckBucket(2590): Check bucket failed, S3 response:
NoSuchBucketThe specified bucket does not existprd.project.files.s3.amazonaws.comE8AFB833D9BDD27BTpy4XIzbzs3N4CsM2UeKUQN1YuEvGUlVGWtps2o7LrHjsLIW6kcqqgMPzIfXkc7Ts3fs: bucket not found
I tried mounting other buckets and get the same output. From the S3 dashboard and Cloudberry Explorer, we can see that the buckets I'm trying to mount exist.
I'm unclear how to proceed. We had a brief ticket with AWS (which was promptly dropped since S3FS is not supported). They confirm that the bucket exists and looks fine.
The reason that the issue appears similar to the original poster's problem is that if one attempts to access the bucket after using either of the mount statements shown above (or via an /etc/fstab entry) displays the error:
[TEXTURAAWSGOV\bill.stone@govseesbuat01 ~]$ ls -al /java_data
ls: cannot access /java_data/s3projects: Transport endpoint is not connected
total 4
drwxr-xr-x 3 root root 23 Mar 27 13:35 .
drwxr-xr-x 25 root root 4096 Mar 27 14:13 ..
?????????? ? ? ? ? ? s3projects
Any assistance is appreciated.
@wrstone commented on GitHub (Mar 31, 2015):
I discovered the answer to my problem: there has been a code change to S3FS that broke GovCloud redirection.
I've file a separate issue for this here:
https://github.com/s3fs-fuse/s3fs-fuse/issues/161
@ggtakec commented on GitHub (Apr 12, 2015):
Hi, all
I updated #167 and #164(#165), those may have solved this Issue.
Please checkout master branch, and check it.
Thanks in advance for your help.
@teu commented on GitHub (May 15, 2015):
Solution: https://aws.amazon.com/blogs/aws/new-vpc-endpoint-for-amazon-s3/
@chrisschaub commented on GitHub (May 15, 2015):
Thanks!
On Fri, May 15, 2015 at 8:59 AM, Piotr Jasiulewicz <notifications@github.com
Christopher Schaub
http://chris.schaub.com
@julian1 commented on GitHub (Jul 10, 2015):
Same problem debian desktop, compiling latest master. With or without multireq_max=5
@jeyraof commented on GitHub (Dec 3, 2015):
Is this solved? Same problem here.
@ggtakec commented on GitHub (Dec 3, 2015):
@julian1 and @jeyraof I'm sorry for replygin late.
So you can run s3fs and it puts message(error/warning/information), please use dbglevel option.
If you can, I hope that s3fs will put message which will say what is wrong. And if you specify only dbglevel option, you can find messages in /dev/log/**** from s3fs.
If you need to get more information, you can specify curldbg option. It puts many information about communication on HTTP(S).
If You need to run s3fs forground, you can specify -f option. So that you can see messages on stdout(err) on display.
Please see man page for s3fs.
After you get some (error/warning) messages from s3fs, please let me know.
Thanks in advance for your help.
@ggtakec commented on GitHub (Jan 17, 2016):
I'm closing this issue, if you have a problem yet, please post new issue or reopen this issue.
Thanks in advance for your help.
@balamurugan99 commented on GitHub (Jul 5, 2016):
That's because previous mount not unmounted properly. Try unmount and remount again.
fusermount -u
Thanks,
Bala
@amkhullar commented on GitHub (Mar 28, 2017):
I am also facing the same issue.
I added the below bucket policy:
Can some one tell what could be the issue ?
When we check the same s3 link using the browser below is the output