and I can’t destroy it or detach the volume that’s on it. it still shows up in some places (though it is non-responsive and I can’t interact with it via the CLI).
Hey, we are still experiencing an issue with the DB. We have a 2GB volume attached to it and there is a lot of free space. However, the DB continues to crash saying: “Health check for your postgres role has failed. Your cluster’s membership is inconsistent. Health check for your postgres role has failed. Your cluster’s membership is inconsistent.”
Likewise, I also get ‘your database is malfunctioning’. Last time I had to spin up a new database machine with an offsite backup as I doubt fly.io is going to step in here again.
I’ve upgraded my server to three times its usual specs and even scaled it up, but I’m still encountering errors saying the database connection pool is full. As a workaround,
We have been experiencing a slow connection with the database since 11:00 CET today, and we are unsure if they are connected to this incident. In our case, we are connecting to a Supabase-managed database.
The issue also manifests in increased CPU usage, potentially caused by a pool of connections being retried.