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

Commandline option -join does not work when used multiple times #52

Closed
whizz opened this issue Dec 14, 2015 · 1 comment · Fixed by #61
Closed

Commandline option -join does not work when used multiple times #52

whizz opened this issue Dec 14, 2015 · 1 comment · Fixed by #61

Comments

@whizz
Copy link
Contributor

whizz commented Dec 14, 2015

When you specify multiple -join values, the agent will not join a cluster, as the value is wrongly interpreted.

# ./dkron agent -node v-5004.local -bind 0.0.0.0:8946 -http-addr :8080 -backend consul -backend-machine v-211.local:8500 -server -keyspace dkron -encrypt kPpdjphiipNSsjd4QHWbkA== -rpc-port 6868 -tag role=test -join 127.0.0.1:5001 -join 127.0.0.1:5002

INFO[0000] No valid config found: Unsupported Config Type ""
 Applying default values.
Starting Dkron agent...
INFO[2015-12-14T13:37:48+01:00] agent: Dkron agent starting
INFO[2015-12-14T13:37:48+01:00] agent: joining: [127.0.0.1:5001,127.0.0.1:5002] replay: true
WARN[2015-12-14T13:37:48+01:00] agent: error joining: too many colons in address 127.0.0.1:5001,127.0.0.1:5002
INFO[2015-12-14T13:37:48+01:00] api: Running HTTP server                      address=:8080
INFO[2015-12-14T13:37:48+01:00] api: Exiting HTTP server
INFO[2015-12-14T13:37:48+01:00] agent: Listen for events
@vcastellm
Copy link
Member

This was a bug indeed @whizz

Fixed in the related PR

Thanks for testing!

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging a pull request may close this issue.

2 participants