pg db unreachable, unable to restart or scale

1

I’m running a single instance machines postgres db on fly, and today it just became unreachable to other services. I tried to restart the machine, but I keep getting this error:

 fly machine restart
? Select machines: 32874599c655d8 black-sun-3866 (started, region lax)
Error: failed to obtain lease: failed to get lease on VM 32874599c655d8: Post "http://[fc01:a7b:113::]:3593/flyd.v1.LeaseService/Acquire": dial tcp [fc01:a7b:113::]:3593: i/o timeout (Request ID: 01HXCQJBW2C5BWC6GHXT5WDZGF-sjc)
breadcrum-db-flex % fly machine stop  
? Select machines: 32874599c655d8 black-sun-3866 (started, region lax)
Error: failed to obtain lease: failed to get lease on VM 32874599c655d8: Post "http://[fc01:a7b:113::]:3593/flyd.v1.LeaseService/Acquire": dial tcp [fc01:a7b:113::]:3593: i/o timeout (Request ID: 01HXCQTBDKCN9J22YE9SKEX8Y6-sjc)
?1 breadcrum-db-flex % fly machine kill
? Select a machine: 32874599c655d8 black-sun-3866 (started, region lax)
machine 32874599c655d8 was found and is currently in a started state, attempting to kill...
Error: could not kill machine 32874599c655d8: failed to kill VM 32874599c655d8: unavailable: dial tcp [fc01:a7b:113::]:3593: connect: connection refused (Request ID: 01HXCQYV8P2G3A9XCZ8K019KT3-sjc)

Guessing this is related to the network connectivity issue in the first place, and yes I should have some redundancy here. Is there any workaround to kick the machine to restart or move regions?

2

Just saw this in my personal status board:

We are performing emergency maintenance on a host some of your apps instances are running on. Apps may be unavailable until the maintenance is completed.
3

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