Hello,
On 9/10/12 6:18 PM, David wrote:
Hello,
Thanks for the clarification.
I do not see get_statistics on the "micommands" page on the wiki.
Where in the documentation is this command discussed?
Are the stats for all processes or only for the process the responds
to the mi command ?
pkg.
Hello,
Thanks for the clarification.
I do not see get_statistics on the "micommands" page on the wiki. Where
in the documentation is this command discussed?
Are the stats for all processes or only for the process the responds to
the mi command ?
Thanks,
David
On 2012-09-10 12:10, Daniel-
Hello,
-m is shared memory, so it is allocated per instance, it does not matter
how many children you configure.
kamctl fifo get_statistics all - returns internal statistics, including
about shared memory
kamctl stats - it's an alias to the previous command in the 3.3.x
sercmd pkg.stats - to
Daniel-Constantin Mierla writes:
> Maybe we can improve a bit in the way that if there are same ca_list and
> crl path, to load once and do references from the other profiles. I
> don't know if there is lot of coding, but should be kept in mind for
> future optimizations. Perhaps could be added
On 3/19/12 12:59 PM, Juha Heinanen wrote:
Daniel-Constantin Mierla writes:
I guess it is loaded two time, for the server and client profiles. Try
to set it via dedicated module parameter and see if you get better
memory usage:
http://kamailio.org/docs/modules/stable/modules/tls.html#ca_list
btw, the devel branch as well as last stable releases are compiled with
memory debugger on, you can compile with F_MALLOC and try to see if you
get some improvements, but I guess they will not be really relevant over
all.
Cheers,
Daniel
On 3/19/12 4:04 PM, Jan Janak wrote:
I know this is not
I know this is not a solution, but you can also try to run
dpkg-reconfigure ca-certificates
and select only a couple of CA certificates you trust. That should
make the list much smaller. Debian includes a lot of CA certificates
in its default list and I am not sure whether it is a good idea to
tr
On Mon, Mar 19, 2012 at 05:32, Juha Heinanen wrote:
> as i mentioned, with shared memory of 64MB, sip proxy started fine.
> however, it failed to send a request over tls:
>
> Mar 19 11:21:41 test /usr/sbin/sip-proxy[30293]: INFO: Routing INVITE
>
> Mar 19 11:21:41 test /usr/sbin/sip-proxy[30293]
On Mon, Mar 19, 2012 at 05:31, Daniel-Constantin Mierla
wrote:
> Hello,
>
>
> On 3/19/12 10:03 AM, Juha Heinanen wrote:
>>
>> Daniel-Constantin Mierla writes:
>>
>>> is this with default mem size?
>>
>> i would just like to add that once i increased shared memory from
>> 32m to 64m, sip proxy star
Daniel-Constantin Mierla writes:
> I guess it is loaded two time, for the server and client profiles. Try
> to set it via dedicated module parameter and see if you get better
> memory usage:
>
> http://kamailio.org/docs/modules/stable/modules/tls.html#ca_list
i tried and it turned out that it
On 3/19/12 10:47 AM, Juha Heinanen wrote:
Daniel-Constantin Mierla writes:
Is this by one ca_list only, or do you have many tls domains, each with
own profile?
just a single ca_list and tls domain. my tls.cfg looks like this:
[client:default]
verify_certificate = yes
require_certificate =
Daniel-Constantin Mierla writes:
> Is this by one ca_list only, or do you have many tls domains, each with
> own profile?
just a single ca_list and tls domain. my tls.cfg looks like this:
[client:default]
verify_certificate = yes
require_certificate = yes
tls_method = TLSv1
private_key = /etc/
as i mentioned, with shared memory of 64MB, sip proxy started fine.
however, it failed to send a request over tls:
Mar 19 11:21:41 test /usr/sbin/sip-proxy[30293]: INFO: Routing INVITE
Mar 19 11:21:41 test /usr/sbin/sip-proxy[30293]: WARNING:
[forward.c:268]: WARNING: get_send_socket: protocol
Hello,
On 3/19/12 10:03 AM, Juha Heinanen wrote:
Daniel-Constantin Mierla writes:
is this with default mem size?
i would just like to add that once i increased shared memory from
32m to 64m, sip proxy started, but only about 10M was left as free:
afaik, the ca_list is loaded by libssl interna
Daniel-Constantin Mierla writes:
> is this with default mem size?
i would just like to add that once i increased shared memory from
32m to 64m, sip proxy started, but only about 10M was left as free:
Shared Memory
free_size 8510256
max_used_size 58623504
real_use
Daniel-Constantin Mierla writes:
> is this with default mem size?
sorry, in the test proxy om my laptop i only had 32M of shared memory.
when i increased it to 64M, the error message about insufficient memory
went away.
-- juha
___
SIP Express Router
Hello,
On 3/19/12 7:57 AM, Juha Heinanen wrote:
in tls.cfg, i made ca_list to point to ca-certificates.crt file that
comes with debian. when i then started sip router, i got errors
Mar 19 08:45:42 test /usr/sbin/sip-proxy[28093]: ERROR: tls [tls_domain.c:447]:
TLSc: Unable to load CA list '/e
On Wednesday 29 February 2012, Robert R wrote:
> The openser service died on my servers after "memory allocation failure".
> This issue has been occurred a couple of times on two different servers
> within the last two months.
>
> Feb 29 08:31:59 /usr/sbin/openser[7115]: ERROR:core:do_action: mem
Hello,
the old kamailio (openser) devel guide is very actual at the part with
memory management, so this reading may help:
http://www.asipto.com/pub/kamailio-devel-guide/#c04memory
Cheers,
Daniel
On 10/8/11 4:35 PM, Klaus Darilion wrote:
On 08.10.2011 14:53, Austin Einter wrote:
Hi
Just a
On 08.10.2011 14:53, Austin Einter wrote:
Hi
Just a quick question. How memory is allocated in Kamailio code.
Few places I saw pkg_malloc function.
Is it the only function used to allocate memory or there are similar
functions present in kamailio.
Basically there are 2 concepts: private memory
20 matches
Mail list logo
