[SR-Users] kamailio slow/no response for requests on particular ports

Tue May 12 21:42:36 CEST 2015

Daniel,

A question regarding when I should run your suggested gdb commands.

Do I run them at anytime after we see the issue on a particular port or
would you like me to run them at a particular instance/event after the
issue occurs (for example, make a test call and immediately run the
command;  or maybe run the command after the test call completes; or at
some other time/event.)

Karthik

On Mon, May 11, 2015 at 2:43 PM, Karthik Srinivasan <ksriniva2002 at gmail.com>
wrote:

>
> Our operating system is RHEL 5.9 and selinux is disabled.
>
> We had already added an xlog message at the top of the request;  and the
> result showed that the message was being received by kamailio during the
> problematic-port issue.
>
> I will run your suggested commands when the problem recurs.
>
> Much appreciated regarding your help.
>
> Thanks,
>
> Karthik
>
>
> On Mon, May 11, 2015 at 1:47 PM, Daniel-Constantin Mierla <
> miconda at gmail.com> wrote:
>
>>  Hello,
>>
>> what is your operating system? Do you have selinux enabled?
>>
>> Can you add an xlog() message at the top of request_route block and see
>> if the message is printed in syslog when you see the packet coming on the
>> network? This ensures that kamailio is receiving it.
>>
>> If you are familiar with gdb, when one port is not responding, do:
>>
>> kamctl ps
>>
>> See the pid of the processes listening on that port. Select one and do:
>>
>> gdb /path/to/kamailio PID
>> bt full
>>
>> That will show what that process is doing at that moment. Send the output
>> here.
>>
>> Cheers,
>> Daniel
>>
>> On 11/05/15 20:34, Karthik Srinivasan wrote:
>>
>>  Hi Daniel,
>>
>>  Thanks for the response.
>>
>>  We are not using the pike module.
>>
>>  The requests to a port are not dismissed;  rather, in most cases, there
>> is a delay in response from kamailio.   Also, the delay is not restricted
>> to any particular message request.  it happens for any type of request.
>> (register; subscribe; etc...).
>>
>>  But those same requests, if pointed to different port, have no issues.
>>
>>  Also, to note, I am not restarting kamailio when the issue occurs on a
>> particular port.  kamailio is kept running and pointing traffic to a
>> non-problematic port seems fine.
>>
>>  Karthik
>>
>> On Mon, May 11, 2015 at 12:41 PM, Daniel-Constantin Mierla <
>> miconda at gmail.com> wrote:
>>
>>>  Hello,
>>>
>>> do you have pike module loaded and enabled?
>>>
>>> Are all requests to a port dismissed or just some of them?
>>>
>>> Cheers,
>>> Daniel
>>>
>>> On 11/05/15 19:20, Karthik Srinivasan wrote:
>>>
>>>  Hi,
>>>
>>>  I have encountered an issue with kamailio and am hoping someone on
>>> this email distro can help:
>>>
>>>  Here's my setup and description of the issue:
>>>
>>>  I am running kamailio version 3.1.4.
>>>
>>>  I have the kamailio process bound to ports 5060, 5070, and 5090.  all
>>> UDP.
>>>
>>>  I have several client devices registering to the kamailio registrar.
>>>
>>>  The issue I have encountered is this:
>>>
>>>  SIP registrations to port 5070 are fine for a period of time;  by fine
>>> I mean clients send SIP registration requests to kamailio; and kamailio
>>> responds promptly to the request.   by period of time I mean (this could be
>>> somewhat random) that for10 hours;  12 hours;  1 hour; that kamailo has no
>>> issue processing requests.  after this random time period has elapsed,
>>> kamailo isn't able to respond to sip registrations and other messages in
>>> timely manner;   to the point where the clients timeout and have to resend
>>> their registration requests.  at times, kamailio does respond to the
>>> requests (with a significant delay) and at other times no response is
>>> received by the client.  the user experience is intermittent registration
>>> delays/failures.
>>>
>>>  The same behavior is seen on port 5090.
>>>
>>>  I have not encountered the issue yet on port 5060.
>>>
>>>  During times when kamailio isn't able to respond timely to requests on
>>> a particular port,  requests to other ports are responded to timely.
>>>
>>>  for ex:   if port 5070 encounters the issue;  port 5060 and 5090 seem
>>> fine.  meaning, I can point my client devices to 5060 or  5090 and kamailio
>>> processes the requests timely.
>>>
>>>  I have studied a tcp dump on the server end (kamailio side) and
>>> noticed that the network layer shows the messages from the client to be
>>> received timely while kamailio is encountering this issue.   which
>>> indicates to me that it probably isn't a network lag related issue.
>>>
>>>  Something at the application layer is probably causing kamailio to not
>>> respond timely.
>>>
>>>  Furthermore the issue resolves itself after a period of time;  that
>>> is, kamailio begins to respond to messages timely on the problematic port.
>>> I haven't had a chance yet to determine exactly how long it takes to
>>> recover.  it certainly takes some time though.  at least 30 minutes; maybe
>>> more.
>>>
>>>  I can also state that the load on the kamailio system is minimal.  far
>>> below than what the performance metrics state it can handle.
>>>
>>>  Has anyone encountered this issue where kamalio isn't responding to
>>> registration and other requests timely on a particular port but does so
>>> fine for other ports?
>>>
>>>  Any help on this would be appreciated.
>>>
>>>  Thanks,
>>>
>>>  Karthik
>>>
>>>
>>>
>>>
>>>
>>>
>>>
>>> _______________________________________________
>>> SIP Express Router (SER) and Kamailio (OpenSER) - sr-users mailing listsr-users at lists.sip-router.orghttp://lists.sip-router.org/cgi-bin/mailman/listinfo/sr-users
>>>
>>>
>>> --
>>> Daniel-Constantin Mierlahttp://twitter.com/#!/miconda - http://www.linkedin.com/in/miconda
>>> Kamailio World Conference, May 27-29, 2015
>>> Berlin, Germany - http://www.kamailioworld.com
>>>
>>>
>>> _______________________________________________
>>> SIP Express Router (SER) and Kamailio (OpenSER) - sr-users mailing list
>>> sr-users at lists.sip-router.org
>>> http://lists.sip-router.org/cgi-bin/mailman/listinfo/sr-users
>>>
>>>
>>
>> --
>> Daniel-Constantin Mierlahttp://twitter.com/#!/miconda - http://www.linkedin.com/in/miconda
>> Kamailio World Conference, May 27-29, 2015
>> Berlin, Germany - http://www.kamailioworld.com
>>
>>
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.sip-router.org/pipermail/sr-users/attachments/20150512/d5128d97/attachment.html>