-
Notifications
You must be signed in to change notification settings - Fork 4.4k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Vagrant up results in mount.nfs: Connection timed out Mac Mojave #11555
Comments
Hey there, |
I'm seeing the same problem. The problem happens on macOS Catalina 10.15.4, the most two recent versions of VirtualBox 6.1.4 and 6.1.6, and version 2.2.7 and 2.2.8 of vagrant. It is the same problem as described in #11234 (comment) and related issues... Essentially, |
Hello @soapy1 , thanks for your comment and apologies for my delay. My vagrant version is 2.2.7, VirtualBox version is 6.1.4, and the debug logfile has 1000+ lines. Is there any way to upload the debug log file somewhere, please? |
Last few lines from the logfile are:
|
@tshahed, thanks for the extra information! If you could share the full debug log in a public gist (https://gist.github.com/) that would be awesome 😃 |
@soapy1 Just uploaded the file here - https://gist.github.com/tshahed/0721e7a13fe2eecc43427e1ab665f917 |
@tshahed could you also share the Vagrantfile used to produce this error? Thanks! |
Hi @soapy1 , as the vagrant file belongs to my company, can I please only share how NFS share has been configured in the file, as that's where the problem is? Meanwhile, I have tried the same vagrant file for virtual box 5.2.42 and earlier version of 6, but the result is same.
|
Hi @soapy1 Vagrant log: https://gist.github.com/pasankg/c7fea5df203f1149bd6ce8e4da1ebc77 Would really appreciate if someone could help. |
Is your firewall enabled? Try disabling it and then try again.
…On Mon, Jun 29, 2020, 1:11 AM Pasan Gamage ***@***.***> wrote:
Hi @soapy1 <https://github.com/soapy1>
I'm getting a timeout on nfs mount.
Vagrant 2.2.9
Virtualbox: 6.1.10 r138449 (Qt5.6.3)
Host: MacOs 10.15.5
Guest Os: Ubuntu 18.04.4 LTS (GNU/Linux 4.15.0-76-generic x86_64)
Vagrant log:
https://gist.github.com/pasankg/c7fea5df203f1149bd6ce8e4da1ebc77
VagrantFile:
https://gist.github.com/pasankg/59a337e87cbc1f417cfed48cdbac1ade
Would really appreciate if someone could help.
Thank you
—
You are receiving this because you commented.
Reply to this email directly, view it on GitHub
<#11555 (comment)>,
or unsubscribe
<https://github.com/notifications/unsubscribe-auth/AABLAGHKYH3SDAI6ZCU4S2TRZAPAHANCNFSM4MRXXBJA>
.
|
Hi @nemonik |
Vagrant sync folder on the recent OS X Catalina has been problematic for me too. Both NFS and the default manner. Sometimes both will just stop working. Uninstalling and re-installing VirtualBox has helped. |
@nemonik I've tried that as well. Pretty much cornered now :( |
Have you tried... and I dunno why this has worked... But toggling the
firewall on and then back off as vagrant appears stuck at nfs sync folder
operation.
…On Mon, Jun 29, 2020, 10:49 PM Pasan Gamage ***@***.***> wrote:
@nemonik <https://github.com/nemonik> I've tried that as well. Pretty
much cornered now :(
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
<#11555 (comment)>,
or unsubscribe
<https://github.com/notifications/unsubscribe-auth/AABLAGDNNSIC6RVNOTMZNWTRZFHC3ANCNFSM4MRXXBJA>
.
|
I cannot toggle the Firewall on my office mac, it shows as off. I think there is a different firewall overriding the default |
Since the mount command is timing out, it seems like this may be a networking issue. This guide https://github.com/hashicorp/vagrant/blob/80e94b5e4ed93a880130b815329fcbce57e4cfed/website/pages/docs/synced-folders/nfs.mdx#troubleshooting-nfs-issues (still under development) lists out some thing to check for to identify what the issue might be. |
Thanks @soapy1 I'll give it a go. |
Hi @soapy1 The only options that I couldn't do are as below;
I have given a static IP from the config.yml file for the environment and used that ip to run the command
Not sure the options I should use for Thank you |
Right, from the logs above it looks like the IP you want to use is 192.168.200.1. So, you can check if that nfs folder is available on the guest by running a
You should also be able to run that on the host system and get similar results |
Hi @soapy1 |
Since the share is not available on the guest but is available on the host, it seems like this is probably a networking issue. Please ensure that the ports for nfs are not being blocked by a firewall on the guest. The ports that should be available 111, 2049 and 33333 |
I'll check it and get back to you. Thank you @soapy1 |
Hi @soapy1 I checked the ports via Network Utility and here is what I got;
I didn't get 33333 in the results And no results came back when scanning 192.168.200.190 Thank you |
Hi @soapy1 |
@pasankg Vagrant doesn't have configuration options to change firewall rules on your host or guest. You may find the shell provisioner useful for doing this after boot. However, a more simple option might be to change boxes (if the problem seems to be with the guest not allowing traffic on the required ports). |
For me same issue, and problem solved. Vagrant Version: 2.2.19 Host Machine: 192.168.56.1 Here are my situation:
References:
|
In my case, suddenly it started to stop working.. |
I am facing the exact same issue as #11209, and I have tried giving full disk access to iterm, terminal, mount_nfs, nfsd, turning nfs_export: false, restarting NFS, put only one line in /etc/exports file, turning firewall off but still facing the problem. Any guideline will be very much apprecitaed.
The text was updated successfully, but these errors were encountered: