PG machines had disruption and never came back

Team, at some point an app (arcadia-pg) on my account listed a disruption with postgres last night… but the machines themselves have still not come back. Since it has disk persistence, how do I get the machine back?


I’d guess a restart would bring it back?

For example:

fly machine restart <machine-id> -a <db-app-name>

You should be able to get that machine ID value using:

fly machine list -a <db-app-name>

Looks like that did it.

I got too hung up on the fly postgres restart workflow - which did not go well and didn’t even venture into machine restart. Thank you!

1 Like

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