edson
March 28, 2019, 8:49pm
1
Can’t start SEMS on dedicated server, management server starts fine, setting it up like the example.
/etc/yeti/management.cfg
Versions
** Management **
root@yetiweb:/var/log/yeti# netstat -lpn | grep yeti
** dedicated SEMS node **sems -E -D3
[2003/2003] [core/AmPlugIn.cpp:242] DEBUG: Initializing 9 plugins...
[2003/2003] [core/AmPlugIn.cpp:855] DEBUG: DI Interface 'sctp_bus' registered.
[2003/2003] [apps/sctp_bus/config.cpp:43] DEBUG: configuration file: /etc/sems/etc/sctp_bus.conf could not be read: No such file or directory
[2003/2003] [apps/sctp_bus/SctpServerConnection.cpp:28] DEBUG: bind sctp socket to: 127.0.0.1:10101
[2003/2003] [apps/sctp_bus/SctpBus.cpp:131] DEBUG: SctpBus configured
[2003/2003] [apps/sctp_bus/SctpBus.cpp:158] DEBUG: SctpBus initialized
[2003/2033] [core/AmThread.cpp:85] INFO: Thread 139799015249664 is starting.
[2003/2032] [core/AmThread.cpp:85] INFO: Thread 139799016302336 is starting.
[2003/2032] [yeti:yeti.cpp:249] DEBUG: start yeti-worker
[2003/2031] [core/AmThread.cpp:85] INFO: Thread 139799017355008 is starting.
[2003/2031] [apps/sctp_bus/SctpClientConnection.cpp:35] DEBUG: connect to 190.96.78.134:4444
[2003/2030] [core/AmThread.cpp:85] INFO: Thread 139799576381184 is starting.
[2003/2031] [apps/sctp_bus/SctpClientConnection.cpp:92] ERROR: 190.96.78.134:4444 (43,9) connection error: Connection refused
[2003/2031] [apps/sctp_bus/SctpConnection.cpp:81] DEBUG: close connection with id 0, socket: 43
[2003/2031] [apps/sctp_bus/SctpBus.cpp:457] DEBUG: remove fd 43 from the client connections sockets map
[2003/2003] [yeti:yeti.cpp:132] ERROR: timeout waiting yeti config via SCTP
[2003/2003] [yeti:SBC.cpp:148] ERROR: yeti configuration error
[2003/2003] [core/AmThread.cpp:142] DEBUG: Thread yeti-worker 139799016302336 (139799016302336)calling on_stop, give it a chance to clean up.
[2003/2003] [yeti:yeti.cpp:262] DEBUG: Yeti::on_stop
[2003/2003] [yeti:SqlRouter.cpp:80] DEBUG: SqlRouter::stop()
[2003/2032] [yeti:yeti.cpp:257] INFO: yeti-worker finished
[2003/2032] [core/AmThread.cpp:92] INFO: Thread yeti-worker 139799016302336 is ending.
[2003/2003] [core/AmThread.cpp:151] DEBUG: pthread_detach failed with code ESRCH: thread could not be found.
[2003/2003] [core/AmThread.cpp:159] DEBUG: Thread yeti-worker 139799016302336 (139799016302336) finished detach.
[2003/2003] [core/sems.cpp:699] INFO: Disposing plug-ins
[2003/2003] [core/AmPlugIn.cpp:117] DEBUG: decreasing reference to plug-in factory: session_timer
[2003/2003] [core/AmPlugIn.cpp:117] DEBUG: decreasing reference to plug-in factory: uac_auth
[2003/2003] [core/AmPlugIn.cpp:117] DEBUG: decreasing reference to plug-in factory: sctp_bus
[2003/2003] [core/AmPlugIn.cpp:117] DEBUG: decreasing reference to plug-in factory: yeti
[2003/2003] [yeti:SqlRouter.cpp:75] INFO: SqlRouter instance[0x559d98613f20] destroyed
[2003/2003] [core/AmPlugIn.cpp:117] DEBUG: decreasing reference to plug-in factory: core
[2003/2003] [core/AmPlugIn.cpp:117] DEBUG: decreasing reference to plug-in factory: di_log
[2003/2003] [core/AmPlugIn.cpp:117] DEBUG: decreasing reference to plug-in factory: jsonrpc
[2003/2003] [core/AmPlugIn.cpp:117] DEBUG: decreasing reference to plug-in factory: registrar_client
[2003/2003] [core/AmPlugIn.cpp:117] DEBUG: decreasing reference to plug-in factory: sctp_bus
[2003/2003] [apps/sctp_bus/SctpConnection.cpp:23] DEBUG: ~SctpConnection()
[2003/2003] [apps/sctp_bus/SctpConnection.cpp:23] DEBUG: ~SctpConnection()
[2003/2003] [apps/sctp_bus/SctpConnection.cpp:81] DEBUG: close connection with id 0, socket: 42
[2003/2003] [core/AmPlugIn.cpp:117] DEBUG: decreasing reference to plug-in factory: uac_auth
[2003/2003] [core/AmPlugIn.cpp:117] DEBUG: decreasing reference to plug-in factory: di_log
[2003/2003] [core/AmPlugIn.cpp:117] DEBUG: decreasing reference to plug-in factory: syslog
[2003/2003] [core/SipCtrlInterface.cpp:430] DEBUG: Stopping SIP control interface threads
[2003/2003] [core/SipCtrlInterface.cpp:461] DEBUG: dec_ref(0x559d985ced40)
[2003/2003] [core/SipCtrlInterface.cpp:472] DEBUG: dec_ref(0x559d985cf170)
[2003/2003] [core/sems.cpp:719] INFO: Exiting (failure)
@edson
sctp {
address = "127.0.0.1"
port = 4444
}
with
sctp {
address = "0.0.0.0"
port = 4444
}
and restart yeti-management process.
edson
March 29, 2019, 2:36pm
3
I did that at some point, but I reverted it, when I did it the error was:
[3256/3256] [core/AmPlugIn.cpp:242] DEBUG: Initializing 9 plugins…
[3256/3256] [yeti:cdr/TrustedHeaders.cpp:60] ERROR: can’t load trusted headers config
edson
March 29, 2019, 7:39pm
4
I think I’ve got it working, the template of the node defined in /etc/yeti/system.cfg should point to a reachable IP address to the node in the yeti and cdr sections. And obviously modify permissions in postgresql (/etc/postgresql/10/main/pg_hba.conf) so the node can connect to the databases.