<div dir="ltr">any insight from the debug log I provided</div><div class="gmail_extra"><br><br><div class="gmail_quote">2013/12/18 Dragomir Haralambiev <span dir="ltr"><<a href="mailto:goup2010@gmail.com" target="_blank">goup2010@gmail.com</a>></span><br>
<blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><div dir="ltr"><div>Didn't have to wait too long. Here is the debug output from opensipsctl trap: </div><div><br></div>
<div><a href="http://pastebin.com/3GpqxLrX" target="_blank">http://pastebin.com/3GpqxLrX</a></div></div><div class="HOEnZb"><div class="h5"><div class="gmail_extra">
<br><br><div class="gmail_quote">2013/12/18 Ovidiu Sas <span dir="ltr"><<a href="mailto:osas@voipembedded.com" target="_blank">osas@voipembedded.com</a>></span><br><blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;padding-left:1ex;border-left-color:rgb(204,204,204);border-left-width:1px;border-left-style:solid">
<p dir="ltr">Correct!</p><div><div>
<div class="gmail_quote">On Dec 17, 2013 6:29 PM, "Dragomir Haralambiev" <<a href="mailto:goup2010@gmail.com" target="_blank">goup2010@gmail.com</a>> wrote:<br type="attribution"><blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;padding-left:1ex;border-left-color:rgb(204,204,204);border-left-width:1px;border-left-style:solid">
<div dir="ltr">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?</div>
<div class="gmail_extra"><br><br><div class="gmail_quote">2013/12/18 Ovidiu Sas <span dir="ltr"><<a href="mailto:osas@voipembedded.com" target="_blank">osas@voipembedded.com</a>></span><br><blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;padding-left:1ex;border-left-color:rgb(204,204,204);border-left-width:1px;border-left-style:solid">
You can run it even now, to test it :)<div><div><br><br>On Tuesday, December 17, 2013, Dragomir Haralambiev wrote:<br><blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;padding-left:1ex;border-left-color:rgb(204,204,204);border-left-width:1px;border-left-style:solid">
<div dir="ltr">
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?</div><div>
<br><br><div>2013/12/18 Ovidiu Sas <span dir="ltr"><<a>osas@voipembedded.com</a>></span><br><blockquote style="margin:0px 0px 0px 0.8ex;padding-left:1ex;border-left-color:rgb(204,204,204);border-left-width:1px;border-left-style:solid">
Try this:<br>
1. clone a clean opensips 1.9 repo:<br>
git clone <a href="https://github.com/OpenSIPS/opensips.git" target="_blank">https://github.com/OpenSIPS/opensips.git</a> -b 1.8 opensips-1.8<br>
2. go into the repo:<br>
cd opensips-1.8<br>
3. pull from master branch my commits:<br>
git cherry-pick -x 9d25d0c7cf4391ca85bb25a23e2e933e6878a48a<br>
git cherry-pick -x 54a22de28833d674350b919a4791f1a2c2953ba9<br>
4. re-install opensips from the new repo<br>
<br>
Regards,<br>
Ovidiu Sas<br>
<br>
On Tue, Dec 17, 2013 at 6:05 PM, Dragomir Haralambiev<br>
<div><div><<a>goup2010@gmail.com</a>> wrote:<br>
> Thanks Ovidiu,<br>
><br>
> indeed I have multiple processes stuck at 100% when the issue occurs.<br>
><br>
> I am not sure how to backport the patch you mentioned. git pull doesn't give<br>
> me new files (1.8 LTS)<br>
><br>
><br>
> 2013/12/18 Ovidiu Sas <<a>osas@voipembedded.com</a>><br>
>><br>
>> That process is stuck in a lock.<br>
>> Most likely there is another opensips process that is stuck in a similar<br>
>> lock.<br>
>> I pushed a new opensipsctl 'trap' command in trunk.<br>
>> You can backport the commit into your existing repo and use that<br>
>> command to gather all the required info in one single command and then<br>
>> post the file or the content of the file.<br>
>> You will need to run:<br>
>> opensipsctl trap<br>
>><br>
>> Here's the link to the commit:<br>
>><br>
>> <a href="https://github.com/OpenSIPS/opensips/commit/9d25d0c7cf4391ca85bb25a23e2e933e6878a48a" target="_blank">https://github.com/OpenSIPS/opensips/commit/9d25d0c7cf4391ca85bb25a23e2e933e6878a48a</a><br>
>><br>
>> Regards,<br>
>> Ovidiu Sas<br>
>><br>
>> On Tue, Dec 17, 2013 at 5:01 PM, Dragomir Haralambiev<br>
>> <<a>goup2010@gmail.com</a>> wrote:<br>
>> > Finally I managed to capture a gdb output from opensips process stuck at<br>
>> > 100% CPU:<br>
>> ><br>
>> > <a href="http://pastebin.com/Fvz9Whi1" target="_blank">http://pastebin.com/Fvz9Whi1</a><br>
>> ><br>
>> ><br>
>> > 2013/12/16 Răzvan Crainea <<a>razvan@opensips.org</a>><br>
>> >><br>
>> >> Hello!<br>
>> >><br>
>> >> Can you attach with gdb to one of the processes that are using 100% CPU<br>
>> >> and post the backtrace on pastebin? You should do something like:<br>
>> >><br>
>> >> gdb /path/to/opensips pid<br>
>> >> bt full<br>
>> >><br>
>> >> And upload the entire output on pastebin.<br>
>> >><br>
>> >> Best regards,<br>
>> >><br>
>> >> Razvan Crainea<br>
>> >> OpenSIPS Core Developer<br>
>> >> <a href="http://www.opensips-solutions.com" target="_blank">http://www.opensips-solutions.com</a><br>
>> >><br>
>> >><br>
>> >> On 12/16/2013 12:08 PM, <a>pavel@eremina.net</a> wrote:<br>
>> >>><br>
>> >>> I had same problem when my Debian can't resolve one of gateways.<br>
>> >>><br>
>> >>><br>
>> >>> 2013/12/16 Dragomir Haralambiev <<a>goup2010@gmail.com</a><br>
>> >>> <mailto:<a>goup2010@gmail.com</a>>><br>
>> >>><br>
>> >>><br>
>> >>> i have not Registrant module.<br>
>> >>><br>
>> >>> On Dec 16, 2013 11:53 AM, "<a>pavel@eremina.net</a><br>
>> >>> <mailto:<a>pavel@eremina.net</a>>" <<a>eremina.net@gmail.com</a><br>
>> >>><br>
>> >>> </div></div></blockquote></div></div></blockquote><br><br></div></div><div><div>-- <br>VoIP Embedded, Inc.<br><a href="http://www.voipembedded.com" target="_blank">http://www.voipembedded.com</a><br>
</div></div><br>_______________________________________________<br>
Users mailing list<br>
<a href="mailto:Users@lists.opensips.org" target="_blank">Users@lists.opensips.org</a><br>
<a href="http://lists.opensips.org/cgi-bin/mailman/listinfo/users" target="_blank">http://lists.opensips.org/cgi-bin/mailman/listinfo/users</a><br>
<br></blockquote></div><br></div>
<br>_______________________________________________<br>
Users mailing list<br>
<a href="mailto:Users@lists.opensips.org" target="_blank">Users@lists.opensips.org</a><br>
<a href="http://lists.opensips.org/cgi-bin/mailman/listinfo/users" target="_blank">http://lists.opensips.org/cgi-bin/mailman/listinfo/users</a><br>
<br></blockquote></div>
</div></div><br>_______________________________________________<br>
Users mailing list<br>
<a href="mailto:Users@lists.opensips.org" target="_blank">Users@lists.opensips.org</a><br>
<a href="http://lists.opensips.org/cgi-bin/mailman/listinfo/users" target="_blank">http://lists.opensips.org/cgi-bin/mailman/listinfo/users</a><br>
<br></blockquote></div><br></div>
</div></div></blockquote></div><br></div>