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

Handle missing influxdb on init in InfluxDB Publisher #113

Closed
BrianJKoopman opened this issue Mar 8, 2020 · 0 comments · Fixed by #154
Closed

Handle missing influxdb on init in InfluxDB Publisher #113

BrianJKoopman opened this issue Mar 8, 2020 · 0 comments · Fixed by #154
Assignees
Labels
bug Something isn't working
Milestone

Comments

@BrianJKoopman
Copy link
Member

If the InfluxDB isn't running when you start the publisher it won't be able to connect and will crash. While we handle the DB disappearing after startup, we don't handle the case of a missing DB pre-startup. We suggest Influx is run separate from other ocs containers (in a different docker-compose file) and kept online at all times, if a user configures both services in a single docker-compose likely the publisher comes up before influx and thus will crash immediately.

@BrianJKoopman BrianJKoopman added the bug Something isn't working label Mar 8, 2020
@BrianJKoopman BrianJKoopman self-assigned this Mar 8, 2020
BrianJKoopman added a commit that referenced this issue Jul 20, 2020
Failing to fetch the database list from InfluxDB is indicative of the database
not being up yet. This could occur if InfluxDB is in the same docker-compose
file as a freshly starting OCS system. Attempt to reconnect forever.

Fixes #113
BrianJKoopman added a commit that referenced this issue Jul 20, 2020
@BrianJKoopman BrianJKoopman added this to the v0.7.0 milestone Jul 20, 2020
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Something isn't working
Projects
None yet
Development

Successfully merging a pull request may close this issue.

1 participant