sr-dev

sr-dev@lists.kamailio.org

17 participants
44125 discussions

[kamailio/kamailio] Kamailio crash on http_async_client module callback invocation (Issue #4019)

by Ivanuschak Nikolay

### Description Kamailio service crashed occasionally on `sock_cb` callback function of `http_async_client` module #### Reproduction The crash happens occasionally, no specific conditions have been identified for this issue. #### Debugging Data ``` Program terminated with signal SIGSEGV, Segmentation fault. (gdb) bt full #0 0x0000ffff9f4205e4 in event_del_ () from /lib64/libevent-2.1.so.6 No symbol table info available. #1 0x0000ffff9e7c9b24 in sock_cb (e=0xffffa2027ba8, s=9, what=4, cbp=0xffffa1c0fe58, sockp=0xffffa202d258) at http_multi.c:166 g = 0xffffa1c0fe58 cell = 0xffffa202d258 whatstr = {0xffff9e7eb508 "none", 0xffff9e7eb510 "IN", 0xffff9e7eb518 "OUT", 0xffff9e7eb520 "INOUT", 0xffff9e7eb528 "REMOVE"} __func__ = "sock_cb" #2 0x0000ffff9e73ffa8 in Curl_multi_closed () from /lib64/libcurl.so.4 No symbol table info available. #3 0x0000ffff9e73d43c in Curl_closesocket () from /lib64/libcurl.so.4 No symbol table info available. #4 0x0000ffff9e72c8f8 in conn_free.part () from /lib64/libcurl.so.4 No symbol table info available. #5 0x0000ffff9e72d544 in Curl_disconnect () from /lib64/libcurl.so.4 No symbol table info available. #6 0x0000ffff9e740948 in multi_done () from /lib64/libcurl.so.4 No symbol table info available. #7 0x0000ffff9e742b10 in curl_multi_remove_handle () from /lib64/libcurl.so.4 No symbol table info available. #8 0x0000ffff9e7c7f2c in event_cb (fd=59, kind=1, userp=0xffffa2027ba8) at http_multi.c:123 error = 0xffff9e7eac70 "TIMEOUT" g = 0xffffa1c0fe58 rc = 1968268110 easy = 0xffffa2027ba8 cell = 0xffffa202d258 __func__ = "event_cb" action = 0 #9 0x0000ffff9f423628 in event_process_active_single_queue () from /lib64/libevent-2.1.so.6 No symbol table info available. #10 0x0000ffff9f423ee8 in event_base_loop () from /lib64/libevent-2.1.so.6 No symbol table info available. #11 0x0000ffff9e7b7160 in async_http_run_worker (worker=0xffffa1606ed8) at async_http.c:95 ret = 65535 __func__ = "async_http_run_worker" #12 0x0000ffff9e7dc364 in child_init (rank=0) at http_async_client_mod.c:380 pid = 0 i = 0 __func__ = "child_init" #13 0x0000000000607fa8 in init_mod_child (m=0xffffb136c2f0, rank=0) at core/sr_module.c:899 --Type <RET> for more, q to quit, c to continue without paging-- ret = 0 __func__ = "init_mod_child" #14 0x0000000000607b38 in init_mod_child (m=0xffffb136d018, rank=0) at core/sr_module.c:892 ret = 0 __func__ = "init_mod_child" #15 0x0000000000607b38 in init_mod_child (m=0xffffb136ead0, rank=0) at core/sr_module.c:892 ret = 0 __func__ = "init_mod_child" #16 0x0000000000607b38 in init_mod_child (m=0xffffb13a98f8, rank=0) at core/sr_module.c:892 ret = 0 __func__ = "init_mod_child" #17 0x0000000000607b38 in init_mod_child (m=0xffffb140ab28, rank=0) at core/sr_module.c:892 ret = 0 __func__ = "init_mod_child" #18 0x0000000000607b38 in init_mod_child (m=0xffffb145ebf8, rank=0) at core/sr_module.c:892 ret = 1 __func__ = "init_mod_child" #19 0x00000000006089c4 in init_child (rank=0) at core/sr_module.c:953 ret = -783429656 type = 0x923dc0 "PROC_MAIN" __func__ = "init_child" #20 0x0000000000433030 in main_loop () at main.c:1843 i = 8 pid = 2823204 si = 0x0 si_desc = "udp receiver child=7 sock=[2605:84c0:48:205:1::6]:5080\000\000\220\036ٰ\377\377\000\000 \321M\321\377\377\000\000h\220\066\261\377\377\000\000\320\377\377\377\200\377\377\377\020\321M\321\377\377\000\000 \321M\321\377\377\000\000 \321M\321\377\377\000\000\360\320M\321\377\377\000\000\320\377\377\377\200\377\377\377" nrprocs = 8 woneinit = 1 __func__ = "main_loop" #21 0x000000000043f4e8 in main (argc=11, argv=0xffffd14dd6a8) at main.c:3086 cfg_stream = 0xc2502a0 c = -1 r = 0 tmp = 0xffffd14dfe34 "" tmp_len = 0 port = 0 proto = 65535 ahost = 0x0 --Type <RET> for more, q to quit, c to continue without paging-- aport = 0 options = 0x8e7c08 ":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 = 203142350 rfd = 4 debug_save = 0 debug_flag = 0 dont_fork_cnt = 2 n_lst = 0xffffffff p = 0xffffb3d34348 <__libc_start_main+160> "" st = {st_dev = 25, st_ino = 18459, st_mode = 16877, st_nlink = 3, st_uid = 0, st_gid = 987, st_rdev = 0, __pad1 = 0, st_size = 80, st_blksize = 65536, __pad2 = 0, st_blocks = 0, st_atim = {tv_sec = 1707863213, tv_nsec = 9999979}, st_mtim = {tv_sec = 1729635590, tv_nsec = 702238079}, st_ctim = { tv_sec = 1729635598, tv_nsec = 32030431}, __glibc_reserved = {0, 0}} tbuf = '\000' <repeats 56 times>, "x\376\b\264\377\377\000\000h\376\b\264\377\377\000\000\b\376\b\264\377\377\000\000(\376\b\264\377\377\000\000\070\376\b\264\377\377\000\000\250\376\b\264\377\377\000\000\270\376\b\264\377\377\000\000\310\376\b\264\377\377\000\000H\376\b\264\377\377\000\000X\376\b\264\377\377", '\000' <repeats 18 times>, "\330\375\b\264\377\377", '\000' <repeats 42 times>... option_index = 12 long_options = {{name = 0x8e9fe0 "help", has_arg = 0, flag = 0x0, val = 104}, {name = 0x8e4e48 "version", has_arg = 0, flag = 0x0, val = 118}, { name = 0x8e9fe8 "alias", has_arg = 1, flag = 0x0, val = 1024}, {name = 0x8e9ff0 "subst", has_arg = 1, flag = 0x0, val = 1025}, {name = 0x8e9ff8 "substdef", has_arg = 1, flag = 0x0, val = 1026}, {name = 0x8ea008 "substdefs", has_arg = 1, flag = 0x0, val = 1027}, {name = 0x8ea018 "server-id", has_arg = 1, flag = 0x0, val = 1028}, {name = 0x8ea028 "loadmodule", has_arg = 1, flag = 0x0, val = 1029}, {name = 0x8ea038 "modparam", has_arg = 1, flag = 0x0, val = 1030}, {name = 0x8ea048 "log-engine", has_arg = 1, flag = 0x0, val = 1031}, {name = 0x8ea058 "debug", has_arg = 1, flag = 0x0, val = 1032}, { name = 0x8ea060 "cfg-print", has_arg = 0, flag = 0x0, val = 1033}, {name = 0x8ea070 "atexit", has_arg = 1, flag = 0x0, val = 1034}, { name = 0x8ea078 "all-errors", has_arg = 0, flag = 0x0, val = 1035}, {name = 0x0, has_arg = 0, flag = 0x0, val = 0}} __func__ = "main" (gdb) f 8 #8 0x0000ffff9e7c7f2c in event_cb (fd=59, kind=1, userp=0xffffa2027ba8) at http_multi.c:123 123 curl_multi_remove_handle(g->multi, easy); (gdb) f 1 #1 0x0000ffff9e7c9b24 in sock_cb (e=0xffffa2027ba8, s=9, what=4, cbp=0xffffa1c0fe58, sockp=0xffffa202d258) at http_multi.c:166 166 event_del(cell->ev); (gdb) p cell $1 = (struct http_m_cell *) 0xffffa202d258 (gdb) p cell->ev $2 = (struct event *) 0x92fbf0 (gdb) p *cell->ev $3 = {type = 1701998435, name = {s = 0x615f7273752f6572 <error: Cannot access memory at address 0x615f7273752f6572>, len = 1663987830}, params = {hooks = {contact = { expires = 0x7273752f65726f63, q = 0x632e7076615f, methods = 0x5b203e65726f633c, received = 0x7273752f65726f63, instance = 0x393a632e7076615f, reg_id = 0x203a5d32, ob = 0x6f6e20646c756f63, flags = 0x61636f6c6c612074}, uri = {transport = 0x7273752f65726f63, lr = 0x632e7076615f, r2 = 0x5b203e65726f633c, maddr = 0x7273752f65726f63, ttl = 0x393a632e7076615f, dstip = 0x203a5d32, dstport = 0x6f6e20646c756f63, ftag = 0x61636f6c6c612074, ob = 0x6572616873206574}, event_dialog = {call_id = 0x7273752f65726f63, from_tag = 0x632e7076615f, to_tag = 0x5b203e65726f633c, include_session_description = 0x7273752f65726f63, sla = 0x393a632e7076615f, ma = 0x203a5d32}}, list = 0x79726f6d656d2064}} ``` As it's seen in the stack backtrace the `cell` object is already released at the moment when `event_del` with this object is called. #### Log Messages - #### SIP Traffic - ### Possible Solutions - ### Additional Information ``` [centos@esrp-1b ~]$ kamailio -v version: kamailio 5.7.2 (aarch64/linux) 968dbe flags: USE_TCP, USE_TLS, USE_SCTP, TLS_HOOKS, USE_RAW_SOCKS, DISABLE_NAGLE, USE_MCAST, DNS_IP_HACK, SHM_MMAP, PKG_MALLOC, MEM_JOIN_FREE, Q_MALLOC, F_MALLOC, TLSF_MALLOC, DBG_SR_MEMORY, USE_FUTEX, FAST_LOCK-ADAPTIVE_WAIT-NOSMP, 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: 968dbe compiled on 19:25:05 Nov 10 2023 with gcc 8.5.0 ``` * **Operating System**: ``` [centos@esrp-1b ~]$ cat /etc/centos-release CentOS Stream release 8 [centos@esrp-1b ~]$ uname -a Linux esrp-1b.fl.base911.com 4.18.0-536.el8.aarch64 #1 SMP Thu Jan 18 15:21:54 UTC 2024 aarch64 aarch64 aarch64 GNU/Linux ``` -- Reply to this email directly or view it on GitHub: https://github.com/kamailio/kamailio/issues/4019 You are receiving this because you are subscribed to this thread. Message ID: <kamailio/kamailio/issues/4019(a)github.com>

28 minutes

[kamailio/kamailio] tcp_timer_check_connections() logs on CRITICAL and is not caught by event_route[tcp:timeout] (Issue #3995)

by Fritjof Höst

### Description Hi! We are in the progress of upgrading from Kamailio 5.5 to 5.8. During our testing we have noticed a new error being reported from Kamailio. We don’t see any other errors following it. ```jsx /usr/sbin/kamailio[201]: CRITICAL: <core> [core/tcp_main.c:5544]: tcp_timer_check_connections(): message processing timeout on connection id: 67896 (state: 3) - closing ``` It does seem to be [new code](https://github.com/kamailio/kamailio/blob/master/src/core/tcp_main.c#… in Kamailio reporting this issue. Given that this is a fairly expected thing, cleaning up a connection which receives no traffic within the given time, is there a need for it to be reported on CRITICAL? I’d also expect it to be caught by ``` event_route[tcp:timeout] { xlog("L_INFO","connection $conid timeouts (unanswered keepalives)"); } ``` given that [the description](https://www.kamailio.org/docs/modules/stable/modules/tcpops.ht… of this one is `Called for connection timeouts (unanswered keepalives).`. ### Troubleshooting We don't have any way to reproduce it, we are still investigating it to figure out the cause. It happens around every 2 hours, so we think there might some some scheduled test or job running in our test system causing this. ### Additional Information * **Kamailio Version** - 5.8.3 * **Operating System**: Debian 12 AMI from the AWS Marketplace. -- Reply to this email directly or view it on GitHub: https://github.com/kamailio/kamailio/issues/3995 You are receiving this because you are subscribed to this thread. Message ID: <kamailio/kamailio/issues/3995(a)github.com>

9 hours, 30 minutes

[kamailio/kamailio] Possibly adjusting the SDP parser to be more lenient towards scenarios where a stream is being removed/rejected and connection-information "c=" is only available per media (no session-wide "c=") and the removed/rejected stream omits all fields (Issue #3982)

by thomas414

### Description I encountered an issue with a specific device that is receiving a T.38 fax. The call gets established towards the device normally with inband media, then the device requests T.38 media and tries to remove the audio media via sending port 0 in the ReInvite SDP. Also it sends connection-information only on the media level and there is no "c=" on the session level. Reading through the related RFCs and the kamailio code and discussing this on the mailing list, we came to the conclusion that kamailio is doing everything correct as per RFC. Though we were wondering if it would be possible to adjust the parser to be not as strict as it is right now, and allow a missing "c=" line on the media-level if the stream is removed/rejected via port 0, since i see no sense in requiring connection information. Of course we are also in contact with the vendor to hopefully adjust on their side. Here are the related RFCs: 1. RFC8866 5.7 `A session description MUST contain either at least one "c=" line in each media description or a single "c=" line at the session level. It MAY contain a single session-level "c=" line and additional media-level "c=" line(s) per-media-description, in which case the media-level values override the session-level settings for the respective media.` 2. RFC3264 8.2 `Existing media streams are removed by creating a new SDP with the port number for that stream set to zero. The stream description MAY omit all attributes present previously, and MAY list just a single media format.` At first i was especially confused by the RFC3264 8.2 part, since it seemed correct what the device is sending, but if you read carefully and keep the wording for SDP in mind only attributes ("a=") MAY be omitted. So a "c=" line should still be in the SDP for the removed media if it's not included on the session-level. Or do you see this differently? ### Expected behavior Kamailio allows and parses the SDP when there is no session-wide "c=", a media stream is being removed via port zero and there is no "c=" for this media stream and only the remaining media streams include a "c=" line. #### Actual observed behavior Kamailio throws an error when trying to parse the SDP. #### Log Messages ``` <core> [core/parser/sdp/sdp.c:523]: parse_sdp_session(): can't find media IP in the message ``` #### SIP Traffic ``` v=0 o=xmserver 1726638425 1726638427 IN IP4 169.254.1.1 s=xmserver t=0 0 m=audio 0 RTP/AVP 8 m=image 56002 udptl t38 c=IN IP4 169.254.1.1 a=sendrecv a=T38FaxVersion:0 a=T38MaxBitRate:14400 a=T38FaxFillBitRemoval:0 a=T38FaxTranscodingMMR:0 a=T38FaxTranscodingJBIG:0 a=T38FaxRateManagement:transferredTCF a=T38FaxMaxBuffer:200 a=T38FaxMaxDatagram:72 a=T38FaxUdpEC:t38UDPRedundancy ``` ### Possible Solutions ### Additional Information * **Kamailio Version** - output of `kamailio -v` ``` version: kamailio 5.8.3 (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, MEM_JOIN_FREE, 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_SEND_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 12.2.0 ``` * **Operating System**: ``` Debian 12 Linux hostname 6.1.0-20-amd64 #1 SMP PREEMPT_DYNAMIC Debian 6.1.85-1 (2024-04-11) x86_64 GNU/Linux ``` -- Reply to this email directly or view it on GitHub: https://github.com/kamailio/kamailio/issues/3982 You are receiving this because you are subscribed to this thread. Message ID: <kamailio/kamailio/issues/3982(a)github.com>

9 hours, 30 minutes

[kamailio/kamailio] cmake is overriding distro build flags (Issue #4082)

by space88man

### Description ping @xkaraman cmake is overriding distro build flags Here is typical CFLAGS for EL distros ``` export CFLAGS='-O2 -flto=auto -ffat-lto-objects -fexceptions -g -grecord-gcc-switches -pipe -Wall -Werror=format-security -Wp,-D_FORTIFY_SOURCE=2 -Wp,-D_GLIBCXX_ASSERTIONS -specs=/usr/lib/rpm/redhat/redhat-hardened-cc1 -fstack-protector-strong -specs=/usr/lib/rpm/redhat/redhat-annobin-cc1 -m64 -march=x86-64-v2 -mtune=generic -fasynchronous-unwind-tables -fstack-clash-protection -fcf-protection' ## try to build cd build/ make [ 1%] Building C object src/CMakeFiles/kamailio.dir/lib/srdb1/db_row.c.o In file included from /usr/include/bits/libc-header-start.h:33, from /usr/include/string.h:26, from /home/centos/src/kamailio-5.8/src/lib/srdb1/../../core/str.h:26, from /home/centos/src/kamailio-5.8/src/lib/srdb1/db_con.h:33, from /home/centos/src/kamailio-5.8/src/lib/srdb1/db_val.h:40, from /home/centos/src/kamailio-5.8/src/lib/srdb1/db_row.h:37, from /home/centos/src/kamailio-5.8/src/lib/srdb1/db_row.c:33: /usr/include/features.h:412:4: warning: #warning _FORTIFY_SOURCE requires compiling with optimization (-O) [-Wcpp] 412 | # warning _FORTIFY_SOURCE requires compiling with optimization (-O) ``` It is probably due to `cmake/compiler-specific.cmake`: ``` # If GCC version is greater than 4.2.0, enable the following flags if(CMAKE_C_COMPILER_VERSION VERSION_GREATER 4.2.0) target_compile_options( common INTERFACE -m64 -minline-all-stringops -falign-loops -ftree-vectorize -fno-strict-overflow -mtune=generic ) endif() ``` Packaging for ELx requires respecting the default flags - for EL9 included here for reference ``` CFLAGS='-O2 -flto=auto -ffat-lto-objects -fexceptions -g -grecord-gcc-switches -pipe -Wall -Werror=format-security -Wp,-D_FORTIFY_SOURCE=2 -Wp,-D_GLIBCXX_ASSERTIONS -specs=/usr/lib/rpm/redhat/redhat-hardened-cc1 -fstack-protector-strong -specs=/usr/lib/rpm/redhat/redhat-annobin-cc1 -m64 -march=x86-64-v2 -mtune=generic -fasynchronous-unwind-tables -fstack-clash-protection -fcf-protection' CXXFLAGS='-O2 -flto=auto -ffat-lto-objects -fexceptions -g -grecord-gcc-switches -pipe -Wall -Werror=format-security -Wp,-D_FORTIFY_SOURCE=2 -Wp,-D_GLIBCXX_ASSERTIONS -specs=/usr/lib/rpm/redhat/redhat-hardened-cc1 -fstack-protector-strong -specs=/usr/lib/rpm/redhat/redhat-annobin-cc1 -m64 -march=x86-64-v2 -mtune=generic -fasynchronous-unwind-tables -fstack-clash-protection -fcf-protection' FCFLAGS='-O2 -flto=auto -ffat-lto-objects -fexceptions -g -grecord-gcc-switches -pipe -Wall -Werror=format-security -Wp,-D_FORTIFY_SOURCE=2 -Wp,-D_GLIBCXX_ASSERTIONS -specs=/usr/lib/rpm/redhat/redhat-hardened-cc1 -fstack-protector-strong -specs=/usr/lib/rpm/redhat/redhat-annobin-cc1 -m64 -march=x86-64-v2 -mtune=generic -fasynchronous-unwind-tables -fstack-clash-protection -fcf-protection -I/usr/lib64/gfortran/modules' FFLAGS='-O2 -flto=auto -ffat-lto-objects -fexceptions -g -grecord-gcc-switches -pipe -Wall -Werror=format-security -Wp,-D_FORTIFY_SOURCE=2 -Wp,-D_GLIBCXX_ASSERTIONS -specs=/usr/lib/rpm/redhat/redhat-hardened-cc1 -fstack-protector-strong -specs=/usr/lib/rpm/redhat/redhat-annobin-cc1 -m64 -march=x86-64-v2 -mtune=generic -fasynchronous-unwind-tables -fstack-clash-protection -fcf-protection -I/usr/lib64/gfortran/modules' LDFLAGS='-Wl,-z,relro -Wl,--as-needed -Wl,-z,now -specs=/usr/lib/rpm/redhat/redhat-hardened-ld -specs=/usr/lib/rpm/redhat/redhat-annobin-cc1 ' ``` ELx packaging typically involves this dance: ``` # in practice RPM build tools have macros for all the following steps # use standard distro flags export CFLAGS=.... export CXXFLAGS=... export LDFLAGS=.... ./configure ``` Is there a way we can respect distro build flags with cmake? -- Reply to this email directly or view it on GitHub: https://github.com/kamailio/kamailio/issues/4082 You are receiving this because you are subscribed to this thread. Message ID: <kamailio/kamailio/issues/4082(a)github.com>

11 hours, 22 minutes

[kamailio/kamailio] htable: `$shtcn` also counts expired items (Issue #4080)

by Bastian Triller

### Description  `$shtcn` (and probably also `$shtcv`, but not tested) includes expired entries in count until `timer` process removes expired items. ### Troubleshooting #### Reproduction  ``` #!KAMAILIO listen=udp:127.0.0.1:9999 log_stderror=yes loadmodule "xlog.so" loadmodule "pv.so" loadmodule "sl.so" loadmodule "htable.so" modparam("htable", "htable", "foo=>autoexpire=1;updateexpire=0") request_route { $sht(foo=>bar-$Ts) = 1; xlog("$Ts count $shtcn(foo=>%~bar-)\n"); sl_send_reply("200", "Hello"); } ``` ``` while true; do sleep 0.3; sipsak -vs sip:localhost:9999 ; done ``` #### Log Messages  ``` 0(1415871) ERROR: <script>: 1734540011 count 1 0(1415871) ERROR: <script>: 1734540012 count 2 0(1415871) ERROR: <script>: 1734540012 count 2 0(1415871) ERROR: <script>: 1734540012 count 2 0(1415871) ERROR: <script>: 1734540013 count 3 0(1415871) ERROR: <script>: 1734540013 count 3 0(1415871) ERROR: <script>: 1734540013 count 3 0(1415871) ERROR: <script>: 1734540014 count 4 0(1415871) ERROR: <script>: 1734540014 count 4 0(1415871) ERROR: <script>: 1734540014 count 4 0(1415871) ERROR: <script>: 1734540015 count 5 0(1415871) ERROR: <script>: 1734540015 count 5 0(1415871) ERROR: <script>: 1734540015 count 5 0(1415871) ERROR: <script>: 1734540016 count 6 0(1415871) ERROR: <script>: 1734540016 count 6 0(1415871) ERROR: <script>: 1734540016 count 6 0(1415871) ERROR: <script>: 1734540016 count 6 0(1415871) ERROR: <script>: 1734540017 count 7 0(1415871) ERROR: <script>: 1734540017 count 7 0(1415871) ERROR: <script>: 1734540017 count 7 0(1415871) ERROR: <script>: 1734540018 count 8 0(1415871) ERROR: <script>: 1734540018 count 8 0(1415871) ERROR: <script>: 1734540018 count 8 0(1415871) ERROR: <script>: 1734540019 count 9 0(1415871) ERROR: <script>: 1734540019 count 9 0(1415871) ERROR: <script>: 1734540019 count 9 0(1415871) ERROR: <script>: 1734540020 count 10 0(1415871) ERROR: <script>: 1734540020 count 10 0(1415871) ERROR: <script>: 1734540020 count 10 0(1415871) ERROR: <script>: 1734540021 count 11 0(1415871) ERROR: <script>: 1734540021 count 11 0(1415871) ERROR: <script>: 1734540021 count 11 0(1415871) ERROR: <script>: 1734540022 count 12 0(1415871) ERROR: <script>: 1734540022 count 12 0(1415871) ERROR: <script>: 1734540022 count 12 0(1415871) ERROR: <script>: 1734540023 count 13 0(1415871) ERROR: <script>: 1734540023 count 13 0(1415871) ERROR: <script>: 1734540023 count 13 0(1415871) ERROR: <script>: 1734540024 count 14 0(1415871) ERROR: <script>: 1734540024 count 14 0(1415871) ERROR: <script>: 1734540024 count 14 0(1415871) ERROR: <script>: 1734540025 count 15 0(1415871) ERROR: <script>: 1734540025 count 15 0(1415871) ERROR: <script>: 1734540025 count 15 0(1415871) ERROR: <script>: 1734540026 count 16 0(1415871) ERROR: <script>: 1734540026 count 16 0(1415871) ERROR: <script>: 1734540026 count 16 0(1415871) ERROR: <script>: 1734540026 count 16 0(1415871) ERROR: <script>: 1734540027 count 17 0(1415871) ERROR: <script>: 1734540027 count 17 0(1415871) ERROR: <script>: 1734540027 count 17 0(1415871) ERROR: <script>: 1734540028 count 18 0(1415871) ERROR: <script>: 1734540028 count 2 0(1415871) ERROR: <script>: 1734540028 count 2 0(1415871) ERROR: <script>: 1734540029 count 3 0(1415871) ERROR: <script>: 1734540029 count 3 0(1415871) ERROR: <script>: 1734540029 count 3 0(1415871) ERROR: <script>: 1734540030 count 4 0(1415871) ERROR: <script>: 1734540030 count 4 0(1415871) ERROR: <script>: 1734540030 count 4 0(1415871) ERROR: <script>: 1734540031 count 5 0(1415871) ERROR: <script>: 1734540031 count 5 0(1415871) ERROR: <script>: 1734540031 count 5 0(1415871) ERROR: <script>: 1734540032 count 6 ``` ### Additional Information * **Kamailio Version** - output of `kamailio -v` ``` % /usr/sbin/kamailio -V version: kamailio 5.8.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, MEM_JOIN_FREE, 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_SEND_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 12.2.0 ``` * **Operating System**:  ``` % cat /etc/os-release PRETTY_NAME="Debian GNU/Linux 12 (bookworm)" NAME="Debian GNU/Linux" VERSION_ID="12" VERSION="12 (bookworm)" VERSION_CODENAME=bookworm ID=debian ``` -- Reply to this email directly or view it on GitHub: https://github.com/kamailio/kamailio/issues/4080 You are receiving this because you are subscribed to this thread. Message ID: <kamailio/kamailio/issues/4080(a)github.com>

15 hours, 1 minute

[kamailio/kamailio] Common style of CMakeLists.txt for modules (Issue #4081)

by Daniel-Constantin Mierla

I noticed at least two styles of CMakeLists.txt for modules: ``` ❯ cat src/modules/acc/CMakeLists.txt file(GLOB acc_SRC "*.c") add_library(acc SHARED ${acc_SRC}) ``` and ``` ❯ cat src/modules/xlog/CMakeLists.txt file(GLOB SRC_FILES "*.c") add_library(xlog SHARED ${SRC_FILES}) # # target_link_libraries(.*PRIVATE) ``` Which one should be used? The one with `modname_SRC` (e.g., `acc_SRC`) or the one with `SRC_FILES`? Also, I guess that the comment with `target_link_libraries()` can be removed. -- Reply to this email directly or view it on GitHub: https://github.com/kamailio/kamailio/issues/4081 You are receiving this because you are subscribed to this thread. Message ID: <kamailio/kamailio/issues/4081(a)github.com>

22 hours, 4 minutes

git:master:b5cb581b: tls: warn if tls_threads_mode=1 and force value to 2

by S-P Chan

Module: kamailio Branch: master Commit: b5cb581bd8f529dab8f4bcc6173e0cf1ad936550 URL: https://github.com/kamailio/kamailio/commit/b5cb581bd8f529dab8f4bcc6173e0cf… Author: S-P Chan <shihping.chan(a)gmail.com> Committer: S-P Chan <shihping.chan(a)gmail.com> Date: 2024-12-20T20:56:09+08:00 tls: warn if tls_threads_mode=1 and force value to 2 --- Modified: src/modules/tls/tls_mod.c --- Diff: https://github.com/kamailio/kamailio/commit/b5cb581bd8f529dab8f4bcc6173e0cf… Patch: https://github.com/kamailio/kamailio/commit/b5cb581bd8f529dab8f4bcc6173e0cf… --- diff --git a/src/modules/tls/tls_mod.c b/src/modules/tls/tls_mod.c index 1d7169b27e6..8a0b781831e 100644 --- a/src/modules/tls/tls_mod.c +++ b/src/modules/tls/tls_mod.c @@ -408,6 +408,12 @@ static int mod_init(void) "tls.so must be the first module loaded\n"); } } + + if(ksr_tls_threads_mode == KSR_TLS_THREADS_MTEMP) { + LM_WARN("tls_threads_mode=1 is invalid on kamailio version >= 6; " + "forcing tls_threads_mode=2\n"); + ksr_tls_threads_mode = KSR_TLS_THREADS_MFORK; + } #endif /* OPENSSL_VERSION_NUMBER*/ if(tls_disable) {

23 hours, 25 minutes

Heads-up: master/libssl - going to revert tls_threads_mode=1

by Richard Chan

HI devs, In trying to solve the libssl3 issue the original attempt with tls_threads_mode=1 turns out to be not quite correct. Since the release of 5.8 we have consistently recommended tls_threads_mode=2 for users of libssl 1.1.1 and 3. For master/6.0.0-pre I will start to revert the changes of tls_threads_mode=1. I will also add a new simpler mode tls_threads_mode=3 based on the diff by Ondrej Jirman <megi(a)xff.cz> (@meengu). Regards Richard

23 hours, 44 minutes

git:master:ea96d46a: cmake/utils: Fix double kamctl lib path

by Xenofon Karamanos

Module: kamailio Branch: master Commit: ea96d46a6ab4d60614a1f1cb86bcc1d983811b06 URL: https://github.com/kamailio/kamailio/commit/ea96d46a6ab4d60614a1f1cb86bcc1d… Author: Xenofon Karamanos <xk(a)gilawa.com> Committer: Xenofon Karamanos <xk(a)gilawa.com> Date: 2024-12-20T11:04:53Z cmake/utils: Fix double kamctl lib path --- Modified: utils/kamctl/CMakeLists.txt --- Diff: https://github.com/kamailio/kamailio/commit/ea96d46a6ab4d60614a1f1cb86bcc1d… Patch: https://github.com/kamailio/kamailio/commit/ea96d46a6ab4d60614a1f1cb86bcc1d… --- diff --git a/utils/kamctl/CMakeLists.txt b/utils/kamctl/CMakeLists.txt index e71af919240..5893aa79308 100644 --- a/utils/kamctl/CMakeLists.txt +++ b/utils/kamctl/CMakeLists.txt @@ -11,7 +11,7 @@ message(STATUS "Temporary kamctl.{db} files in : ${KAMCTL_TMP_DIR}") file(MAKE_DIRECTORY ${KAMCTL_TMP_DIR}) set(BIN_DIR "${CMAKE_INSTALL_FULL_SBINDIR}") -set(LIB_DIR "${CMAKE_INSTALL_FULL_LIBDIR}/${MAIN_NAME}/kamctl") +set(LIB_DIR "${CMAKE_INSTALL_FULL_LIBDIR}/${MAIN_NAME}") set(CFG_DIR "${CMAKE_INSTALL_FULL_SYSCONFDIR}/${MAIN_NAME}") set(SHARE_DIR "${CMAKE_INSTALL_FULL_DATADIR}/${MAIN_NAME}")

1 day

git:master:003a9294: cmake/utills: Config all files for build and install

by Xenofon Karamanos

Module: kamailio Branch: master Commit: 003a92942aeefd6611f9a2754f71b293ac73caaf URL: https://github.com/kamailio/kamailio/commit/003a92942aeefd6611f9a2754f71b29… Author: Xenofon Karamanos <xk(a)gilawa.com> Committer: Xenofon Karamanos <xk(a)gilawa.com> Date: 2024-12-20T11:04:53Z cmake/utills: Config all files for build and install - Config and install all kamctl related files - Config and install all kamdb related files - Format file --- Modified: utils/kamctl/CMakeLists.txt --- Diff: https://github.com/kamailio/kamailio/commit/003a92942aeefd6611f9a2754f71b29… Patch: https://github.com/kamailio/kamailio/commit/003a92942aeefd6611f9a2754f71b29…

1 day

Jump to page:

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

sr-dev