EFS utils timeout

[dovidio]

Description

I'm experiencing a timeout issue when using efs utils, but when using nfs4 using a specific mount tthe mounting works

More information

I've double checked my security group configuration and that works fine
I've successfully mounted a target using the ip address

mount -t nfs4 -o nfsvers=4.1 $ip:/ /efs

However when using efs this does not work
This can be reproduced as following

• Create a vpc created using the following 1 click deployment. This will setup security groups

Follow this tutorial to mount an efs volume on ec2

Debug logs

[efs]
client = yes
accept = 127.0.0.1:20242
connect = fs-09545ad5edae28ac1.efs.us-east-1.amazonaws.com:2049
sslVersion = TLSv1.2
renegotiation = no
TIMEOUTbusy = 20
TIMEOUTclose = 0
TIMEOUTidle = 70
delay = yes
verify = 2
CAfile = /etc/amazon/efs/efs-utils.crt
cert = /var/run/efs/fs-09545ad5edae28ac1.var.www.html.wp-content.20242+/certificate.pem
key = /etc/amazon/efs/privateKey.pem
2025-03-01 21:24:15 UTC - DEBUG - Closing socket used to choose proxy listen port 20242.
2025-03-01 21:24:15 UTC - INFO - Starting efs-proxy: "/sbin/efs-proxy /var/run/efs/stunnel-config.fs-09545ad5edae28ac1.var.www.html.wp-content.20242 --tls"
2025-03-01 21:24:15 UTC - INFO - Started efs-proxy, pid: 36530
2025-03-01 21:24:15 UTC - DEBUG - Trying to connect to 127.0.0.1: 20242
2025-03-01 21:24:15 UTC - DEBUG - The tlsport 20242 cannot be connected yet, sleep 0.05(s), 5 retry time(s) left
2025-03-01 21:24:15 UTC - DEBUG - Trying to connect to 127.0.0.1: 20242
2025-03-01 21:24:15 UTC - INFO - Executing: "/sbin/mount.nfs4 127.0.0.1:/ /var/www/html/wp-content -o rw,_netdev,nfsvers=4.1,rsize=1048576,wsize=1048576,hard,timeo=600,retrans=2,noresvport,port=20242" with 15 sec time limit.
2025-03-01 21:24:30 UTC - ERROR - Mounting fs-09545ad5edae28ac1.efs.us-east-1.amazonaws.com to /var/www/html/wp-content failed due to timeout after 15 sec, mount attempt 1/3, wait 0 sec before next attempt.
2025-03-01 21:24:30 UTC - INFO - Executing: "/sbin/mount.nfs4 127.0.0.1:/ /var/www/html/wp-content -o rw,_netdev,nfsvers=4.1,rsize=1048576,wsize=1048576,hard,timeo=600,retrans=2,noresvport,port=20242" with 15 sec time limit.
2025-03-01 21:24:45 UTC - ERROR - Mounting fs-09545ad5edae28ac1.efs.us-east-1.amazonaws.com to /var/www/html/wp-content failed due to timeout after 15 sec, mount attempt 2/3, wait 0 sec before next attempt.
2025-03-01 21:24:45 UTC - INFO - Executing: "/sbin/mount.nfs4 127.0.0.1:/ /var/www/html/wp-content -o rw,_netdev,nfsvers=4.1,rsize=1048576,wsize=1048576,hard,timeo=600,retrans=2,noresvport,port=20242"
2025-03-01 21:25:39 UTC - INFO - version=2.1.0 options={'rw': None, 'tls': None, 'iam': None, '_netdev': None}
2025-03-01 21:25:39 UTC - DEBUG - Identified init system: systemd
2025-03-01 21:25:39 UTC - DEBUG - Retrieve property region from instance metadata
2025-03-01 21:25:39 UTC - DEBUG - Using dns_name_suffix amazonaws.com in config section [mount]
2025-03-01 21:25:39 UTC - DEBUG - mount_with_proxy: efs_proxy_enabled = True
2025-03-01 21:25:39 UTC - INFO - binding 20515
2025-03-01 21:25:39 UTC - DEBUG - Retrieve property region from instance metadata
2025-03-01 21:25:39 UTC - DEBUG - Instance metadata already retrieved in previous call, use the cached values.
2025-03-01 21:25:39 UTC - DEBUG - Removed /var/run/efs/efs-utils-lock successfully
2025-03-01 21:25:39 UTC - DEBUG - amazon-efs-mount-watchdog is already running
2025-03-01 21:25:39 UTC - DEBUG - Using stunnel_cafile /etc/amazon/efs/efs-utils.crt in config section [mount]
2025-03-01 21:25:39 UTC - DEBUG - Writing stunnel configuration:
fips = no
foreground = yes
socket = l:SO_REUSEADDR=yes
socket = a:SO_BINDTODEVICE=lo
pid = /var/run/efs/fs-09545ad5edae28ac1.var.www.html.wp-content.20515+/stunnel.pid
[efs]
client = yes
accept = 127.0.0.1:20515
connect = fs-09545ad5edae28ac1.efs.us-east-1.amazonaws.com:2049
sslVersion = TLSv1.2
renegotiation = no
TIMEOUTbusy = 20
TIMEOUTclose = 0
TIMEOUTidle = 70
delay = yes
verify = 2
CAfile = /etc/amazon/efs/efs-utils.crt
cert = /var/run/efs/fs-09545ad5edae28ac1.var.www.html.wp-content.20515+/certificate.pem
key = /etc/amazon/efs/privateKey.pem
2025-03-01 21:25:39 UTC - DEBUG - Closing socket used to choose proxy listen port 20515.
2025-03-01 21:25:39 UTC - INFO - Starting efs-proxy: "/sbin/efs-proxy /var/run/efs/stunnel-config.fs-09545ad5edae28ac1.var.www.html.wp-content.20515 --tls"
2025-03-01 21:25:39 UTC - INFO - Started efs-proxy, pid: 36676
2025-03-01 21:25:39 UTC - DEBUG - Trying to connect to 127.0.0.1: 20515
2025-03-01 21:25:39 UTC - DEBUG - The tlsport 20515 cannot be connected yet, sleep 0.05(s), 5 retry time(s) left
2025-03-01 21:25:39 UTC - DEBUG - Trying to connect to 127.0.0.1: 20515
2025-03-01 21:25:39 UTC - INFO - Executing: "/sbin/mount.nfs4 127.0.0.1:/ /var/www/html/wp-content -o rw,_netdev,nfsvers=4.1,rsize=1048576,wsize=1048576,hard,timeo=600,retrans=2,noresvport,port=20515" with 15 sec time limit.
2025-03-01 21:25:54 UTC - ERROR - Mounting fs-09545ad5edae28ac1.efs.us-east-1.amazonaws.com to /var/www/html/wp-content failed due to timeout after 15 sec, mount attempt 1/3, wait 0 sec before next attempt.
2025-03-01 21:25:54 UTC - INFO - Executing: "/sbin/mount.nfs4 127.0.0.1:/ /var/www/html/wp-content -o rw,_netdev,nfsvers=4.1,rsize=1048576,wsize=1048576,hard,timeo=600,retrans=2,noresvport,port=20515" with 15 sec time limit.
2025-03-01 21:26:09 UTC - ERROR - Mounting fs-09545ad5edae28ac1.efs.us-east-1.amazonaws.com to /var/www/html/wp-content failed due to timeout after 15 sec, mount attempt 2/3, wait 0 sec before next attempt.
2025-03-01 21:26:09 UTC - INFO - Executing: "/sbin/mount.nfs4 127.0.0.1:/ /var/www/html/wp-content -o rw,_netdev,nfsvers=4.1,rsize=1048576,wsize=1048576,hard,timeo=600,retrans=2,noresvport,port=20515"
2025-03-01 21:29:09 UTC - ERROR - Failed to mount fs-09545ad5edae28ac1.efs.us-east-1.amazonaws.com at /var/www/html/wp-content: returncode=32, stderr="b'mount.nfs4: mount system call failed'"