Skip to content
This repository has been archived by the owner on Jan 30, 2020. It is now read-only.

fleetd no longer has default etcd endpoints #1301

Closed
mischief opened this issue Jul 9, 2015 · 0 comments · Fixed by #1302
Closed

fleetd no longer has default etcd endpoints #1301

mischief opened this issue Jul 9, 2015 · 0 comments · Fixed by #1302
Assignees

Comments

@mischief
Copy link
Contributor

mischief commented Jul 9, 2015

since approximately 30f9f1f, fleetd no longer has default etcd endpoints, resulting in fleetd exiting if no configuration is specified.

Jul 09 22:03:22 localhost systemd[1]: Started fleet daemon.
Jul 09 22:03:22 localhost systemd[1]: Starting fleet daemon...
Jul 09 22:03:22 localhost fleetd[566]: INFO fleetd.go:64: Starting fleetd version 0.11.0
Jul 09 22:03:22 localhost fleetd[566]: INFO fleetd.go:168: No provided or default config file found - proceeding without
Jul 09 22:03:22 localhost fleetd[566]: FATAL fleetd.go:90: Failed creating Server: client: no endpoints available
Jul 09 22:03:22 localhost systemd[1]: fleet.service: Main process exited, code=exited, status=1/FAILURE
Jul 09 22:03:22 localhost systemd[1]: fleet.service: Unit entered failed state.
Jul 09 22:03:22 localhost systemd[1]: fleet.service: Failed with result 'exit-code'.
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Projects
None yet
Development

Successfully merging a pull request may close this issue.

1 participant