Thanks Henning, we'll try.
--
Reply to this email directly or view it on GitHub:
https://github.com/kamailio/kamailio/issues/3885#issuecomment-2180606968
You are receiving this because you are subscribed to this thread.
Message ID: ___
Kamailio (SER)
It's unconfigured. And I couldn't find any documentation for it except in the
sample kamailio.cfg file. So I don't know what the default is.
--
Reply to this email directly or view it on GitHub:
https://github.com/kamailio/kamailio/issues/3885#issuecomment-2180449543
You are receiving this
### Description
We updated one of our endpoint facing proxies last night, from 5.7.4 to 5.8.2.
After running for about 12 hours, it crashed. It had about 1.8k TLS connections
at the time of the crash.
When crashing, Kamailio produced core dumps of two processes. One of them must
be the TCP
Thanks for the hint. Although I think, those type of behavior changes are
something for a major version and should be mentioned in a Changelog, it's good
that it is configurable.
Closing.
--
Reply to this email directly or view it on GitHub:
Closed #3755 as completed.
--
Reply to this email directly or view it on GitHub:
https://github.com/kamailio/kamailio/issues/3755#event-11817268626
You are receiving this because you are subscribed to this thread.
Message ID: ___
Kamailio (SER) -
### Description
Scenario: Kamailio servers running behind a loadbalancer (AWS network
loadbalancer in this case). This causes all packets to come from the same IP
address in Kamailio's POV.
The change
https://github.com/kamailio/kamailio/commit/a902e4a032a85a7755de32eeadac800a1312e64f
@space88man I just checked it on a test system with exactly one connected
client, and all 4 TCP listeners as well as the TCP main process show this
output:
```
(gdb) p ossl_err_get_state_int()
No symbol "ossl_err_get_state_int" in current context.
(gdb)
```
--
Reply to this email directly or
Just to give a feedback: A nightly build has been running on one of our
affected systems for three weeks now, and we haven't had a crash since. So the
fix seems to improve the behavior. Next step is to test it on a system with
client devices on the other end, handling much more TLS connections
I really had overlooked the init_mode parameter. Have set it now, it is
deployed to one production system, waiting if it crashes or not.
--
Reply to this email directly or view it on GitHub:
https://github.com/kamailio/kamailio/issues/3635#issuecomment-1820658576
You are receiving this because
Closed #3523 as completed.
--
Reply to this email directly or view it on GitHub:
https://github.com/kamailio/kamailio/issues/3523#event-10969811645
You are receiving this because you are subscribed to this thread.
Message ID: ___
Kamailio (SER) -
Since we are obviously the only ones having this problem and it's not possible
for us to set up a useful test system and to find anything without it, I'm
going to close it. Seems to be an edge case and we'll write a "restart every 4
weeks" wrapper around.
--
Reply to this email directly or
After seeing the crashes on a system serving a lot of user requests, we see it
happening on a system being connected to some carriers dealing with only
outbound TLS connections, too.
Here are four more resolved core dumps.
### Description
We have updated one system from a Ubuntu Focal 5.6.x container to a Ubuntu
Jammy 5.7.2 container. In the last 24 hours, we saw three crashes. The logs of
the last crash say:
```
Nov 09 20:39:34 sipproxy /usr/sbin/kamailio[4332]: CRITICAL:
[core/mem/q_malloc.c:519]: qm_free():
Okay, the problem is not gone in current 5.7 (5.7.2 from the official repo).
We restarted one affected system 2 days ago. Since then, I have dumped the shm
summary a few times.
Shortly after restart:
```
NOTICE: qm_sums: qm_sums(): count= 159 size= 42000 bytes from core:
We will first update two systems to the latest 5.7 branch release (and a new OS
as well) and watch if the behavior has changed. Will take another week or so.
--
Reply to this email directly or view it on GitHub:
https://github.com/kamailio/kamailio/issues/3523#issuecomment-1768374938
You are
15 matches
Mail list logo
