dinghy: Problems with unfs

This may very well be an issue with the unfs native lib and not dinghy per se, but having some issues with dinghy up.

Waiting for NFS daemon...
/usr/local/Cellar/dinghy/3.0.2/cli/dinghy/unfs.rb:18:in `sleep': execution expired (Timeout::Error)
    from /usr/local/Cellar/dinghy/3.0.2/cli/dinghy/unfs.rb:18:in `block in wait_for_unfs'
    from /usr/local/Cellar/dinghy/3.0.2/cli/dinghy/unfs.rb:15:in `wait_for_unfs'
    from /usr/local/Cellar/dinghy/3.0.2/cli/dinghy/unfs.rb:11:in `up'
    from /usr/local/Cellar/dinghy/3.0.2/cli/cli.rb:34:in `up'
    from /usr/local/Cellar/dinghy/3.0.2/cli/thor/lib/thor/command.rb:27:in `run'
    from /usr/local/Cellar/dinghy/3.0.2/cli/thor/lib/thor/invocation.rb:126:in `invoke_command'
    from /usr/local/Cellar/dinghy/3.0.2/cli/thor/lib/thor.rb:359:in `dispatch'
    from /usr/local/Cellar/dinghy/3.0.2/cli/thor/lib/thor/base.rb:440:in `start'
    from /usr/local/bin/dinghy:5:in `<main>’

Any ideas? Thanks!

About this issue

Original URL
State: closed
Created 9 years ago
Comments: 23 (8 by maintainers)

Most upvoted comments

Just for posterity, I was getting the same error when running dinghy up. I managed to get it working after trying to re-install Dinghy and finding that brew was unhappy and I needed to link unfs3

screen shot 2015-12-14 at 10 32 36 am

Ran brew link, and then finished a re-install of Dinghy, now everything is fine.

slwen on Dec 14, 2015

@codekitchen My colleague ran into this issue too. We thought that upgrading VirtualBox and installing Extension pack was something to try but noticed after running dinghy halt && dinghy destroy we still saw dinghy running in ps. Reason we checked is that VirtualBox installer told us it found a running VM and refused to upgrade unless all VMs were stopped.

ps auxwww | grep VBox
<user>           17831   0.0  0.0  2465932    228   ??  S    10:31AM   0:00.02 /Applications/VirtualBox.app/Contents/MacOS/VBoxHeadless --comment dinghy --startvm 31a6077c-1cb8-4846-97fd-2b2b4c09c936 --vrde config

VirtualBox also did not have any dinghy machine in its list. So maybe this phantom VM is what is causing the binded port.

Killing that running dinghy vm process and upgrading VirtualBox did not fix it for him, but after a restart it did. So future people that may encounter this problem, please look for a rouge process and report it please 😃

michaellopez on Nov 26, 2015