Possible bug: RuntimeError no datagram socket about landrush HOT 5 CLOSED

I ran into this just now. Turns out I had a rogue vagrant up that had left the landrush daemon running.

I tracked it down with sudo lsof -i -P | grep 10053 and killed the process.

from landrush.

Thank you for the suggestion, but this did not work in my case. I've got no landrush (or any other ruby process) running, but am still running into this issue using Vagrant 1.5.2.

from landrush.

Hey thanks for the report and sorry for the troubles!

Even though we've verified it's not a rogue landrush server, it does have
the shape of a port in use scenario.

Can you check to see if anything else is listening on port 10053?

On Thursday, April 3, 2014, Bruno Wassermann [email protected]
wrote:

Thank you for the suggestion, but this did not work in my case. I've got
no landrush (or any other ruby process) running, but am still running into
this issue using Vagrant 1.5.2.

Reply to this email directly or view it on GitHubhttps://github.com//issues/54#issuecomment-39418482
.

from landrush.

Unfortunately, neither netstat nor lsof reveal anything bound to port 10053.

from landrush.

Happy to report that this issue seems to have resolved itself (by installing the latest version of vagrant 1.5.4?).

from landrush.