Description

Error loading module websocket.so

Since the last update of the websocket.so module gives an error when starting Kamailio

Troubleshooting

Reproduction

# service kamailio restart
Job for kamailio.service failed. See 'systemctl status kamailio.service' and 'journalctl -xn' for details.

# systemctl status kamailio.service
● kamailio.service - LSB: Start the Kamailio SIP proxy server
   Loaded: loaded (/etc/init.d/kamailio)
   Active: failed (Result: exit-code) since Thu 2018-12-20 11:51:30 CET; 5s ago
  Process: 24396 ExecStop=/etc/init.d/kamailio stop (code=exited, status=0/SUCCESS)
  Process: 24442 ExecStart=/etc/init.d/kamailio start (code=exited, status=1/FAILURE)

Dec 20 11:51:30 debian kamailio[24442]: Not starting Kamailio SIP Server: invalid configuration file! ... failed!
Dec 20 11:51:30 debian kamailio[24442]: failed!
Dec 20 11:51:30 debian kamailio[24442]: 0(24451) INFO: tls [tls_init.c:503]: init_tls_compression(): disabling compression... 0(24451) ERROR: <core> [core/sr_module.c:498]: load_module():...l: ws_rm_delay
Dec 20 11:51:30 debian kamailio[24442]: failed!
Dec 20 11:51:30 debian systemd[1]: kamailio.service: control process exited, code=exited status=1
Dec 20 11:51:30 debian systemd[1]: Failed to start LSB: Start the Kamailio SIP proxy server.
Dec 20 11:51:30 debian systemd[1]: Unit kamailio.service entered failed state.
Hint: Some lines were ellipsized, use -l to show in full.

# journalctl -xn
-- Logs begin at Wed 2018-12-12 02:36:41 CET, end at Thu 2018-12-20 11:51:35 CET. --
Dec 20 11:51:23 debian kernel: iptables denied: IN=eth0 OUT= MAC=00:50:56:a4:88:be:00:1c:73:8e:f6:8f:08:00 SRC=94.102.56.235 DST=5.57.231.245 LEN=40 TOS=0x00 PREC=0x00 TTL=252 ID=55056 PROTO=TCP SPT=58501
Dec 20 11:51:30 debian systemd[1]: Starting LSB: Start the Kamailio SIP proxy server...
-- Subject: Unit kamailio.service has begun with start-up
-- Defined-By: systemd
-- Support: http://lists.freedesktop.org/mailman/listinfo/systemd-devel
-- 
-- Unit kamailio.service has begun starting up.
Dec 20 11:51:30 debian kamailio[24442]: Not starting Kamailio SIP Server: invalid configuration file! ... failed!
Dec 20 11:51:30 debian kamailio[24442]: failed!
Dec 20 11:51:30 debian kamailio[24442]: 0(24451) INFO: tls [tls_init.c:503]: init_tls_compression(): disabling compression... 0(24451) ERROR: <core> [core/sr_module.c:498]: load_module(): could not open m
Dec 20 11:51:30 debian kamailio[24442]: failed!
Dec 20 11:51:30 debian systemd[1]: kamailio.service: control process exited, code=exited status=1
Dec 20 11:51:30 debian systemd[1]: Failed to start LSB: Start the Kamailio SIP proxy server.
-- Subject: Unit kamailio.service has failed
-- Defined-By: systemd
-- Support: http://lists.freedesktop.org/mailman/listinfo/systemd-devel
-- 
-- Unit kamailio.service has failed.
-- 
-- The result is failed.
Dec 20 11:51:30 debian systemd[1]: Unit kamailio.service entered failed state.
Dec 20 11:51:35 debian kernel: iptables denied: IN=eth0 OUT= MAC=00:50:56:a4:88:be:00:1c:73:8f:13:f3:08:00 SRC=89.248.168.107 DST=5.57.231.245 LEN=40 TOS=0x00 PREC=0x00 TTL=252 ID=28132 PROTO=TCP SPT=5834
r

Debugging Data

(paste your debugging data here)

Log Messages

(paste your log messages here)

SIP Traffic

(paste your sip traffic here)

Possible Solutions

Additional Information

• Kamailio Version - output of kamailio -v

version: kamailio 5.3.0-dev1 (i386/linux) baa542
flags: STATS: Off, USE_TCP, USE_TLS, USE_SCTP, TLS_HOOKS, USE_RAW_SOCKS, DISABLE_NAGLE, USE_MCAST, DNS_IP_HACK, SHM_MEM, SHM_MMAP, PKG_MALLOC, Q_MALLOC, F_MALLOC, TLSF_MALLOC, DBG_SR_MEMORY, USE_FUTEX, FAST_LOCK-ADAPTIVE_WAIT, USE_DNS_CACHE, USE_DNS_FAILOVER, USE_NAPTR, USE_DST_BLACKLIST, HAVE_RESOLV_RES
ADAPTIVE_WAIT_LOOPS=1024, MAX_RECV_BUFFER_SIZE 262144 MAX_URI_SIZE 1024, BUF_SIZE 65535, DEFAULT PKG_SIZE 8MB
poll method support: poll, epoll_lt, epoll_et, sigio_rt, select.
id: baa542 
compiled on 11:42:31 Dec 20 2018 with gcc 4.9.2

• Operating System:

Linux debian 3.16.0-4-686-pae #1 SMP Debian 3.16.43-2+deb8u2 (2017-06-26) i686 GNU/Linux

—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub, or mute the thread.