<p>hey <a href="https://github.com/bogdan-iancu" class="user-mention">@bogdan-iancu</a> I actually have an entirelog from startup to shutdown of this happening - its not very verbose though.</p>

<p>basically i set up a cronjob to search the log fork pkg mem warnings - as soon as it detects one it kills opensips and makes a back up of the log, then starts opensips again, this is kind of a cheap way to keep things running as well as catch it in the act.</p>

<p>The full log is available at the following link:</p>

<p><a href="https://owncloud.uphreak.com/index.php/s/ql8qPgJD2vEqtTQ">https://owncloud.uphreak.com/index.php/s/ql8qPgJD2vEqtTQ</a></p>

<p style="font-size:small;-webkit-text-size-adjust:none;color:#666;">&mdash;<br>Reply to this email directly or <a href="https://github.com/OpenSIPS/opensips/issues/651#issuecomment-149285944">view it on GitHub</a>.<img alt="" height="1" src="https://github.com/notifications/beacon/AFOciSVWsdM5jV-VLKboDg_fT15Ji0d4ks5o9R0qgaJpZM4GD9a4.gif" width="1" /></p>
<div itemscope itemtype="http://schema.org/EmailMessage">
<div itemprop="action" itemscope itemtype="http://schema.org/ViewAction">
  <link itemprop="url" href="https://github.com/OpenSIPS/opensips/issues/651#issuecomment-149285944"></link>
  <meta itemprop="name" content="View Issue"></meta>
</div>
<meta itemprop="description" content="View this Issue on GitHub"></meta>
</div>