-
-
Notifications
You must be signed in to change notification settings - Fork 589
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
"ProgrammingError" after Database Migration #3198
Comments
please enable debug and share the tandoor logs from first boot |
@smilerz I get a slightly different error about a duplicate RecipeBook this time
|
|
@smilerz this really isn't advice, just quoting my own message back to me - how do I fix it if it's not true? And/or what debugging tool/ui do I use to figure it out? |
you need to go into the database, find the duplicate name and delete it. Alternatively, return the state to a prior working version and find the duplicate recipe book and delete it from the Tandoor UI |
Can do, but I'm hoping I can try your other suggestion first, just to avoid a total clustertruck in the event I botch it. Luckily I work with a few former and current DBAs who I might be able to call in for a favor.
I tried to find documentation of version compatibility, but got lost - any idea what Tandoor version last supported postgres 11 by any chance? I figured this would work, but I couldn't seem to go back far enough in the tags. |
Unfortunately, it would have to be the exact version that you had installed previously. |
sorry for the inconvenice on this, this was a very old inconsistency error that came up trough a migration a few month ago. You need to remove the duplicates (there are maybe more than one), after that just run the migrations again. The changelog says on which version Postgres 11 support was dropped, i would migrate first to that version and then upgrade to pg 16 and then do the last few migrations which should run smoothly. |
Issue
I upgraded from postgres 11 to postgres 16 successfully, tested using a blank db before clearing the db, letting postgres 16 set it up empty, and then loading in the old postgres 11 dump, all per the Thomas Brandt guide.
After importing, restarting the db container, then allowing the tandoor container to start and perform its migration steps, it shows a "Programming Error" screen with the following key points (full traceback below that)
Tandoor Version
Can't see the version, docker hash as follows: sha256:177a634dc07d0b94013dd94c98174836fa00e8513829fd47467e725964857126
OS Version
Synology DSM 7.1.1-42962
Setup
Docker / Docker-Compose
Reverse Proxy
Nginx Proxy Manager (NPM)
Other
Portainer-managed docker
Environment file
Docker-Compose file
Relevant logs
No response
The text was updated successfully, but these errors were encountered: