Machine stuck "starting" for 1.5+ hours, can't be killed

Questions / Help
1

It’s all there in the topic. I have a machine stuck in “starting” state that can’t be killed or restarted:

❯ fly machine restart 683037ebe69518 -a kts-parts-db 2>&1
Restarting machine 683037ebe69518
Error: failed to restart machine 683037ebe69518: could not stop machine 683037ebe69518: failed to restart VM 683037ebe69518: failed_precondition: machine still restarting (Request ID: 01KS0JVK4D9ZDANK4SM7BM8N82-dfw)
❯ fly machine kill 683037ebe69518 -a kts-parts-db 2>&1
machine 683037ebe69518 was found and is currently in a starting state, attempting to kill…
Error: could not kill machine 683037ebe69518: failed to kill VM 683037ebe69518: deadline_exceeded: failed to wait for machine to be ready (Requ

2

Hi, this machine is a Postgres server, we don’t recommend running a single-node Postgres because it’s susceptible to downtime due to trouble starting machines. This machine is failing to start due to an issue on our side, we’re fixing it, I’ll let you know when it’s back up.

3

Hi, this machine should be up and running now. Let us know if it still gives trouble!

4

This app is infrequently used so I opted to have the Postgres and application server suspend when not used. I extended the volume on the postures server thinking maybe it was running out of resources. What you recommend short of moving to managed Postgres?