-
Notifications
You must be signed in to change notification settings - Fork 303
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
Authentication Failure in test and prod env #418
Comments
Postgres 14 is not yet compatible. Use <= 13. |
Thanks for the prompt reply. My mad. it was actually using postgresversion 13 |
Do you have any kind of custom rule for DB? |
no |
@joao-p-marques do you know what is happening? |
@bosd did you have an old password set up and then changed? If so, it might be that that password is not getting updated. It should be done automatically, but try running |
just checked if this was related to the single line yaml input for domain prod and domain test. But even with leaving these values empty it occurs. log from freshly installed test on a vps: db_1 | 2021-04-16 14:05:16.937 GMT [1] LOG: starting PostgreSQL 13.1 on x86_64-pc-linux-musl, compiled by gcc (Alpine 10.2.1_pre1) 10.2.1 20201203, 64-bit The devel environment is working fine. |
No, I experienced this from a fresh copier install. Will try your suggestions and report back. |
Ok, it might also be that the container that is not updating is the Postgres one, so you could try to delete the volumes ( |
ran but still an authentication eror |
Ok, what about the last suggestion and recreating the DB volumes? |
it is still executing :) I noticed that the conents of odoo.conf is set to almost finished loading now. Looks like it is connecting. Because there is the not initilazed db error.
|
🎉 it's working now After my previous message I had to initialize the db. after a for testing purposes... continueing the test. similar, the prod environment will not launch db_1 | 2021-04-16 15:15:36.072 GMT [1] LOG: database system is ready to accept connections so Summary for my understanding. Further remarks: |
Thanks for the detailed description @bosd I am glad it is working for you now. A few remarks and answers to your questions:
Just for reference,
Maybe @yajo can give some more insight on the way this should be handled, but the main use case for the
AFAICS that variable is only being used in the |
Yes, and not only the volumes. The image doodba builds for devel isn't compatible with the image built for test/prod.
Nope, devel is always done in English. This seems fixed, so closing 😺 |
Yes, issue is fixed. I am actually using the devel environment on a different machine and the production env on the server. Seems, like Im not following the correct workflow for developing local and then take take it into production. What is the correct workflow? |
That seems like a subject you better ask in the forum. |
Thank you all here for exposing your experience regarding this issue, I spent hours trying to find out why it didn't work and thanks to your comments I was able to do it. It was because I was using the project created by copier to use as development and then intend to use as production (certainly not recommended). However, the key to switching between modes is to purge the volumes and images with: Remember that it is necessary to point the domain to the IP of the pc you are using, at least by editing the hosts file and placing |
I add another partial solution when even doing all this the error appears: "Internal Server Error" |
If you are having problems using development and test/production environments on the same computer, you may be asking yourself some questions like: Why doesn't the copier ask you what type of environment you are going to work in? Should the projects be called something else? |
Used image postgres
1413.Occurs in both odoo 13 and 14
Describe the bug
When starting the production environment the log reads:
A clear and concise description of what the bug is.
To Reproduce
Follow regular workflow:
Install copier
invoke img-pull img-build --pull git-aggregate resetdb start
set the secrets in:
./.docker/db-access.env
toPGPASSWORD=odoopassword
./.docker/db-creation.env
toPOSTGRES_PASSWORD=odoopassword
(or leve them alone as they are filled from the copier script)
initiate the database with
docker-compose run --rm odoo --stop-after-init -i base
(Docker may throw an network error, preform an extra compose down and
docker network prune
)start production environment with:
docker-compose -f prod.yaml up
Affected versions:
Used image postgres
1413. (edit: typo)Occurs in both odoo 13 and 14
Expected behavior
Booting into production environment.
Additional context Add any other context about the problem here. (e.g. OS, Docker
version, ...)
host system debian10
The text was updated successfully, but these errors were encountered: