is there anything one can do when 'mi ul_dump' gives
error: 500 - Internal server error processing 's': buffer too small
i guess there is too many contacts.
-- juha
Hello,
you can increase the buffer size via mod param: http://kamailio.org/docs/modules/stable/modules/ctl.html#binrpc_max_body_siz...
Cheers, Daniel
On 9/15/10 3:47 PM, Juha Heinanen wrote:
is there anything one can do when 'mi ul_dump' gives
error: 500 - Internal server error processing 's': buffer too small
i guess there is too many contacts.
-- juha
SIP Express Router (SER) and Kamailio (OpenSER) - sr-users mailing list sr-users@lists.sip-router.org http://lists.sip-router.org/cgi-bin/mailman/listinfo/sr-users
Daniel-Constantin Mierla writes:
you can increase the buffer size via mod param: http://kamailio.org/docs/modules/stable/modules/ctl.html#binrpc_max_body_siz...
daniel,
after increasing binrpc_struct_max_body_size to 30:
modparam("ctl", "binrpc_max_body_size", 30)
error message:
error: 500 - Internal server error processing 's': buffer too small
went away, but was replaced by error:
ERROR: reply too big
how to get rid of that?
we tried and increased binrpc_struct_max_body_size to 1000, which means 1 MB:
modparam("ctl", "binrpc_struct_max_body_size", 1000)
however, we still get the error on 'ul_dump brief' when there is less than 1000 AoRs in location table. estimating that one line in the reply has on the average 30 characters, 1000 lines should consume about 30 KB of memory, which is way less that 1 MB.
what is the cause of this new error message and is there some way to get rid of it or is 1000 AoRs simply too much?
-- juha
Hello,
On 9/21/10 6:43 PM, Juha Heinanen wrote:
Daniel-Constantin Mierla writes:
you can increase the buffer size via mod param: http://kamailio.org/docs/modules/stable/modules/ctl.html#binrpc_max_body_siz...
daniel,
after increasing binrpc_struct_max_body_size to 30:
modparam("ctl", "binrpc_max_body_size", 30)
error message:
error: 500 - Internal server error processing 's': buffer too small
went away, but was replaced by error:
ERROR: reply too big
how to get rid of that?
this seems to come from sercmd tool. Quickly grepping its sources, the internal limit is 4K for rpc replies. You can try to recompile sercmd after setting bigger value for MAX_*_SIZE defines.
If you try via xmlrpc with a web client, does it work?
Maybe Andrei can give more details about sercmd limits.
Cheers, Daniel
we tried and increased binrpc_struct_max_body_size to 1000, which means 1 MB:
modparam("ctl", "binrpc_struct_max_body_size", 1000)
however, we still get the error on 'ul_dump brief' when there is less than 1000 AoRs in location table. estimating that one line in the reply has on the average 30 characters, 1000 lines should consume about 30 KB of memory, which is way less that 1 MB.
what is the cause of this new error message and is there some way to get rid of it or is 1000 AoRs simply too much?
-- juha
Daniel-Constantin Mierla writes:
ERROR: reply too big
how to get rid of that?
this seems to come from sercmd tool. Quickly grepping its sources, the internal limit is 4K for rpc replies. You can try to recompile sercmd after setting bigger value for MAX_*_SIZE defines.
ok. i'll try that unless andrei tells that it is not a good idea to increase the MAX_*_SIZE defines.
If you try via xmlrpc with a web client, does it work?
i have not yet tried anything else except sercmd.
-- juha
On Sep 21, 2010 at 21:09, Juha Heinanen jh@tutpro.com wrote:
Daniel-Constantin Mierla writes:
ERROR: reply too big
how to get rid of that?
this seems to come from sercmd tool. Quickly grepping its sources, the internal limit is 4K for rpc replies. You can try to recompile sercmd after setting bigger value for MAX_*_SIZE defines.
ok. i'll try that unless andrei tells that it is not a good idea to increase the MAX_*_SIZE defines.
I've increased them to 64k and commited the change.
Andrei
-
Andrei Pelinescu-Onciul -
Daniel-Constantin Mierla -
Juha Heinanen