sr-dev April 2023

sr-dev@lists.kamailio.org

15 participants
264 discussions

[kamailio/kamailio] tm:local-request not documented (#980)
by Olle E. Johansson 18 Oct '23

18 Oct '23

The local-request event route is not documented. When using our friend google I find an old blog post by @miconda but not much else. I can come up with some good text, but need to know what can be done in the route, like - modify request uri - add/remove headers - drop request - add/modify destination uri ($du) -- 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/980

3 8

[kamailio/kamailio] No warning generated when UDP and no Content-Length header (PR #3359)
by sergey-safarov 12 Sep '23

12 Sep '23

GH # #### 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) - [x] 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 - [x] 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 #3210 #### Description Added 'always_log_missed_content_length' mode for sanity module. If 'always_log_missed_content_length' is 1 then the SIP message with no 'Content-Length' header will cause warning message in the logs. Otherwise warning message is not generated for cases when SIP message with no 'Content-Length' header is sent over UDP. You can view, comment on, or merge this pull request online at: https://github.com/kamailio/kamailio/pull/3359 -- Commit Summary -- * No warning generated when UDP and no Content-Length header -- File Changes -- M src/modules/sanity/doc/sanity_admin.xml (21) M src/modules/sanity/sanity.c (4) M src/modules/sanity/sanity_mod.c (12) M src/modules/sanity/sanity_mod.h (3) -- Patch Links -- https://github.com/kamailio/kamailio/pull/3359.patch https://github.com/kamailio/kamailio/pull/3359.diff -- Reply to this email directly or view it on GitHub: https://github.com/kamailio/kamailio/pull/3359 You are receiving this because you are subscribed to this thread. Message ID: <kamailio/kamailio/pull/3359(a)github.com>

4 9

[kamailio/kamailio] Module db_postgresql not found (Issue #3196)
by MenschLink 23 Aug '23

23 Aug '23

### Description I loaded module "db_postgres.so". I expected kamilio to start. It didn't ### Troubleshooting #### Reproduction  #### config file ``` #!KAMAILIO #!define WITH_POSTGRESSQL #!define WITH_AUTH #!define WITH_USRLOCDB #!define WITH_PRESENCE #!define WITH_MSGREBUILD #!define WITH_NAT #!define WITH_NATSIPPING .. . .. #!ifdef WITH_POSTGRESSQL loadmodule "db_postgres.so" #!endif ``` #### Log Messages  ``` Jul 22 10:31:16 opensips /usr/sbin/kamailio[8975]: ERROR: <core> [db.c:204]: db_bind_mod(): Module db_postgresql not found. Missing loadmodule? Jul 22 10:31:16 opensips /usr/sbin/kamailio[8975]: ERROR: usrloc [usrloc_mod.c:361]: mod_init(): failed to bind database module Jul 22 10:31:16 opensips /usr/sbin/kamailio[8975]: ERROR: <core> [core/sr_module.c:942]: init_mod(): Error while initializing module usrloc (/usr/lib/x86_64-linux-gnu/kamailio/modules/usrloc.so) ``` output from ls of modules directory: ``` acc.so call_obj.so dialog.so ipops.so msrp.so presence_conference.so qos.so sipcapture.so statsd.so uid_avp_db.so acc_diameter.so carrierroute.so dialplan.so jsonrpcs.so mtree.so presence_dialoginfo.so ratelimit.so sipdump.so stun.so uid_domain.so alias_db.so cfg_db.so dispatcher.so keepalive.so nat_traversal.so presence_mwi.so regex.so sipjson.so tcpops.so uid_gflags.so app_jsdt.so cfg_rpc.so diversion.so kemix.so nathelper.so presence_profile.so registrar.so sipt.so textops.so uid_uri_db.so app_sqlang.so cfgt.so dmq.so kex.so nosip.so presence_reginfo.so rls.so siptrace.so textopsx.so uri_db.so async.so cfgutils.so dmq_usrloc.so lcr.so outbound.so presence_xml.so rr.so siputils.so timer.so userblocklist.so auth.so corex.so domain.so log_custom.so p_usrloc.so pua.so rtimer.so sl.so tm.so usrloc.so auth_db.so counters.so domainpolicy.so lrkproxy.so path.so pua_bla.so rtjson.so sms.so tmrec.so xcap_client.so auth_diameter.so ctl.so drouting.so mangler.so pdb.so pua_dialoginfo.so rtpengine.so smsops.so tmx.so xcap_server.so auth_xkeys.so db2_ops.so enum.so matrix.so pdt.so pua_reginfo.so rtpproxy.so speeddial.so topoh.so xhttp.so avp.so db_cluster.so evrexec.so maxfwd.so permissions.so pua_rpc.so sanity.so sqlops.so topos.so xhttp_prom.so avpops.so db_flatstore.so exec.so mediaproxy.so pike.so pua_usrloc.so sca.so ss7ops.so tsilo.so xhttp_rpc.so benchmark.so db_postgres.so group.so mohqueue.so pipelimit.so pua_xmpp.so sdpops.so sst.so uac.so xlog.so blst.so db_text.so htable.so mqueue.so prefix_route.so pv.so seas.so statistics.so uac_redirect.so xprint.so call_control.so debugger.so imc.so msilo.so presence.so pv_headers.so secfilter.so statsc.so uid_auth_db.so ``` ### Possible Solutions  tried renaming db_postgres.so to db_postgresql.so, but that didn't work, so I reversed it ### Additional Information * **Kamailio Version** - output of `kamailio -v` ``` version: kamailio 5.5.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_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 10.2.1 ``` * **Operating System**:  ``` Distributor ID: Debian Description: Debian GNU/Linux 11 (bullseye) Release: 11 Codename: bullseye Linux opensips 5.10.0-16-amd64 #1 SMP Debian 5.10.127-1 (2022-06-30) x86_64 GNU/Linux ``` -- Reply to this email directly or view it on GitHub: https://github.com/kamailio/kamailio/issues/3196 You are receiving this because you are subscribed to this thread. Message ID: <kamailio/kamailio/issues/3196(a)github.com>

3 4

Re: Performances issue when freeing shared memory in custom module (Kamailio 5.5.2)
by Henning Westerholt 04 Aug '23

04 Aug '23

Hello, (Adding sr-dev to CC) This looks indeed a bit strange. Do you get any error messages in the log? In which process you are freeing the memory, one of the worker processes or the RPC process? You could also try to use another memory manager to see if you get better performance. There is a command line parameter to choose one during startup. Cheers, Henning -- Henning Westerholt - https://skalatan.de/blog/ Kamailio services - https://gilawa.com<https://gilawa.com/> From: Chaigneau, Nicolas <nicolas.chaigneau(a)capgemini.com> Sent: Wednesday, January 18, 2023 6:49 PM To: Kamailio (SER) - Users Mailing List <sr-users(a)lists.kamailio.org> Subject: [SR-Users] Performances issue when freeing shared memory in custom module (Kamailio 5.5.2) Hello, I'm encountering performance issues with Kamailio (5.5.2). I'm using a custom Kamailio module that loads routing data in memory, using Kamailio shared memory. This routing data is very large. It can be fully reloaded through a Kamailio RPC command (which is done once each day). When reloading, two sets of data are maintained, one "loading" and another "current" (the latter being used to handle SIP requests). When loading of the new data is finished, it is swapped to "current". Then, memory of the old (now unused) data is freed. I've noticed that when Kamailio is freeing the old data, there is a very significant performance impact on SIP requests. This is surprising to me, because the SIP requests do not use this old data. This is not a CPU issue, idle CPU% is at about 99% at that moment. I'm using the following functions : - shm_mallocxz - shm_free From what I understand, shm_free is actually "qm_shm_free" defined in "src\core\mem\q_malloc.c" (the default shared memory manager being "qm"). I've noticed that there is also a variant shm_free_unsafe ("qm_free"), which does not perform locking. I'm wondering if the lock could be the cause of my performances issues ? (But I'm not sure how this could be possible, because although the SIP requests need to access the shared memory allocated, they do not use directly the functions from the share memory manager.) If the performances issues are causes by the lock, could I use the unsafe version "safely" ? (considering that it is guaranteed that the old data cannot be used by anyone else) Thanks for your help. Regards, Nicolas. This message contains information that may be privileged or confidential and is the property of the Capgemini Group. It is intended only for the person to whom it is addressed. If you are not the intended recipient, you are not authorized to read, print, retain, copy, disseminate, distribute, or use this message or any part thereof. If you receive this message in error, please notify the sender immediately and delete all copies of this message.

3 13

[kamailio/kamailio] Kamailio sending CCR TERMINATE request without waiting for the CCR INITIAL request response (#2143)
by harishyadav1465 03 Aug '23

03 Aug '23

**Description** We are using ims_charging module and Freediameter as diameter server for billing process....recently we faced one issue...For Initial **INVITEs** kamailio sending **CCR request (INITIAL_REQUEST)** to **diameter server** but if we receive Immediate **CANCLE** for the **INVITE**, kamailio sending **CCR request ( TERMINATE_REQUEST )** without waiting for the **CCR request (INITIAL_REQUEST) response** from the **Diameter server.**.. **Expected behavior** Kamailio has to send **CCR request ( TERMINATE_REQUEST )** after getting the **response** from the **INITIAL_REQUEST.** **Additional Info** kamailio server : 4.2 platform : 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/2143

3 6

[kamailio/kamailio] siptrace: frong IPv4 address value (#2092)
by sergey-safarov 30 Jul '23

30 Jul '23

### Description Please check attached pcap. [siptrace.pcap.gz](https://github.com/kamailio/kamailio/files/3688791/siptra… Kamailio send INVITE (packet 1) from port `TCP/42394`. SIP trace encapsulate INVITE (packet 2) and encodes Kamailio source port `TCP/5060` #### Debugging Data HEP header parsed by lua [disector](https://github.com/sipcapture/hep-wireshark) ``` HEP3 Protocol HEP ID: HEP3 Length (Bytes): 1574 Protocol family: IPv4 Protocol ID: TCP Source IPv4 address: 172.21.0.131 Destination IPv4 address: 192.168.57.11 Source port: 5060 Destination port: 5060 Timestamp: 1570150645 Timestamp us: 740165 Protocol Type: SIP Capture ID: 1 Payload [truncated]: INVITE sip:911@192.168.57.11;transport=tcp SIP/2.0\r\nRecord-Route: <sip:172.21.0.131;transport=tcp;lr=on;ftag=KvNj7jXrmK89p>\r\nVia: SIP/2.0/TCP 172.21.0.131;branch=z9hG4bK7c2d.2d8104273b7063309f5694ac963c9ad8.0;i=21 ``` [HEP format description located here](https://github.com/sipcapture/HEP/blob/master/docs/HEP3_Network_Proto…. ### Additional Information * **Kamailio Version** - output of `kamailio -v` ``` / # kamailio -v version: kamailio 5.1.6 (x86_64/linux) flags: STATS: Off, USE_TCP, USE_TLS, USE_SCTP, TLS_HOOKS, USE_RAW_SOCKS, DISABLE_NAGLE, USE_MCAST, DNS_IP_HACK, SHM_MEM, SHM_MMAP, PKG_MALLOC, Q_MALLOC, F_MALLOC, TLSF_MALLOC, DBG_SR_MEMORY, USE_FUTEX, FAST_LOCK-ADAPTIVE_WAIT, USE_DNS_CACHE, USE_DNS_FAILOVER, USE_NAPTR, USE_DST_BLACKLIST, HAVE_RESOLV_RES ADAPTIVE_WAIT_LOOPS=1024, MAX_RECV_BUFFER_SIZE 262144 MAX_URI_SIZE 1024, BUF_SIZE 65535, DEFAULT PKG_SIZE 8MB poll method support: poll, epoll_lt, epoll_et, sigio_rt, select. id: unknown compiled on 11:01:40 Oct 4 2018 with gcc 6.4.0 ``` * **Operating System**: Docker container Userland ``` / # cat /etc/os-release NAME="Alpine Linux" ID=alpine VERSION_ID=3.8.1 PRETTY_NAME="Alpine Linux v3.8" HOME_URL="http://alpinelinux.org" BUG_REPORT_URL="http://bugs.alpinelinux.org" ``` Kernel Amazon Linux 2 ``` / # uname -a Linux proxy-dc0-0 4.14.128-112.105.amzn2.x86_64 #1 SMP Wed Jun 19 16:53:40 UTC 2019 x86_64 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/2092

2 7

[kamailio/kamailio] NATS Module not working (Issue #3253)
by iliesh 10 Jul '23

10 Jul '23

### Description Trying to get NATS module working but Kamailio is refusing to start. ``` Sep 27 23:08:27 server kernel: kamailio[338880]: segfault at 70 ip 00007fe97b06f1cc sp 00007fff72d158f0 error 4 in libuv.so.1.0.0[7fe97b066000+1f000] Sep 27 23:08:27 server kernel: Code: 5a 85 ff ff b8 ea ff ff ff c3 0f 1f 40 00 f3 0f 1e fa 8b 4e 30 83 f9 ff 0f 84 80 00 00 00 48 83 ec 08 85 c9 0f 88 90 00 00 00 <3b> 4f 70 73 45 f7 d2 21 56 28 48 8d 4e 18 48 89 f0 48 8b 76 18 75 Sep 27 23:08:27 server systemd[1]: Started Process Core Dump (PID 338886/UID 0). ``` #### Log Messages In the log message I'm getting the following error: ``` INFO: nats [nats_mod.c:437]: nats_init_connection(): adding server [nats://192.168.1.1:4222] [1] ERROR: nats [nats_mod.c:456]: nats_init_connection(): could not create nats options [System Error] ``` ### Additional Information * **Kamailio Version** - output of `kamailio -v` ``` (version: kamailio 5.6.1 (x86_64/linux) 34e6dd) ``` NATS Server version: ``` nats-server: v2.9.0 ``` libnats version: ``` libnats.so.3.4.0 ``` * **Operating System**: ``` CentOS Stream 9 5.14.0-163.el9.x86_64 #1 SMP PREEMPT_DYNAMIC Thu Sep 8 13:52:29 UTC 2022 x86_64 x86_64 x86_64 GNU/Linux ``` * **Module Configuration**: ``` loadmodule "nats.so" modparam("nats", "nats_url", "nats://192.168.1.1:4222") ``` There is no issue at the network/firewall level as by using telnet I'm able to connect to the NATS server successfully. What is weird is that with tcpdump I can't see even attempts to connect to the NATS server. -- Reply to this email directly or view it on GitHub: https://github.com/kamailio/kamailio/issues/3253 You are receiving this because you are subscribed to this thread. Message ID: <kamailio/kamailio/issues/3253(a)github.com>

5 31

[kamailio/kamailio] tlsa + OpenSSL 3.0.5: multiple unpredictable shm corruption (Issue #3222)
by space88man 08 Jul '23

08 Jul '23

### Description * kamailio 5.6.1 on AlmaLinux 9 and OpenSSL 3.0.5 * Used tlsa to separate the OS version of OpenSSL (which is 3.0.1). The same issue happens with the OS version of OpenSSL * Generating TLS client traffic * The issue will occur at about 25 conn/sec * Multiple unpredicatable types of shm corruption ### Troubleshooting * No issue with tlsa + OpenSSL 1.1.1q; the module can sustain 50 conn/sec up to 500 persistent connections. #### Reproduction 1. Used kamailio configuration from the outbound module documentation; i.e., configure kamailio as a TLS edge proxy. To isolate the registrar is another kamailio system 1. Use a SIP load tester to generate REGISTER traffic(Expires: 600) ; at the end of the REGISTER, keep the connection alive and reREGISTER at 300 secs. 1. Generate traffic at > 25 conn/sec (with < 25 conn/sec the test usually succeeds) #### Debugging Data BT in comments below #### Log Messages #### SIP Traffic ### Possible Solutions ### Additional Information 5.6.1 * **Operating System**: AlmaLinux 9, with (OS) OpenSSL 3.0.1. I used tlsa + OpenSSL 3.0.5 -- Reply to this email directly or view it on GitHub: https://github.com/kamailio/kamailio/issues/3222 You are receiving this because you are subscribed to this thread. Message ID: <kamailio/kamailio/issues/3222(a)github.com>

4 16

[kamailio/kamailio] Kamailio Random Crash Alert - 5.4.7 (Issue #3186)
by hardikpatel89 07 Jul '23

07 Jul '23

### Description -- Hello Team, We are using Kamailio 5.4.7 and we found there is a random crash. We have observed the core logs and we noticed it is due to some of the RPC events. We have noticed it has been crashed from the "ctl handler" process. -- #### Debugging Data -- Core dump files are attached. [core-7519.txt](https://github.com/kamailio/kamailio/files/9099633/core-7519… [core-17582.txt](https://github.com/kamailio/kamailio/files/9099634/core-175… [core-7519.txt](https://github.com/kamailio/kamailio/files/9099638/core-7519… [core-17582.txt](https://github.com/kamailio/kamailio/files/9099639/core-175… -- ### Additional Information * **Kamailio Version** - output of `kamailio -v` ``` version: kamailio 5.4.7 (x86_64/linux) a19fe1 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: a19fe1 compiled on 02:56:57 Feb 16 2022 with gcc 8.3.0 ``` -- Reply to this email directly or view it on GitHub: https://github.com/kamailio/kamailio/issues/3186 You are receiving this because you are subscribed to this thread. Message ID: <kamailio/kamailio/issues/3186(a)github.com>

3 5

[kamailio/kamailio] Segmentation fault on kamailio 5.7.0 (Issue #3259)
by admin-toneca 07 Jul '23

07 Jul '23

I have seen a segmentation fault on a kamailio 5.7.0 ``` Core was generated by `/usr/local/sbin/kamailio -P /run/kamailio/kamailio.pid -f /usr/local/etc/kamailio/kamailio.cfg -m 512 -M 12 --atexit=no'. Stack trace of thread 221186: #0 0x00007fbc28ffb97d n/a (libc.so.6 + 0x19d97d) #1 0x00007fbc28ed4db1 n/a (libc.so.6 + 0x76db1) #2 0x00007fbc28f7c16a n/a (libc.so.6 + 0x11e16a) #3 0x00007fbc28f7c64a syslog (libc.so.6 + 0x11e64a) #4 0x000056472e67feeb qm_debug_check_frag (kamailio + 0x358eeb) #5 0x000056472e684788 qm_free (kamailio + 0x35d788) #6 0x000056472e69054e qm_shm_free (kamailio + 0x36954e) #7 0x00007fbc24832698 ser_free (tls.so + 0x34698) #8 0x00007fbc277028e6 ERR_pop_to_mark (libcrypto.so.3 + 0x16d8e6) #9 0x00007fbc2765119e asn1_d2i_read_bio (libcrypto.so.3 + 0xbc19e) #10 0x00007fbc277fd137 n/a (libcrypto.so.3 + 0x268137) #11 0x00007fbc277ede9d n/a (libcrypto.so.3 + 0x258e9d) #12 0x00007fbc276fe62b n/a (libcrypto.so.3 + 0x16962b) #13 0x00007fbc277ef718 n/a (libcrypto.so.3 + 0x25a718) #14 0x00007fbc276fe62b n/a (libcrypto.so.3 + 0x16962b) #15 0x00007fbc276fe901 OSSL_DECODER_from_bio (libcrypto.so.3 + 0x169901) #16 0x00007fbc276fec2e OSSL_DECODER_from_data (libcrypto.so.3 + 0x169c2e) #17 0x00007fbc277d45d4 n/a (libcrypto.so.3 + 0x23f5d4) #18 0x00007fbc27663b3b n/a (libcrypto.so.3 + 0xceb3b) #19 0x00007fbc27665388 n/a (libcrypto.so.3 + 0xd0388) #20 0x00007fbc27663cb9 n/a (libcrypto.so.3 + 0xcecb9) #21 0x00007fbc27665388 n/a (libcrypto.so.3 + 0xd0388) #22 0x00007fbc27663cb9 n/a (libcrypto.so.3 + 0xcecb9) #23 0x00007fbc27664433 ASN1_item_d2i_ex (libcrypto.so.3 + 0xcf433) #24 0x00007fbc27a44f14 n/a (libssl.so.3 + 0x6df14) #25 0x00007fbc27a3aa05 n/a (libssl.so.3 + 0x63a05) #26 0x00007fbc27a3c608 n/a (libssl.so.3 + 0x65608) #27 0x00007fbc2485b216 tls_accept (tls.so + 0x5d216) #28 0x00007fbc2486686d tls_h_read_f (tls.so + 0x6886d) #29 0x000056472e6289f3 tcp_read_headers (kamailio + 0x3019f3) #30 0x000056472e631c9d tcp_read_req (kamailio + 0x30ac9d) #31 0x000056472e638c23 handle_io (kamailio + 0x311c23) #32 0x000056472e622d70 io_wait_loop_epoll (kamailio + 0x2fbd70) #33 0x000056472e63a760 tcp_receive_loop (kamailio + 0x313760) #34 0x000056472e616dde tcp_init_children (kamailio + 0x2efdde) #35 0x000056472e36565c main_loop (kamailio + 0x3e65c) #36 0x000056472e3705b0 main (kamailio + 0x495b0) #37 0x00007fbc28e87d90 n/a (libc.so.6 + 0x29d90) #38 0x00007fbc28e87e40 __libc_start_main (libc.so.6 + 0x29e40) #39 0x000056472e351805 _start (kamailio + 0x2a805) #0 __strlen_avx2 () at ../sysdeps/x86_64/multiarch/strlen-avx2.S:74 No locals. #1 0x00007fbc28ed4db1 in __vfprintf_internal (s=s@entry=0x56472ec58a00, format=format@entry=0x56472e8246e0 "%s: %.*s%s%s%sBUG: qm: fragm. %p (address %p) beginning overwritten (%lx)! Memory allocator was called from %s:%u. Fragment marked by %s:%lu. Exec from %s:%u.\n", ap=ap@entry=0x7fff8baf6450, mode_flags=mode_flags@entry=0) at ./stdio-common/vfprintf-internal.c:1517 len = <optimized out> ptrptr = 0x20 signed_number = <optimized out> step0_jumps = {0, 2488, 2400, 1600, 1512, 2624, 1408, 2728, 2976, 1864, 2888, 608, 528, 2224, 2016, 1968, 2352, 2240, 2376, -880, 48, -96, 1776, 1688, 272, -392, -876, -960, -956, 3088, 688} space = <optimized out> is_short = <optimized out> use_outdigits = <optimized out> step1_jumps = {0, 0, 0, 0, 0, 0, 0, 0, 0, 1864, 2888, 608, 528, 2224, 2016, 1968, 2352, 2240, 2376, -880, 48, -96, 1776, 1688, 272, -392, -876, -960, -956, 0, 688} group = <optimized out> prec = -1 step2_jumps = {0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 2888, 608, 528, 2224, 2016, 1968, 2352, 2240, 2376, -880, 48, -96, 1776, 1688, 272, -392, -876, -960, -956, 0, 688} string = 0x6e6f73616e615020 <error: Cannot access memory at address 0x6e6f73616e615020> left = <optimized out> is_long_double = <optimized out> width = <optimized out> step3a_jumps = {0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 2544, 0, 0, 0, 2016, 1968, 2352, 2240, 2376, 0, 0, 0, 0, 1688, 0, 0, 0, 0, 0, 0, 688} alt = <optimized out> showsign = <optimized out> is_long = <optimized out> is_char = <optimized out> pad = <optimized out> step3b_jumps = {0 <repeats 11 times>, 528, 0, 0, 2016, 1968, 2352, 2240, 2376, -880, 48, -96, 1776, 1688, 272, -392, -876, 0, 0, 0, 688} step4_jumps = {0 <repeats 14 times>, 2016, 1968, 2352, 2240, 2376, -880, 48, -96, 1776, 1688, 272, -392, -876, 0, 0, 0, 688} is_negative = <optimized out> number = <optimized out> base = <optimized out> the_arg = {pa_wchar = 89781848 L'\x559f658', pa_int = 89781848, pa_long_int = 140445520361048, pa_long_long_int = 140445520361048, pa_u_int = 89781848, pa_u_long_int = 140445520361048, pa_u_long_long_int = 140445520361048, pa_double = 6.9389306722691122e-310, pa_long_double = <invalid float value>, pa_float128 = 1.67756396290316875220685842695669771e-4932, pa_string = 0x7fbc0559f658 "\355\357ͫ", pa_wstring = 0x7fbc0559f658 L"\xabcdefed", pa_pointer = 0x7fbc0559f658, pa_user = 0x7fbc0559f658} spec = 115 's' _cleanup_start_doit = <optimized out> _buffer = {__routine = 0x7fff8baf5f10, __arg = 0x56472ec58a00, __canceltype = 89781560, __prev = 0x7fbc047fe000} _cleanup_routine = <optimized out> thousands_sep = 0x0 grouping = 0xffffffffffffffff <error: Cannot access memory at address 0xffffffffffffffff> done = 238 f = 0x56472e824767 "s:%lu. Exec from %s:%u.\n" lead_str_end = 0x56472e8246e0 "%s: %.*s%s%s%sBUG: qm: fragm. %p (address %p) beginning overwritten (%lx)! Memory allocator was called from %s:%u. Fragment marked by %s:%lu. Exec from %s:%u.\n" end_of_spec = <optimized out> work_buffer = "`\355\177\004\274\177\000\000`\355\177\004\274\177\000\000P\241\207$\274\177\000\000(Xh.C\001\000\000\220\271\207$\274\177\000\000T\241\207$\274\177\000\000p\365Y\005\274\177\000\000\000\340\177\004\274\177\000\000\220\271\207$\274\177\000\000T\241\207$\274\177\000\000\000\366Y\005\274\177\000\000\000\340\177\004\274\177\000\000(\000\000\000\000\000\000\000\070\365Y\005\274\177\000\000\200\001\000\000\000\000\000\000\000\340\177\004\274\177\000\000\260\364Y\005\274\177\000\000\310\365Y\005\274\177\000\000\360\000\000\000\000\000\000\000\000\340\177\004\274\177\000\000\070\365Y\005\274\177\000\000X\366Y\005\274\177\000\000\001\000\000\000\000\000\000\000\310v\203\004\274\177\000\000\001\000\000\000\000\000\000\000"... workend = 0x7fff8baf62e8 "" ap_save = {{gp_offset = 16, fp_offset = 48, overflow_arg_area = 0x7fff8baf6530, reg_save_area = 0x7fff8baf6470}} nspecs_done = 10 save_errno = 0 readonly_format = 0 do_longlong_number = <optimized out> __result = <optimized out> #2 0x00007fbc28f7c16a in __vsyslog_internal (pri=<optimized out>, fmt=0x56472e8246e0 "%s: %.*s%s%s%sBUG: qm: fragm. %p (address %p) beginning overwritten (%lx)! Memory allocator was called from %s:%u. Fragment marked by %s:%lu. Exec from %s:%u.\n", ap=0x7fff8baf6450, mode_flags=0) at ./misc/syslog.c:229 __clframe = {__cancel_routine = <optimized out>, __cancel_arg = <synthetic pointer>, __do_it = 1, __cancel_type = <optimized out>} now_tm = {tm_sec = 51, tm_min = 27, tm_hour = 0, tm_mday = 9, tm_mon = 9, tm_year = 122, tm_wday = 0, tm_yday = 281, tm_isdst = 0, tm_gmtoff = 0, tm_zone = 0x56472ec59350 "UTC"} now = 1665275271 fd = <optimized out> --Type <RET> for more, q to quit, c to continue without paging-- f = 0x56472ec58a00 buf = 0x0 bufsize = 0 msgoff = 21 saved_errno = <optimized out> failbuf = "\000\340\177\004\274\177\000\000\030\027r\005\274\177\000\000\220M^\005\274\177\000\000\000\340\177\004\274" clarg = {buf = 0x0, oldaction = <optimized out>} #3 0x00007fbc28f7c64a in __syslog (pri=<optimized out>, fmt=<optimized out>) at ./misc/syslog.c:109 ap = {{gp_offset = 48, fp_offset = 48, overflow_arg_area = 0x7fff8baf6570, reg_save_area = 0x7fff8baf6470}} #4 0x000056472e67feeb in qm_debug_check_frag (qm=0x7fbc047fe000, f=0x7fbc0562dfe8, file=0x7fbc2487a154 "tls: tls_init.c", line=323, efile=0x56472e824559 "core/mem/q_malloc.c", eline=511) at core/mem/q_malloc.c:123 __llevel = -3 p = 0x56472e824554 __func__ = "qm_debug_check_frag" #5 0x000056472e684788 in qm_free (qmp=0x7fbc047fe000, p=0x7fbc0562e020, file=0x7fbc2487a154 "tls: tls_init.c", func=0x7fbc2487b990 <__func__.0> "ser_free", line=323, mname=0x7fbc2487a150 "tls") at core/mem/q_malloc.c:511 qm = 0x7fbc047fe000 f = 0x7fbc0562dfe8 size = 1016 next = 0x7fbc0562e1e8 prev = 0x7fbc0562e0f8 __func__ = "qm_free" #6 0x000056472e69054e in qm_shm_free (qmp=0x7fbc047fe000, p=0x7fbc0562e020, file=0x7fbc2487a154 "tls: tls_init.c", func=0x7fbc2487b990 <__func__.0> "ser_free", line=323, mname=0x7fbc2487a150 "tls") at core/mem/q_malloc.c:1350 No locals. #7 0x00007fbc24832698 in ser_free (ptr=0x7fbc0562e020, fname=0x7fbc278ce6e5 "../crypto/err/err_local.h", fline=86) at tls_init.c:323 __func__ = "ser_free" #8 0x00007fbc277028e6 in ERR_pop_to_mark () from /lib/x86_64-linux-gnu/libcrypto.so.3 No symbol table info available. #9 0x00007fbc2765119e in asn1_d2i_read_bio () from /lib/x86_64-linux-gnu/libcrypto.so.3 No symbol table info available. #10 0x00007fbc277fd137 in ?? () from /lib/x86_64-linux-gnu/libcrypto.so.3 No symbol table info available. #11 0x00007fbc277ede9d in ?? () from /lib/x86_64-linux-gnu/libcrypto.so.3 No symbol table info available. #12 0x00007fbc276fe62b in ?? () from /lib/x86_64-linux-gnu/libcrypto.so.3 No symbol table info available. #13 0x00007fbc277ef718 in ?? () from /lib/x86_64-linux-gnu/libcrypto.so.3 No symbol table info available. #14 0x00007fbc276fe62b in ?? () from /lib/x86_64-linux-gnu/libcrypto.so.3 No symbol table info available. #15 0x00007fbc276fe901 in OSSL_DECODER_from_bio () from /lib/x86_64-linux-gnu/libcrypto.so.3 No symbol table info available. #16 0x00007fbc276fec2e in OSSL_DECODER_from_data () from /lib/x86_64-linux-gnu/libcrypto.so.3 No symbol table info available. #17 0x00007fbc277d45d4 in ?? () from /lib/x86_64-linux-gnu/libcrypto.so.3 No symbol table info available. #18 0x00007fbc27663b3b in ?? () from /lib/x86_64-linux-gnu/libcrypto.so.3 No symbol table info available. #19 0x00007fbc27665388 in ?? () from /lib/x86_64-linux-gnu/libcrypto.so.3 No symbol table info available. #20 0x00007fbc27663cb9 in ?? () from /lib/x86_64-linux-gnu/libcrypto.so.3 No symbol table info available. #21 0x00007fbc27665388 in ?? () from /lib/x86_64-linux-gnu/libcrypto.so.3 No symbol table info available. #22 0x00007fbc27663cb9 in ?? () from /lib/x86_64-linux-gnu/libcrypto.so.3 No symbol table info available. #23 0x00007fbc27664433 in ASN1_item_d2i_ex () from /lib/x86_64-linux-gnu/libcrypto.so.3 No symbol table info available. #24 0x00007fbc27a44f14 in ?? () from /lib/x86_64-linux-gnu/libssl.so.3 No symbol table info available. #25 0x00007fbc27a3aa05 in ?? () from /lib/x86_64-linux-gnu/libssl.so.3 No symbol table info available. #26 0x00007fbc27a3c608 in ?? () from /lib/x86_64-linux-gnu/libssl.so.3 No symbol table info available. --Type <RET> for more, q to quit, c to continue without paging-- #27 0x00007fbc2485b216 in tls_accept (c=0x7fbc056d3ef0, error=0x7fff8baf7994) at tls_server.c:468 ret = -1951434416 ssl = 0x7fbc056d82f8 cert = 0x7fbc056d2388 tls_c = 0x7fbc056d1fa0 tls_log = 612737204 __func__ = "tls_accept" pkey = 0x0 #28 0x00007fbc2486686d in tls_h_read_f (c=0x7fbc056d3ef0, flags=0x7fff8bb17e9c) at tls_server.c:1173 r = 0x7fbc056d4018 bytes_free = 16383 bytes_read = 1713 read_size = 16383 ssl_error = 0 ssl_read = 0 ssl = 0x7fbc056d82f8 rd_buf = "\026\003\003\004\071\v\000\004\065\000\004\062\000\004/0\202\004+0\202\003\023\240\003\002\001\002\002\t\000\267\207\251\066\225\277\372\335\060\r\006\t*\206H\206\367\r\001\001\v\005\000\060\201\217\061\v0\t\006\003U\004\006\023\002JP1\020\060\016\006\003U\004\b\f\aFukuoka1-0+\006\003U\004\n\f$ Panasonic System Networks co., Ltd.1?0=\006\003U\004\003\f6SIP Phone Client Authentication Self CA Certificate V2"... wr_buf = "\025\003\003\000\002\002\060\000-\003\003\210z\357o\213$\017\235\231\334~\207\233\365\026\261\307~lV\214A\277\337DOWNGRD\001\000\000=\000\000\005\377\001\000\001\000\026\003\003\026\035\v\000\026\031\000\026\026\000\006\070\060\202\006\064\060\202\005\034\240\003\002\001\002\002\020&~b\352RT\000\227\236Dq\264RL\271\304\060\r\006\t*\206H\206\367\r\001\001\v\005\000\060\201\217\061\v0\t\006\003U\004\006\023\002GB1\033\060\031\006\003U\004\b\023\022Greater Manchester1\020\060\016\006\003U\004\a\023\aSalford1\030\060\026\006\003U\004\n\023\017Sectigo Lim"... rd = {buf = 0x7fff8baf7af0 "\026\003\003\004\071\v", pos = 1086, used = 1713, size = 65536} wr = {buf = 0x7fff8bb07af0 "\025\003\003", pos = 0, used = 0, size = 65536} tls_c = 0x7fbc056d1fa0 enc_rd_buf = 0x0 n = 0 flush_flags = 0 err_src = 0x7fbc248839b0 "TLS read:" ip_buf = "10.20.0.100", '\000' <repeats 52 times> x = 0 tls_dbg = 0 __func__ = "tls_h_read_f" #29 0x000056472e6289f3 in tcp_read_headers (c=0x7fbc056d3ef0, read_flags=0x7fff8bb17e9c) at core/tcp_read.c:441 bytes = -1 remaining = 0 p = 0x7fbc054ebd60 "\002" r = 0x7fbc056d4018 mc = 2638013693 body_len = 50944 mfline = 0x7fbc054ec0e8 "REGISTER sip:voip.isip.ca:443 SIP/2.0\r\nv: SIP/2.0/TLS 89.28.64.156:52319;rport;branch=z9hG4bKPjr.w8BMId-6xgyjA5coZyVJeC2QNp6cni;alias\r\nMax-Forwards: 70\r\nf: <sip:1217264@voip.isip.ca>;tag=Dt75LCcpfD8Oe"... mtransid = {s = 0xffff00000000 <error: Cannot access memory at address 0xffff00000000>, len = 0} __func__ = "tcp_read_headers" #30 0x000056472e631c9d in tcp_read_req (con=0x7fbc056d3ef0, bytes_read=0x7fff8bb17e94, read_flags=0x7fff8bb17e9c) at core/tcp_read.c:1469 bytes = -1 total_bytes = 0 resp = 1 size = 2 req = 0x7fbc056d4018 dst = {send_sock = 0x7fff8bb17e10, to = {s = {sa_family = 27615, sa_data = "E.\001\000\000\000\300}\261\213\377\177\000"}, sin = {sin_family = 27615, sin_port = 11845, sin_addr = {s_addr = 1}, sin_zero = "\300}\261\213\377\177\000"}, sin6 = {sin6_family = 27615, sin6_port = 11845, sin6_flowinfo = 1, sin6_addr = {__in6_u = {__u6_addr8 = "\300}\261\213\377\177\000\000\030\000\000\000Q\000\000", __u6_addr16 = { 32192, 35761, 32767, 0, 24, 0, 81, 0}, __u6_addr32 = {2343665088, 32767, 24, 81}}}, sin6_scope_id = 4294967294}, sas = {ss_family = 27615, __ss_padding = "E.\001\000\000\000\300}\261\213\377\177\000\000\030\000\000\000Q\000\000\000\376\377\377\377\377\377\377\377\210\256p\005\274\177\000\000 \260p\005\274\177\000\000(a){\221.GV\000\000p~\261\213\001 \000\000\340\204I(\274\177\000\000\320}\261\213\001\000\000\000\020\200\203\004Q\000\000\000\001\000\000\000\000\000\000\000H\275N\005\274\177\000\000\340~\261\213\377\177\000\000\b\000\000\000\000\000\000", __ss_align = 140445521849992}}, id = -2, send_flags = {f = 65535, blst_imask = 65535}, proto = 36 '$', proto_pad0 = 0 '\000', proto_pad1 = 0} c = 46 '.' ret = 778163298 __func__ = "tcp_read_req" #31 0x000056472e638c23 in handle_io (fm=0x7fbc284984e0, events=1, idx=-1) at core/tcp_read.c:1855 ret = -1 n = 0 read_flags = RD_CONN_SHORT_READ --Type <RET> for more, q to quit, c to continue without paging-- con = 0x7fbc056d3ef0 s = 36 resp = -2 t = 359788347 ee = 0x0 __func__ = "handle_io" #32 0x000056472e622d70 in io_wait_loop_epoll (h=0x56472e917980 <io_w>, t=2, repeat=0) at core/io_wait.h:1070 n = 1 r = 0 fm = 0x7fbc284984e0 revents = 1 __func__ = "io_wait_loop_epoll" #33 0x000056472e63a760 in tcp_receive_loop (unix_sock=81) at core/tcp_read.c:1976 __func__ = "tcp_receive_loop" #34 0x000056472e616dde in tcp_init_children (woneinit=0x7fff8bb18288) at core/tcp_main.c:5236 r = 0 i = 7 reader_fd_1 = 81 pid = 0 si_desc = "tcp receiver (generic)\000\000\317jZ.GV\000\000`\202\261\213\377\177\000\000\036Xd.\000\000\000\000\340\345.(\000\000\000\000\253\066\200.GV\000\000\250\000\261\213\377\177\000\000\f\332v.GV\000\000\000\000\000\000\000\000\000\000\020\200\203\004\274\177\000\000\067\000\000\000\000\000\000\000\320\066\302\004\001\000\000\000P\202\261\213\377\177\000\000\036\334v.GV\000" si = 0x0 __func__ = "tcp_init_children" #35 0x000056472e36565c in main_loop () at main.c:1851 i = 8 pid = 221167 si = 0x0 si_desc = "udp receiver child=7 sock=10.20.20.100:5060\000\063.124.220.146:5080)\000X7\211.GV\000\000\210`{.GV\000\000\000\000\000\000\000\000\000\000s\314|.GV\000\000\067\000\000\000\000\000\000\000\260\305\367(\274\177\000\000 \204\261\213\377\177\000\000z\271Q.GV\000" nrprocs = 8 woneinit = 1 __func__ = "main_loop" #36 0x000056472e3705b0 in main (argc=10, argv=0x7fff8bb18998) at main.c:3085 cfg_stream = 0x56472eb33380 c = -1 r = 0 tmp = 0x7fff8bb18e39 "" tmp_len = 0 port = 0 proto = 0 ahost = 0x0 aport = 0 options = 0x56472e7b9278 ":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 = 3559158303 rfd = 4 debug_save = 0 debug_flag = 0 dont_fork_cnt = 0 n_lst = 0x7fff8bb18998 p = 0x7fff8bb18910 "" st = {st_dev = 26, st_ino = 85318, st_nlink = 2, st_mode = 16888, st_uid = 114, st_gid = 121, __pad0 = 0, st_rdev = 0, st_size = 40, st_blksize = 4096, st_blocks = 0, st_atim = {tv_sec = 1665275250, tv_nsec = 283708644}, st_mtim = {tv_sec = 1665275250, tv_nsec = 283708644}, st_ctim = {tv_sec = 1665275250, tv_nsec = 283708644}, __glibc_reserved = {0, 0, 0}} tbuf = "@\003\000\000@\003\000\000@\003\000\000@\003\000\000@\003\000\000@\003\000\000@\003\000\000@\003", '\000' <repeats 50 times>, "\377\000\000\000\377\000\000\000\000\000\377\000\000\000\000\377", '/' <repeats 16 times>, "\230\r", '\000' <repeats 14 times>, "`", '\000' <repeats 15 times>, "\001", '\000' <repeats 145 times>... option_index = 12 long_options = {{name = 0x56472e7bb6b6 "help", has_arg = 0, flag = 0x0, val = 104}, {name = 0x56472e7b6521 "version", has_arg = 0, flag = 0x0, val = 118}, {name = 0x56472e7bb6bb "alias", has_arg = 1, flag = 0x0, val = 1024}, { name = 0x56472e7bb6c1 "subst", has_arg = 1, flag = 0x0, val = 1025}, {name = 0x56472e7bb6c7 "substdef", has_arg = 1, flag = 0x0, val = 1026}, {name = 0x56472e7bb6d0 "substdefs", has_arg = 1, flag = 0x0, val = 1027}, { name = 0x56472e7bb6da "server-id", has_arg = 1, flag = 0x0, val = 1028}, {name = 0x56472e7bb6e4 "loadmodule", has_arg = 1, flag = 0x0, val = 1029}, {name = 0x56472e7bb6ef "modparam", has_arg = 1, flag = 0x0, val = 1030}, { name = 0x56472e7bb6f8 "log-engine", has_arg = 1, flag = 0x0, val = 1031}, {name = 0x56472e7bb703 "debug", has_arg = 1, flag = 0x0, val = 1032}, {name = 0x56472e7bb709 "cfg-print", has_arg = 0, flag = 0x0, val = 1033}, { name = 0x56472e7bb713 "atexit", has_arg = 1, flag = 0x0, val = 1034}, {name = 0x56472e7bb71a "all-errors", has_arg = 0, flag = 0x0, val = 1035}, {name = 0x0, has_arg = 0, flag = 0x0, val = 0}} __func__ = "main" (gdb) (gdb) info locals No locals. (gdb) list 69 in ../sysdeps/x86_64/multiarch/strlen-avx2.S (gdb) ``` ### Additional Information * version: kamailio 5.7.0-dev0 (x86_64/linux) da0178 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: da0178 compiled on 19:15:18 Aug 9 2022 with gcc 11.2.0 ``` * **Operating System**: ``` Distributor ID: Ubuntu Description: Ubuntu 22.04.1 LTS Release: 22.04 Codename: jammy Linux kamailio-prod 5.15.0-1019-aws #23-Ubuntu SMP Wed Aug 17 18:33:13 UTC 2022 x86_64 x86_64 x86_64 GNU/Linux ``` -- Reply to this email directly or view it on GitHub: https://github.com/kamailio/kamailio/issues/3259 You are receiving this because you are subscribed to this thread. Message ID: <kamailio/kamailio/issues/3259(a)github.com>

4 7

← Newer
1
...
8
9
10
11
12
13
14
...
27
Older →

Jump to page:

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

sr-dev April 2023