Troubleshooting Phoenix Docker Postgres Migration Errors | Arize AI Community

Arize AI Community Icon

Troubleshooting Phoenix Docker Postgres Migration Errors | Arize AI Community

RunLLM
APP
·
The error you're encountering suggests that the database migration process is failing, possibly due to a dirty state or version mismatch. This can occur if the database was initialized with a different version of PostgreSQL than the one currently being used. According to the Phoenix GitHub issue, one solution is to ensure that the PostgreSQL version is consistent. You can pin the PostgreSQL version in your Docker Compose file to avoid compatibility issues, as suggested in the Phoenix GitHub pull request.Try updating your Docker Compose file to specify a compatible PostgreSQL version, such as version 16, to prevent version-related errors: LBKSdb: image: postgres:16 restart: always environment: - POSTGRES_USER=phoenix - POSTGRES_PASSWORD=postgres - POSTGRES_DB=postgres ports: - 5434 volumes: - database_data:/var/lib/postgresql/dataLBKSWould you like more details on resolving migration issues?Sources: - Phoenix GitHub issue - Phoenix GitHub pull request
💡 Hint: Mention RunLLM in the thread for followups.
Dustin N.
·
Hi Muhammad K. is there any chance you’ve installed a prerelease build of Phoenix in the past? The migration errors are worrying and it’s very unlikely you encounter them if you’re only updating Phoenix
Muhammad K.
·
No, I haven't. Although have been using phoenix before with SQLite but now I want to switch to Postgres and each time I try build the image with a postgres db it fails
Xander S.
·
Do you have any other pre-existing tables in your Postgres instance, or is it a fresh instance?
Muhammad K.
·
It's a fresh instance. From the compose file, I expect it spins up a fresh postgres instance.
Xander S.
·
it looks like it has a volume mount to disk.
Xander S.
·
can you try a fresh location on disk and see if the issue persists?
Muhammad K.
·
Hmmm, I think I saw that. Let me try what you said and revert
Muhammad K.
·
Wow it worked That was the problem all along. Apparently, I have another postgres instance running my system and was mapped to the same volume. I stopped the other container but I didn't realise there were mapped to the same volume. Thank you Xander S. and Dustin N.
🙌1
Muhammad K.
·
I have a question then. Does it mean I have to use a fresh postgres instance for phoenix. Is it possible I configure it to use an already existing postgres instance?
Xander S.
·
we definitely recommend using a fresh instance of postgres to avoid collision between previously existing tables and tables used by phoenix
Muhammad K.
·
Alright, thanks Xander S.
Roger Y.
·
just as a bit of extra info, there is an environment variable called PHOENIX_SQL_DATABASE_SCHEMA, which is a string (say xyz) that if specified will create a new schema (which is kind of like a subfolder) of that same name (say xyz) in postgres and use that instead (so the queries will be select … from xyz.table etc).
Muhammad K.
·
Alright thanks
👍1
Muhammad K.
·
Can I not create a new database on the same postgres instance which phoenix can not to. Since it's a fresh database I expect it to work. But when I tried that it didn't work, it gave the same error as the above. I am trying to avoid creating a new instance because my llm application already have a postgres instance running. What do you advice