Old fly postgres app running V1 can not be migrated and is stuck in bad state - restart not available - migrate not available

1

We have a few old fly pg deployments on v1 and we are completely stuck, we are not able to restart these or migrate them to v2.

image
image2750×526 51.5 KB

We cant seem to find a way to get that second VM to properly restart and begin to pass all its checks.

Error:

cmd/keeper.go:720 cannot get configured pg parameters {"error": "dial unix /tmp/.s.PGSQL.5433: connect: no such file or directory"}

ERROR cmd/keeper.go:1452 different local dbUID but init mode is none, this shouldn't happen. Something bad happened to the keeper data. Check that keeper data is on a persistent volume and that the keeper state files weren't removed

fly apps restart rotator-api-pg                                                                                                                                                                    
Error: postgres apps should use `fly pg restart` instead

fly pg restart                                                                                                                                                                                       
Error: command is not compatible with this image

Running the fly migrate-to-v2 command returns this:

Error: 404: 404 page not found

App: rotator-api-pg

Any help would be greatly appreciated.

2

This topic was automatically closed 7 days after the last reply. New replies are no longer allowed.