On Tue, Jul 6, 2010 at 1:10 PM, Bogdan-Andrei Iancu <span dir="ltr"><<a href="mailto:bogdan@voice-system.ro">bogdan@voice-system.ro</a>></span> wrote:<br><div class="gmail_quote"><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex;">
Hi Brett,<br>
<br>
The only way to hunt this down is to enable the mem debug (see<br>
<a href="http://www.opensips.org/Resources/DocsTsMem" target="_blank">http://www.opensips.org/Resources/DocsTsMem</a>). Once compiled in, use:<br>
mem_log=10<br>
mem_dump=1<br>
debug = 2<br>
<br>
This will prevent the mem runtime logs, but it will allow you to do the<br>
mem dump .<br>
<br>
After that, at runtime, when proc X reports the mem outage, simply do a<br>
"kill -SIGUSR1 X" to force proc X do dump the mem....and send me the<br>
dump to check.<br><br></blockquote><div><br></div><div>Bogdan,</div><div>Thanks. I'll do this.</div><div>-Brett</div><div><br></div></div>