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

Boundary tries to connect to 127.0.0.1:9201 even when -cluster-listen-address is set #727

Closed
tcassaert opened this issue Oct 18, 2020 · 5 comments
Assignees
Labels
bug Something isn't working needs-response

Comments

@tcassaert
Copy link

tcassaert commented Oct 18, 2020

Describe the bug
When trying to run boundary in dev mode, with a different cluster-listen-address, boundary tries to reach 127.0.0.1:9201 instead of the provided cluster-listen-address.

To Reproduce
Steps to reproduce the behavior:

  1. Run boundary dev -cluster-listen-address=10.69.0.24
  2. Boundary starts, but shows following error:
2020-10-18T18:35:48.201Z [ERROR] worker: error making status request to controller: error="rpc error: code = Unavailable desc = last connection error: connection error: desc = "transport: Error while dialing unable to dial to controller: dial tcp 127.0.0.1:9201: connect: connection refused""

Expected behavior
Boundary should try to connect to the provided cluster-listen-address.

I realize there's not much reason to change the cluster-listen-address in dev mode, but when trying the options, it was confusing to see it fail.

@malnick
Copy link
Collaborator

malnick commented Oct 19, 2020

Thanks @tcassaert - I was able to repro this and will work on getting a fix in soon!

@malnick malnick added the bug Something isn't working label Oct 19, 2020
@malnick malnick self-assigned this Oct 19, 2020
@malnick
Copy link
Collaborator

malnick commented Oct 19, 2020

@tcassaert We fixed this on #705 and I've added a changelog update to reflect it: #730

Feel free to build and test from main. Thanks!

@tcassaert
Copy link
Author

Thanks!
I wanted to try it out, but it looks like there is a problem with building it:

make tools
go generate -tags tools tools/tools.go
go: github.com/golang-migrate/migrate/[email protected] requires
        modernc.org/[email protected]: reading modernc.org/b/go.mod at revision v1.0.0: git fetch -f origin refs/heads/*:refs/heads/* refs/tags/*:refs/tags/* in /root/go/pkg/mod/cache/vcs/e4d822a6e5117a941675151e51943e806b98394310c31351bf5d1078e126484b: exit status 128:
        error: RPC failed; result=22, HTTP code = 404
        fatal: The remote end hung up unexpectedly
make: *** [tools] Error 1

I don't know if this is a known issue?

@jefferai
Copy link
Member

jefferai commented Oct 20, 2020

This looks like a (hopefully temporary) issue with a downstream dep of a dep.

I just ran go clean -modcache followed by make tools and it worked for me, so give it another go!

@tcassaert
Copy link
Author

tcassaert commented Oct 26, 2020

Works fine, thanks!

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Something isn't working needs-response
Projects
None yet
Development

No branches or pull requests

3 participants