[OpenSIPS-Users] 100% CPU usage

[Ovidiu Sas]

Correct!
On Dec 17, 2013 6:29 PM, "Dragomir Haralambiev" <goup2010 at gmail.com> wrote:

> Yes, I tried - creates the debug file in /tmp. But it would be no useful
> if opensips is functioning properly at the time of run. The idea is to
> collect the data when processes are stuck at 100% - correct?
>
>
> 2013/12/18 Ovidiu Sas <osas at voipembedded.com>
>
>> You can run it even now, to test it :)
>>
>>
>> On Tuesday, December 17, 2013, Dragomir Haralambiev wrote:
>>
>>>  Thanks for the guide! Got the new opensopsctl in place now. So - next
>>> time I get opensips processes stuck at 100%, I just run the trap command
>>> and provide the file for investigation - rigth?
>>>
>>>
>>> 2013/12/18 Ovidiu Sas <osas at voipembedded.com>
>>>
>>> Try this:
>>> 1. clone a clean opensips 1.9 repo:
>>> git clone https://github.com/OpenSIPS/opensips.git -b 1.8 opensips-1.8
>>> 2. go into the repo:
>>> cd opensips-1.8
>>> 3. pull from master branch my commits:
>>> git cherry-pick -x 9d25d0c7cf4391ca85bb25a23e2e933e6878a48a
>>> git cherry-pick -x 54a22de28833d674350b919a4791f1a2c2953ba9
>>> 4. re-install opensips from the new repo
>>>
>>> Regards,
>>> Ovidiu Sas
>>>
>>> On Tue, Dec 17, 2013 at 6:05 PM, Dragomir Haralambiev
>>> <goup2010 at gmail.com> wrote:
>>> > Thanks Ovidiu,
>>> >
>>> > indeed I have multiple processes stuck at 100% when the issue occurs.
>>> >
>>> > I am not sure how to backport the patch you mentioned. git pull
>>> doesn't give
>>> > me new files (1.8 LTS)
>>> >
>>> >
>>> > 2013/12/18 Ovidiu Sas <osas at voipembedded.com>
>>> >>
>>> >> That process is stuck in a lock.
>>> >> Most likely there is another opensips process that is stuck in a
>>> similar
>>> >> lock.
>>> >> I pushed a new opensipsctl 'trap' command in trunk.
>>> >> You can backport the commit into your existing repo and use that
>>> >> command to gather all the required info in one single command and then
>>> >> post the file or the content of the file.
>>> >> You will need to run:
>>> >> opensipsctl trap
>>> >>
>>> >> Here's the link to the commit:
>>> >>
>>> >>
>>> https://github.com/OpenSIPS/opensips/commit/9d25d0c7cf4391ca85bb25a23e2e933e6878a48a
>>> >>
>>> >> Regards,
>>> >> Ovidiu Sas
>>> >>
>>> >> On Tue, Dec 17, 2013 at 5:01 PM, Dragomir Haralambiev
>>> >> <goup2010 at gmail.com> wrote:
>>> >> > Finally I managed to capture a gdb output from opensips process
>>> stuck at
>>> >> > 100% CPU:
>>> >> >
>>> >> > http://pastebin.com/Fvz9Whi1
>>> >> >
>>> >> >
>>> >> > 2013/12/16 Răzvan Crainea <razvan at opensips.org>
>>> >> >>
>>> >> >> Hello!
>>> >> >>
>>> >> >> Can you attach with gdb to one of the processes that are using
>>> 100% CPU
>>> >> >> and post the backtrace on pastebin? You should do something like:
>>> >> >>
>>> >> >> gdb /path/to/opensips pid
>>> >> >> bt full
>>> >> >>
>>> >> >> And upload the entire output on pastebin.
>>> >> >>
>>> >> >> Best regards,
>>> >> >>
>>> >> >> Razvan Crainea
>>> >> >> OpenSIPS Core Developer
>>> >> >> http://www.opensips-solutions.com
>>> >> >>
>>> >> >>
>>> >> >> On 12/16/2013 12:08 PM, pavel at eremina.net wrote:
>>> >> >>>
>>> >> >>> I had same problem when my Debian can't resolve one of gateways.
>>> >> >>>
>>> >> >>>
>>> >> >>> 2013/12/16 Dragomir Haralambiev <goup2010 at gmail.com
>>> >> >>> <mailto:goup2010 at gmail.com>>
>>> >> >>>
>>> >> >>>
>>> >> >>>     i have not Registrant module.
>>> >> >>>
>>> >> >>>     On Dec 16, 2013 11:53 AM, "pavel at eremina.net
>>> >> >>>     <mailto:pavel at eremina.net>" <eremina.net at gmail.com
>>> >> >>>
>>> >> >>>
>>>
>>>
>>
>> --
>> VoIP Embedded, Inc.
>> http://www.voipembedded.com
>>
>> _______________________________________________
>> Users mailing list
>> Users at lists.opensips.org
>> http://lists.opensips.org/cgi-bin/mailman/listinfo/users
>>
>>
>
> _______________________________________________
> Users mailing list
> Users at lists.opensips.org
> http://lists.opensips.org/cgi-bin/mailman/listinfo/users
>
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.opensips.org/pipermail/users/attachments/20131217/8d4d5f90/attachment-0001.htm>