SEMS node installation >>Launch traffic switch Fails with 404 unknow node


#1

Am new in this, trying to get things work here.

I am stuck and my traffic switch would not start.

  1. On WEB interface installation >> Invoice PDF generation i did not set up
  2. On WEB interface installation >> DAP Authentication I did not set up. I will not use it unless its mandatory. Please confirm this.

i created node Id 8
Signalling ip is my server ip
port : 5060
Rcp endpoint: 127.0.0.1:7080

When launching my switch i get this error

root@Yeti-softswitch:~# service sems start
Job for sems.service failed because the control process exited with error code.
See “systemctl status sems.service” and “journalctl -xe” for details.

if i check log this is what i get

*oot@Yeti-softswitch:~# journalctl -xe**
Feb 09 23:10:39 Yeti-softswitch sems[896]: Configuration:**
Feb 09 23:10:39 Yeti-softswitch sems[896]:        configuration file:  /etc/sems/sems.conf**
Feb 09 23:10:39 Yeti-softswitch sems[896]:        plug-in path:        /usr/lib/sems/plug-in/**
Feb 09 23:10:39 Yeti-softswitch sems[896]:        daemon mode:         yes**
Feb 09 23:10:39 Yeti-softswitch sems[896]:        daemon UID:          root**
Feb 09 23:10:39 Yeti-softswitch sems[896]:        daemon GID:          root**
Feb 09 23:10:39 Yeti-softswitch sems[896]: Configuration:**
Feb 09 23:10:39 Yeti-softswitch sems[896]:        configuration file:  /etc/sems/sems.conf**
Feb 09 23:10:39 Yeti-softswitch sems[896]:        plug-in path:        /usr/lib/sems/plug-in/**
Feb 09 23:10:39 Yeti-softswitch sems[896]:        daemon mode:         yes**
Feb 09 23:10:39 Yeti-softswitch sems[896]:        daemon UID:          root**
Feb 09 23:10:39 Yeti-softswitch sems[896]:        daemon GID:          root**
Feb 09 23:10:39 Yeti-softswitch yeti-management[740]: [741] info: server/src/SctpServer.cpp:247: associated with 127.0.0.1:42366/2 (7)**
Feb 09 23:10:39 Yeti-softswitch yeti-management[740]: [741] info: server/src/mgmt_server.cpp:211: process request for 'signalling' node 8**
Feb 09 23:10:39 Yeti-softswitch yeti-management[740]: [741] error: server/src/SctpServer.cpp:468: internal_exception: 404 unknown node**
Feb 09 23:10:39 Yeti-softswitch sems[896]: Configuration:**
Feb 09 23:10:39 Yeti-softswitch sems[896]:        configuration file:  /etc/sems/sems.conf**
Feb 09 23:10:39 Yeti-softswitch sems[896]:        plug-in path:        /usr/lib/sems/plug-in/**
Feb 09 23:10:39 Yeti-softswitch sems[896]:        daemon mode:         yes**
Feb 09 23:10:39 Yeti-softswitch sems[896]:        daemon UID:          root**
Feb 09 23:10:39 Yeti-softswitch sems[896]:        daemon GID:          root**
Feb 09 23:10:39 Yeti-softswitch systemd[1]: sems.service: Control process exited, code=exited status=1**
Feb 09 23:10:39 Yeti-softswitch systemd[1]: Failed to start SEMS for YETI project.**
-- Subject: Unit sems.service has failed**
-- Defined-By: systemd**
-- Support: https://www.debian.org/support**
--**
-- Unit sems.service has failed.**
--**
-- The result is failed.**
Feb 09 23:10:39 Yeti-softswitch systemd[1]: sems.service: Unit entered failed state.**
Feb 09 23:10:39 Yeti-softswitch systemd[1]: sems.service: Failed with result 'exit-code'.**

When i run in debug mode sems -E -D3 start**
this is what i get (NB i have truncated the output to highlight the error alone!)**

[9750/9778] [apps/sctp_bus/SctpClientConnection.cpp:35] DEBUG: connect to 127.0.0.1:4444** 
 [9750/9778] [apps/sctp_bus/SctpClientConnection.cpp:103] INFO: connected to 127.0.0.1:4444/-1 (43)**
 [9750/9778] [apps/sctp_bus/SctpClientConnection.cpp:180] INFO: SCTP_ASSOC_CHANGE: 19. remote: 127.0.0.1:4444**
 [9750/9778] [apps/sctp_bus/SctpBus.cpp:321] DEBUG: process sctp send raw event request yeti -> 0:mgmt**
 [9750/9778] [apps/sctp_bus/SctpClientConnection.cpp:268] DEBUG: SEND sctp_bus event** request 8:yeti/19 -> 0:mgmt seq: 1
 [9750/9779] [yeti:yeti.cpp:329] ERROR: cfg error from server: 404 unknown node
 [9750/9750] [yeti:SBC.cpp:148] ERROR: yeti configuration error
 [9750/9750] [core/AmThread.cpp:142] DEBUG: Thread yeti-worker 139865285777152 (139865285777152)calling on_stop, give it a chance to clean up.
 [9750/9750] [yeti:yeti.cpp:262] DEBUG: Yeti::on_stop

#2

see https://yeti-switch.org/docs/en/installation/management.html#etc-yeti-system-cfg

/etc/yeti/system.cfg should contain configuration for node 18, so you should replace in your config

...
  node 8 { }
}

with:

...
  node 18 { }
}

you should restart yeti-management to apply configuration changes


#3

Done the node change to 18 in /etc/yeti/system.cfg but still when i run “service sems start” it tells me unknown node 8 and would not start service


#4

Did you restart yeti-management service?


#5

Yes i did and did not get any errors on restarting the yeti-management` service but on next step on launching the switch that is where i got 404 unknown node 8


#6

My mistake. looks like your node id is 8, so you should define node 8 in system.cfg


#7

Am still stuck even when i edit it to node 8. Do you mind have a look at my installation?


#8

Could you attach your system.cfg. Looks like your configuration is not valid. Have you copied it from https://yeti-switch.org/docs/en/installation/management.html ?


#9

@dmitry.s we managed resolve the issue, just a few lines in the config. /etc/sems/sems.conf , /etc/yeti/management.cfg, /etc/yeti/system.cfg. Thanks to @amitiyer he identified the problem and did a few abra ka dabra and pap the switch launched. This has been resolved