Just to confirm, we verified the fix. Thanks very much for your help!<br><br><div class="gmail_quote">On Wed, Apr 1, 2009 at 1:45 PM, Bogdan-Andrei Iancu <span dir="ltr"><<a href="mailto:bogdan@voice-system.ro">bogdan@voice-system.ro</a>></span> wrote:<br>
<blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;">Hi Bobby,<br>
<br>
Thanks for your help with tracing and debugging this problem. It should be fixed now - the fix is available on all branches + trunk on SVN.<br>
I ran several tests and it looks good - the problem was with malformed messages were the Content-len hdr was advertising a length longer the real package size, leading to overflow - now, such cases are detected and an err is reported instead of simply crashing :).<br>
<br>
Please update and test.<br>
<br>
Thanks again,<br>
Bogdan<br>
<br>
Bobby Smith wrote:<br>
<blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;"><div class="im">
Opensips 1.4.5 -- the latest release as of yesterday (non-1.5).<br>
<br>
Working on getting you your trace now, will take a few minutes.<br>
<br>
Much thanks.<br>
<br></div>
2009/3/24 Bogdan-Andrei Iancu <<a href="mailto:bogdan@voice-system.ro" target="_blank">bogdan@voice-system.ro</a> <mailto:<a href="mailto:bogdan@voice-system.ro" target="_blank">bogdan@voice-system.ro</a>>><div class="im">
<br>
<br>
Hi Bobby,<br>
<br>
can you get the logs with debug=6 and post (or send priv to me) ?<br>
Also, what is the rev number your are using?<br>
<br>
<br>
Regards,<br>
Bogdan<br>
<br></div><div class="im">
<a href="mailto:bobby.smith@gmail.com" target="_blank">bobby.smith@gmail.com</a> <mailto:<a href="mailto:bobby.smith@gmail.com" target="_blank">bobby.smith@gmail.com</a>> wrote:<br>
<br>
A little more information into the problem. We enabled some<br>
additional logging around the point where the anchor_lump<br>
function was being called to print out the contents of the SIP<br>
message. You can see that after processing this message<br>
several times, it craps out and kills all the children processes.<br>
<br>
If someone could once over the routing script that I included<br>
to see, if for example, that I'm trying to correct a nat'ed<br>
contact where I shouldn't be, that would be much appreciated.<br>
Further, if that's not the case, is there a way where we can<br>
gracefully kill one child without killing the whole application?<br>
<br>
Last -- this is with an emergency update to production to<br>
Opensips 1.4.5 last night. This happened this morning around<br>
9. More importantly, Opensips consumed temporarily almost 2 GB<br>
of memory before dying, and then cached it. Huge memory spike.<br>
<br>
Again, tunables: 32 MB private per process, 16 processes total<br>
(at this point, we figured less private memory, more processes<br>
to work the CPU), 512 Shared memory, on a 4 GB, 2 x Dual Core box.<br>
<br>
<br>
<br></div>
------------------------------------------------------------------------<br>
<br>
_______________________________________________<br>
Users mailing list<br>
<a href="mailto:Users@lists.opensips.org" target="_blank">Users@lists.opensips.org</a> <mailto:<a href="mailto:Users@lists.opensips.org" target="_blank">Users@lists.opensips.org</a>><div class="im"><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>
<br>
<br>
</div></blockquote>
<br>
</blockquote></div><br>