[prev in list] [next in list] [prev in thread] [next in thread] 

List:       sr-users
Subject:    Re: [SR-Users] Kamailio unresponsive with Dialog+DMQ
From:       Patrick Wakano <pwakano () gmail ! com>
Date:       2020-10-28 22:11:35
Message-ID: CAPu3kNWZrxHgpAKYB9LmS7xKvA0Ri=qL5zRxgG7z_RDawVJrUw () mail ! gmail ! com
[Download RAW message or body]

[Attachment #2 (multipart/alternative)]


Hello,
For reference, we updated Kamailio to version 5.4.2 and the problem still
persists. So I opened the ticket (
https://github.com/kamailio/kamailio/issues/2535) to track the issue.

Thank you,
Patrick Wakano

On Wed, 28 Oct 2020 at 10:38, Patrick Wakano <pwakano@gmail.com> wrote:

> Hi Daniel!
> Thanks for your reply!
> I managed to get the kamctl trap output, it is attached here. This is a
> case where Kamailio is unresponsive with the UDP workers stuck in the
> mutex...
> I agree with your observations, it goes along with what we were thinking...
>
> Kind regards,
> Patrick Wakano
>
> On Tue, 27 Oct 2020 at 19:17, Daniel-Constantin Mierla <miconda@gmail.com>
> wrote:
>
>> The increase of memory is very likely the side effect of processes not
>> handing the traffic, sip_msg_shm_clone() is manly used when creating the
>> transactions. They can accumulate if the timer processes are stuck or other
>> callback functions block the transactions hash table. As said in the other
>> email, try to get the output of kamctl trap to have information about what
>> all processes do at that moment.
>>
>> Cheers,
>> Daniel
>>
>>

[Attachment #5 (text/html)]

<div dir="ltr"><div>Hello,</div><div>For reference, we updated Kamailio to version \
5.4.2 and the problem still persists. So I opened the ticket (<a \
href="https://github.com/kamailio/kamailio/issues/2535">https://github.com/kamailio/kamailio/issues/2535</a>) \
to track the issue.</div><div><br></div><div>Thank you,</div><div>Patrick \
Wakano<br></div></div><br><div class="gmail_quote"><div dir="ltr" \
class="gmail_attr">On Wed, 28 Oct 2020 at 10:38, Patrick Wakano &lt;<a \
href="mailto:pwakano@gmail.com">pwakano@gmail.com</a>&gt; wrote:<br></div><blockquote \
class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left:1px solid \
rgb(204,204,204);padding-left:1ex"><div dir="ltr"><div>Hi Daniel!</div><div>Thanks \
for your reply!</div><div>I managed to  get the kamctl trap output, it is attached \
here. This is a case where  Kamailio is unresponsive with the UDP workers stuck in \
the mutex...<br></div><div>I agree with your observations, it goes along with what we \
were thinking...</div><div><br></div><div>Kind regards,</div><div>Patrick \
Wakano</div><div><br></div><div class="gmail_quote"><div dir="ltr" \
class="gmail_attr">On Tue, 27 Oct 2020 at 19:17, Daniel-Constantin Mierla &lt;<a \
href="mailto:miconda@gmail.com" target="_blank">miconda@gmail.com</a>&gt; \
wrote:<br></div><blockquote class="gmail_quote" style="margin:0px 0px 0px \
0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex">  
    
  
  <div>
    <p>The increase of memory is very likely the side effect of
      processes not handing the traffic, sip_msg_shm_clone() is manly
      used when creating the transactions. They can accumulate if the
      timer processes are stuck or other callback functions block the
      transactions hash table. As said in the other email, try to get
      the output of kamctl trap to have information about what all
      processes do at that moment.</p>
    <p>Cheers,<br>
      Daniel<br>
    </p><br></div>

</blockquote></div></div>
</blockquote></div>



_______________________________________________
Kamailio (SER) - Users Mailing List
sr-users@lists.kamailio.org
https://lists.kamailio.org/cgi-bin/mailman/listinfo/sr-users


[prev in list] [next in list] [prev in thread] [next in thread]