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

Consul RPC errors if non-explicit bind address #148

Closed
armon opened this issue May 13, 2014 · 3 comments
Closed

Consul RPC errors if non-explicit bind address #148

armon opened this issue May 13, 2014 · 3 comments
Labels
type/bug Feature does not function as expected

Comments

@armon
Copy link
Member

armon commented May 13, 2014

Errors like:

agent: failed to sync remote state: failed to get conn: dial tcp [::]:8300: network is unreachable

Are caused by a non-explicit bind address on consul server nodes only.

@armon armon added the bug label May 13, 2014
@armon armon added this to the 0.3 milestone Jun 9, 2014
@davidfeldi
Copy link

How can I fix this kind of errors ?
agent: failed to sync remote state: failed to get conn: dial tcp [::]:8300: network is unreachable

this is my first deploy of consul , on 1 server + web gui , just want to try it out .
the server is running 5 diffrenet services ..

i'm starting the server with ::
consul agent -server -bootstrap -data-dir /home/admin/apps/consul/ -ui-dir /home/admin/apps/consul/dist

now i get this message all the time ..
is it ok ? not ok ? how can i tell what i going on ?

Thanks.

@armon
Copy link
Member Author

armon commented Jun 10, 2014

@davidfeldi Currently it is fixed by providing the -bind configuration. Its an issue when not provided

@armon armon closed this as completed in ab4e3de Jun 11, 2014
@davidfeldi
Copy link

@armon Thanks!

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
type/bug Feature does not function as expected
Projects
None yet
Development

No branches or pull requests

2 participants