Hi Ryan,
The problem is that the opensips process that does the reload has too
little private memory and the rules can not be loaded from database.
You should increase the private memory. You do this by editing config.h
file and re-writing the value for PKG_MEM_POOL_SIZE, eg:
PKG_MEM_POOL_SIZE 1024*1024*4
( it sets 4M of private memory per process)
Regards,
--
Anca Vamanu
OpenSIPS Developer
On 04/26/2011 05:44 PM, thrillerbee wrote:
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?
Thanks.
On Thu, Apr 21, 2011 at 8:56 AM, thrillerbee <[email protected]
<mailto:[email protected]>> wrote:
I'm trying to track down the source of the following errors in syslog:
/usr/local/sbin/opensips[25490]: WARNING:core:fm_malloc: Not
enough free memory, will atempt defragmenation
/usr/local/sbin/opensips[25490]: ERROR:core:db_allocate_rows: no
memory left
/usr/local/sbin/opensips[25490]:
ERROR:db_postgres:db_postgres_convert_rows: no private memory left
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:
23:56:00
00:26:08
00:56:08
01:26:03
01:56:05
02:26:03
02:56:01
03:26:02
and then it stopped...
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.
Any advice would be appreciated to help narrow down the source of
these messages.
Thanks,
Ryan
_______________________________________________
Users mailing list
[email protected]
http://lists.opensips.org/cgi-bin/mailman/listinfo/users
