devstack: Hanging in 'Mounting NFS shared folders...' followed by timeout and giving up

[Luis Duarte]

Hi everyone,

I'm running the devstack on my Mac using the VirtualBox and Vagrant method from here. It's worked fine in the past. Recently I rebased to the current master branch and since then I have not been able to reach my VM anymore. When I run 'vagrant up' I get the following:

The following SSH command responded with a non-zero exit status.
Vagrant assumes that this means the command failed!
mount -o 'vers=3,udp' 192.168.33.1:'/path/to/configuration/vagrant/release/devstack/edx-platform' /edx/app/edxapp/edx-platform
Stdout from the command:
Stderr from the command:
stdin: is not a tty
mount.nfs: mount to NFS server '192.168.33.1:/path/to/configuration/vagrant/release/devstack/edx-platform' failed: timed out, giving up

I tried following the instructions here of just trying again, and made sure my firewall is off and even tried 'vagrant destroy' followed by 'vagrant up' but still nothing.

Any idea what's going on? Thanks!

~Luis 

[Stuti Rastogi]

vagrant reload
vagrant up
vagrant provision

This worked for me on my Ubuntu 12.04
See if you can try.

All the best!

[Greg Price]

I have also encountered this problem when connecting and disconnecting from a VPN. One thing that has worked for me to fix the problem is to go into VirtualBox preferences, Network->Network Preference->Host Only Networks and delete the entries. This gist also offers other solutions:

https://gist.github.com/johnkary/4962501

[Luis Duarte]

Thanks for the replies everyone. Turns out the solution was much simpler...I hadn't updated to the latest VirtualBox and Vagrant versions. It was weird that the errors were so cryptic that I couldn't figure that out...strange. 

Anyway, thanks for the help!

[Dadaso Zanzane]

Try -

VAGRANT_USE_VBOXFS=true vagrant up

[Ben Patterson]

Luis - 

Other things you can try:

• On VirtualBox, remove your host-only networks and try again:
• I have found I need to do this if I have jumped back and forth between VPNs
• Go to VirtualBox
• Go to Preferences (note on a Mac this is not in the GUI; this is in the menu items for the application)
• Go to Network
• host-only networks -- remove the network (mine is listed as 'vboxnet0')
• Restart nfs on your host machine
• I've only had to do this once, but I did have to do it once!
• `nfsd restart` (or `sudo nfsd restart` depending on your credentials)

Ben

--
You received this message because you are subscribed to the Google Groups "General Open edX discussion" group.
To view this discussion on the web visit https://groups.google.com/d/msgid/edx-code/f44ef188-bf13-48dd-bfe3-8d07a957171c%40googlegroups.com.

[Колпаков Евгений]

Looks like something happened recently (i.e. OS/VirtualBox update) that made this thread relevant as well.

In my case, despite having all firewalls disabled, nfs mount failed when using UDP, but worked with TCP. Using UDP is the default setting in vagrant, so temporary workaround might be to add nfs_udp:false to all config.vm.synced_folder in Vagrantfile that also have nfs: true.

Regards,

Eugeny

@Opencraft

среда, 18 июня 2014 г., 17:34:17 UTC+3 пользователь Luis Duarte написал:

[Felipe Montoya]

Thanks Eugeny,

I agree, something must have changed recently that broke the nfs on vagrant. Meanwhile, your idea of turning off udp `(nfs_udp:false` ) worked for me as well using the latest Vagrant (1.7.4) on an ubuntu 14.04 as host.

Cheers

--

Felipe Montoya

[Vishal Mopari]

Thank you, Dadso

Disclaimer
This email communication (including any attachments) contains information which is confidential and may be legally privileged. It is for the exclusive use of the intended recipient/s. If you are not the intended recipient, please delete this email communication (including any attachments) and hard copies immediately, please preserve its confidentiality and notify the sender. Any unauthorized use or dissemination of this email communication (including any attachments) in any manner whatsoever, in whole or in part, is strictly prohibited. This email communication (including any attachments), may not be free of viruses, you should carry out your own virus checks before opening any attachment to this e-mail. The sender of this e-mail and Cuelogic Technologies shall not be liable for any damage that you may sustain as a result of viruses, in completeness of this message, a delay in receipt of this message. Any views or opinions presented in this email are solely those of the author and do not necessarily represent those of Cuelogic Technologies. Cuelogic Technologies will not accept any liability in respect of such content of this email, and the author shall be solely responsible and will be personally liable for any damages or other liability.