Yeti Managment starting BUT WITH error's

Yeti installation and upgrade
1

root@vmi273096:/home/yeti-web# cat /var/log/yeti/yeti-management.log
Jun 11 22:01:25 vmi273096 yeti-management[14728]: [14728] dbg: server/src/yeti_mgmt_server.cpp:138: configure mgmt
Jun 11 22:01:25 vmi273096 yeti-management[14723]: Starting YETI MGMT server: yeti_managementconfig_error: unexpected token ‘(’
Jun 11 22:01:25 vmi273096 yeti-management[14728]: [14728] error: server/src/cfg_reader.cpp:25: unexpected token ‘(’
Jun 11 22:01:25 vmi273096 yeti-management[14728]: [14728] error: server/src/cfg_reader.cpp:45: configuration file ‘/etc/yeti/system.cfg’ parse error
Jun 11 22:01:25 vmi273096 yeti-management[14728]: [14728] error: server/src/yeti_mgmt_server.cpp:165: can’t load system config
Jun 11 22:01:25 vmi273096 yeti-management[14728]: [14728] info: server/src/yeti_mgmt_server.cpp:177: terminated
Jun 11 22:01:25 vmi273096 yeti-management[14723]: failed!
Jun 11 22:07:15 vmi273096 yeti-management[14988]: Stopping YETI MGMT server: yeti_management.
Jun 11 22:10:32 vmi273096 yeti-management[15224]: [15224] dbg: server/src/yeti_mgmt_server.cpp:138: configure mgmt
Jun 11 22:10:32 vmi273096 yeti-management[15219]: Starting YETI MGMT server: yeti_managementconfig_error: unexpected token ‘(’
Jun 11 22:10:32 vmi273096 yeti-management[15224]: [15224] error: server/src/cfg_reader.cpp:25: unexpected token ‘(’
Jun 11 22:10:32 vmi273096 yeti-management[15219]: failed!
Jun 11 22:10:32 vmi273096 yeti-management[15224]: [15224] error: server/src/cfg_reader.cpp:45: configuration file ‘/etc/yeti/system.cfg’ parse error
Jun 11 22:10:32 vmi273096 yeti-management[15224]: [15224] error: server/src/yeti_mgmt_server.cpp:165: can’t load system config
Jun 11 22:10:32 vmi273096 yeti-management[15224]: [15224] info: server/src/yeti_mgmt_server.cpp:177: terminated

Jun 11 22:10:32 yeti-management[15219]: Starting YETI MGMT server: yeti_managementconfig_error: unexpected token ’
(’
Jun 11 22:10:32 yeti-management[15219]: failed!

Starting YETI MGMT server: yeti_managementconfig_error: unexpected token ’
(’
Jun 11 22:01:25 yeti-management[14728]: [14728] error: server/src/cfg_reader.cpp:25: unexpected token ‘(’

Jun 11 22:01:25 yeti-management[14728]: [14728] error: server/src/cfg_reader.cpp:45: configuration file ‘/
etc/yeti/system.cfg’ parse error

2

looks like your /etc/yeti/system.cfg invalid

3

for system.cfg i copied the current example on the documentation for version 1.8. Find below my current config as is on the server

signalling {
globals {
yeti {
pop_id = 4
msg_logger_dir = /var/spool/sems/dump
log_dir = /var/spool/sems/logdump
routing {
schema = switch17
function = route_release
init = init
master_pool {
host = 127.0.0.1
port = 5432
name = yeti
user = yeti
pass = (fire~fire1)
size = 4
check_interval = 10
max_exceptions = 0
statement_timeout=3000
}
failover_to_slave = false
slave_pool {
host = 127.0.0.1
port = 5432
name = yeti
user = yeti
pass = (~fire~fire1~)
size = 4
check_interval = 10
max_exceptions = 0
statement_timeout=3000
}
cache {
enabled = false
check_interval = 60
buckets = 100000
}
}
cdr {
dir = /var/spool/sems/cdrs
completed_dir = /var/spool/sems/cdrs/completed
pool_size = 2
schema = switch
function = writecdr
master {
host = 127.0.0.1
port = 5432
name = cdr
user = cdr
pass = (~fire~fire1~)
}
failover_to_slave = false
slave {
host = 127.0.0.1
port = 5432
name = cdr
user = cdr
pass = (~fire~fire1~)
}
failover_requeue = true
failover_to_file = false
serialize_dynamic_fields = true
batch_size = 1
batch_timeout = 5000
}
resources {
reject_on_error = false
write {
host = 127.0.0.1
port = 6379
size = 2
timeout = 500
}
read {
host = 127.0.0.1
port = 6379
size = 2
timeout = 1000
}
}
registrations {
check_interval = 5000
}
rpc {
calls_show_limit = 10000
}
}
}
node 8 { }
}

4

try pass = “(fire~fire1)”

5

Worked like a charm. Thanks very much