3 Mar
2020
3 Mar
'20
11:48 a.m.
If you can reproduce it, watch what the timer processes do during that
time frame. Get the list of processes with 'kamctl ps', then when the
issue is exposed, grab the backtraces of all processes with:
kamctl trap
A file is created with the backtraces taken with gdb. Sent it over here
to analyze, if you cannot spot an issue there.
Cheers,
Daniel
On 03.03.20 05:39, Juha Heinanen wrote:
Here is some more details about the shm usage. Usage
was steady at
about 10 MB until time 17:05. Then it usage started to steadily grow
during 15 min period and 17:21 hit 80 MB at which point tm.clean was
executed. After that usage dropped straight back to 10 MB level.
How is that possible, i.e,, why the expired transactions were not
automatically cleared?
According to tm README:
An INVITE transaction will be kept in memory for maximum:
max_inv_lifetime+fr_timer(from the ACK to the final reply
wait)+wt_timer.
In this case the max memory time was 180 + 5 + 5 = 190 sec, which is
much less than 16 minutes.
-- Juha
--
Daniel-Constantin Mierla -- www.asipto.com
www.twitter.com/miconda -- www.linkedin.com/in/miconda
Kamailio Advanced Training - March 9-11, 2020, Berlin - www.asipto.com
Kamailio World Conference - April 27-29, 2020, in Berlin -- www.kamailioworld.com