Skip to content
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

NFS Mount fails when doing Vagrant Up #5232

Closed
alyn000r opened this issue Jan 21, 2015 · 9 comments
Closed

NFS Mount fails when doing Vagrant Up #5232

alyn000r opened this issue Jan 21, 2015 · 9 comments

Comments

@alyn000r
Copy link

I am trying to start up vagrant on my virtual box. It however freezes when mounting the nfs drive. Any help will be appreciated I have viewed and tried almost everything on the closed bug - 1941 but nothing helped.

My config:
OS: MAC OS X 10.10
VirtualBox: 4.3.12
Vagrant: 1.6.5

this is the debug log for help:

==> default: Mounting NFS shared folders...
    DEBUG ssh: Checking whether SSH is ready...
    DEBUG ssh: Re-using SSH connection.
     INFO ssh: SSH is ready!
    DEBUG ssh: Re-using SSH connection.
     INFO ssh: Execute:  (sudo=false)
    DEBUG ssh: Exit status: 0
    DEBUG guest: Searching for cap: mount_nfs_folder
    DEBUG guest: Checking in: redhat
    DEBUG guest: Checking in: linux
    DEBUG guest: Found cap: mount_nfs_folder in linux
     INFO guest: Execute capability: mount_nfs_folder [#<Vagrant::Machine: default (VagrantPlugins::ProviderVirtualBox::Provider)>, "192.168.33.1", {"/host_profile_home"=>{:nfs=>true, :guestpath=>"/host_profile_home", :hostpath=>"/Users/nnasiruddin", :disabled=>false, :type=>:nfs, :map_uid=>502, :map_gid=>20, :nfs_udp=>true, :nfs_version=>3, :uuid=>"3137651595"}}] (redhat)
    DEBUG ssh: Checking whether SSH is ready...
    DEBUG ssh: Re-using SSH connection.
     INFO ssh: SSH is ready!
    DEBUG ssh: Re-using SSH connection.
     INFO ssh: Execute:  (sudo=false)
    DEBUG ssh: Exit status: 0
    DEBUG guest: Searching for cap: shell_expand_guest_path
    DEBUG guest: Checking in: redhat
    DEBUG guest: Checking in: linux
    DEBUG guest: Found cap: shell_expand_guest_path in linux
     INFO guest: Execute capability: shell_expand_guest_path [#<Vagrant::Machine: default (VagrantPlugins::ProviderVirtualBox::Provider)>, "/host_profile_home"] (redhat)
    DEBUG ssh: Re-using SSH connection.
     INFO ssh: Execute: echo; printf /host_profile_home (sudo=false)
    DEBUG ssh: stdout: 
    /host_profile_home
    DEBUG ssh: Exit status: 0
    DEBUG ssh: Re-using SSH connection.
     INFO ssh: Execute: mkdir -p /host_profile_home (sudo=true)
    DEBUG ssh: Re-using SSH connection.
     INFO ssh: Execute: echo; printf $SSH_AUTH_SOCK (sudo=false)
    DEBUG ssh: stdout: 
    /tmp/ssh-TxhxzU2467/agent.2467
    DEBUG ssh: Exit status: 0
     INFO ssh: Setting SSH_AUTH_SOCK remotely: /tmp/ssh-TxhxzU2467/agent.2467
    DEBUG ssh: Exit status: 0
    DEBUG ssh: Re-using SSH connection.
     INFO ssh: Execute: mount -o 'vers=3,udp' 192.168.33.1:'/Users/nnasiruddin' /host_profile_home (sudo=true)
    DEBUG ssh: Re-using SSH connection.
     INFO ssh: Execute: echo; printf $SSH_AUTH_SOCK (sudo=false)
    DEBUG ssh: stdout: 
    /tmp/ssh-TxhxzU2467/agent.2467
    DEBUG ssh: Exit status: 0
     INFO ssh: Setting SSH_AUTH_SOCK remotely: /tmp/ssh-TxhxzU2467/agent.2467
    DEBUG ssh: Sending SSH keep-alive...
    DEBUG ssh: Sending SSH keep-alive...
    DEBUG ssh: Sending SSH keep-alive...
    DEBUG ssh: Sending SSH keep-alive...
    DEBUG ssh: Sending SSH keep-alive...
    DEBUG ssh: Sending SSH keep-alive...
    DEBUG ssh: Sending SSH keep-alive...
    DEBUG ssh: Sending SSH keep-alive...
    DEBUG ssh: Sending SSH keep-alive...
    DEBUG ssh: Sending SSH keep-alive...
    DEBUG ssh: Sending SSH keep-alive...
    DEBUG ssh: Sending SSH keep-alive...
    DEBUG ssh: Sending SSH keep-alive...
    DEBUG ssh: Sending SSH keep-alive...
    DEBUG ssh: Sending SSH keep-alive...
    DEBUG ssh: Sending SSH keep-alive...
    DEBUG ssh: Sending SSH keep-alive...
    DEBUG ssh: Sending SSH keep-alive...
    DEBUG ssh: Sending SSH keep-alive...
    DEBUG ssh: Sending SSH keep-alive...
    DEBUG ssh: Sending SSH keep-alive...
    DEBUG ssh: Sending SSH keep-alive...
    DEBUG ssh: Sending SSH keep-alive...
    DEBUG ssh: Sending SSH keep-alive...
    DEBUG ssh: stderr: mount.nfs: Connection timed out

    DEBUG ssh: Exit status: 32
     INFO retryable: Retryable exception raised: #<Vagrant::Errors::LinuxNFSMountFailed: 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:'/Users/nnasiruddin' /host_profile_home

    Stdout from the command:

Things that I have tried are:
Power Off all Virtual Machines, Reboot my Vagrant , Completely reinstall Vagrant, Re install Virtual Box,
ifconfig...down thing, added 127.0.0.1 localhost to my hosts file

I however cannot turn of my firewall since its enterprise, but other people are doing fine so it may not be the firewall.

@mrjason
Copy link

mrjason commented Feb 3, 2015

Having the same issue

My config:
OS: MAC OS X 10.10.2
VirtualBox: 4.3.20
Vagrant: 1.7.2

@alyn000r
Copy link
Author

alyn000r commented Feb 3, 2015

I figured mine was an IP conflict issue the IP I had in my VagrantFile was
same as my ethos0 for my mac and hence it could not mount.

On Tuesday, February 3, 2015, Jason Hardin notifications@github.com wrote:

Having the same issue

My config:
OS: MAC OS X 10.10.2
VirtualBox: 4.3.20
Vagrant: 1.7.2


Reply to this email directly or view it on GitHub
#5232 (comment).

@mrjason
Copy link

mrjason commented Feb 10, 2015

My issue seems to be related to a usb hub that I had plugged in. It it possible it was one of the external drives that were plugged into it causing the issue or the hub. Removing the hub has resolved my issue though.

@rando305
Copy link

rando305 commented Mar 5, 2015

So alyn000r - how do you solve it?

@alyn000r
Copy link
Author

alyn000r commented Mar 5, 2015

Change the IP in Vagrant File to be a different IP it will work then.

On Thu, Mar 5, 2015 at 2:20 PM, Randy Ostler notifications@github.com
wrote:

So alyn000r - how do you solve it?


Reply to this email directly or view it on GitHub
#5232 (comment).

@mitchellh
Copy link
Contributor

I'm not able to reproduce this. The hunch that @alyn000r has sounds right. Vagrant uses the IP from the host only network and if this conflicts with other IPs, it very likely won't work. It is difficult for Vagrant to detect this.

@OZZlE
Copy link

OZZlE commented Oct 22, 2019

I had this issue on Catalina after I rebooted and I just CTRL+C'd when this error happened + vagrant ssh .. tried creating a file on my host system and it synced fine... everything works.. so I think there is some faulty check going on here also..

@OZZlE
Copy link

OZZlE commented Nov 28, 2019

I got this again now after my Mac crashed with vagrant running, MacOs Catalina (19A602). This time ctrl+c and vagrant ssh hasn't run everything like shell scripts etc

@ghost
Copy link

ghost commented Jan 28, 2020

I'm going to lock this issue because it has been closed for 30 days ⏳. This helps our maintainers find and focus on the active issues.

If you have found a problem that seems similar to this, please open a new issue and complete the issue template so we can capture all the details necessary to investigate further.

@hashicorp hashicorp locked and limited conversation to collaborators Jan 28, 2020
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Projects
None yet
Development

No branches or pull requests

6 participants