Hello
I've upgraded to 3.1.2 and compiled with the DEFS+= -DMI_SYSTEM_MALLOC option. Looking good so far. Any thoughts about my second question, that is, how to be aware from the scripts if the any problems has arisen in the mi command?
Thanks
Javi
On Mon, Feb 21, 2011 at 5:21 PM, Javier Gallart jgallartm@gmail.com wrote:
Thanks Henning,
I'll go with to recompile option and post the results...
Regards
Javier
2011/2/21 Henning Westerholt henning.westerholt@1und1.de
On Monday 21 February 2011, Javier Gallart wrote:
we are running kamailio 3.1.1. Basically for every call it has to query
a
mtree that is reloaded every 15 minutes. The mtree table is about 4M records and is stored in a Pgostgres database. For the reload we use
the
command mi mt_reload embedded in a xmlrpc request. The code for this is: route[XMLRPC]{ if (method == "POST" || method == "GET") { if (search("^User-Agent:")) { xlog("xmlrpc request\n"); set_reply_close(); set_reply_no_connect(); # optional dispatch_rpc(); } exit; } } This server has been running with no issued for some weeks now, but at
some
point during the weekend the mi command started to fail. This is what
the
logs show:
ERROR: <core> [db_res.c:181]: no private memory left ERROR: db_postgres [km_res.c:225]: could not allocate rows ERROR: db_postgres [km_dbase.c:280]: failed to convert rows ERROR: mtree [mtree_mod.c:627]: Error while fetching result ERROR: db_postgres [km_dbase.c:318]: invalid parameter value ERROR: mtree [mtree_mod.c:738]: cannot re-load info from database
I've restarted kamailio and now it's working fine. Should we increase
the
private memory? On the other hand, we'd like to detect this failure condition on the script and act accordingly (for instance sending an
with an alarm message), is there anyway to do this?
Hi Javier,
this probably caused of the fragmentation of the internal private memory pool from the frequent dumps and other load. You could increase the pool, or better
- switch the MI to the system memory pool by uncommenting this line in
kmi/Makefile
#DEFS+= -DMI_SYSTEM_MALLOC
and recompile the server.
Cheers,
Henning