Postgres suddenly stopped working

Questions / Help
1

Not sure what happened, but my postgres instance just suddenly stopped working,

This is the error from the logs

2022-02-18T21:12:05Z runner[84905eaa] lax [info]Shutting down virtual machine
2022-02-18T21:12:35Z app[84905eaa] lax [info]Sending signal SIGTERM to main child process w/ PID 518
2022-02-18T21:12:35Z app[84905eaa] lax [info]Got terminated, stopping
2022-02-18T21:12:35Z app[84905eaa] lax [info]supervisor stopping
2022-02-18T21:12:35Z app[84905eaa] lax [info]exporter | signal: interrupt
2022-02-18T21:12:35Z app[84905eaa] lax [info]flypg    | Process exited 0
2022-02-18T21:12:36Z app[84905eaa] lax [info]Main child exited normally with code: 0
2022-02-18T21:12:36Z app[84905eaa] lax [info]Starting clean up.
2022-02-18T21:12:36Z app[84905eaa] lax [info]Umounting /dev/vdc from /data

I cant seem to restore the postgres instance, tried scaling up and down, no luck

2

We are performing emergency maintenance on a disk array in LAX right now: Fly.io Status - Emergency hardware maintenance in LAX region

We’re hoping to get this array back up soon. We’ll post more updates on the status page when we get them.

3

@kurt Thanks, just received the status update email

4

@kurt Im having issues with my apps after the LAX maintenance, my app cannot connect to the database anymore.

app: classly-dev
db: classly-dev-pg

5

No worries, I was able to get it up and running again. Adding a volume to my instance changed the region of the app as well which I figure caused some issues