> fly machines stop 4d89613b696987
Sending kill signal to machine 4d89613b696987...
Error: could not stop machine 4d89613b696987: failed to stop VM 4d89613b696987: aborted: unable to stop machine, current state invalid, replacing
You might want to keep the machine around in case it helps folks at Fly debug it; but if you don’t want it around for any number of reasons, fly m destroy 4d89613b696987 -f should get rid of it. Exercise caution.
Had the same thing while I was trying to bring back my Postgres DB, gave up and destroyed the machines.
I’ve tried
cloning a previous machine fly machines clone 7811694b97d528 --region ams -a dert-gg-production-db --attach-volume vol_n0l9vlpoqlg4635d:/data
running a new machine from scratch and attaching the existing volume using fly machines run flyio/postgres-flex:15.3 --memory 2048 --vm-cpus 1 --region ams --volume vol_n0l9vlpoqlg4635d:/path -a dert-gg-production-db
Some of the machine IDs that I’ve created & destroyed
080e652f625048
784e290f26ee08
2874536f043398
e82d492f732248
d891d69b60ee78
Also when you “run” a new machine with the Postgres image, the checks are not setup, which would somehow be there if you create a new Postgres app, so I’m not sure whether not having any checks would have any effect on the app.