You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I have observed cases where waterfurnace_aurora has stopped publishing new events to my MQTT broker, but I don't see any errors in the waterfurnace_aurora docker containers logs to indicate anything is wrong. Restarting the docker container resolves this.
Ideally I think I would create a healthcheck in docker compose that restarts my service if it is not sending events as expected.
reacted with thumbs up emoji reacted with thumbs down emoji reacted with laugh emoji reacted with hooray emoji reacted with confused emoji reacted with heart emoji reacted with rocket emoji reacted with eyes emoji
-
I have observed cases where waterfurnace_aurora has stopped publishing new events to my MQTT broker, but I don't see any errors in the waterfurnace_aurora docker containers logs to indicate anything is wrong. Restarting the docker container resolves this.
Ideally I think I would create a healthcheck in docker compose that restarts my service if it is not sending events as expected.
I attempted to add the following healthcheck:
but see this in the logs after:
Does anyone have any suggestions for what a simple health check could look like for this service?
I'm happy to MR it back to https://github.com/ccutrer/waterfurnace_aurora/blob/main/docker/README.md once I've observed it restarting the service after a failure.
Beta Was this translation helpful? Give feedback.
All reactions