Error while migrating schema

[geek1s42]

I am trying to spin up self hosted langfuse and getting below error at during the startup. Any help would be appreciated !!! I tried enabling debug/trace but this is the only logs it's printing.

Script executed successfully.
Prisma schema loaded from packages/shared/prisma/schema.prisma
Datasource "db": PostgreSQL database "langfuse", schema "public" at
270 migrations found in prisma/migrations
Error: P3009
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
The 20240528214728_add_cursor_index_04 migration started at 2024-11-21 22:05:01.329236 UTC failed
Applying database migrations failed. This is mostly caused by the database being unavailable.
Exiting...

[dosubot[bot]]

Hey @geek1s42! I'm here to help you with any bugs or questions you have. Let's squash this bug together!

It seems like you're encountering an issue with a failed migration. There are a few similar discussions that might help you resolve this:

1. In a discussion about Deployment on K8s, a similar issue was addressed. It was suggested that the migration might have failed due to short session timeouts configured on the PostgreSQL user. You can try using a separate user for migrations with longer timeouts. Additionally, check if the index from the migration exists on the table. If not, you can remove the row from the _prisma_migrations table and restart your container to reapply the migrations ^[1].

2. Another discussion on Auto-migration DB error when upgrading Langfuse version suggests checking if the migration changes are already applied in your database. If they are, you can mark the migration as finished in the migrations table by adding a date in finished_at and setting applied_step_count=1. If not, delete the row from the migrations table ^[2].

These steps should help you resolve the migration issue you're facing.

To continue talking to Dosu, mention @dosu.

[marcklingen]

@geek1s42 is this a new langfuse installation? if yes, can you try to just wipe the postgres database?

[geek1s42]

@marcklingen Thank you !!! This was resolved after wipe out.

[marcklingen]

Thank you for confirming. This process is usually unnecessary, but the recovery paths here are more complex than simply wiping the PostgreSQL data.