This week my first db stopped working, when i try to do some “upgrade” or “restart” on the db, i got this error : Error no active leader found Then i tried to create a new db from a snapshot of the first db. But i got this error when i started to deploy an image to get external connection : 2023-…

Is it easier to change my app connection to the new db or to solve the problem with the first db ? You should be able to fix your api db by doing something like: fly volumes list --app <app-name> Take note of the volume that doesn’t have an attached VM. This holds your primary’s data. fly mac…

[image] Musto: Error no active leader found Not sure what’s up with the db, but someone in the past reported that scaling up / down, for example flyctl scale count <n> -a mydb-app, has worked (I am not sure how). Prudent to check the status of the db (flyctl status --all -a mydb-app) to rule…

flyctl pg create --snapshot-id <sid> -a <app-name> --flex This unfortunately will not work. You will need to perform a pg dump/restore to move to flex as of right now. We are actively working to make this transition process easier for users.

flyctl status --all -a mydb-app ID STATE ROLE REGION HEALTH CHECKS IMAGE CREATED UPDATED 9080291c6d3dd8 started error cdg 3 total flyio/postgres:14.6 (v0.0.34) 2023-01-08T12:44:20Z 2023-02-19T12:45:56Z…

[image] ignoramous: flyctl scale count -a mydb-app flyctl scale count 1 -a app_name Error it looks like your app is running on v2 of our platform, and does not support this legacy command```

@Musto I took a look at your app and looks like your standby does not have a volume attached to it. I would remove that machine using: fly machines stop <machine-id> --app <app-name> fly machines remove <machine-id> --app <app-name> Then create a new one using: fly machines clone <primarys-mac…

Hey thanks for your help ! fly machines stop <908..(machine-id)> -a <app-name> //Success fly machines remove <908..(machine-id)> -a <app-name> //Success fly machines clone <908..(machine-id)> //Could not find app fly machines clone<908..(machine-id)> -a <app-name> //Success /* Cloning machine <908.…

Strange… Looks like the volume didn’t get created. I went ahead and created a new volume for you: fly volumes create pg_data --size 1 --region cdg You can view you volumes by running: fly volumes list Then I performed the clone command as follows: fly machines clone <primary-machine-id> --att…

Be careful, i was modifying the first db (portfo…-api-m…-db) and not the new one (m…-db) Is it easier to change my app connection to the new db or to solve the problem with the first db ?

Flyctl version : v0.0.464 I executed the clone of my existing machine with the unallocated volume : Machine has been successfully cloned! And it works ! Thank you very much ! Do you know what was the problem? It works perfectly fine for weeks and suddenly this problem appears. It will help many…

Postgre App looping with error : exit status 1

Questions / Help Build debugging

shaun February 25, 2023, 8:44pm 11

If you don’t have any data in these dbs yet, I would update your flyctl version and re-provision them. You’ll then be on the latest implementation of our Postgres offering: