Closed delize closed 1 year ago
I did attempt to get support over on the Discord prior to posting this: https://discord.com/channels/890556779023466497/891608709313232916/1031735252269400115
Hello sir, please assign this issue to me as i already worked on this kind of problem in past and has a great experience.
@GeeteshMehto, if you can correct the underlying issue, I am sure that they would be willing to accept a PR to fix the problem.
I am not sure why assigning the issue to you specifically is preventing you from working on the problem.
Backed up database for recipes in postgres11, created a new postgres14 db, pointed recipes to the new db, and restored the old one.
Solved my issue. Closing this.
I wanted to add that I ran into this. Had these characters in my password: "`", "$", "#", "@". Same issue as author reports, connection fails when I am able to open it from the container manually. Guessing the backtick did it in? Changing to alpha-only password fixed the issue.
I've got the same issue switching form PG11 to PG15, with just postgres
for DB credentials. Deleting the DB and letting it generate a new one works, but after I import my backup dump it breaks again.
I've got the same issue switching form PG11 to PG15, with just
postgres
for DB credentials. Deleting the DB and letting it generate a new one works, but after I import my backup dump it breaks again.
on the db dump comment out the two lines creating the account and setting the password
I wanted to add that I ran into this. Had these characters in my password: "`", "$", "#", "@". Same issue as author reports, connection fails when I am able to open it from the container manually. Guessing the backtick did it in? Changing to alpha-only password fixed the issue.
Thanks for the suggestion but I guess I made a different mistake. I usually don't work with psql and got the syntax wrong.
This is stated in the Postgres upgrade guide in the FAQ:
/usr/local/bin/docker-compose exec -T <database_container_name> psql -U <postgres_user_name> postgres < /path/to/dump.sql
I thought the keyword postgres would be the password of the djangodb
in my case and you don't have to specify the password as all.
Issue
After a recent upgrade, Tandoor / Recipes no longer seems to connect to the Postgres database, even though the information is correct.
Logs can be found attached
However, if I login to postgres manually:
There is much more content in the DB, but too much to paste in the above codeblock.
Using the same password in the .env file, everything works great.
My postgres password does contain special characters, which I am wondering if this is the cause of the problem for some reason.
I am using Docker here, and the latest version I have is:
Docker-Compose Env File
Tandoor Version
1.4.4
OS Version
Ubuntu 22.04.1
Setup
Docker / Docker-Compose
Reverse Proxy
SWAG
Other
No response
Environment file
Docker-Compose file
Relevant logs