Error with SEMS

Yeti installation and upgrade
1

Hello Everyone,

I’m having following error when trying to start SEMS service with “sems -E -D3 start”.

[3940/3940] [yeti:cdr/TrustedHeaders.cpp:47] ERROR: pqxx_exception: FATAL: password authentication failed for user "yeti"
FATAL: password authentication failed for user "yeti"

[3940/3940] [yeti:cdr/TrustedHeaders.cpp:60] ERROR: can’t load trusted headers config

I have checked the passwords of both “yeti” and “cdr” and it works.

** /opt/yeti-web/config/database.yml**

production:
adapter: postgresql
encoding: unicode
database: yeti
pool: 5
username: yeti
password: Abc1234#
host: 127.0.0.1
schema_search_path: ‘gui, public, switch, billing, class4, runtime_stats, sys, logs, data_import’
port: 5432
min_messages: notice

secondbase:
production:
adapter: postgresql
encoding: unicode
database: cdr
pool: 5
username: yeti
password: Abc1234#
host: 127.0.0.1
schema_search_path: ‘cdr, reports, billing, public’
port: 5432
min_messages: notice

/opt/yeti-web/config/database.yml

production:
adapter: postgresql
encoding: unicode
database: yeti
pool: 5
username: yeti
password: Abc1234#
host: 127.0.0.1
schema_search_path: ‘gui, public, switch, billing, class4, runtime_stats, sys, logs, data_import’
port: 5432
min_messages: notice

secondbase:
production:
adapter: postgresql
encoding: unicode
database: cdr
pool: 5
username: yeti
password: Abc1234#
host: 127.0.0.1
schema_search_path: ‘cdr, reports, billing, public’
port: 5432
min_messages: notice

Nodes

nodes

OS - Debian GNU/Linux 9 (stretch)

Thanks in advance.

2

Have you tried to use config files from documentation, not default configs?

3

Yes Dimitri. I have followed documentation very carefully. I’m wondering which configuration file this piece of code is referring to.

[3940/3940] [yeti:cdr/TrustedHeaders.cpp:47] ERROR: pqxx_exception: FATAL: password authentication failed for user "yeti"
FATAL: password authentication failed for user "yeti"

4

Quite strange, because your database.yml differs from provided in documentation. I think exactly same situation with other configs.

Also error FATAL: password authentication failed for user "yeti" is pretty clear - wrong password specified in configuration

5

Thanks a lot Dimitri for your quick and prompt response. I highly appreciate it.
Will check the configurations again and update the thread.