sr-dev June 2025

sr-dev@lists.kamailio.org

20 participants
221 discussions

[kamailio/kamailio] alpine: failed build after libjwt-dev upgrade (Issue #4264)
by sergey-safarov 13 Jun '25

13 Jun '25

sergey-safarov created an issue (kamailio/kamailio#4264) On `alpine:edge` upgraded `libjwt-dev` from `1.17.2-r0` to `3.2.1-r0` and on now present this error in the build log. ``` make[2]: --libs: No such file or directory make[2]: --libs: No such file or directory CC (cc) [M jwt.so] jwt_mod.o jwt_mod.c: In function 'ki_jwt_generate_hdrs': jwt_mod.c:215:17: error: implicit declaration of function 'jwt_free_str'; did you mean 'jwt_alg_str'? [-Wimplicit-function-declaration] 215 | jwt_free_str(_jwt_result.s); | ^~~~~~~~~~~~ | jwt_alg_str jwt_mod.c:275:15: error: implicit declaration of function 'jwt_new' [-Wimplicit-function-declaration] 275 | ret = jwt_new(&jwt); | ^~~~~~~ jwt_mod.c:283:15: error: implicit declaration of function 'jwt_add_grant_int' [-Wimplicit-function-declaration] 283 | ret = jwt_add_grant_int(jwt, "iat", iat); | ^~~~~~~~~~~~~~~~~ jwt_mod.c:293:39: error: implicit declaration of function 'jwt_add_grant' [-Wimplicit-function-declaration] 293 | ret = jwt_add_grant(jwt, pit->name.s, pit->body.s); | ^~~~~~~~~~~~~ jwt_mod.c:311:39: error: implicit declaration of function 'jwt_add_header' [-Wimplicit-function-declaration] 311 | ret = jwt_add_header(jwt, header->name.s, header->body.s); | ^~~~~~~~~~~~~~ jwt_mod.c:313:39: error: implicit declaration of function 'jwt_add_header_int'; did you mean 'jwt_header_get'? [-Wimplicit-function-declaration] 313 | ret = jwt_add_header_int(jwt, header->name.s, lval); | ^~~~~~~~~~~~~~~~~~ | jwt_header_get jwt_mod.c:324:15: error: implicit declaration of function 'jwt_set_alg'; did you mean 'jwt_get_alg'? [-Wimplicit-function-declaration] 324 | ret = jwt_set_alg(jwt, valg, (unsigned char *)kdata.s, (size_t)kdata.len); | ^~~~~~~~~~~ | jwt_get_alg jwt_mod.c:330:25: error: implicit declaration of function 'jwt_encode_str' [-Wimplicit-function-declaration] 330 | _jwt_result.s = jwt_encode_str(jwt); | ^~~~~~~~~~~~~~ jwt_mod.c:330:23: error: assignment to 'char *' from 'int' makes pointer from integer without a cast [-Wint-conversion] 330 | _jwt_result.s = jwt_encode_str(jwt); | ^ jwt_mod.c:337:9: error: implicit declaration of function 'jwt_free'; did you mean 'jwks_free'? [-Wimplicit-function-declaration] 337 | jwt_free(jwt); | ^~~~~~~~ | jwks_free jwt_mod.c: In function 'ki_jwt_verify_key': jwt_mod.c:443:9: error: unknown type name 'jwt_valid_t'; did you mean 'jwt_value_t'? 443 | jwt_valid_t *jwt_valid = NULL; | ^~~~~~~~~~~ | jwt_value_t jwt_mod.c:477:15: error: implicit declaration of function 'jwt_valid_new' [-Wimplicit-function-declaration] 477 | ret = jwt_valid_new(&jwt_valid, valg); | ^~~~~~~~~~~~~ jwt_mod.c:484:9: error: implicit declaration of function 'jwt_valid_set_headers' [-Wimplicit-function-declaration] 484 | jwt_valid_set_headers(jwt_valid, 1); | ^~~~~~~~~~~~~~~~~~~~~ jwt_mod.c:485:9: error: implicit declaration of function 'jwt_valid_set_now' [-Wimplicit-function-declaration] 485 | jwt_valid_set_now(jwt_valid, iat); | ^~~~~~~~~~~~~~~~~ jwt_mod.c:492:39: error: implicit declaration of function 'jwt_valid_add_grant' [-Wimplicit-function-declaration] 492 | ret = jwt_valid_add_grant(jwt_valid, pit->name.s, pit->body.s); | ^~~~~~~~~~~~~~~~~~~ jwt_mod.c:494:39: error: implicit declaration of function 'jwt_valid_add_grant_int' [-Wimplicit-function-declaration] 494 | ret = jwt_valid_add_grant_int(jwt_valid, pit->name.s, lval); | ^~~~~~~~~~~~~~~~~~~~~~~ jwt_mod.c:505:15: error: implicit declaration of function 'jwt_decode' [-Wimplicit-function-declaration] 505 | ret = jwt_decode( | ^~~~~~~~~~ jwt_mod.c:511:22: error: implicit declaration of function 'jwt_validate' [-Wimplicit-function-declaration] 511 | if((jwtret = jwt_validate(jwt, jwt_valid)) != JWT_VALIDATION_SUCCESS) { | ^~~~~~~~~~~~ jwt_mod.c:511:55: error: 'JWT_VALIDATION_SUCCESS' undeclared (first use in this function) 511 | if((jwtret = jwt_validate(jwt, jwt_valid)) != JWT_VALIDATION_SUCCESS) { | ^~~~~~~~~~~~~~~~~~~~~~ jwt_mod.c:511:55: note: each undeclared identifier is reported only once for each function it appears in jwt_mod.c:512:38: error: implicit declaration of function 'jwt_valid_get_status' [-Wimplicit-function-declaration] 512 | _jwt_verify_status = jwt_valid_get_status(jwt_valid); | ^~~~~~~~~~~~~~~~~~~~ jwt_mod.c:521:9: error: implicit declaration of function 'jwt_valid_free'; did you mean 'jwt_builder_free'? [-Wimplicit-function-declaration] 521 | jwt_valid_free(jwt_valid); | ^~~~~~~~~~~~~~ | jwt_builder_free make[2]: *** [../../Makefile.rules:100: jwt_mod.o] Error 1 make[1]: *** [Makefile:509: modules] Error 1 make[1]: Leaving directory '/usr/src/kamailio/pkg/kamailio/alpine/src/kamailio-78541805e73f1ca2a220e84734090ebd606bc5e4/src' make: *** [Makefile:34: all] Error 2 >>> ERROR: kamailio: build failed >>> kamailio: Uninstalling dependencies... (1/1) Purging .makedepends-kamailio (20250527.180[501](https://github.com/sergey-safarov/kamailio/actions/runs/1…) OK: 1028 MiB in 240 packages ``` -- Reply to this email directly or view it on GitHub: https://github.com/kamailio/kamailio/issues/4264 You are receiving this because you are subscribed to this thread. Message ID: <kamailio/kamailio/issues/4264(a)github.com>

3 3

[kamailio/kamailio] tcp_timer_check_connections() logs on CRITICAL and is not caught by event_route[tcp:timeout] (Issue #3995)
by Fritjof Höst 13 Jun '25

13 Jun '25

### 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>

6 12

git:master:2af2c80f: core: tcp - log message on message processing timeout made debug
by Daniel-Constantin Mierla 13 Jun '25

13 Jun '25

Module: kamailio Branch: master Commit: 2af2c80fde4e82614846af9d817ab2bffa2d954d URL: https://github.com/kamailio/kamailio/commit/2af2c80fde4e82614846af9d817ab2b… Author: Daniel-Constantin Mierla <miconda(a)gmail.com> Committer: Daniel-Constantin Mierla <miconda(a)gmail.com> Date: 2025-06-13T09:51:13+02:00 core: tcp - log message on message processing timeout made debug --- Modified: src/core/tcp_main.c --- Diff: https://github.com/kamailio/kamailio/commit/2af2c80fde4e82614846af9d817ab2b… Patch: https://github.com/kamailio/kamailio/commit/2af2c80fde4e82614846af9d817ab2b… --- diff --git a/src/core/tcp_main.c b/src/core/tcp_main.c index 369bfb1f159..277ae960091 100644 --- a/src/core/tcp_main.c +++ b/src/core/tcp_main.c @@ -5589,9 +5589,9 @@ void tcp_timer_check_connections(unsigned int ticks, void *param) if(n > 0) { for(i = 0; i < n; i++) { if((con = tcpconn_get(tcpidlist[i], 0, 0, 0, 0))) { - LM_CRIT("message processing timeout on connection id: %d " - "(state: %d) - " - "closing\n", + LM_DBG("message processing timeout on connection id: %d " + "(state: %d) - " + "closing\n", tcpidlist[i], con->state); mcmd[0] = (long)con; mcmd[1] = CONN_EOF;

1 0

git:master:7f68f5bf: modules: readme files regenerated - jwt ... [skip ci]
by Kamailio Dev 13 Jun '25

13 Jun '25

Module: kamailio Branch: master Commit: 7f68f5bfaf931f4e0eb4625a1eefaf330309c879 URL: https://github.com/kamailio/kamailio/commit/7f68f5bfaf931f4e0eb4625a1eefaf3… Author: Kamailio Dev <kamailio.dev(a)kamailio.org> Committer: Kamailio Dev <kamailio.dev(a)kamailio.org> Date: 2025-06-13T09:31:10+02:00 modules: readme files regenerated - jwt ... [skip ci] --- Modified: src/modules/jwt/README --- Diff: https://github.com/kamailio/kamailio/commit/7f68f5bfaf931f4e0eb4625a1eefaf3… Patch: https://github.com/kamailio/kamailio/commit/7f68f5bfaf931f4e0eb4625a1eefaf3… --- diff --git a/src/modules/jwt/README b/src/modules/jwt/README index 7101d714c9c..03ef468df9a 100644 --- a/src/modules/jwt/README +++ b/src/modules/jwt/README @@ -75,7 +75,8 @@ Chapter 1. Admin Guide Kamailio configuration file. It relies on libjwt (at least v1.12.0) library - (https://github.com/benmcollins/libjwt). + (https://github.com/benmcollins/libjwt), but it is not working with the + new libjwt3. 2. Dependencies @@ -91,7 +92,7 @@ Chapter 1. Admin Guide The following libraries or applications must be installed before running Kamailio with this module loaded: - * libjwt - minimum version 1.12.0. + * libjwt - minimum version 1.12.0, but less than libjwt 3.0. 3. Parameters

1 0

git:master:36c466bc: jwt: added to the notes about libjwt versions
by Daniel-Constantin Mierla 13 Jun '25

13 Jun '25

Module: kamailio Branch: master Commit: 36c466bce5a57df72806a0915361612c32cc838e URL: https://github.com/kamailio/kamailio/commit/36c466bce5a57df72806a0915361612… Author: Daniel-Constantin Mierla <miconda(a)gmail.com> Committer: Daniel-Constantin Mierla <miconda(a)gmail.com> Date: 2025-06-13T09:26:17+02:00 jwt: added to the notes about libjwt versions - module is not compatible with the new libjwt3 --- Modified: src/modules/jwt/doc/jwt_admin.xml --- Diff: https://github.com/kamailio/kamailio/commit/36c466bce5a57df72806a0915361612… Patch: https://github.com/kamailio/kamailio/commit/36c466bce5a57df72806a0915361612… --- diff --git a/src/modules/jwt/doc/jwt_admin.xml b/src/modules/jwt/doc/jwt_admin.xml index 5389bb61f30..4aecc4d0a8b 100644 --- a/src/modules/jwt/doc/jwt_admin.xml +++ b/src/modules/jwt/doc/jwt_admin.xml @@ -20,7 +20,8 @@ in &kamailio; configuration file. </para> <para> - It relies on libjwt (at least v1.12.0) library (https://github.com/benmcollins/libjwt). + It relies on libjwt (at least v1.12.0) library (https://github.com/benmcollins/libjwt), + but it is not working with the new libjwt3. </para> </section> @@ -47,7 +48,8 @@ <itemizedlist> <listitem> <para> - <emphasis>libjwt</emphasis> - minimum version 1.12.0. + <emphasis>libjwt</emphasis> - minimum version 1.12.0, but less + than libjwt 3.0. </para> </listitem> </itemizedlist>

1 0

[kamailio/kamailio] Subscriptions replication and presence sync via dmq (PR #4239)
by Viktor Litvinov 13 Jun '25

13 Jun '25

#### Pre-Submission Checklist    - [x] Commit message has the format required by CONTRIBUTING guide - [x] Commits are split per component (core, individual modules, libs, utils, ...) - [x] 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) - [x] 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 - [x] Tested changes locally - [ ] Related to issue #XXXX (replace XXXX with an open issue number) #### Description  Added subscriptions replication and presentity sync via dmq for presence module. You can view, comment on, or merge this pull request online at: https://github.com/kamailio/kamailio/pull/4239 -- Commit Summary -- * Subscriptions replication and presence sync -- File Changes -- M src/modules/presence/hash.c (92) M src/modules/presence/hash.h (6) M src/modules/presence/notify.c (9) M src/modules/presence/presence.c (18) M src/modules/presence/presence.h (6) M src/modules/presence/presence_dmq.c (334) M src/modules/presence/presence_dmq.h (6) M src/modules/presence/presentity.c (93) M src/modules/presence/presentity.h (2) M src/modules/presence/publish.c (4) M src/modules/presence/subscribe.c (55) M src/modules/presence/subscribe.h (1) -- Patch Links -- https://github.com/kamailio/kamailio/pull/4239.patch https://github.com/kamailio/kamailio/pull/4239.diff -- Reply to this email directly or view it on GitHub: https://github.com/kamailio/kamailio/pull/4239 You are receiving this because you are subscribed to this thread. Message ID: <kamailio/kamailio/pull/4239(a)github.com>

4 4

[kamailio/kamailio] sht_setxi() exits script (stops message processing). (Issue #4283)
by Ben Kaufman 12 Jun '25

12 Jun '25

whosgonna created an issue (kamailio/kamailio#4283) ### Description Using function `sht_setxi()` causes the script to exit and stop processing messages. Using the example from the documention: ``` #!KAMAILIO loadmodule "pv" loadmodule "ctl" loadmodule "htable" loadmodule "xlog" modparam("htable", "htable", "ha=>size=4"); request_route { xnotice("Request received [$ru]\n"); ## this prints sht_setxi("ha", "test", "100", "10"); ## exactly as documented xnotice("log line after sht_setxi()\n"); ## This does not print. } ``` ### Troubleshooting As shown above. Note that the similar function `sht_setxs()` (for setting string values) works as expected. #### Reproduction Trivial to reproduce. #### SIP Traffic Tested from localhost with `sipsak -s sip:127.0.0.1`, but any message seems to do this. ### Possible Solutions I believe that the issue is in [`/src/modules/htable/htable.c`](/src/modules/htable/htable.c) within function `static int ki_ht_setxi()` where the return is `0` (last line in the function). I'm guessing it should return `1`, like ``static int ki_ht_setxs()` (sting function equivilent) ### Additional Information Tested in 6.0.1 and 5.8.5 ``` version: kamailio 6.0.1 (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**:  ``` version: kamailio 5.8.5 (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 on 19:38:35 Jan 30 2025 with gcc 14.2.0 ``` -- Reply to this email directly or view it on GitHub: https://github.com/kamailio/kamailio/issues/4283 You are receiving this because you are subscribed to this thread. Message ID: <kamailio/kamailio/issues/4283(a)github.com>

2 2

git:master:f789f6a5: core: parser - count diversion header body len based on last param
by Daniel-Constantin Mierla 12 Jun '25

12 Jun '25

Module: kamailio Branch: master Commit: f789f6a5fa4d651ad3bcb657cb2a1dc765de6460 URL: https://github.com/kamailio/kamailio/commit/f789f6a5fa4d651ad3bcb657cb2a1dc… Author: Daniel-Constantin Mierla <miconda(a)gmail.com> Committer: Daniel-Constantin Mierla <miconda(a)gmail.com> Date: 2025-06-12T17:43:20+02:00 core: parser - count diversion header body len based on last param - take in consideratio quoted param values --- Modified: src/core/parser/parse_diversion.c --- Diff: https://github.com/kamailio/kamailio/commit/f789f6a5fa4d651ad3bcb657cb2a1dc… Patch: https://github.com/kamailio/kamailio/commit/f789f6a5fa4d651ad3bcb657cb2a1dc… --- diff --git a/src/core/parser/parse_diversion.c b/src/core/parser/parse_diversion.c index 1b5d70a5f80..098ae19afa6 100644 --- a/src/core/parser/parse_diversion.c +++ b/src/core/parser/parse_diversion.c @@ -52,10 +52,10 @@ int parse_diversion_body(char *buf, int len, diversion_body_t **body) { static to_body_t uri_b[NUM_DIVERSION_BODIES]; /* Temporary storage */ int num_uri = 0; - int body_len = 0; char *tmp; int i; to_param_t *params; + to_param_t *lparam; memset(uri_b, 0, NUM_DIVERSION_BODIES * sizeof(to_body_t)); @@ -66,17 +66,27 @@ int parse_diversion_body(char *buf, int len, diversion_body_t **body) } /* id.body should contain all info including uri and params */ - body_len = uri_b[num_uri].body.len; - /* Loop over all params */ params = uri_b[num_uri].param_lst; + lparam = NULL; while(params) { - body_len += - params->name.len + params->value.len + 2; // 2 for '=' and ';' + lparam = params; params = params->next; } - uri_b[num_uri].body.len = body_len; + if(lparam) { + if(lparam->value.len > 0) { + uri_b[num_uri].body.len = + lparam->value.s + lparam->value.len - uri_b[num_uri].body.s; + if(*(lparam->value.s - 1) == '"' + || *(lparam->value.s - 1) == '\'') { + uri_b[num_uri].body.len++; + } + } else { + uri_b[num_uri].body.len = + lparam->name.s + lparam->name.len - uri_b[num_uri].body.s; + } + } num_uri++; while(*tmp == ',' && (num_uri < NUM_DIVERSION_BODIES)) { @@ -132,17 +142,25 @@ int parse_diversion_body(char *buf, int len, diversion_body_t **body) } /* id.body should contain all info including uri and params */ - body_len = uri_b[num_uri].body.len; - /* Loop over all params */ params = uri_b[num_uri].param_lst; while(params) { - body_len += params->name.len + params->value.len - + 2; /* 2 for '=' and ';' */ + lparam = params; params = params->next; } - - uri_b[num_uri].body.len = body_len; + if(lparam) { + if(lparam->value.len > 0) { + uri_b[num_uri].body.len = lparam->value.s + lparam->value.len + - uri_b[num_uri].body.s; + if(*(lparam->value.s - 1) == '"' + || *(lparam->value.s - 1) == '\'') { + uri_b[num_uri].body.len++; + } + } else { + uri_b[num_uri].body.len = lparam->name.s + lparam->name.len + - uri_b[num_uri].body.s; + } + } num_uri++; }

1 0

git:master:9ded810b: htable: return true for sht_setxi()
by Daniel-Constantin Mierla 12 Jun '25

12 Jun '25

Module: kamailio Branch: master Commit: 9ded810b2dfe527db8d8be409fe1f34b002f3325 URL: https://github.com/kamailio/kamailio/commit/9ded810b2dfe527db8d8be409fe1f34… Author: Daniel-Constantin Mierla <miconda(a)gmail.com> Committer: Daniel-Constantin Mierla <miconda(a)gmail.com> Date: 2025-06-12T17:43:20+02:00 htable: return true for sht_setxi() - GH #4283 --- Modified: src/modules/htable/htable.c --- Diff: https://github.com/kamailio/kamailio/commit/9ded810b2dfe527db8d8be409fe1f34… Patch: https://github.com/kamailio/kamailio/commit/9ded810b2dfe527db8d8be409fe1f34… --- diff --git a/src/modules/htable/htable.c b/src/modules/htable/htable.c index d458e83141a..63c0b4ced02 100644 --- a/src/modules/htable/htable.c +++ b/src/modules/htable/htable.c @@ -1406,7 +1406,7 @@ static int ki_ht_setxi( return -1; } - return 0; + return 1; } /**

1 0

[kamailio/kamailio] tls_wolfssl: crash qm_free / qm_debug_check_frag (Issue #4074)
by Fred Posner 12 Jun '25

12 Jun '25

### Introduction First, I apologize for the lack of detail here. I am unable to get a core dump and as a production box, I was unable to run in debug mode. ### Description Using Kamailio 5.8.4 on Debian 12, every 60-80 minutes, the software would crash, blaming tls_wolfssl, such as: ``` 2024-12-16T14:58:27.554497+00:00 ip-172-16-0-52 /usr/local/sbin/kamailio[9084]: CRITICAL: <core> [core/mem/q_malloc.c:535]: qm_free(): BUG: bad pointer 0x1 (out of memory block!) called from tls_wolfssl: tls_init.c: ser_free(240) - ignoring 2024-12-16T14:58:27.554555+00:00 ip-172-16-0-52 /usr/local/sbin/kamailio[9084]: CRITICAL: <core> [core/mem/q_malloc.c:126]: qm_debug_check_frag(): BUG: qm: fragm. 0x7f3440ba7560 (address 0x7f3440ba75a0) beginning overwritten (23)! Memory allocator was called from tls_wolfssl: tls_init.c:240. Fragment marked by :29. Exec from core/mem/q_malloc.c:546. 2024-12-16T14:58:27.616558+00:00 ip-172-16-0-52 /usr/local/sbin/kamailio[9089]: CRITICAL: <core> [core/pass_fd.c:281]: receive_fd(): EOF on 103 2024-12-16T14:58:27.617684+00:00 ip-172-16-0-52 /usr/local/sbin/kamailio[8992]: ALERT: <core> [main.c:805]: handle_sigs(): child process 9084 exited by a signal 6 2024-12-16T14:58:27.618339+00:00 ip-172-16-0-52 /usr/local/sbin/kamailio[8992]: ALERT: <core> [main.c:809]: handle_sigs(): core was not generated 2024-12-16T14:58:27.618477+00:00 ip-172-16-0-52 /usr/local/sbin/kamailio[8992]: INFO: <core> [main.c:832]: handle_sigs(): terminating due to SIGCHLD 2024-12-16T14:58:27.618589+00:00 ip-172-16-0-52 /usr/local/sbin/kamailio[9088]: INFO: <core> [main.c:888]: sig_usr(): signal 15 received ``` ``` 2024-12-16T14:57:52.029277+00:00 ip-172-16-0-73 /usr/local/sbin/kamailio[21605]: CRITICAL: <core> [core/mem/q_malloc.c:535]: qm_free(): BUG: bad pointer 0x1 (out of memory block!) called from tls_wolfssl: tls_init.c: ser_free(240) - ignoring 2024-12-16T14:57:52.029347+00:00 ip-172-16-0-73 /usr/local/sbin/kamailio[21605]: CRITICAL: <core> [core/mem/q_malloc.c:126]: qm_debug_check_frag(): BUG: qm: fragm. 0x7f085996b500 (address 0x7f085996b540) beginning overwritten (0)! Memory allocator was called from tls_wolfssl: tls_init.c:240. Fragment marked by (null):0. Exec from core/mem/q_malloc.c:546. 2024-12-16T14:57:52.048597+00:00 ip-172-16-0-73 /usr/local/sbin/kamailio[21611]: CRITICAL: <core> [core/pass_fd.c:281]: receive_fd(): EOF on 101 2024-12-16T14:57:52.048921+00:00 ip-172-16-0-73 /usr/local/sbin/kamailio[21512]: ALERT: <core> [main.c:805]: handle_sigs(): child process 21605 exited by a signal 6 2024-12-16T14:57:52.048953+00:00 ip-172-16-0-73 /usr/local/sbin/kamailio[21512]: ALERT: <core> [main.c:809]: handle_sigs(): core was not generated 2024-12-16T14:57:52.048975+00:00 ip-172-16-0-73 /usr/local/sbin/kamailio[21512]: INFO: <core> [main.c:832]: handle_sigs(): terminating due to SIGCHLD 2024-12-16T14:57:52.048997+00:00 ip-172-16-0-73 /usr/local/sbin/kamailio[21609]: INFO: <core> [main.c:888]: sig_usr(): signal 15 received ``` ``` 2024-12-16T16:21:35.967576+00:00 ip-172-16-0-52 /usr/local/sbin/kamailio[10591]: CRITICAL: <core> [core/mem/q_malloc.c:126]: qm_debug_check_frag(): BUG: qm: fragm. 0x7f442778d110 (address 0x7f442778d150) beginning overwritten (0)! Memory allocator was called from tls_wolfssl: tls_init.c:240. Fragment marked by (null):0. Exec from core/mem/q_malloc.c:546. ``` ``` 2024-12-16T13:31:55.995222+00:00 ip-172-16-0-52 /usr/local/sbin/kamailio[7602]: CRITICAL: <core> [core/mem/q_malloc.c:555]: qm_free(): BUG: freeing already freed pointer (0x7f8e55830a70), called from tls_wolfssl: tls_init.c: ser_free(240), first free tls_wolfssl: tls_init.c: ser_malloc(228) - ignoring 2024-12-16T13:32:40.093954+00:00 ip-172-16-0-52 /usr/local/sbin/kamailio[7603]: CRITICAL: <core> [core/mem/q_malloc.c:535]: qm_free(): BUG: bad pointer 0x7a100000000 (out of memory block!) called from tls_wolfssl: tls_init.c: ser_free(240) - ignoring 2024-12-16T13:32:40.094047+00:00 ip-172-16-0-52 /usr/local/sbin/kamailio[7603]: CRITICAL: <core> [core/mem/q_malloc.c:126]: qm_debug_check_frag(): BUG: qm: fragm. 0x7f8e55762720 (address 0x7f8e55762760) beginning overwritten (0)! Memory allocator was called from tls_wolfssl: tls_init.c:240. Fragment marked by (null):0. Exec from core/mem/q_malloc.c:546. 2024-12-16T13:32:40.260913+00:00 ip-172-16-0-52 /usr/local/sbin/kamailio[7504]: CRITICAL: <core> [core/mem/q_malloc.c:555]: qm_free(): BUG: freeing already freed pointer (0x7f8e55761a70), called from core: core/tcp_main.c: _tcpconn_free(1666), first free tls_wolfssl: tls_init.c: ser_free(240) - ignoring 2024-12-16T13:32:40.263520+00:00 ip-172-16-0-52 /usr/local/sbin/kamailio[7504]: CRITICAL: <core> [core/mem/q_malloc.c:126]: qm_debug_check_frag(): BUG: qm: fragm. 0x7f8e55762720 (address 0x7f8e55762760) beginning overwritten (0)! Memory allocator was called from tls_wolfssl: tls_init.c:240. Fragment marked by (null):0. Exec from core/mem/q_malloc.c:546. ``` The system was handling ~900 TLS registrations with ~2700 presence SUBSCRIBE events. **Running the same config with `tls.so` does not result in crash.** ### Additional Information * **Kamailio Version** - 5.8.4 ``` version: kamailio 5.8.4 (x86_64/linux) 598105-dirty 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: 598105 -dirty compiled on 04:31:34 Dec 16 2024 with gcc 12.2.0 ``` * **Operating System**: ``` Distributor ID: Debian Description: Debian GNU/Linux 12 (bookworm) Release: 12 Codename: bookworm Linux ip-172-16-0-52 6.1.0-28-cloud-amd64 #1 SMP PREEMPT_DYNAMIC Debian 6.1.119-1 (2024-11-22) x86_64 GNU/Linux ``` * TCP Settings ``` children=16 disable_tcp=no tcp_connection_lifetime=3605 tcp_accept_no_cl=yes tcp_max_connections=8192 tcp_defer_accept=yes tcp_accept_unique=0 tcp_connection_lifetime=3605 tcp_connection_match=1 tcp_connect_timeout=10 tcp_crlf_ping=yes tcp_linger2=1 tcp_keepalive=yes tcp_reuse_port=yes tcp_keepidle=20 tcp_keepintvl=15 tcp_rd_buf_size=65536 tcp_msg_data_timeout=40 tcp_msg_read_timeout=40 tcp_check_timer=20 tls_threads_mode=2 tls_max_connections=8192 ``` -- Reply to this email directly or view it on GitHub: https://github.com/kamailio/kamailio/issues/4074 You are receiving this because you are subscribed to this thread. Message ID: <kamailio/kamailio/issues/4074(a)github.com>

3 6

← Newer
1
...
10
11
12
13
14
15
16
...
23
Older →

Jump to page:

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

sr-dev June 2025