Fly.io problem after deployment
Hello,
I made deployment to fly.io but i mixed toml files.
I interrupted deploymend process when i saw this missmatch
Right now after deployment app with correct toml i got error probably with prisma.
2024-06-18T12:54:51.486 app[90801932c7dd78] ams [info] Error: P3009
2024-06-18T12:54:51.486 app[90801932c7dd78] ams [info] migrate found failed migrations in the target database, new migrations will not be applied. Read more about how to resolve migration issues in a production database: https://pris.ly/d/migrate-resolve
2024-06-18T12:54:51.486 app[90801932c7dd78] ams [info] The 20240606165441_0606024v2 migration started at 2024-06-18 12:06:55.657890 UTC failed
2024-06-18T12:53:50.809 app[d8dd626f075208] ams [info] > npm run db-migrate-prod && NODE_ENV=production npm run start
2024-06-18T12:53:34.293 proxy[90801932c7dd78] ams [info] Starting machine
2024-06-18T12:53:34.295 proxy[90801932c7dd78] ams [error] [PM07] failed to change machine state: machine still active, refusing to start
2024-06-18T12:53:56.645 proxy[d8dd626f075208] ams [info] Starting machine
2024-06-18T12:53:56.647 proxy[d8dd626f075208] ams [error] [PM07] failed to change machine state: machine still active, refusing to start
2024-06-18T12:53:37.337 proxy[90801932c7dd78] ams [info] Starting machine
2024-06-18T12:53:37.339 proxy[90801932c7dd78] ams [error] [PM07] failed to change machine state: machine still active, refusing to start
2024-06-18T12:53:59.623 proxy[d8dd626f075208] ams [info] Starting machine
2024-06-18T12:53:59.624 proxy[d8dd626f075208] ams [error] [PM07] failed to change machine state: machine still active, refusing to star
I made deployment to fly.io but i mixed toml files.
I interrupted deploymend process when i saw this missmatch
Right now after deployment app with correct toml i got error probably with prisma.
2024-06-18T12:54:51.486 app[90801932c7dd78] ams [info] Error: P3009
2024-06-18T12:54:51.486 app[90801932c7dd78] ams [info] migrate found failed migrations in the target database, new migrations will not be applied. Read more about how to resolve migration issues in a production database: https://pris.ly/d/migrate-resolve
2024-06-18T12:54:51.486 app[90801932c7dd78] ams [info] The 20240606165441_0606024v2 migration started at 2024-06-18 12:06:55.657890 UTC failed
2024-06-18T12:53:50.809 app[d8dd626f075208] ams [info] > npm run db-migrate-prod && NODE_ENV=production npm run start
2024-06-18T12:53:34.293 proxy[90801932c7dd78] ams [info] Starting machine
2024-06-18T12:53:34.295 proxy[90801932c7dd78] ams [error] [PM07] failed to change machine state: machine still active, refusing to start
2024-06-18T12:53:56.645 proxy[d8dd626f075208] ams [info] Starting machine
2024-06-18T12:53:56.647 proxy[d8dd626f075208] ams [error] [PM07] failed to change machine state: machine still active, refusing to start
2024-06-18T12:53:37.337 proxy[90801932c7dd78] ams [info] Starting machine
2024-06-18T12:53:37.339 proxy[90801932c7dd78] ams [error] [PM07] failed to change machine state: machine still active, refusing to start
2024-06-18T12:53:59.623 proxy[d8dd626f075208] ams [info] Starting machine
2024-06-18T12:53:59.624 proxy[d8dd626f075208] ams [error] [PM07] failed to change machine state: machine still active, refusing to star
How to reconcile the migration history after applying a hotfix or patch to a production environment.
