Issues with Database Migration After Update - Seeking Advice

Samantha Z. · 2025-02-14T19:28:59.463Z

We're running into problems with migrating the database after updating to the latest version (self-hosted). We're thinking the safest bet is to wipe the database (since there's nothing important in there, yet), but has anyone else run into this problem?

RunLLM
APP
·
Yes, database migration issues have been reported by other users. A common solution is to use the Alembic CLI to revert any partial migrations and reset the migration state. This can be done by running `alembic stamp` from the `src/phoenix/db` directory inside the Phoenix project root, as mentioned in <https://github.com/Arize-ai/phoenix/issues/3246|this GitHub issue>. If the database is not critical, wiping it and starting fresh is a viable option, as suggested in <https://arize-ai.slack.com/archives/C04R3GXC8HK/p1720689418.425939|this Slack conversation>. Would you like more detail on how to perform these steps? Sources: - <https://github.com/Arize-ai/phoenix/issues/3246|GitHub Issue 3246> - <https://arize-ai.slack.com/archives/C04R3GXC8HK/p1720689418.425939|Slack Conversation>
💡 Hint: Mention RunLLM in the thread for followups.
Anthony P.
·
Hey Samantha Z. really sorry to hear that, this is certainly unexpected. Can you elaborate on the problems you are seeing?
Samantha Z.
·
I think the issue is that we're trying to convert the docker-compose examples found online into a terraform/helm chart type setup, and troubleshoot why when we try to restart the database, we're getting these same 'migration failed' errors mentioned in this ticket
Anthony P.
·
Is it possible to rule out connection issues between your phoenix container and your database container? Namely the database url is correct and accessible from the phoenix container? I am wondering if the migration error is somewhat of a red herring; We try to perform migrations on startup, and if the database is not accessible then technically the migration has failed
Samantha Z.
·
Yes, what we're seeing is that the container comes up and immediately crashes, so we can't log into it to run migrations
Samantha Z.
·
We doublechecked the database url
Anthony P.
·
Dustin N. do you have more insight into the migration process for Phoenix? My understanding is that we will attempt to connect to your configured database url on boot-up, perform migrations, and then proceed
Anthony P.
·
if we fail to connect, or migrate, we will crash
Anthony P.
·
Just to clarify, you are using postgres correct?
Samantha Z.
·
yes, postgres
Anthony P.
·
cool, thanks
Anthony P.
·
Are you pinning your phoenix version directly or using the latest tag?
Samantha Z.
·
Yeah, it would be better if the container didn't just crash, but would let us log in to troubleshoot
Samantha Z.
·
It's pinned
Anthony P.
·
Are you connecting to the same database instance that you had pre-update?

Issues with Database Migration After Update - Seeking Advice

22 comments

Issues with Database Migration After Update - Seeking Advice

22 comments