Hello!
I was just following the advice here to update the image of our app’s Postgres instance, in order to update some configuration settings using stolonctl
.
I ran flyctl image update --app <app_name>
to update the image on our staging server, which worked without issue. Running the same on the production database has brought it down.
It looks like the production image has updated from 14.2 to 14.6, but is no longer responsive. The logs are repetitively showing the following:
ERRO[0255] Error opening connection to database (postgresql://...): dial tcp [...]:5433: connect: connection refused source="postgres_exporter.go:1658"
app[324551e6] ord [info] checking stolon status
ERROR cmd/keeper.go:719 cannot get configured pg parameters {"error": "dial unix /tmp/.s.PGSQL.5433: connect: no such file or directory"}
WARN cmd/sentinel.go:276 no keeper info available {"db": "338c1aa7", "keeper": "9ad9175e2"}
ERROR cmd/sentinel.go:1018 no eligible masters
Anyone know what might be going on, or how to get a functional database back up and running?