@hnimminh unfortunately I am not using app_python3 any longer but it looks like
@miconda may be pointing in the right direction.
--
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/288
@miconda this is happening for us with latest stable version.
Can you point the sources files that could be involved in this memory leak, or
any hint? I wonder why this memory seems to be cleaned if the client closes the
TCP socket, but not cleaned if it's closed due to timeout.
--
You are re
Yes, is needed for the manually disabled nodes, under maintenance, to give them
as much time as necessary, until a manual enable.
--
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/pull/2886
Hello,
if it is needed/useful, then new fields can be added in the internal
structures (e.g., tcp connection, received info) to keep the haproxy
address/port.
Otherwise, I haven't needed to haproxy so far to become familiar with,
so cannot comment much, but adding an alias seems to be the right
LGTM. I guess this is for the allow_op=1 use case?
--
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/pull/2886#issuecomment-945724564___
Kamailio