How to Debug Failing Mount

winnfsd / vagrant-winnfsd

Manage and adds support for NFS for Vagrant on Windows.

Other

570 stars 61 forks source link

How to Debug Failing Mount #57

Open jamiejackson opened 9 years ago

jamiejackson commented 9 years ago

When I'm at work, I don't usually have problems with the NFS shares. At home, I almost always do. (Same laptop, running Win7 64 Enterprise; Vagrant 1.7.2; vagrant-winnfsd 1.0.11.)

The symptom:

[NFS] Status: halted
[NFS] Start: started
==> default: Mounting NFS shared folders...

...and wait there indefinitely (minutes, hours).

However, there seem to be several tickets relating to similar issues, so I'll keep this one focused on debugging.

How do I enable debugging?

As far as I know, this is supposed to do it:

Vagrant.configure(VAGRANTFILE_API_VERSION) do |config|
  config.winnfsd.logging = "on"

...but during:

[NFS] Status: halted
[NFS] Start: started

... I only see the other window flash in and out of existence. Isn't it supposed to stay open?

jamiejackson commented 9 years ago

I'm at work now, and was still in the same Windows session that I started at home. vagrant reload yielded the same results as above.

I uninstalled vagrant-winnfsd and deleted any files/directories that mentioned winnfsd (including C:\HashiCorp\Vagrant\embedded\gems\gems\vagrant-1.7.2\nfspaths), and tried a vagrant up. It still didn't show the winnfsd daemon window (and FWIW, winnfsd didn't show in the processes).

Then I rebooted, ran vagrant up, and afterwards the winnfsd daemon window came up and stayed up. (Though this time, everything was successful, so there was nothing to debug.)

Can you tell me what the reboot did that got things working? It would be nice to know what that thing is, so when I need to debug, I don't have to do the full reboot for things to take effect.

bdw429s commented 9 years ago

Having the same issue here with Windows 7 host, Vagrant 1.7.2, vagrant-winnfsd 1.1.0 and a CentOS guest. The winnfsd.exe shows for a brief second in my Windows task manager, then automatically closes. When I enable logging a DOS window appears for a second or two but closes very quickly. I had to use a screen capture software just to catch what it said, which doesn't appear to be any kind of errors:

Commenting out all but one of my shares works, but I'm unclear how on earth to debug the issue with multiple shares. The Internet is long on people with similar issues, but short on actual answers.