<div dir="ltr">As soon as a few re-registrations are going out, should be enough.<div><br></div><div>Regards,</div><div>Ovidiu Sas</div></div><div class="gmail_extra"><br><br><div class="gmail_quote">On Tue, Oct 15, 2013 at 3:26 PM, Jeff Pyle <span dir="ltr"><<a href="mailto:jpyle@fidelityvoice.com" target="_blank">jpyle@fidelityvoice.com</a>></span> wrote:<br>
<blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><div dir="ltr"><div>Ovidiu,</div><div><br></div>I might not have been as explicit about uac_registrant on the devel list. Then it was just a theory. Now I have some evidence.<div>
<br></div><div>This last time my test with 200 registrants began to show "no more pkg mem" without showing a huge real_used_size value. It self-destructed after a bit less than 3 hours. I'll test next with the memory debugs enabled as you instruct.</div>
<div><br></div><div>To ensure I get the correct data for you... If I estimate this configuration will have a problem in approximately 3 hours, would it make sense to grab the two SIGUSR1 log dumps at, say, 30 and 90 minutes?</div>
<span class="HOEnZb"><font color="#888888">
<div><br></div><div><br></div><div>- Jeff</div></font></span><div><div class="h5"><div class="gmail_extra"><div><div dir="ltr"><div>
<br></div></div></div>
<br><br><div class="gmail_quote">On Tue, Oct 15, 2013 at 11:18 AM, Ovidiu Sas <span dir="ltr"><<a href="mailto:osas@voipembedded.com" target="_blank">osas@voipembedded.com</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
<div dir="ltr">Please try the following test in your lab:<div> - compile opensips with memory debug enabled;</div><div> - let opensips to act as a registrant only (create a simple config that will only load uac_registrant and the relevant required modules);</div>
<div> - provide me with the output of 'opensipsctl ps';</div><div> - send a SIGUSR1 to the process that is leaking memory and capture the logs;</div><div> - wait for a few more re-registrations;</div><div> - send a second SIGUSR1 to the process that is leaking memory and capture the logs;</div>
<div> - send me the logs.</div><div><br></div><div>I will take a look and let you know my findings.</div><div><br></div><div>In your e-mail sent to dev I missed your reference to the uac_registrant module.</div><div>Sorry about that.</div>
<div><br></div><div>Regards,</div><div>Ovidiu Sas</div></div><div class="gmail_extra"><br><br><div class="gmail_quote"><div><div>On Tue, Oct 15, 2013 at 10:52 AM, Jeff Pyle <span dir="ltr"><<a href="mailto:jpyle@fidelityvoice.com" target="_blank">jpyle@fidelityvoice.com</a>></span> wrote:<br>
</div></div><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><div><div><div dir="ltr">Hello,<div><br></div><div><div><div dir="ltr"><div>This is on version 1.9 revision 7606eab from August 13 this year.</div>
<div><br></div><div>I've been able to verify the more entries in the uac_registrant table, the quicker something like this happens:</div>
<div><br></div><div><div># opensipsctl fifo get_statistics all | grep real_used_size</div><div>shmem:real_used_size = 3056920</div><div>pkmem:0-real_used_size = 181472</div><div>pkmem:1-real_used_size = 225304</div><div>
pkmem:2-real_used_size = 181456</div>
<div>pkmem:3-real_used_size = 18446744073706908112</div><div>pkmem:4-real_used_size = 982512</div><div>pkmem:5-real_used_size = 189624</div><div>pkmem:6-real_used_size = 189624</div><div>pkmem:7-real_used_size = 189624</div>
<div>pkmem:8-real_used_size = 189624</div><div>pkmem:9-real_used_size = 181048</div><div>pkmem:10-real_used_size = 189616</div></div><div><br></div><div>It always seems to happen on pkmem:3. Once this occurs I see lots of "no more pkg mem" errors in the log.</div>
<div><br></div><div>It took about eight hours for this occur on a test configuration doing nothing but registering 100 users from the uac_registrant module with 1M of pkg mem. I've increased the number of users to 200 in an effort to get it fail faster.</div>
<div><br></div><div>In order to provide information to isolate and fix this problem, what kind of data to I need to gather and what do I do with it? I tried to follow the instructions on the <a href="http://www.opensips.org/Documentation/TroubleShooting-OutOfMem" target="_blank">memory troubleshooting page</a> but I didn't get a response from the devel list.</div>
<div><br></div><div><br></div><div>Regards,<br>Jeff</div><div><br></div></div></div>
</div></div>
<br></div></div>_______________________________________________<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><span><font color="#888888"><br><br clear="all"><div><br></div>-- <br>VoIP Embedded, Inc.<br><a href="http://www.voipembedded.com" target="_blank">http://www.voipembedded.com</a>
</font></span></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></div>
<br>_______________________________________________<br>
Users mailing list<br>
<a href="mailto:Users@lists.opensips.org">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><br clear="all"><div><br></div>-- <br>VoIP Embedded, Inc.<br><a href="http://www.voipembedded.com" target="_blank">http://www.voipembedded.com</a>
</div>