Convoy EFS Issue


#1

Getting these errors in convoy-efs_convoy-efs_X when connecting to ECS instances with nfs installed:

9/6/2016 1:47:17 PMWaiting for metadata
9/6/2016 1:47:18 PMtime=“2016-09-06T17:47:18Z” level=info msg="Execing [/usr/bin/nsenter --mount=/proc/774/ns/mnt -F – /var/lib/docker/aufs/mnt/17e99756b017761fea0e7a387371bd4adfa3a420a76f2622e6b14a042a97d05c/var/lib/rancher/convoy-agent/share-mnt --stage2 /var/lib/rancher/convoy/convoy-efs-b4063772-cde5-4d39-914b-725e2b17a813 – /launch volume-agent-efs-internal 774]"
9/6/2016 1:47:18 PMRegistering convoy socket at /var/run/convoy-convoy-efs.sock
9/6/2016 1:47:18 PMMounting at: /var/lib/rancher/convoy/convoy-efs-b4063772-cde5-4d39-914b-725e2b17a813/mnt
9/6/2016 1:47:18 PMMounting nfs. Command: mount -t nfs -o nfsvers=4.1 us-east-1a.fs-cf408c86.efs.us-east-1.amazonaws.com:/efs /var/lib/rancher/convoy/convoy-efs-b4063772-cde5-4d39-914b-725e2b17a813/mnt
9/6/2016 1:47:18 PMmount.nfs: mounting us-east-1a.fs-cf408c86.efs.us-east-1.amazonaws.com:/efs failed, reason given by server: No such file or directory


#2

Also seeing this in Node syslogs:

Sep 6 17:53:14 node001 systemd-udevd[29879]: Could not generate persistent MAC address for veth261a3f3: No such file or directory

Not sure if it is related.


#3

@jaypasz

Can you try mount -t nfs -o nfsvers=4.1 us-east-1a.fs-cf408c86.efs.us-east-1.amazonaws.com:/efs <what_ever_path_you_want_to_mount> in the host to see if it’s a valid command? It seems server complains.


#4

OK, All is good now. I needed to just use “/” as mount path for Convoy EFS