<div>Some more information... this only occurs when issuing 'opensipsctl fifo dr_reload'. All other fifo commands seem to work without issue. Anyone have any suggestions on how I can track this down?<br></div><div>
<br></div><div>Thanks.</div><br><div class="gmail_quote">On Thu, Apr 21, 2011 at 8:56 AM, thrillerbee <span dir="ltr"><<a href="mailto:thrillerbee@gmail.com">thrillerbee@gmail.com</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex;">
<div>I'm trying to track down the source of the following errors in syslog:</div><div><br></div><div>/usr/local/sbin/opensips[25490]: WARNING:core:fm_malloc: Not enough free memory, will atempt defragmenation </div><div>
/usr/local/sbin/opensips[25490]: ERROR:core:db_allocate_rows: no memory left </div><div>/usr/local/sbin/opensips[25490]: ERROR:db_postgres:db_postgres_convert_rows: no private memory left</div><div><br></div><div>What makes this even more unusual is that it will print these errors at almost exactly 30-min intervals for several hours and then just stop. For example, last night, it printed the above errors at:</div>
<div>23:56:00</div><div>00:26:08</div><div>00:56:08</div><div>01:26:03</div><div>01:56:05</div><div>02:26:03</div><div>02:56:01</div><div>03:26:02</div><div>and then it stopped...</div><div><br></div><div>I see no errors in postgresql logs and I haven't yet found any issues with the actual performance of OpenSIPS. I have increased private memory to 100MB and continue to see this randomly. This OpenSIPS instance is using drouting module with about 16,000 lines in the dr_rules table.</div>
<div><br></div><div>Any advice would be appreciated to help narrow down the source of these messages.</div><div><br></div><div>Thanks,</div><div>Ryan</div>
</blockquote></div><br>