[sr-dev] Re: [kamailio/kamailio] Segfault when using kamailio 5.8.4 (and later) as a presence proxy (Issue #4102)

2025-08-03 Thread Joe Mordica via sr-dev
jmordica left a comment (kamailio/kamailio#4102) New backtace from nightly build: ``` version: kamailio 6.1.0-dev1 (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_MAL

[sr-dev] Re: [kamailio/kamailio] Segfault when using kamailio 5.8.4 (and later) as a presence proxy (Issue #4102)

2025-07-28 Thread Joe Mordica via sr-dev
jmordica left a comment (kamailio/kamailio#4102) Here are the logs from the nightly build `kamailio 6.1.0-dev1 (x86_64/linux)`: ``` ERROR 2025-07-28T06:48:22.540978560Z [resource.labels.containerName: kamailio] 7(28) CRITICAL: {1 1 SUBSCRIBE 0_3612378093@10.225.90.220} tm [t_fwd.c:799]: add_uac

[sr-dev] Re: [kamailio/kamailio] Segfault when using kamailio 5.8.4 (and later) as a presence proxy (Issue #4102)

2025-07-18 Thread Joe Mordica via sr-dev
jmordica left a comment (kamailio/kamailio#4102) It's possibly not there. I can atleast use `KSR.kx.gete_fuser()` instead of `KSR.kx.get_fuser()` which should fix any issues related to that? -- Reply to this email directly or view it on GitHub: https://github.com/kamailio/kamailio/issues/4102#i

[sr-dev] Re: [kamailio/kamailio] Segfault when using kamailio 5.8.4 (and later) as a presence proxy (Issue #4102)

2025-07-17 Thread Joe Mordica via sr-dev
jmordica left a comment (kamailio/kamailio#4102) This is stock kamailio using this build: `ghcr.io/kamailio/kamailio:5.8.5-bookworm` with no custom modules. I do have more than 12 destinations loaded in the dispatcher memory (more like 20), however, 9 of those are used for presence with the sam

[sr-dev] Re: [kamailio/kamailio] Segfault when using kamailio 5.8.4 (and later) as a presence proxy (Issue #4102)

2025-07-16 Thread Joe Mordica via sr-dev
jmordica left a comment (kamailio/kamailio#4102) Should this be resolved in 6.0.2? -- Reply to this email directly or view it on GitHub: https://github.com/kamailio/kamailio/issues/4102#issuecomment-3079886496 You are receiving this because you are subscribed to this thread. Message ID: ___

[sr-dev] Re: [kamailio/kamailio] Segfault when using kamailio 5.8.4 (and later) as a presence proxy (Issue #4102)

2025-06-17 Thread Joe Mordica via sr-dev
jmordica left a comment (kamailio/kamailio#4102) Sadly no we don’t normally save subscribe requests. I was about to grab a capture but after a few minutes of this happening it stopped and things were normal again. If it happens again I’ll try to be quicker and grab a pcap. -- Reply to this ema

[sr-dev] Re: [kamailio/kamailio] Segfault when using kamailio 5.8.4 as a presence proxy (Issue #4102)

2025-06-14 Thread Joe Mordica via sr-dev
jmordica left a comment (kamailio/kamailio#4102) Still having these happen. Here are some new logs: ``` 8(27) BUG: {1 1 SUBSCRIBE 0_683092625@10.212.57.217} tm [t_lookup.c:2064]: t_unref(): REQ_ERR DELAYED should have been caught much earlier for 0x7f5efcde7630: 24 (hex 18) 6(2

[sr-dev] Re: [kamailio/kamailio] Segfault when using kamailio 5.8.4 as a presence proxy (Issue #4102)

2025-05-08 Thread Joe Mordica via sr-dev
jmordica left a comment (kamailio/kamailio#4102) This is still an issue. -- Reply to this email directly or view it on GitHub: https://github.com/kamailio/kamailio/issues/4102#issuecomment-2862933818 You are receiving this because you are subscribed to this thread. Message ID: _

[sr-dev] Re: [kamailio/kamailio] Crash involving rtpengine (Issue #4179)

2025-04-28 Thread Joe Mordica via sr-dev
jmordica left a comment (kamailio/kamailio#4179) Oops. I meant to comment in the other issue. This crash does not happen as frequently. Once every 6 months or so. And yes the backtrace logs always look the same. -- Reply to this email directly or view it on GitHub: https://github.com/kamailio/

[sr-dev] Re: [kamailio/kamailio] Crash involving rtpengine (Issue #4179)

2025-04-26 Thread Joe Mordica via sr-dev
jmordica left a comment (kamailio/kamailio#4179) This occurs about once per week. -- Reply to this email directly or view it on GitHub: https://github.com/kamailio/kamailio/issues/4179#issuecomment-2832199797 You are receiving this because you are subscribed to this thread. Message ID:

[sr-dev] Re: [kamailio/kamailio] Crash involving rtpengine (Issue #4179)

2025-04-25 Thread Joe Mordica via sr-dev
jmordica left a comment (kamailio/kamailio#4179) Commenting to keep open. -- Reply to this email directly or view it on GitHub: https://github.com/kamailio/kamailio/issues/4179#issuecomment-2831792809 You are receiving this because you are subscribed to this thread. Message ID:

[sr-dev] Re: [kamailio/kamailio] Segfault when using kamailio 5.8.4 as a presence proxy (Issue #4102)

2025-04-05 Thread Joe Mordica via sr-dev
jmordica left a comment (kamailio/kamailio#4102) New logs from the most recent crash: ``` CRITICAL: {1 1 SUBSCRIBE 0_1097988702@10.58.1.164} [core/ip_addr.h:516]: su2ip_addr(): unknown address family 0 ERROR: {1 1 SUBSCRIBE 0_1097988702@10.58.1.164} [core/udp_server.c:810]: udp_send(): sendto

[sr-dev] Re: [kamailio/kamailio] Segfault when using kamailio 5.8.4 as a presence proxy (Issue #4102)

2025-03-26 Thread Joe Mordica via sr-dev
jmordica left a comment (kamailio/kamailio#4102) Any updates here? SUBSCRIBE's are now to much for a single kamailio proxy to handle so offloading presence to multiple instances is necessary and these crashes are still occurring. What else do I need to provide to help troubleshoot? -- Reply t

[sr-dev] [kamailio/kamailio] Crash involving rtpengine (Issue #4179)

2025-03-15 Thread Joe Mordica via sr-dev
jmordica created an issue (kamailio/kamailio#4179) ### Description Kamailio crash involving rtpengine ### Troubleshooting Reproduction Debugging Data ``` GNU gdb (Debian 13.1-3) 13.1 Copyright (C) 2023 Free Software Foundation, Inc. License GPLv3+: GNU GPL version 3 or later

[sr-dev] Re: [kamailio/kamailio] Segfault when using kamailio 5.8.4 as a presence proxy (Issue #4102)

2025-03-14 Thread Joe Mordica via sr-dev
jmordica left a comment (kamailio/kamailio#4102) @miconda some interesting new data in the output of a new crash: ran the following: ``` bt full info locals list ``` ``` GNU gdb (Debian 13.1-3) 13.1 Copyright (C) 2023 Free Software Foundation, Inc. License GPLv3+: GNU GPL version 3 or later

[sr-dev] Re: [kamailio/kamailio] Segfault when using kamailio 5.8.4 as a presence proxy (Issue #4102)

2025-02-26 Thread Joe Mordica via sr-dev
jmordica left a comment (kamailio/kamailio#4102) @miconda some new logs produced here on the most recent crash: ``` 6(25) CRITICAL: {1 1 SUBSCRIBE 0_4120981205@10.58.1.197} [core/msg_translator.c:924]: lumps_len(): null send_sock 2(21) CRITICAL: {1 1 SUBSCRIBE 0_1936556268@10.58.1.157} tm [tim

[sr-dev] Re: [kamailio/kamailio] Segfault when using kamailio 5.8.4 as a presence proxy (Issue #4102)

2025-02-12 Thread Joe Mordica via sr-dev
Just bumping this. Do we need any further info on this one in order to dig deeper? Thanks! -- Reply to this email directly or view it on GitHub: https://github.com/kamailio/kamailio/issues/4102#issuecomment-2655340450 You are receiving this because you are subscribed to this thread. Message ID

[sr-dev] Re: [kamailio/kamailio] Segfault when using kamailio 5.8.4 as a presence proxy (Issue #4102)

2025-01-29 Thread Joe Mordica via sr-dev
Hey there just checking on this one. Thanks! -- Reply to this email directly or view it on GitHub: https://github.com/kamailio/kamailio/issues/4102#issuecomment-2622413995 You are receiving this because you are subscribed to this thread. Message ID: _

[sr-dev] Re: [kamailio/kamailio] Segfault when using kamailio 5.8.4 as a presence proxy (Issue #4102)

2025-01-27 Thread Joe Mordica via sr-dev
Here's the latest output of bt full for a segfault for pid 45: ``` GNU gdb (Debian 13.1-3) 13.1 Copyright (C) 2023 Free Software Foundation, Inc. License GPLv3+: GNU GPL version 3 or later This is free software: you are free to change and redistribute it. There i

[sr-dev] Re: [kamailio/kamailio] Segfault when using kamailio 5.8.4 as a presence proxy (Issue #4102)

2025-01-23 Thread Joe Mordica via sr-dev
Thanks will get it loaded up and report back! -- Reply to this email directly or view it on GitHub: https://github.com/kamailio/kamailio/issues/4102#issuecomment-2610349326 You are receiving this because you are subscribed to this thread. Message ID: _

[sr-dev] Re: [kamailio/kamailio] Segfault when using kamailio 5.8.4 as a presence proxy (Issue #4102)

2025-01-23 Thread Joe Mordica via sr-dev
Ok. Does the 5.8.5 version have your changes? -- Reply to this email directly or view it on GitHub: https://github.com/kamailio/kamailio/issues/4102#issuecomment-2610193403 You are receiving this because you are subscribed to this thread. Message ID: _

[sr-dev] Re: [kamailio/kamailio] Segfault when using kamailio 5.8.4 as a presence proxy (Issue #4102)

2025-01-22 Thread Joe Mordica via sr-dev
Had another crash with the same exact output from gdb as before. The template is `%t.%e.%s.%p.core` The filename is `1737592676.kamailio.11.24.core` 24 is a `udp receiver child=4`. Anything else I can obtain from the core dump that might point to the cause? I do see a new log line produced righ

[sr-dev] Re: [kamailio/kamailio] Segfault when using kamailio 5.8.4 as a presence proxy (Issue #4102)

2025-01-20 Thread Joe Mordica via sr-dev
Ok I added this and will report back when the new core dump is initiated. -- Reply to this email directly or view it on GitHub: https://github.com/kamailio/kamailio/issues/4102#issuecomment-2602731687 You are receiving this because you are subscribed to this thread. Message ID: _

[sr-dev] Re: [kamailio/kamailio] Segfault when using kamailio 5.8.4 as a presence proxy (Issue #4102)

2025-01-20 Thread Joe Mordica via sr-dev
Only one. Here’s the format: %t.%e.%s.core 173648827.kamailio.11.core.26 26 is a udp listener in this case. -- Reply to this email directly or view it on GitHub: https://github.com/kamailio/kamailio/issues/4102#issuecomment-2602488729 You are receiving this because you are subscribed to this thr

[sr-dev] Re: [kamailio/kamailio] Segfault when using kamailio 5.8.4 as a presence proxy (Issue #4102)

2025-01-16 Thread Joe Mordica via sr-dev
We have core pattern so a static 8 children for tcp and for udp listeners. -- Reply to this email directly or view it on GitHub: https://github.com/kamailio/kamailio/issues/4102#issuecomment-259637 You are receiving this because you are subscribed to this thread. Message ID:

[sr-dev] Re: [kamailio/kamailio] Segfault when using kamailio 5.8.4 as a presence proxy (Issue #4102)

2025-01-15 Thread Joe Mordica via sr-dev
``` (gdb) p *send_info->send_sock $3 = {socket = 9, gindex = 0, name = {s = 0x7ff9528f1020 "10.206.0.9", len = 10}, address = {af = 2, len = 4, u = {addrl = {151047690, 0}, addr32 = {151047690, 0, 0, 0}, addr16 = { 52746, 2304, 0, 0, 0, 0, 0, 0}, addr = "\n\316\000\t", '\000' }}, address_

[sr-dev] Re: [kamailio/kamailio] Segfault when using kamailio 5.8.4 as a presence proxy (Issue #4102)

2025-01-15 Thread Joe Mordica via sr-dev
Here you go: ``` (gdb) frame 0 #0 via_builder (len=len@entry=0x7ffed7e3ecb8, msg=msg@entry=0x7ff9529548b0, send_info=send_info@entry=0x7ff764d20bb0, branch=branch@entry=0x7ffed7e3ecc0, extra_params=0x0, hp=hp@entry=0x7ffed7e3ebb0) at core/msg_translator.c:2910 2910in core/msg_translato

[sr-dev] Re: [kamailio/kamailio] Segfault when using kamailio 5.8.4 as a presence proxy (Issue #4102)

2025-01-15 Thread Joe Mordica via sr-dev
Here's the output of the commands: ``` --Type for more, q to quit, c to continue without paging--frame 0 slen = xparams = id_buf = id_len = 0 __func__ = "create_via_hf" __llevel = __kld = #2 0x56217f1592f7 in build_req_buf_from_sip

[sr-dev] [kamailio/kamailio] Segfault when using kamailio 5.8.4 as a presence proxy (Issue #4102)

2025-01-10 Thread Joe Mordica via sr-dev
### Description We are now using kamailio on the edge as a presence proxy to scale presence. We have 3 internal kamailio instances handling the actual subscriptions and publishing. This works well, however, once per 24-36hours we experience a crash on the border proxy instance. We did not exp