Can't start SEMS

Yeti installation and upgrade
1

I have followed the documentation and installed yeti 1.13 on debian 12, everything went fine except starting sems, on systemctl status sems i get:

sems[1332]: [#ffffffffd60fa6c0] [disconnectCallback, redis:RedisConnection.cpp:52] INFO: redis subscription_read[0x560f85b5aad0] 127.0.0.1:6379 disconnected
sems[1332]: [#ffffffffd60fa6c0] [disconnectCallback, redis:RedisConnection.cpp:52] INFO: redis registrar_write[0x7fc2f00014d0] 127.0.0.1:6379 disconnected
sems[1332]: [#ffffffffd64fe6c0] [onSock, postgresql:PoolWorker.cpp:270] ERROR: epoll error. reset connection 0x7fc2ec002f50
sems[1332]: [#ffffffffd64fe6c0] [onSock, postgresql:PoolWorker.cpp:270] ERROR: epoll error. reset connection 0x7fc2ec00f420
sems[1332]: [#ffffffffd64fe6c0] [onSock, postgresql:PoolWorker.cpp:270] ERROR: epoll error. reset connection 0x7fc2ec018c40
sems[1332]: [#ffffffffd64fe6c0] [onSock, postgresql:PoolWorker.cpp:270] ERROR: epoll error. reset connection 0x7fc2ec022020

If I do systemctl restart sems, i get

sems[2537]: [#1c3ff6c0] [onConnectionFailed, postgresql:PoolWorker.cpp:231] ERROR: pg connection routing:0x7f5b34002f50/127.0.0.1:5432/yeti failed: FATAL:  password authentication failed for user "yeti"
                                    connection to server at "127.0.0.1", port 5432 failed:
sems[2537]: [#1c3ff6c0] [onSock, postgresql:PoolWorker.cpp:270] ERROR: epoll error. reset connection 0x7f5b34022020
sems[2537]: [#1c3ff6c0] [onSock, postgresql:PoolWorker.cpp:270] ERROR: epoll error. reset connection 0x7f5b34022020
sems[2537]: [#1c3ff6c0] [onConnectionFailed, postgresql:PoolWorker.cpp:231] ERROR: pg connection routing:0x7f5b34022020/127.0.0.1:5432/yeti failed: FATAL:  password authentication failed for user "yeti"
                                    connection to server at "127.0.0.1", port 5432 failed:
sems[2537]: [#1c3ff6c0] [onSock, postgresql:PoolWorker.cpp:270] ERROR: epoll error. reset connection 0x7f5b3400f420
sems[2537]: [#1c3ff6c0] [onSock, postgresql:PoolWorker.cpp:270] ERROR: epoll error. reset connection 0x7f5b3400f420
sems[2537]: [#1c3ff6c0] [onConnectionFailed, postgresql:PoolWorker.cpp:231] ERROR: pg connection routing:0x7f5b3400f420/127.0.0.1:5432/yeti failed: FATAL:  password authentication failed for user "yeti"
                                    connection to server at "127.0.0.1", port 5432 failed:
sems[2537]: [#1c3ff6c0] [onSock, postgresql:PoolWorker.cpp:270] ERROR: epoll error. reset connection 0x7f5b34018c40
sems[2537]: [#1c3ff6c0] [onSock, postgresql:PoolWorker.cpp:270] ERROR: epoll error. reset connection 0x7f5b34018c40
sems[2537]: [#1c3ff6c0] [onConnectionFailed, postgresql:PoolWorker.cpp:231] ERROR: pg connection routing:0x7f5b34018c40/127.0.0.1:5432/yeti failed: FATAL:  password authentication failed for user "yeti"
                                    connection to server at "127.0.0.1", port 5432 failed:

It says clearly that the postgress password for yeti@yeti is wrong but i tested the password that i entered in /opt/yeti-web/config/database.yml and it’s working, is there anywhere else i need to change the password?

2

incorrect password specified in sems.conf

3

Password was correct, it had a issue with one or all of the following characters #@*&!, once removed I don’t get the errors

4

I have 2 more questions in regards to setup:
1: When doing journalctl -u sems i get

Starting sems 1.162.0
sems[1780]:    configuration file:  /etc/sems/sems.conf
sems[1780]:    plug-in path:        /usr/lib/sems/plug-in
sems[1780]: [#481fb6c0] [connectCallback, redis:RedisConnection.cpp:36] INFO: redis registrar_read[0x562a841d6a70] 127.0.0.1:6379 connected
sems[1780]: [#481fb6c0] [connectCallback, redis:RedisConnection.cpp:36] INFO: redis subscription_read[0x562a841d7b10] 127.0.0.1:6379 connected
sems[1780]: [#481fb6c0] [connectCallback, redis:RedisConnection.cpp:36] INFO: redis registrar_write[0x7f5c680014d0] 127.0.0.1:6379 connected
sems[1780]: [#485ff6c0] [onConnect, postgresql:PoolWorker.cpp:183] INFO: connection routing:0x7f5c6000f420/127.0.0.1:5432/yeti success
sems[1780]: [#485ff6c0] [onConnect, postgresql:PoolWorker.cpp:183] INFO: connection routing:0x7f5c60018c40/127.0.0.1:5432/yeti success
sems[1780]: [#485ff6c0] [onConnect, postgresql:PoolWorker.cpp:183] INFO: connection routing:0x7f5c60002f50/127.0.0.1:5432/yeti success
sems[1780]: [#485ff6c0] [onConnect, postgresql:PoolWorker.cpp:183] INFO: connection routing:0x7f5c60022020/127.0.0.1:5432/yeti success
sems[1780]: [#485ff6c0] [onConnectionFailed, postgresql:PoolWorker.cpp:231] ERROR: pg connection cdr:0x7f5c600102d0/127.0.0.1:5433/cdr failed: Connection refused
                                            Is the server running on that host and accepting TCP/IP connections?
sems[1780]: [#485ff6c0] [onConnectionFailed, postgresql:PoolWorker.cpp:231] ERROR: pg connection cdr:0x7f5c600b5140/127.0.0.1:5433/cdr failed: Connection refused
                                            Is the server running on that host and accepting TCP/IP connections?
sems[1780]: [#485ff6c0] [onConnectionFailed, postgresql:PoolWorker.cpp:231] ERROR: pg connection auth_log:0x7f5c600f4bf0/127.0.0.1:5433/cdr failed: Connection refused
                                            Is the server running on that host and accepting TCP/IP connections?
sems[1780]: [#485ff6c0] [onConnectionFailed, postgresql:PoolWorker.cpp:231] ERROR: pg connection auth_log:0x7f5c600f30b0/127.0.0.1:5433/cdr failed: Connection refused
                                            Is the server running on that host and accepting TCP/IP connections?

Is that a misconfiguration on my end that something is trying to connect on 5433?

2: In documentation WEB interface installation — Yeti documentation, it says for /opt/yeti-web/config/database.yml

cdr:
    adapter: postgresql
    encoding: unicode
    database: cdr
    username: yeti
    password: somepassword
    host: 127.0.0.1
    port: 5432

Is username yeti a mistake and it has to be cdr and if it has be user yeti, is it also the yeti password that you need here or cdr password?

5

I think it trying to connect to port 5433 because it specified in sems.conf

Is username yeti a mistake and it has to be cdr and if it has be user yeti, is it also the yeti password that you need here or cdr password?

It looks like problem of documentation consistency.

6

Yes, thank you!

For some reason, in the setup documentation it says 5433 for cdr in sems.conf.

cdr {
            dir = /var/spool/sems/cdrs
            completed_dir = /var/spool/sems/cdrs/completed
            pool_size = 2
            auth_pool_size = 2
            schema = switch
            function = writecdr
            master {
                host = 127.0.0.1
                port = 5433
                name = cdr
                user = cdr
                pass = somepassword
            }
            failover_to_slave = false
            slave {
                host = 127.0.0.1
                port = 5433
                name = cdr
                user = cdr
                pass = somepassword
            }
            failover_requeue = true
            failover_to_file = false
            serialize_dynamic_fields = true
            batch_size = 1
            batch_timeout = 5000
            auth_batch_size = 1
            auth_batch_timeout = 20000
        }