Published a year ago
Published a year ago
mvdk27
Updated a year ago
0
`I've installed safeline 3 month ago on PROD server (24.04.2 LTS) and it works perfect!
Today I run the same procedure to install safeline on TEST server (24.04.2 LTS) and it fails for 2 containers.
Working in PROD
Not workin in TEST
safeline-mgt logs
panic: failed to init pg db: cannot parse
postgres://safeline-ce:xxxxxx@safeline-pg/safeline-ce?sslmode=disable: failed to parse as URL (parse "postgres://safeline-ce:{postgres-password}@safeline-pg/safeline-ce?sslmode=disable": net/url: invalid userinfo)
safeline-luigi logs
[error] failed to initialize database, got error cannot parse
postgres://safeline-ce:xxxxxx@safeline-pg/safeline-ce?sslmode=disable: failed to parse as URL (parse "postgres://safeline-ce:{postgres-password}@safeline-pg/safeline-ce?sslmode=disable": net/url: invalid userinfo)
panic: init db failed: cannot parsepostgres://safeline-ce:xxxxxx@safeline-pg/safeline-ce?sslmode=disable: failed to parse as URL (parse "postgres://safeline-ce:{postgres-password}@safeline-pg/safeline-ce?sslmode=disable": net/url: invalid userinfo)
Monster
Updated a year ago
0
This problem may be that you included some special characters when configuring the db password, affecting the integrity of the configuration file.
mvdk27
Updated a year ago
0
The manual deploy procedure (https://docs.waf.chaitin.com/en/GetStarted/Deploy) mention to adapt .env file with POSTGRES_PASSWORD={postgres-password}. I kept this, since for my production install the password changed automatically. Or I missed something...
ULemosewa
Updated a year ago
0
you should change {postgres-password} to new password, like abcdefg, {} is special characters