sr-dev May 2022

sr-dev@lists.kamailio.org

12 participants
286 discussions

[kamailio/kamailio] lib: big integers should not be treated as negative ones (#2106)
by Ivan Murashko 08 Dec '23

08 Dec '23

0xffffffff00000000ULL mask does not take into consideration signed 32 bit integers and as result 2147483648 will be stored as -2147483648. Another mask should be used to correct the issue: 0xffffffff80000000ULL. It processes correctly the case of integers that are greater than 2147483647. There are several gdb tests below: (gdb) p ((unsigned long long)2147483648 & 0xffffffff80000000ULL) $1= 2147483648 (gdb) p ((unsigned long long)2147483647 & 0xffffffff80000000ULL) $2 = 0 (gdb) p ((unsigned long long)2147483646 & 0xffffffff80000000ULL) $3 = 0 (gdb) p ((unsigned long long)4147483646 & 0xffffffff80000000ULL) $4 = 2147483648   #### Pre-Submission Checklist    - [ ] Commit message has the format required by CONTRIBUTING guide - [ ] Commits are split per component (core, individual modules, libs, utils, ...) - [ ] Each component has a single commit (if not, squash them into one commit) - [ ] No commits to README files for modules (changes must be done to docbook files in `doc/` subfolder, the README file is autogenerated) #### Type Of Change - [ ] Small bug fix (non-breaking change which fixes an issue) - [ ] New feature (non-breaking change which adds new functionality) - [ ] Breaking change (fix or feature that would change existing functionality) #### Checklist:  - [ ] PR should be backported to stable branches - [ ] Tested changes locally - [ ] Related to issue #XXXX (replace XXXX with an open issue number) #### Description  You can view, comment on, or merge this pull request online at: https://github.com/kamailio/kamailio/pull/2106 -- Commit Summary -- * lib: big integers should not be treated as negative ones -- File Changes -- M src/lib/srdb1/db_ut.c (2) -- Patch Links -- https://github.com/kamailio/kamailio/pull/2106.patch https://github.com/kamailio/kamailio/pull/2106.diff -- You are receiving this because you are subscribed to this thread. Reply to this email directly or view it on GitHub: https://github.com/kamailio/kamailio/pull/2106

4 6

[kamailio/kamailio] sslv3 errors showing up with 'tls_method' set as 'TLSv1.2+' (Issue #3085)
by Vinicius K. Ruoso 07 Dec '23

07 Dec '23

### Description Some users are having issues connecting to kamailio websocket using TLS. The logs show SSLv3 errors. Cannot find why that error would show up if SSLv2/3 is not enabled. Double checked it via SSLLabs that only TLSv1.2 is allowed in the service. Any pointers would be appreciated. Also, let me know if more debug information is needed. ### Troubleshooting #### Debugging Data This is the TLS config: ``` modparam("tls", "tls_method", "TLSv1.2+") modparam("tls", "verify_certificate", 0) modparam("tls", "require_certificate", 0) modparam("tls", "low_mem_threshold1", 0) modparam("tls", "low_mem_threshold2", 0) modparam("tls", "private_key", "/etc/certs/tls.key") modparam("tls", "certificate", "/etc/certs/tls.crt") ``` This is the output from tls module in kamcmd: ``` kamcmd> tls.info { max_connections: 2048 opened_connections: 353 clear_text_write_queued_bytes: 0 } kamcmd> tls.options { force_run: 0 method: TLSv1.2+ verify_certificate: 0 verify_depth: 9 require_certificate: 0 private_key: /etc/certs/tls.key ca_list: <null string> certificate: /etc/certs/tls.crt cipher_list: <null string> session_cache: 0 session_id: kamailio-tls-5.x.y config: <null string> log: 3 debug: 3 connection_timeout: 600 disable_compression: 1 ssl_release_buffers: -1 ssl_freelist_max: -1 ssl_max_send_fragment: -1 ssl_read_ahead: 0 send_close_notify: 0 low_mem_threshold1: 0 low_mem_threshold2: 0 ct_wq_max: 10485760 con_ct_wq_max: 65536 ct_wq_blk_size: 4096 } ``` #### Log Messages I see this log messages related to SSLv3: ``` 15(36) ERROR: tls [tls_util.h:42]: tls_err_ret(): TLS accept:error:14094416:SSL routines:ssl3_read_bytes:sslv3 alert certificate unknown 15(36) ERROR: <core> [core/tcp_read.c:1512]: tcp_read_req(): ERROR: tcp_read_req: error reading - c: 0x7fafc8768190 r: 0x7fafc8768278 (-1) ``` ### Additional Information * **Kamailio Version** - output of `kamailio -v` ``` version: kamailio 5.3.9 (x86_64/linux) flags: USE_TCP, USE_TLS, USE_SCTP, TLS_HOOKS, USE_RAW_SOCKS, DISABLE_NAGLE, USE_MCAST, DNS_IP_HACK, 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, TLS_PTHREAD_MUTEX_SHARED 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: unknown compiled with gcc 6.3.0 ``` * **Operating System**: Debian 9.13. ``` Linux 4.19.112+ #1 SMP Wed Sep 23 07:53:39 PDT 2020 x86_64 GNU/Linux ``` -- Reply to this email directly or view it on GitHub: https://github.com/kamailio/kamailio/issues/3085 You are receiving this because you are subscribed to this thread. Message ID: <kamailio/kamailio/issues/3085(a)github.com>

3 5

[kamailio/kamailio] kamailio 5.5 (commit 54c9df) SIGSEGV on atomic_get (Issue #3107)
by MayamaTakeshi 23 Nov '23

23 Nov '23

### Description Crash occurred during load test. #### Reproduction This cannot be reproduced at will. It happened after about 45 days of load testing. #### Debugging Data ``` [root@lab002207-flip-server ~]$ gdb /usr/local/src/git/kamailio-5.5/src/kamailio /core GNU gdb (Debian 10.1-1.7) 10.1.90.20210103-git Copyright (C) 2021 Free Software Foundation, Inc. License GPLv3+: GNU GPL version 3 or later <http://gnu.org/licenses/gpl.html> This is free software: you are free to change and redistribute it. There is NO WARRANTY, to the extent permitted by law. Type "show copying" and "show warranty" for details. This GDB was configured as "x86_64-linux-gnu". Type "show configuration" for configuration details. For bug reporting instructions, please see: <https://www.gnu.org/software/gdb/bugs/>. Find the GDB manual and other documentation resources online at: <http://www.gnu.org/software/gdb/documentation/>. For help, type "help". Type "apropos word" to search for commands related to "word"... Reading symbols from /usr/local/src/git/kamailio-5.5/src/kamailio... warning: Can't open file /dev/zero (deleted) during file-backed mapping note processing [New LWP 189001] [Thread debugging using libthread_db enabled] Using host libthread_db library "/lib/x86_64-linux-gnu/libthread_db.so.1". Core was generated by `/usr/local/src/git/kamailio-5.5/src/kamailio -m 1024 -f /usr/local/etc/kamailio'. Program terminated with signal SIGSEGV, Segmentation fault. #0 0x00007f909231e31e in atomic_get (v=0x7f96781153a0) at ../../core/mem/../atomic/atomic_common.h:66 66 return atomic_get_int(&(v->val)); (gdb) bt full #0 0x00007f909231e31e in atomic_get (v=0x7f96781153a0) at ../../core/mem/../atomic/atomic_common.h:66 No locals. #1 0x00007f909232b1a4 in dlg_ref_helper (dlg=0x7f905640bbe0, cnt=1, fname=0x7f9092368a61 "dlg_handlers.c", fline=1057) at dlg_hash.c:1074 mypid = 189001 d_entry = 0x7f9678115388 __func__ = "dlg_ref_helper" #2 0x00007f9092311fbf in dlg_set_tm_waitack (t=0x7f9053a98af8, dlg=0x7f905640bbe0) at dlg_handlers.c:1057 iuid = 0x7f905739a3c8 __func__ = "dlg_set_tm_waitack" #3 0x00007f909230c412 in dlg_onreply (t=0x7f9053a98af8, type=1048576, param=0x7ffeb3d73300) at dlg_handlers.c:578 dlg = 0x7f905640bbe0 iuid = 0x7f9055715ea0 new_state = 5 old_state = 2 unref = 1 event = 4 tag = {s = 0x80d000001ff <error: Cannot access memory at address 0x80d000001ff>, len = -1832753723} req = 0x7f90555eff70 rpl = 0xffffffffffffffff __func__ = "dlg_onreply" #4 0x00007f9092b5d399 in run_trans_callbacks_internal (cb_lst=0x7f9053a98b70, type=1048576, trans=0x7f9053a98af8, params=0x7ffeb3d73300) at t_hooks.c:258 cbp = 0x7f905362d490 backup_from = 0x555a7cfc3e90 <def_list+16> backup_to = 0x555a7cfc3e98 <def_list+24> backup_dom_from = 0x555a7cfc3ea0 <def_list+32> backup_dom_to = 0x555a7cfc3ea8 <def_list+40> backup_uri_from = 0x555a7cfc3e80 <def_list> backup_uri_to = 0x555a7cfc3e88 <def_list+8> backup_xavps = 0x555a7cfc3fd8 <_xavp_list_head> backup_xavus = 0x555a7cfc3fe0 <_xavu_list_head> backup_xavis = 0x555a7cfc3fe8 <_xavi_list_head> __func__ = "run_trans_callbacks_internal" #5 0x00007f9092b5d5b2 in run_trans_callbacks_with_buf (type=1048576, rbuf=0x7f9053a98bc8, req=0x7f90555eff70, repl=0xffffffffffffffff, flags=0) at t_hooks.c:303 params = {req = 0x7f90555eff70, rpl = 0xffffffffffffffff, param = 0x7f905362d4a0, code = 408, flags = 0, branch = 0, t_rbuf = 0x7f9053a98bc8, dst = 0x7f9053a98c18, send_buf = { s = 0x7f9054157d60 "SIP/2.0 408 Request Timeout\r\nVia: SIP/2.0/UDP 10.255.255.208:5015;rport=5015;branch=z9hG4bK-2093375-4498-18;received=192.168.2.253\r\nFrom: \"the.username.for.the.user.546\" <sip:the.username.for.the.user"..., len = 449}} trans = 0x7f9053a98af8 #6 0x00007f9092bd422d in relay_reply (t=0x7f9053a98af8, p_msg=0xffffffffffffffff, branch=0, msg_status=408, cancel_data=0x7ffeb3d73520, do_put_on_wait=0) at t_reply.c:2094 relay = 0 save_clone = 0 buf = 0x7f9092f17b68 "SIP/2.0 408 Request Timeout\r\nVia: SIP/2.0/UDP 10.255.255.208:5015;rport=5015;branch=z9hG4bK-2093375-4498-18;received=192.168.2.253\r\nFrom: \"the.username.for.the.user.546\" <sip:the.username.for.the.user"... res_len = 449 relayed_code = 408 relayed_msg = 0xffffffffffffffff reply_bak = 0x7ffeb3d734c0 bm = {to_tag_val = { s = 0x7f9092f17c88 "67946a7773289cd2c8623ce9ed050d66-614e90ad\r\nCall-ID: 4498-2093375(a)10.255.255.208\r\nCSeq: 802 INVITE\r\nServer: kamailio (5.5.4 (x86_64/linux))\r\nContent-Length: 0\r\n\r\n", len = 41}} totag_retr = 0 reply_status = RPS_COMPLETED uas_rb = 0x7f9053a98bc8 to_tag = 0x7f9092c3db30 <tm_tag> reason = {s = 0x555a7ce2b463 "Request Timeout", len = 15} --Type <RET> for more, q to quit, c to continue without paging--c onsend_params = {req = 0x28, rpl = 0x7f9052b1eac0, param = 0x157b82568, code = 1365092040, flags = 32656, branch = 0, t_rbuf = 0x7ffeb3d73450, dst = 0x0, send_buf = {s = 0x21d8 <error: Cannot access memory at address 0x21d8>, len = 1365092040}} ip = {af = 3017225408, len = 32766, u = {addrl = {140257839409728, 1}, addr32 = {1387391552, 32656, 1, 0}, addr16 = {59968, 21169, 32656, 0, 1, 0, 0, 0}, addr = "@\352\261R\220\177\000\000\001\000\000\000\000\000\000"}} __func__ = "relay_reply" #7 0x00007f9092b61ec0 in fake_reply (t=0x7f9053a98af8, branch=0, code=408) at timer.c:295 cancel_data = {cancel_bitmap = 0, reason = {cause = 0, u = {text = {s = 0x0, len = 1403620088}, e2e_cancel = 0x0, packed_hdrs = {s = 0x0, len = 1403620088}}}} do_cancel_branch = 1 reply_status = 189001 #8 0x00007f9092b6232e in final_response_handler (r_buf=0x7f9053a98d98, t=0x7f9053a98af8) at timer.c:462 silent = 0 branch_ret = 0 prev_branch = 0 now = 0 #9 0x00007f9092b623f2 in retr_buf_handler (ticks=2176292369, tl=0x7f9053a98db8, p=0x1f40) at timer.c:518 rbuf = 0x7f9053a98d98 fr_remainder = 0 retr_remainder = 32656 retr_interval = 1365093472 new_retr_interval_ms = 4294967296 crt_retr_interval_ms = 0 t = 0x7f9053a98af8 __func__ = "retr_buf_handler" #10 0x0000555a7ccb5a9f in timer_list_expire (t=2176292369, h=0x7f905161ed40, slow_l=0x7f905161fab8, slow_mark=5300) at core/timer.c:857 tl = 0x7f9053a98db8 ret = 0 #11 0x0000555a7ccb5fa9 in timer_handler () at core/timer.c:922 saved_ticks = 2176292369 run_slow_timer = 0 i = 180 __func__ = "timer_handler" #12 0x0000555a7ccb64ac in timer_main () at core/timer.c:961 No locals. #13 0x0000555a7c9fe6cf in main_loop () at main.c:1839 i = 12 pid = 0 si = 0x0 si_desc = "udp receiver child=11 sock=192.168.2.207:9060\000\270\000\200\070׳\376\177\000\000\000\000\000\000\000\000\000\000\220\070׳\376\177\000\000);]\221\220\177\000\000\b$Β\220\177\000\000]\201]\221\220\177", '\000' <repeats 14 times>, "\001\000\000\000\220\070׳\376\177\000\000\342\f\320|ZU\000" nrprocs = 12 woneinit = 1 __func__ = "main_loop" #14 0x0000555a7ca092ab in main (argc=8, argv=0x7ffeb3d73e78) at main.c:3053 cfg_stream = 0x555a7ea552d0 c = -1 r = 0 tmp = 0x7ffeb3d74d0a "" tmp_len = 0 port = 0 proto = 0 ahost = 0x0 aport = 0 options = 0x555a7ce150b8 ":f:cm:M:dVIhEeb:l:L:n:vKrRDTN:W:w:t:u:g:P:G:SQ:O:a:A:x:X:Y:" ret = -1 seed = 487513963 rfd = 4 debug_save = 0 debug_flag = 0 dont_fork_cnt = 0 n_lst = 0x0 p = 0xc2 <error: Cannot access memory at address 0xc2> st = {st_dev = 22, st_ino = 2337, st_nlink = 2, st_mode = 16877, st_uid = 0, st_gid = 0, __pad0 = 0, st_rdev = 0, st_size = 60, st_blksize = 4096, st_blocks = 0, st_atim = {tv_sec = 1646805011, tv_nsec = 284331240}, st_mtim = {tv_sec = 1647223778, tv_nsec = 289750340}, st_ctim = {tv_sec = 1647223782, tv_nsec = 957818051}, __glibc_reserved = {0, 0, 0}} tbuf = "\020\377y\223\220\177\000\000\300\nG\223\001\000\000\000\377\377\377\377", '\000' <repeats 12 times>, "(\346z\223\220\177\000\000\350\231}\223\220\177\000\000\377\377\377\377", '\000' <repeats 12 times>, "@\305E\223\220\177\000\000\020\004z\223\220\177\000\000\350\244}\223\220\177\000\000\204\351z\223\220\177\000\000\060\344z\223\220\177\000\000Xbc\223\220\177\000\000h\231}\223\220\177\000\000`\220}\223\220\177\000\000\300>׳\376\177\000\000\200\241}\223\220\177\000\000\000\000\000\000\000\000\000\000#\326{\223\220\177\000\000\001", '\000' <repeats 23 times>, "(\346z\223\220\177\000\000\320<׳\376\177\000\000\003E"... option_index = 12 long_options = {{name = 0x555a7ce17516 "help", has_arg = 0, flag = 0x0, val = 104}, {name = 0x555a7ce12514 "version", has_arg = 0, flag = 0x0, val = 118}, {name = 0x555a7ce1751b "alias", has_arg = 1, flag = 0x0, val = 1024}, {name = 0x555a7ce17521 "subst", has_arg = 1, flag = 0x0, val = 1025}, {name = 0x555a7ce17527 "substdef", has_arg = 1, flag = 0x0, val = 1026}, {name = 0x555a7ce17530 "substdefs", has_arg = 1, flag = 0x0, val = 1027}, {name = 0x555a7ce1753a "server-id", has_arg = 1, flag = 0x0, val = 1028}, {name = 0x555a7ce17544 "loadmodule", has_arg = 1, flag = 0x0, val = 1029}, {name = 0x555a7ce1754f "modparam", has_arg = 1, flag = 0x0, val = 1030}, {name = 0x555a7ce17558 "log-engine", has_arg = 1, flag = 0x0, val = 1031}, {name = 0x555a7ce17563 "debug", has_arg = 1, flag = 0x0, val = 1032}, {name = 0x555a7ce17569 "cfg-print", has_arg = 0, flag = 0x0, val = 1033}, {name = 0x555a7ce17573 "atexit", has_arg = 1, flag = 0x0, val = 1034}, {name = 0x0, has_arg = 0, flag = 0x0, val = 0}} __func__ = "main" (gdb) info locals No locals. (gdb) list 61 62 #define atomic_set(at_var, value) (atomic_set_int(&((at_var)->val), (value))) 63 64 inline static int atomic_get(atomic_t *v) 65 { 66 return atomic_get_int(&(v->val)); 67 } 68 69 /*@} */ 70 (gdb) ``` ### Additional Information * **Kamailio Version** - output of `kamailio -v` ``` version: kamailio 5.5.4 (x86_64/linux) 54c9df flags: USE_TCP, USE_TLS, USE_SCTP, TLS_HOOKS, USE_RAW_SOCKS, DISABLE_NAGLE, USE_MCAST, DNS_IP_HACK, 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_BLOCKLIST, HAVE_RESOLV_RES, TLS_PTHREAD_MUTEX_SHARED 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: 54c9df compiled on 10:27:27 Mar 14 2022 with gcc 10.2.1 ``` * **Operating System**: ``` [root@lab002207-flip-server ~]$ lsb_release -a uNo LSB modules are available. Distributor ID: Debian Description: Debian GNU/Linux 11 (bullseye) Release: 11 Codename: bullseye [root@lab002207-flip-server ~]$ uname -a Linux lab002207-flip-server 5.10.0-11-amd64 #1 SMP Debian 5.10.92-2 (2022-02-28) x86_64 GNU/Linux ``` -- Reply to this email directly or view it on GitHub: https://github.com/kamailio/kamailio/issues/3107 You are receiving this because you are subscribed to this thread. Message ID: <kamailio/kamailio/issues/3107(a)github.com>

2 2

[kamailio/kamailio] sdpops: signedness issue w/ sess-version in o= line (Issue #3099)
by Bastian Triller 23 Nov '23

23 Nov '23

3 4

[kamailio/kamailio] CDP module fails to properly send DPA upon DPR (Issue #3092)
by Atanas Bakalov 23 Nov '23

23 Nov '23

### Description It seems there is a problem with the sending of the DPA from the cdp module to the diameter peer. When we receive the DPR the `Snd_DPA()` and `I_Disc()` are executed from peerstatemachine.c (I_Open/I_Rcv_DPR branch). Since the socket is closed from `I_Disc()` the `select()` in the `receive_loop` exits with a failure and the send pipe (which holds the DPA) is never sent to the other side. ### Troubleshooting #### Reproduction ``` 1. Send DPR from diameter peer to Kamailio 2. DPA is never received on the other end ``` #### Log Messages ``` Apr 24, 2022 @ 20:43:58.854 +0200 pcscf 44(138) DEBUG: cdp [peerstatemachine.c:89]: sm_process(): sm_process(): Peer chordlet State I_Open Event I_Rcv_DPR Apr 24, 2022 @ 20:43:58.854 +0200 pcscf 44(138) DEBUG: <core> [core/mem/q_malloc.c:373]: qm_malloc(): qm_malloc(0x7f54a05dc000, 120) called from cdp: diameter_msg.c: AAANewMessage(192) Apr 24, 2022 @ 20:43:58.854 +0200 pcscf 44(138) DEBUG: <core> [core/mem/q_malloc.c:416]: qm_malloc(): qm_malloc(0x7f54a05dc000, 120) returns address 0x7f54a1005888 frag. 0x7f54a1005850 (size=120) on 1 -th hit Apr 24, 2022 @ 20:43:58.854 +0200 pcscf 44(138) DEBUG: <core> [core/mem/q_malloc.c:373]: qm_malloc(): qm_malloc(0x7f54a05dc000, 56) called from cdp: diameter_avp.c: AAACreateAVP(142) Apr 24, 2022 @ 20:43:58.854 +0200 pcscf 44(138) DEBUG: <core> [core/mem/q_malloc.c:416]: qm_malloc(): qm_malloc(0x7f54a05dc000, 56) returns address 0x7f54d53ae668 frag. 0x7f54d53ae630 (size=56) on 1 -th hit Apr 24, 2022 @ 20:43:58.854 +0200 pcscf 44(138) DEBUG: <core> [core/mem/q_malloc.c:373]: qm_malloc(): qm_malloc(0x7f54a05dc000, 41) called from cdp: diameter_avp.c: AAACreateAVP(157) Apr 24, 2022 @ 20:43:58.854 +0200 pcscf 44(138) DEBUG: <core> [core/mem/q_malloc.c:416]: qm_malloc(): qm_malloc(0x7f54a05dc000, 48) returns address 0x7f54d68446e8 frag. 0x7f54d68446b0 (size=48) on 1 -th hit Apr 24, 2022 @ 20:43:58.854 +0200 pcscf 44(138) DEBUG: <core> [core/mem/q_malloc.c:373]: qm_malloc(): qm_malloc(0x7f54a05dc000, 56) called from cdp: diameter_avp.c: AAACreateAVP(142) Apr 24, 2022 @ 20:43:58.854 +0200 pcscf 44(138) DEBUG: <core> [core/mem/q_malloc.c:416]: qm_malloc(): qm_malloc(0x7f54a05dc000, 56) returns address 0x7f54d2c2e888 frag. 0x7f54d2c2e850 (size=56) on 1 -th hit Apr 24, 2022 @ 20:43:58.854 +0200 pcscf 44(138) DEBUG: <core> [core/mem/q_malloc.c:373]: qm_malloc(): qm_malloc(0x7f54a05dc000, 29) called from cdp: diameter_avp.c: AAACreateAVP(157) Apr 24, 2022 @ 20:43:58.854 +0200 pcscf 44(138) DEBUG: <core> [core/mem/q_malloc.c:416]: qm_malloc(): qm_malloc(0x7f54a05dc000, 32) returns address 0x7f54d4eef830 frag. 0x7f54d4eef7f8 (size=40) on 1 -th hit Apr 24, 2022 @ 20:43:58.854 +0200 pcscf 44(138) DEBUG: cdp [diameter_msg.c:82]: AAABuildMsgBuffer(): AAABuildMsgBuffer(): len=112 Apr 24, 2022 @ 20:43:58.854 +0200 pcscf 44(138) DEBUG: <core> [core/mem/q_malloc.c:373]: qm_malloc(): qm_malloc(0x7f54a05dc000, 112) called from cdp: diameter_msg.c: AAABuildMsgBuffer(84) Apr 24, 2022 @ 20:43:58.854 +0200 pcscf 44(138) DEBUG: <core> [core/mem/q_malloc.c:416]: qm_malloc(): qm_malloc(0x7f54a05dc000, 112) returns address 0x7f54d1242b00 frag. 0x7f54d1242ac8 (size=112) on 1 -th hit Apr 24, 2022 @ 20:43:58.854 +0200 pcscf 44(138) DEBUG: cdp [receiver.c:1013]: peer_send_msg(): peer_send_msg(): Pipe push [0x7f54a1005888] Apr 24, 2022 @ 20:43:58.854 +0200 pcscf 44(138) DEBUG: cdp [diameter_msg.c:411]: AAAFreeMessage(): AAAFreeMessage: Freeing message (0x7f54d75aeb50) 282 Apr 24, 2022 @ 20:43:58.854 +0200 pcscf 44(138) DEBUG: <core> [core/mem/q_malloc.c:482]: qm_free(): qm_free(0x7f54a05dc000, 0x7f54d52aff78), called from cdp: diameter_avp.c: AAAFreeAVP(365) Apr 24, 2022 @ 20:43:58.854 +0200 pcscf 44(138) DEBUG: <core> [core/mem/q_malloc.c:525]: qm_free(): freeing frag. 0x7f54d52aff40 alloc'ed from cdp: diameter_avp.c: AAACreateAVP(142) Apr 24, 2022 @ 20:43:58.854 +0200 pcscf 44(138) DEBUG: <core> [core/mem/q_malloc.c:482]: qm_free(): qm_free(0x7f54a05dc000, 0x7f54c170eff0), called from cdp: diameter_avp.c: AAAFreeAVP(365) Apr 24, 2022 @ 20:43:58.854 +0200 pcscf 44(138) DEBUG: <core> [core/mem/q_malloc.c:525]: qm_free(): freeing frag. 0x7f54c170efb8 alloc'ed from cdp: diameter_avp.c: AAACreateAVP(142) Apr 24, 2022 @ 20:43:58.854 +0200 pcscf 44(138) DEBUG: <core> [core/mem/q_malloc.c:482]: qm_free(): qm_free(0x7f54a05dc000, 0x7f54d31942a0), called from cdp: diameter_avp.c: AAAFreeAVP(365) Apr 24, 2022 @ 20:43:58.854 +0200 pcscf 44(138) DEBUG: <core> [core/mem/q_malloc.c:525]: qm_free(): freeing frag. 0x7f54d3194268 alloc'ed from cdp: diameter_avp.c: AAACreateAVP(142) Apr 24, 2022 @ 20:43:58.854 +0200 pcscf 44(138) DEBUG: <core> [core/mem/q_malloc.c:482]: qm_free(): qm_free(0x7f54a05dc000, 0x7f54d70d3508), called from cdp: diameter_avp.c: AAAFreeAVP(365) Apr 24, 2022 @ 20:43:58.854 +0200 pcscf 44(138) DEBUG: <core> [core/mem/q_malloc.c:525]: qm_free(): freeing frag. 0x7f54d70d34d0 alloc'ed from cdp: diameter_avp.c: AAACreateAVP(142) Apr 24, 2022 @ 20:43:58.854 +0200 pcscf 44(138) DEBUG: <core> [core/mem/q_malloc.c:482]: qm_free(): qm_free(0x7f54a05dc000, 0x7f54d5febb38), called from cdp: diameter_avp.c: AAAFreeAVP(365) Apr 24, 2022 @ 20:43:58.854 +0200 pcscf 44(138) DEBUG: <core> [core/mem/q_malloc.c:525]: qm_free(): freeing frag. 0x7f54d5febb00 alloc'ed from cdp: diameter_avp.c: AAACreateAVP(142) Apr 24, 2022 @ 20:43:58.854 +0200 pcscf 44(138) DEBUG: <core> [core/mem/q_malloc.c:482]: qm_free(): qm_free(0x7f54a05dc000, 0x7f54d1e24700), called from cdp: diameter_msg.c: AAAFreeMessage(421) Apr 24, 2022 @ 20:43:58.854 +0200 pcscf 44(138) DEBUG: <core> [core/mem/q_malloc.c:525]: qm_free(): freeing frag. 0x7f54d1e246c8 alloc'ed from cdp: receiver.c: do_receive(580) Apr 24, 2022 @ 20:43:58.854 +0200 pcscf 44(138) DEBUG: <core> [core/mem/q_malloc.c:482]: qm_free(): qm_free(0x7f54a05dc000, 0x7f54d75aeb50), called from cdp: diameter_msg.c: AAAFreeMessage(424) Apr 24, 2022 @ 20:43:58.854 +0200 pcscf 44(138) DEBUG: <core> [core/mem/q_malloc.c:525]: qm_free(): freeing frag. 0x7f54d75aeb18 alloc'ed from cdp: diameter_msg.c: AAATranslateMessage(485) Apr 24, 2022 @ 20:43:58.854 +0200 pcscf 44(138) ERROR: cdp [receiver.c:688]: receive_loop(): select_recv(): Bad file descriptor Apr 24, 2022 @ 20:43:58.854 +0200 pcscf 44(138) INFO: cdp [receiver.c:222]: disconnect_serviced_peer(): drop_serviced_peer(): [chordlet] Disconnecting from peer ``` ### Possible Solutions  ### Additional Information * **Kamailio Version** - output of `kamailio -v` ``` version: kamailio 5.4.4 (x86_64/linux) flags: USE_TCP, USE_TLS, USE_SCTP, TLS_HOOKS, USE_RAW_SOCKS, DISABLE_NAGLE, USE_MCAST, DNS_IP_HACK, 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, TLS_PTHREAD_MUTEX_SHARED 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: unknown compiled with gcc 10.2.1 ``` * **Operating System**: ``` Linux 5.10.69-flatcar #1 SMP Wed Sep 29 20:48:40 -00 2021 x86_64 x86_64 x86_64 GNU/Linux ``` -- Reply to this email directly or view it on GitHub: https://github.com/kamailio/kamailio/issues/3092 You are receiving this because you are subscribed to this thread. Message ID: <kamailio/kamailio/issues/3092(a)github.com>

2 2

[kamailio/kamailio] http_async_client module crashing kamailio v5.5 on startup (Issue #2999)
by Joey Golan 23 Nov '23

23 Nov '23

### Description Hello, Loading http_async_client module causes kamailio to crash on startup with the following errors: 0(60541) INFO: http_async_client [async_http.c:85]: async_http_init_worker(): started worker process: 1 [warn] kevent: Bad file descriptor 16(60557) CRITICAL: <core> [core/pt.c:405]: fork_tcp_process(): called from a non "main" process 16(60557) ERROR: <core> [core/tcp_main.c:5121]: tcp_init_children(): fork failed: Bad file descriptor 0(60541) ALERT: <core> [main.c:786]: handle_sigs(): child process 60557 exited normally, status=255 0(60541) INFO: <core> [main.c:813]: handle_sigs(): terminating due to SIGCHLD 1(60542) INFO: <core> [main.c:868]: sig_usr(): signal 15 received 5(60546) INFO: <core> [main.c:868]: sig_usr(): signal 15 received Issue reproduced with kamailio sample configuration + loadmodule "http_async_client.so" ### Additional Information * **Kamailio Version** * ``` kamailio -v version: kamailio 5.5.3 (x86_64/darwin) b42dfd flags: USE_TCP, USE_TLS, USE_SCTP, TLS_HOOKS, DISABLE_NAGLE, USE_MCAST, DNS_IP_HACK, SHM_MMAP, PKG_MALLOC, Q_MALLOC, F_MALLOC, TLSF_MALLOC, DBG_SR_MEMORY, FAST_LOCK-ADAPTIVE_WAIT, USE_DNS_CACHE, USE_DNS_FAILOVER, USE_NAPTR, USE_DST_BLOCKLIST, HAVE_RESOLV_RES, TLS_PTHREAD_MUTEX_SHARED ADAPTIVE_WAIT_LOOPS 1024, MAX_RECV_BUFFER_SIZE 262144, MAX_URI_SIZE 1024, BUF_SIZE 65535, DEFAULT PKG_SIZE 8MB poll method support: poll, select, kqueue. id: b42dfd compiled on 22:25:21 Jan 6 2022 with gcc Apple clang version 13.0.0 (clang-1300.0.29.30) ``` * **Operating System**: ``` MacOS ``` -- Reply to this email directly or view it on GitHub: https://github.com/kamailio/kamailio/issues/2999 You are receiving this because you are subscribed to this thread. Message ID: <kamailio/kamailio/issues/2999(a)github.com>

4 7

[kamailio/kamailio] WebSocket keepalive logging "forcibly closing connection" with TCP connection errors (Issue #2990)
by Max Wardell 23 Nov '23

23 Nov '23

6 13

[kamailio/kamailio] Kafka: Wrong format on RPC responses (Issue #2991)
by Olle E. Johansson 23 Nov '23

23 Nov '23

The kafka module use printf-like message to print statistics in rpc_kafka_stats() which doesn't follow the style for other RPC commands that produce data structures parsable as data, like when using jsonrpc. ``` if (rpc->rpl_printf(ctx, "Total messages: %" PRIu64 " Errors: %" PRIu64, msg_total, msg_error) < 0) { rpc->fault(ctx, 500, "Internal error showing total statistics"); return; } ``` I think this is a bug, but easy to fix. -- Reply to this email directly or view it on GitHub: https://github.com/kamailio/kamailio/issues/2991 You are receiving this because you are subscribed to this thread. Message ID: <kamailio/kamailio/issues/2991(a)github.com>

2 2

[kamailio/kamailio] CNXCC doesn't update values on Redis DB (Issue #2948)
by Simone de Blasiis 23 Nov '23

23 Nov '23

### Description We are trying to use CNXCC in order to monitor credit usage but it doesn't appear to be working. The cnxcc_set_max_credit call appears to be working partially as we can see that a new key is created in the Redis DB but with all the values set to 0. The values that we set in the cnxcc_set_max_credit are hardcoded but it doesn't seem to work. This is an example of what we find in the Redis DB: ``` 1637599472.872820 [1 127.0.0.1:53578] "HEXISTS" "cnxcc:money:pippo@dom.domain.it" "concurrent_calls" 1637599472.872942 [1 127.0.0.1:53578] "EXPIRE" "cnxcc:money:pippo@dom.domain.it" "70" 1637599472.873043 [1 127.0.0.1:53578] "HSET" "cnxcc:money:pippo@dom.domain.it" "concurrent_calls" "0" 1637599472.873159 [1 127.0.0.1:53578] "EXPIRE" "cnxcc:money:pippo@dom.domain.it" "70" 1637599472.873292 [1 127.0.0.1:53578] "HSET" "cnxcc:money:pippo@dom.domain.it" "consumed_amount" "0.000000" 1637599472.873404 [1 127.0.0.1:53578] "EXPIRE" "cnxcc:money:pippo@dom.domain.it" "70" 1637599472.873515 [1 127.0.0.1:53578] "HSET" "cnxcc:money:pippo@dom.domain.it" "ended_calls_consumed_amount" "0.000000" 1637599472.873634 [1 127.0.0.1:53578] "EXPIRE" "cnxcc:money:pippo@dom.domain.it" "70" 1637599472.873752 [1 127.0.0.1:53578] "HSET" "cnxcc:money:pippo@dom.domain.it" "max_amount" "0.000000" 1637599472.873875 [1 127.0.0.1:53578] "EXPIRE" "cnxcc:money:pippo@dom.domain.it" "70" 1637599472.874000 [1 127.0.0.1:53578] "HSET" "cnxcc:money:pippo@dom.domain.it" "number_of_calls" "0" 1637599472.874115 [1 127.0.0.1:53578] "EXPIRE" "cnxcc:money:pippo@dom.domain.it" "70" 1637599472.874269 [1 127.0.0.1:53578] "HSET" "cnxcc:money:pippo@dom.domain.it" "type" "1" 1637599472.874381 [1 127.0.0.1:53578] "EXPIRE" "cnxcc:money:pippo@dom.domain.it" "70" 1637599472.874481 [1 127.0.0.1:53578] "SREM" "cnxcc:kill_list:money" "\"pippo(a)dom.domain.it\"" 1637599472.874585 [1 127.0.0.1:53578] "EXPIRE" "cnxcc:money:pippo@dom.domain.it" "70" 1637599472.874747 [1 127.0.0.1:53578] "HINCRBY" "cnxcc:money:pippo@dom.domain.it" "number_of_calls" "1" 1637599472.874845 [1 127.0.0.1:53578] "EXPIRE" "cnxcc:money:pippo@dom.domain.it" "70" ``` This issue is identical to the one described in #1387 ### Troubleshooting #### Reproduction We are running Kamailio 5.5 from the official repos on Debian 10. All the modules are installed through the repo. This is the config that we are currently using to set the values for the modules. We also tried setting the values straight into the function bypassing the variables but the result is the same. ``` $dlg_var(credit) = "50.0"; $var(connect_cost) = "5.0"; $var(cost_per_sec) = "1.0"; $var(i_pulse) = 1; $var(f_pulse) = 1; xlog("$dlg_var(label) $var(credit) $var(connect_cost) "); if (cnxcc_set_max_credit("$dlg_var(label)", "$dlg_var(credit)", "$var(connect_cost)", "$var(cost_per_sec)", "$var(i_pulse) ", "$var(f_pulse)") < 0) { xlog("Failed to setup credit control"); sl_send_reply("503", "Internal Server Error"); exit; } ``` #### Log Messages The call to cnxcc_set_max_credit() doesn't throw any errors and returns 1 as if everything worked correctly ### Additional Information * **Kamailio Version** - output of `kamailio -v` ``` version: kamailio 5.5.2 (x86_64/linux) flags: USE_TCP, USE_TLS, USE_SCTP, TLS_HOOKS, USE_RAW_SOCKS, DISABLE_NAGLE, USE_MCAST, DNS_IP_HACK, 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_BLOCKLIST, HAVE_RESOLV_RES, TLS_PTHREAD_MUTEX_SHARED 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: unknown compiled with gcc 8.3.0 ``` * **Operating System**: ``` No LSB modules are available. Distributor ID: Debian Description: Debian GNU/Linux 10 (buster) Release: 10 Codename: buster Linux kamailio 5.11.22-5-pve #1 SMP PVE 5.11.22-10 (Tue, 28 Sep 2021 08:15:41 +0200) x86_64 GNU/Linux ``` -- You are receiving this because you are subscribed to this thread. Reply to this email directly or view it on GitHub: https://github.com/kamailio/kamailio/issues/2948

4 5

[kamailio/kamailio] kazoo_query causes crash of kamailio (Issue #2922)
by mihovilkolaric 23 Nov '23

23 Nov '23

### Description Found following issue when trying to solve #2895 :  function kazoo_query (as shown in the module's documentation) causes kamailio to crash. ### Troubleshooting #### Reproduction Compile kamailio master-branch from scratch (with module "kazoo" enabled). Modify kamailio-config with minimal settings required to use function "kazoo_query": ``` diff /usr/local/etc/kamailio/kamailio.cfg.sample /usr/local/etc/kamailio/kamailio.cfg 496a497,501 > loadmodule "kazoo.so" > modparam("kazoo", "amqp_connection", "amqp://guest:guest@rabbitmqhost:5672") > modparam("kazoo", "node_hostname", "sipproxy.mydomain.com") > modparam("kazoo", "pua_mode", 0) > 517a523,533 > xlog("SCRIPT: Snipppet from kazoo_query-documentation:\n"); > $var(amqp_payload_request) = "{'Event-Category' : 'call_event' , 'Event-Name' : 'query_user_channels_req', 'Realm' : '" + $fd + "', 'Username' : '" + $fU + "', 'Active-Only' : false }"; > kazoo_encode("$ci", "$var(callid_encoded)"); > $var(amqp_routing_key) = "call.status_req.$var(callid_encoded)"; > if(kazoo_query("callevt", $var(amqp_routing_key), $var(amqp_payload_request), "$var(amqp_result)")) { > kazoo_json("$var(amqp_result)", "Channels[0].switch_url", "$du"); > if($du != $null) { > xlog("L_INFO", "$ci|log|user channels found redirecting call to $du"); > return; > } > } ``` Start kamailio and register. Kamailio crashes when reaching kazoo_query: ``` Nov 6 16:19:37 hostname kamailio: INFO: <core> [core/tcp_main.c:4997]: init_tcp(): using epoll_lt as the io watch method (auto detected) Nov 6 16:19:37 hostname src/kamailio[352171]: INFO: rr [../outbound/api.h:52]: ob_load_api(): unable to import bind_ob - maybe module is not loaded Nov 6 16:19:37 hostname src/kamailio[352171]: INFO: rr [rr_mod.c:188]: mod_init(): outbound module not available Nov 6 16:19:37 hostname src/kamailio[352171]: INFO: <core> [main.c:3035]: main(): processes (at least): 52 - shm size: 67108864 - pkg size: 8388608 Nov 6 16:19:37 hostname src/kamailio[352171]: INFO: <core> [core/udp_server.c:154]: probe_max_receive_buffer(): SO_RCVBUF is initially 212992 Nov 6 16:19:37 hostname src/kamailio[352171]: INFO: <core> [core/udp_server.c:206]: probe_max_receive_buffer(): SO_RCVBUF is finally 425984 Nov 6 16:19:37 hostname src/kamailio[352171]: INFO: <core> [core/udp_server.c:154]: probe_max_receive_buffer(): SO_RCVBUF is initially 212992 Nov 6 16:19:37 hostname src/kamailio[352171]: INFO: <core> [core/udp_server.c:206]: probe_max_receive_buffer(): SO_RCVBUF is finally 425984 Nov 6 16:19:37 hostname src/kamailio[352171]: INFO: <core> [core/udp_server.c:154]: probe_max_receive_buffer(): SO_RCVBUF is initially 212992 Nov 6 16:19:37 hostname src/kamailio[352171]: INFO: <core> [core/udp_server.c:206]: probe_max_receive_buffer(): SO_RCVBUF is finally 425984 Nov 6 16:19:37 hostname src/kamailio[352200]: INFO: jsonrpcs [jsonrpcs_sock.c:443]: jsonrpc_dgram_process(): a new child 0/352200 Nov 6 16:19:37 hostname src/kamailio[352202]: INFO: ctl [io_listener.c:213]: io_listen_loop(): io_listen_loop: using epoll_lt io watch method (config) Nov 6 16:19:37 hostname src/kamailio[352203]: ERROR: kazoo [kz_amqp.c:2387]: kz_amqp_consumer_event_cfg(): kazoo:consumer-event not found Nov 6 16:19:42 hostname src/kamailio[352203]: ERROR: kazoo [kz_amqp.c:2387]: kz_amqp_consumer_event_cfg(): kazoo:consumer-event not found Nov 6 16:19:49 hostname src/kamailio[352213]: ERROR: {1 1 REGISTER OUfeIVS08Xrbmw8Nr-udtg..} <script>: SCRIPT: Snipppet from kazoo_query-documentation: Nov 6 16:19:49 hostname src/kamailio[352221]: CRITICAL: <core> [core/pass_fd.c:277]: receive_fd(): EOF on 72 Nov 6 16:19:49 hostname src/kamailio[352171]: ALERT: <core> [main.c:774]: handle_sigs(): child process 352213 exited by a signal 6 Nov 6 16:19:49 hostname src/kamailio[352171]: ALERT: <core> [main.c:777]: handle_sigs(): core was generated Nov 6 16:19:49 hostname src/kamailio[352171]: INFO: <core> [main.c:799]: handle_sigs(): terminating due to SIGCHLD Nov 6 16:19:49 hostname src/kamailio[352220]: INFO: <core> [main.c:854]: sig_usr(): signal 15 received Nov 6 16:19:49 hostname src/kamailio[352218]: INFO: <core> [main.c:854]: sig_usr(): signal 15 received Nov 6 16:19:49 hostname src/kamailio[352209]: INFO: <core> [main.c:854]: sig_usr(): signal 15 received Nov 6 16:19:49 hostname src/kamailio[352219]: INFO: <core> [main.c:854]: sig_usr(): signal 15 received Nov 6 16:19:49 hostname src/kamailio[352201]: INFO: <core> [main.c:854]: sig_usr(): signal 15 received Nov 6 16:19:49 hostname src/kamailio[352187]: INFO: <core> [main.c:854]: sig_usr(): signal 15 received Nov 6 16:19:49 hostname src/kamailio[352207]: INFO: <core> [main.c:854]: sig_usr(): signal 15 received Nov 6 16:19:49 hostname src/kamailio[352205]: INFO: <core> [main.c:854]: sig_usr(): signal 15 received Nov 6 16:19:49 hostname src/kamailio[352202]: INFO: <core> [main.c:854]: sig_usr(): signal 15 received Nov 6 16:19:49 hostname src/kamailio[352199]: INFO: <core> [main.c:854]: sig_usr(): signal 15 received Nov 6 16:19:49 hostname src/kamailio[352195]: INFO: <core> [main.c:854]: sig_usr(): signal 15 received Nov 6 16:19:49 hostname src/kamailio[352210]: INFO: <core> [main.c:854]: sig_usr(): signal 15 received Nov 6 16:19:49 hostname src/kamailio[352193]: INFO: <core> [main.c:854]: sig_usr(): signal 15 received Nov 6 16:19:49 hostname src/kamailio[352196]: INFO: <core> [main.c:854]: sig_usr(): signal 15 received Nov 6 16:19:49 hostname src/kamailio[352183]: INFO: <core> [main.c:854]: sig_usr(): signal 15 received Nov 6 16:19:49 hostname src/kamailio[352191]: INFO: <core> [main.c:854]: sig_usr(): signal 15 received Nov 6 16:19:49 hostname src/kamailio[352176]: INFO: <core> [main.c:854]: sig_usr(): signal 15 received Nov 6 16:19:49 hostname src/kamailio[352203]: INFO: <core> [main.c:854]: sig_usr(): signal 15 received Nov 6 16:19:49 hostname src/kamailio[352189]: INFO: <core> [main.c:854]: sig_usr(): signal 15 received Nov 6 16:19:49 hostname src/kamailio[352192]: INFO: <core> [main.c:854]: sig_usr(): signal 15 received Nov 6 16:19:49 hostname src/kamailio[352175]: INFO: <core> [main.c:854]: sig_usr(): signal 15 received Nov 6 16:19:49 hostname src/kamailio[352208]: INFO: <core> [main.c:854]: sig_usr(): signal 15 received Nov 6 16:19:49 hostname src/kamailio[352185]: INFO: <core> [main.c:854]: sig_usr(): signal 15 received Nov 6 16:19:49 hostname src/kamailio[352182]: INFO: <core> [main.c:854]: sig_usr(): signal 15 received Nov 6 16:19:49 hostname src/kamailio[352216]: INFO: <core> [main.c:854]: sig_usr(): signal 15 received Nov 6 16:19:49 hostname src/kamailio[352190]: INFO: <core> [main.c:854]: sig_usr(): signal 15 received Nov 6 16:19:49 hostname src/kamailio[352206]: INFO: <core> [main.c:854]: sig_usr(): signal 15 received Nov 6 16:19:49 hostname src/kamailio[352194]: INFO: <core> [main.c:854]: sig_usr(): signal 15 received Nov 6 16:19:49 hostname src/kamailio[352177]: INFO: <core> [main.c:854]: sig_usr(): signal 15 received Nov 6 16:19:49 hostname src/kamailio[352215]: INFO: <core> [main.c:854]: sig_usr(): signal 15 received Nov 6 16:19:49 hostname src/kamailio[352186]: INFO: <core> [main.c:854]: sig_usr(): signal 15 received Nov 6 16:19:49 hostname src/kamailio[352173]: INFO: <core> [main.c:854]: sig_usr(): signal 15 received Nov 6 16:19:49 hostname src/kamailio[352204]: INFO: <core> [main.c:854]: sig_usr(): signal 15 received Nov 6 16:19:49 hostname src/kamailio[352184]: INFO: <core> [main.c:854]: sig_usr(): signal 15 received Nov 6 16:19:49 hostname src/kamailio[352188]: INFO: <core> [main.c:854]: sig_usr(): signal 15 received Nov 6 16:19:49 hostname src/kamailio[352217]: INFO: <core> [main.c:854]: sig_usr(): signal 15 received Nov 6 16:19:49 hostname src/kamailio[352214]: INFO: <core> [main.c:854]: sig_usr(): signal 15 received Nov 6 16:19:49 hostname src/kamailio[352180]: INFO: <core> [main.c:854]: sig_usr(): signal 15 received Nov 6 16:19:49 hostname src/kamailio[352198]: INFO: <core> [main.c:854]: sig_usr(): signal 15 received Nov 6 16:19:49 hostname src/kamailio[352172]: INFO: <core> [main.c:854]: sig_usr(): signal 15 received Nov 6 16:19:49 hostname src/kamailio[352221]: INFO: <core> [main.c:854]: sig_usr(): signal 15 received Nov 6 16:19:49 hostname src/kamailio[352174]: INFO: <core> [main.c:854]: sig_usr(): signal 15 received Nov 6 16:19:49 hostname src/kamailio[352197]: INFO: <core> [main.c:854]: sig_usr(): signal 15 received Nov 6 16:19:49 hostname src/kamailio[352200]: INFO: <core> [main.c:854]: sig_usr(): signal 15 received Nov 6 16:19:49 hostname src/kamailio[352211]: INFO: <core> [main.c:854]: sig_usr(): signal 15 received Nov 6 16:19:49 hostname src/kamailio[352212]: INFO: <core> [main.c:854]: sig_usr(): signal 15 received Nov 6 16:19:49 hostname src/kamailio[352181]: INFO: <core> [main.c:854]: sig_usr(): signal 15 received Nov 6 16:19:49 hostname src/kamailio[352179]: INFO: <core> [main.c:854]: sig_usr(): signal 15 received Nov 6 16:19:49 hostname src/kamailio[352178]: INFO: <core> [main.c:854]: sig_usr(): signal 15 received Nov 6 16:19:49 hostname src/kamailio[352171]: INFO: <core> [core/sctp_core.c:53]: sctp_core_destroy(): SCTP API not initialized ``` #### Debugging Data  backtrace with gdb shows: ``` (gdb) bt #0 __GI_raise (sig=sig@entry=6) at ../sysdeps/unix/sysv/linux/raise.c:50 #1 0x00007fc47407a859 in __GI_abort () at abort.c:79 #2 0x00007fc47407a729 in __assert_fail_base (fmt=0x7fc474210588 "%s%s%s:%u: %s%sAssertion `%s' failed.\n%n", assertion=0x7fc46f0fe2d0 "json_object_get_type(jso) == json_type_object", file=0x7fc46f0fe044 "json_object.c", line=476, function=<optimized out>) at assert.c:92 #3 0x00007fc47408bf36 in __GI___assert_fail (assertion=0x7fc46f0fe2d0 "json_object_get_type(jso) == json_type_object", file=0x7fc46f0fe044 "json_object.c", line=476, function=0x7fc46f0fe280 "json_object_object_add_ex") at assert.c:101 #4 0x00007fc46f0f7d26 in json_object_object_add_ex () from /lib/x86_64-linux-gnu/libjson-c.so.4 #5 0x00007fc46f14ebe4 in kz_amqp_add_payload_common_properties (json_obj=0x559b3c3b30c0, server_id=0x7ffda57606f0 "kamailio(a)sipproxy.mydomain.com-<352213>-script-0", unique=0x7ffda5760660) at kz_amqp.c:1023 #6 0x00007fc46f1509a0 in kz_amqp_pipe_send_receive (str_exchange=0x7ffda57609c0, str_routing_key=0x7ffda57609d0, str_payload=0x7ffda57609b0, kz_timeout=0x7ffda57609e0, json_ret=0x7ffda5760a10) at kz_amqp.c:1159 #7 0x00007fc46f158763 in kz_amqp_query_ex (msg=0x7fc47394beb8, exchange=0x7fc4738f03d0 "(q\216s\304\177", routing_key=0x7fc4738f57c8 "0\213\207s\304\177", payload=0x7fc4738f58d8 "hX\217s\304\177") at kz_amqp.c:1494 #8 0x00007fc46f1588b2 in kz_amqp_query (msg=0x7fc47394beb8, exchange=0x7fc4738f03d0 "(q\216s\304\177", routing_key=0x7fc4738f57c8 "0\213\207s\304\177", payload=0x7fc4738f58d8 "hX\217s\304\177", dst=0x7fc4738f04f0 "p\004\217s\304\177") at kz_amqp.c:1517 #9 0x0000559b3b1c7355 in do_action (h=0x7ffda5761370, a=0x7fc4738f1d98, msg=0x7fc47394beb8) at core/action.c:1151 #10 0x0000559b3b1d0463 in run_actions (h=0x7ffda5761370, a=0x7fc4738f1d98, msg=0x7fc47394beb8) at core/action.c:1581 #11 0x0000559b3b1d0bd6 in run_actions_safe (h=0x7ffda5761f70, a=0x7fc4738f1d98, msg=0x7fc47394beb8) at core/action.c:1645 #12 0x0000559b3b16a4b0 in rval_get_int (h=0x7ffda5761f70, msg=0x7fc47394beb8, i=0x7ffda5761750, rv=0x7fc4738f4040, cache=0x0) at core/rvalue.c:949 #13 0x0000559b3b16fa9c in rval_expr_eval_int (h=0x7ffda5761f70, msg=0x7fc47394beb8, res=0x7ffda5761750, rve=0x7fc4738f4038) at core/rvalue.c:1947 #14 0x0000559b3b1c0ec8 in do_action (h=0x7ffda5761f70, a=0x7fc4738f7f28, msg=0x7fc47394beb8) at core/action.c:1052 #15 0x0000559b3b1d0463 in run_actions (h=0x7ffda5761f70, a=0x7fc4738e8ca8, msg=0x7fc47394beb8) at core/action.c:1581 #16 0x0000559b3b1d0ce6 in run_top_route (a=0x7fc4738e8ca8, msg=0x7fc47394beb8, c=0x0) at core/action.c:1666 #17 0x0000559b3b37f932 in receive_msg ( buf=0x559b3c3a0960 "REGISTER sip:10.0.0.24:5060;transport=TCP SIP/2.0\r\nVia: SIP/2.0/TCP 10.0.0.33:47335;branch=z9hG4bK-524287-1---83d016a408b857dd;rport\r\nMax-Forwards: 69\r\nContact: <sip:1234@10.0.0.33:47335;rinstance=837"..., len=578, rcv_info=0x7fc46f4c01a8) at core/receive.c:513 #18 0x0000559b3b41dfb3 in receive_tcp_msg ( tcpbuf=0x7fc46f4c0530 "REGISTER sip:10.0.0.24:5060;transport=TCP SIP/2.0\r\nVia: SIP/2.0/TCP 10.0.0.33:47335;branch=z9hG4bK-524287-1---83d016a408b857dd;rport\r\nMax-Forwards: 70\r\nContact: <sip:1234@10.0.0.33:47335;rinstance=837"..., len=578, rcv_info=0x7fc46f4c01a8, con=0x7fc46f4c0190) at core/tcp_read.c:1424 #19 0x0000559b3b4205f8 in tcp_read_req (con=0x7fc46f4c0190, bytes_read=0x7ffda5762618, read_flags=0x7ffda576261c) at core/tcp_read.c:1607 #20 0x0000559b3b423af5 in handle_io (fm=0x7fc473954a08, events=1, idx=-1) at core/tcp_read.c:1782 #21 0x0000559b3b40eccc in io_wait_loop_epoll (h=0x559b3b6f62e0 <io_w>, t=2, repeat=0) at core/io_wait.h:1070 #22 0x0000559b3b426aa8 in tcp_receive_loop (unix_sock=75) at core/tcp_read.c:1978 #23 0x0000559b3b2a161e in tcp_init_children (woneinit=0x7ffda5762a00) at core/tcp_main.c:5153 #24 0x0000559b3b153f0b in main_loop () at main.c:1843 #25 0x0000559b3b15e745 in main (argc=1, argv=0x7ffda57630e8) at main.c:3058 ``` #### Log Messages  #### SIP Traffic  ``` (paste your sip traffic here) ``` ### Possible Solutions This somehow pointed me to the payload - so I tried to change the AMQP-payload in the config to a minimalistic custom JSON document. With this config, the crash does no longer occur: ``` diff /usr/local/etc/kamailio/kamailio.cfg /usr/local/etc/kamailio/kamailio.cfg.sample 497,501d496 < loadmodule "kazoo.so" < modparam("kazoo", "amqp_connection", "amqp://guest:guest@guest@rabbitmqhost:5672") < modparam("kazoo", "node_hostname", "sipproxy.mydomain.com") < modparam("kazoo", "pua_mode", 0) < 523,533d517 < xlog("SCRIPT: Snipppet from kazoo_query-documentation:\n"); < #$var(amqp_payload_request) = "{'Event-Category' : 'call_event' , 'Event-Name' : 'query_user_channels_req', 'Realm' : '" + $fd + "', 'Username' : '" + $fU + "', 'Active-Only' : false }"; < kazoo_encode("$ci", "$var(callid_encoded)"); < $var(amqp_routing_key) = "call.status_req.$var(callid_encoded)"; < if(kazoo_query("callevt", $var(amqp_routing_key), "{\"blop\":\"example\"}", "$var(amqp_result)")) { < kazoo_json("$var(amqp_result)", "Channels[0].switch_url", "$du"); < if($du != $null) { < xlog("L_INFO", "$ci|log|user channels found redirecting call to $du"); < return; < } < } ``` So, some issue in the exmaple's payload causes the crash. One the one hand, I think an example from the documentation should somehow work, on the other hand I think that an error in a JSON-payload is not indended to crash kamailio anyway.  ### Additional Information * **Kamailio Version** - output of `kamailio -v` ``` kamailio -v version: kamailio 5.6.0-dev2 (x86_64/linux) 63a349 flags: USE_TCP, USE_TLS, USE_SCTP, TLS_HOOKS, USE_RAW_SOCKS, DISABLE_NAGLE, USE_MCAST, DNS_IP_HACK, 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_BLOCKLIST, HAVE_RESOLV_RES, TLS_PTHREAD_MUTEX_SHARED 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: 63a349 compiled on 16:12:36 Nov 6 2021 with gcc 9.3.0 ``` * **Operating System**:  ``` uname -a Linux hostname 5.11.0-38-generic #42~20.04.1-Ubuntu SMP Tue Sep 28 20:41:07 UTC 2021 x86_64 x86_64 x86_64 GNU/Linux lsb_release -a No LSB modules are available. Distributor ID: Ubuntu Description: Ubuntu 20.04.3 LTS Release: 20.04 Codename: focal ``` -- You are receiving this because you are subscribed to this thread. Reply to this email directly or view it on GitHub: https://github.com/kamailio/kamailio/issues/2922

3 4

Jump to page:

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

sr-dev May 2022