1 Aug
2012
1 Aug
'12
10:57 a.m.
Hello,
On 7/31/12 3:39 PM, Bruno Bresciani wrote:
Hello,
I didn't know that log messages related to memory operations can be
controlled by global parameter, but I like to know if is recommendable
I recompile kamailio using q_malloc (default) and not f_malloc...
memory operations using q_malloc is more reliable and avoid problems
or crashes or it is only more suitable for debugging? What do you
suggest Daniel?
q_malloc is more suitable for debugging.
The 'get_statistics all' command is avaliable by a specific module? I
run 'kamctl fifo get_statistics all' and return '500 command
'get_statistics' not available'
Do you have kex module loaded? What is the output of 'kamctl fifo which'?
For while is impossible to start a new installation, first because I
don't know how much time I will spend to port and second because I am
involved with other developments and I have no time to make this. I
know that 3.1 is no longer a official branch but now start a new
installation it's very very difficult, my in intention is discover
what caused the crash and if exists a way to fix or prevent it.
Discovering may
require additional patches, like more debug messages in
the C code, that's why is better to start with the latest stable.
Cheers,
Daniel
Best Regards
2012/7/31 Daniel-Constantin Mierla <miconda(a)gmail.com
<mailto:miconda@gmail.com>>
Hello,
On 7/30/12 9:01 PM, Bruno Bresciani wrote:
--
Daniel-Constantin Mierla - http://www.asipto.com
http://twitter.com/#!/miconda - http://www.linkedin.com/in/miconda
Kamailio Advanced Training, Seattle, USA, Sep 23-26, 2012 - http://asipto.com/u/katu
Kamailio Practical Workshop, Netherlands, Sep 10-12, 2012 - http://asipto.com/u/kpw
Hi,
I compiled kamailio with MEMDBG = 0 because I didn't want the
memory debug in kamailio log, but I didn't know these turns on
f_malloc and disabling q_malloc...
the log messages related to memory
operations can be controlled by
global parameters memdbg and memlog.
Probably the size of shared memory that I start kamailio is 32MB
because I didn't gave a different -m parameter value, exist a
command to verify this information?
kamctl fifo get_statistics all
and see the shared memory total value. It will be interesting to
see available shared memory as well.
At moment that crash happened, there were few registered users
agents and were being made tests with register and calls with TLS
protocol. I got only the two situations that I showed at first email.
If you plan to start a new installation, I strongly recommend 3.3
branch, the code is more actual and easier to debug. 3.1 is no
longer an official maintained branch, those being now 3.3 and 3.2.
I'm looking at this issue to be sure it is no longer in latest stable.
Cheers,
Daniel