I upgraded from Kamailio 3.1 to Kamailio 3.2 (x86_64/linux) 31c991 recently. Since upgrading, my LCR does not work. The "load_gws" command always returns a 2 (meaning no routes found).
When I do a "sercmd lcr.dump_rules", I get the following error: # sercmd lcr.dump_rules error: 500 - Internal server error: out of memory
I've tried increasing "binrpc_max_body_size" and "binrpc_struct_max_body_size", but this doesn't help. -H
Hello,
it may be that the private memory is used completely, so you need to start kamailio with more.
Starting with 3.2.0, it can be adjusted from command line, via '-M':
./kamailio -M 8 ...
will start kamailio with 8MB of private memory instead of the default 4.
Cheers, Daniel
On 1/11/12 12:07 PM, Henning Westerholt wrote:
Thanks for the tip.
I increased this to start with 8MB private memory. Now I'm getting the following error:
error: 500 - Internal server error processing '{': buffer too small (overflow) (-2)
I tried increasing the binrpc_max_body_size and binrpc_struct_max_body_size but this doesn't help. I still get the same error. -H
On 2012-01-11, at 10:47 AM, Daniel-Constantin Mierla wrote:
Hello,
On 1/11/12 6:10 PM, Henry Fernandes wrote:
what are the values for these parameters? How many records do you have in lcr tables?
Cheers, Daniel
I've tried all sorts of values. For binrpc_max_body_size, I've tried from 8 up to 10000. For binrpc_struct_max_body_size, I've tried from 2 up to 10000.
Here are the number of entries in my LCR tables. lcr_gw: 47 lcr_rule: 1841 lcr_rule_target: 1846
-H
On 2012-01-11, at 12:02 PM, Daniel-Constantin Mierla wrote:
Hello,
On 1/11/12 7:53 PM, Henry Fernandes wrote:
I checked a bit in the source of lcr, there are couple of while loops, some of them nested -- not being a user of the module, cannot estimate the size of the dump.
Do you work with git or have kamailio installed from some packages (e.g., rpms, debs)? I plan to make a patch to be able use system memory for output buffer, so it can be increased a lot, without affecting the pkg.
Another thing that can happen, is a bug in giving the length of a lcr attribute. It may be the case, as 10MB looks enough for me. Can you try with less records and discover what is the limit of going over output buffer size?
Cheers, Daniel