Hello,
On 9/21/10 6:43 PM, Juha Heinanen wrote:
Daniel-Constantin Mierla writes:
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
http://www.asipto.com