On Fri, Jul 2, 2010 at 9:45 PM, <span dir="ltr"><<a href="mailto:Kennard_White@logitech.com">Kennard_White@logitech.com</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;">
<div>
<p><font size="2">Hi Brett,</font><br>
<br>
<font size="2">While this doesn't address the root problem, we do two thing: (a) run with ~100MB of pkg mem (per process), and (b) run a monitor script checking syslog for out of memory messages, and restart all the processes. Not elegant, but better than zombies.</font><br>
<br>
<font size="2">I noticed in your log that you're also out of shmem. Do you know which comes first? (running out of pkg or shmem)?</font><br>
<br>
<font size="2">Regards,</font><br>
<font size="2">Kennard</font><br><br></p></div></blockquote><div><br></div><div>Kennard,</div><div>It appears that it runs out of pkg first, then a minute later or so shm shows up too.. Weird thing is that I had converted this config from mediaproxy to rtpproxy. With mediaproxy, we never had these issues.. I'm not sure if that is actually related or not.</div>
<div><br></div><div>Any ideas?<br>-Brett</div><div><br></div></div>