Comments (23)
@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 :)
from dinghy.
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
Ran brew link, and then finished a re-install of Dinghy, now everything is fine.
from dinghy.
I should that when initially installing, there were some issues with mismatched SHA1s on the unfs from sourceforge.
from dinghy.
Yeah it looks like there is a problem starting unfs. You probably ran into #41 , unfortunately it's out of my hands. Waiting on an upstream fix.
from dinghy.
Arite, thanks @codekitchen
from dinghy.
in the meantime I posted a workaround @ #41 (comment)
from dinghy.
I'm getting this too and have unfs v0.9.22 installed.
EDIT: a reboot fixed it for me
from dinghy.
I've had another report of this, I agree that it doesn't look related to #41
We wait 20s for unfsd to start, which should be plenty long enough. I need to try and repro. Is there anything unfs-related in system logs (viewable in Console.app) when the error happens?
from dinghy.
In investigation with @codekitchen we found that this appears to be a launchd issue, but there wasn't significant details in the log to tell us where to dig next.
from dinghy.
@levinotik I had the same problem.
Apparently my brew was a bit messed up. and had a missing link on both unfs and dsnmasq
making brew doctor
happy makes things running smooth now..
from dinghy.
Same issue here
from dinghy.
It might just be coincidence, but I had a co-worker who fixed this issue for him by installing the virtualbox expansion pack, which he didn't have installed yet. https://www.virtualbox.org/wiki/Downloads
from dinghy.
I resolved this with a reboot on my local machine, neglected to mention this in the above comment.
from dinghy.
Had already tried the reboot. Just installed the extension pack too, but the problem persists.
from dinghy.
same problem
fix it after downgrade 5.0.3 to 5.0 and NOT install Extension Pack
from dinghy.
Naah, tried 5.0.0 as well, but the problem is still there
from dinghy.
I wonder if this is related to the error this person saw #72 . If you run the nfs daemon manually, do you get a bind: Address already in use
error?
You'll have to get the virtual interface host IP address to do that, basically run dinghy ip
and replace the last portion with 1
, so 192.168.99.100
-> 192.168.99.1
And then:
sudo /usr/local/sbin/unfsd -e ~/.dinghy/machine-nfs-exports-dinghy -n 19321 -m 19321 -l <ip_addr> -p -b -d
from dinghy.
$ sudo /usr/local/sbin/unfsd -e ~/.dinghy/machine-nfs-exports-dinghy -n 19321 -m 19321 -l 192.168.99.1 -p -b -d
UNFS3 unfsd 0.9.22 (C) 2006, Pascal Schmidt <[email protected]>
bind: Address already in use
Couldn't bind to udp port 19321
from dinghy.
Likely the same root issue then. I'd be very surprised if anything other than our unfsd process is binding to that UDP port on the virtual machine interface, so it seems likely to be an issue with another unfsd
process already running, or something of that nature.
I would expect launchd to prevent this from happening, but maybe we're using it incorrectly.
from dinghy.
Well, when I reboot, dinghy works fine the first time, second time it doesn't. So I'd fathom that it's dinghy's unfsd
that's still running after not being shut down correctly.
from dinghy.
I finally got it to work locally:
- Deleted everything, including the dinghy VM.
- Downloaded the latest patch-level of VirtualBox and installed it.
- Downloaded the same version of VirtualBox Extension Pack and installed it.
- Ran dinghy create ...
I thought I did the same thing last time, but something must have been different.
from dinghy.
Yikes, seems worth filing an issue with VirtualBox as well.
from dinghy.
A lot of the issues with this are because launchd reports success even if the daemon fails to launch (apparently this is by design). Because of all the issues with using/abusing launchd the way we were, we've moved to our own daemon management code in the newest v4.1.0 release of dinghy. I'm going to close this, we'll handle any similar problems on the newest release as a new issue.
from dinghy.
Related Issues (20)
- The Ruby Guard gem is broken on Dinghy 4.6.5 HOT 1
- DNS resolution broken over IPv6 HOT 5
- Error creating machine: Error in driver during machine creation [ boot2docker under xhyve ] HOT 8
- NFS / FsEvents failed to run HOT 9
- [Question] bridge network and port mapping HOT 4
- Can't enable SSL for self-signed domain HOT 5
- Dinghy cannot work when connect through Cisco VPN HOT 4
- 408 response on docker HOT 3
- Dinghy broken after brew upgrade to Docker 19.03.0 HOT 2
- dinghy halt && dinghy up result in error HOT 19
- How to access to same host and port as specified? HOT 5
- Error response from daemon: client version 1.40 is too new. Maximum supported API version is 1.38 HOT 4
- Is it possible to use a different config dir, preferences file?
- env has no docker_host HOT 1
- Hyperkit support HOT 8
- is the support for xhyve broken now? HOT 4
- Question regarding NFS about performance and security HOT 7
- Dinghy broken after update to MacOS Big sure HOT 1
- Apple M1 support
- NFS mounting fails when I start dinghy
Recommend Projects
-
React
A declarative, efficient, and flexible JavaScript library for building user interfaces.
-
Vue.js
🖖 Vue.js is a progressive, incrementally-adoptable JavaScript framework for building UI on the web.
-
Typescript
TypeScript is a superset of JavaScript that compiles to clean JavaScript output.
-
TensorFlow
An Open Source Machine Learning Framework for Everyone
-
Django
The Web framework for perfectionists with deadlines.
-
Laravel
A PHP framework for web artisans
-
D3
Bring data to life with SVG, Canvas and HTML. 📊📈🎉
-
Recommend Topics
-
javascript
JavaScript (JS) is a lightweight interpreted programming language with first-class functions.
-
web
Some thing interesting about web. New door for the world.
-
server
A server is a program made to process requests and deliver data to clients.
-
Machine learning
Machine learning is a way of modeling and interpreting data that allows a piece of software to respond intelligently.
-
Visualization
Some thing interesting about visualization, use data art
-
Game
Some thing interesting about game, make everyone happy.
Recommend Org
-
Facebook
We are working to build community through open source technology. NB: members must have two-factor auth.
-
Microsoft
Open source projects and samples from Microsoft.
-
Google
Google ❤️ Open Source for everyone.
-
Alibaba
Alibaba Open Source for everyone
-
D3
Data-Driven Documents codes.
-
Tencent
China tencent open source team.
from dinghy.