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

Launch error with empty host for a node #180

Closed
eile opened this issue Nov 21, 2012 · 0 comments
Closed

Launch error with empty host for a node #180

eile opened this issue Nov 21, 2012 · 0 comments
Assignees
Labels
Milestone

Comments

@eile
Copy link
Member

eile commented Nov 21, 2012

The setup:

node
{
#    host     "bbplxviz13"
    connection
    {
         hostname      "bbplxviz13"
         filename      "default"
    }
}

will auto-launch the node on 127.0.0.1 which is not bbplxviz13. The reason is that the node's host is empty and the launcher guesses it to be 127.0.0.1. The user forgot to add the commented line, but the resulting behaviour is not easy to debug. Later on Equalizer would try to auto-launch on all connection hostnames, but since the first launch actually starts the client, it doesn't try anymore.

@ghost ghost assigned eile Nov 21, 2012
@eile eile closed this as completed in fcd53e5 Nov 21, 2012
eile pushed a commit that referenced this issue Nov 21, 2012
Instead of using 127.0.0.1 for an empty host, the server::Node now uses
the first hostname from a connection description as a better guess.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

No branches or pull requests

1 participant