search

datacratic / StarCluster

StarCluster is a utility for creating and managing computing clusters hosted on Amazon's Elastic Compute Cloud (EC2).
http://star.mit.edu/cluster
GNU Lesser General Public License v3.0
37 stars 13 forks source link

EFS Mounting Error #64

Closed alexbw closed 7 years ago

alexbw commented 7 years ago

Hi all, really love the idea of an EFS plugin. I've gotten things to work in a bit of a hacky way, by working my way around the following error:

2017-01-15 14:52:32,279 !!! ERROR - Error occured while running plugin 'efs':
2017-01-15 14:52:32,279 !!! ERROR - remote command 'source /etc/profile && mount -t nfs4 -o
2017-01-15 14:52:32,279 !!! ERROR - rsize=1048576,wsize=1048576,hard,timeo=600,retrans=2
2017-01-15 14:52:32,279 !!! ERROR - us-east-1b.fs-XYZ123.efs.us-east-1.amazonaws.com:/
2017-01-15 14:52:32,279 !!! ERROR - /mnt/myefs' failed with status 32:
2017-01-15 14:52:32,279 !!! ERROR - mount.nfs4: Failed to resolve server
>>> 2017-01-15 14:52:32,279 !!! ERROR - us-east-1b.fs-XYZ123.efs.us-east-1.amazonaws.com: Name or
>>> 2017-01-15 14:52:32,279 !!! ERROR - service not known

See the lines with >>>. The address for the EFS drive is correct, according to the AWS EFS console. When I run the mount command manually, logged in as root, the command also fails.

However, replacing the DNS name (e.g. us-east-1b.fs-XYZ123.efs.us-east-1.amazonaws.com:/) with the IP address associated with the EFS drive: (e.g. 123.45.6.78), it works just fine, when run manually, logged in as root.

Any help troubleshooting this discrepancy would be helpful.

Would it be appropriate to just replace the DNS name with the IP address in the plugin? Would a PR like that be accepted?

vasisht commented 7 years ago

Hi Alex,

It looks like DNS is not enabled for the VPC. The mounting via DNS will work once this is turned on. IP addresses are not currently supported in the EFS plugin. It would need to know the IPs for all the available AZs to be able to mount the filesystem across different AZs.

Cheers, Vasisht

Sent from my iPhone

On Jan 16, 2017, at 1:31 AM, Alex Wiltschko notifications@github.com wrote:

Hi all, really love the idea of an EFS plugin. I've gotten things to work in a bit of a hacky way, by working my way around the following error:

2017-01-15 14:52:32,279 !!! ERROR - Error occured while running plugin 'efs': 2017-01-15 14:52:32,279 !!! ERROR - remote command 'source /etc/profile && mount -t nfs4 -o 2017-01-15 14:52:32,279 !!! ERROR - rsize=1048576,wsize=1048576,hard,timeo=600,retrans=2 2017-01-15 14:52:32,279 !!! ERROR - us-east-1b.fs-XYZ123.efs.us-east-1.amazonaws.com:/ 2017-01-15 14:52:32,279 !!! ERROR - /mnt/myefs' failed with status 32: 2017-01-15 14:52:32,279 !!! ERROR - mount.nfs4: Failed to resolve server

2017-01-15 14:52:32,279 !!! ERROR - us-east-1b.fs-XYZ123.efs.us-east-1.amazonaws.com: Name or 2017-01-15 14:52:32,279 !!! ERROR - service not known See the lines with >>>. The address for the EFS drive is correct, according to the AWS EFS console. When I run the mount command manually, logged in as root, the command also fails.

However, replacing the DNS name (e.g. us-east-1b.fs-XYZ123.efs.us-east-1.amazonaws.com:/) with the IP address associated with the EFS drive: (e.g. 123.45.6.78), it works just fine, when run manually, logged in as root.

Any help troubleshooting this discrepancy would be helpful.

Would it be appropriate to just replace the DNS name with the IP address in the plugin? Would a PR like that be accepted?

— You are receiving this because you are subscribed to this thread. Reply to this email directly, view it on GitHub, or mute the thread.

alexbw commented 7 years ago

That was precisely the error. Thanks for guiding me.