[ previous ] [ next ] [ threads ]
 To :  Diana Cionoiu <diana-liste@v...>
 From :  Alfred Stainer <alfred.stainer@g...>
 Subject :  Re: [yate] Core dump
 Date :  Mon, 26 Apr 2010 17:52:37 +0200
Hello Diana,

 my test is done in a dedicated 100Mb network where are running 3 PC:

1. Call generator
2. Yate server on CentOS 5.4
3. Call answer.

To generate and to answer the calls I use sipp.

In my test there are 500 active calls generated with a rate of 4 calls per
second.

In each call is played a pcap audio file in G.729 format of 140 seconds (the
RTP is only in one direction "calling to called").

The regex routing is one line like:

.*=sip/sip:@targetIP

Yate crashes in few hours.

I'm using Yate 2.2 where I have addes the G.729 codecs based on Intel IPP.

Regards,

Alfred


On Mon, Apr 26, 2010 at 3:20 PM, Diana Cionoiu wrote:

> Hello Alfred,
>
> This sounds like a memory coruption.
> Can you provide more informations like how many calls, on which system,
> which g729?
>
> Regards,
> Diana
>
>
> Alfred Stainer wrote:
>
>> Hi,
>> I'm testing yate to put it in a production environment but it crashes a
>> lot.
>> I'm using linux CentOS 5.4 and Yate 2.2
>> I use only a subset of yate modules and this is the start up log:
>>  Yate (11482) is starting Mon Apr 26 09:48:26 2010
>> Loaded module OpenSSL - based on OpenSSL 0.9.8e-fips-rhel5 01 Jul 2008
>> Loaded module RegexRoute
>> Loaded module iLBC - based on iLBC library
>> Loaded module WaveFile
>> Loaded module YSOCKS
>> Loaded module G.729a - based on Intel IPP
>> Loaded module CdrBuild
>> Loaded module ToneDetector
>> Loaded module ToneGen
>> Loaded module SIP Channel
>> Loaded module YRTP
>> Loaded module Sangoma TDM
>> Loaded module Registration from file
>> Loaded module Wanpipe
>> Loaded module Signalling Channel
>> Initializing plugins
>> Initializing module Wanpipe
>> Initializing module Sangoma TDM
>> Initializing module YSOCKS
>> Initializing module OpenSSL
>> Initializing module RegexRoute
>> Initializing module WaveFile
>> Initializing module CdrBuild
>> Initializing module ToneDetector
>> Initializing module ToneGen
>> Initializing module SIP Channel
>> Initializing module YRTP
>> Initializing module Register for file
>> Initializing module Signalling Channel
>> Initialization complete
>> Yate engine is initialized and starting up on localhost.localdomain
>> The hardware is an HP pc with a Core 2 Quad, 4Gb ram.
>>  The problem is that yate crashes and generate a core dump on segmentation
>> fault.
>>  Here the backtrace:  #0  0x004e7860 in malloc_consolidate () from
>> /lib/libc.so.6
>> #1  0x004e9ce3 in _int_malloc () from /lib/libc.so.6
>> #2  0x004ebd87 in malloc () from /lib/libc.so.6
>> #3  0x05ca6ab7 in operator new () from /usr/lib/libstdc++.so.6
>> #4  0x006df081 in incoming (this=0x9de0fa0, e=0xb7ce40a8, t=0xb7b8b4c0) at
>> ysipchan.cpp:1323
>> #5  0x006e0574 in run (this=0x9de0fa0) at ysipchan.cpp:1241
>> #6  0x00b0057e in TelEngine::ThreadPrivate::run (this=0x9ddfdc8) at
>> Thread.cpp:344
>> #7  0x00b005cd in TelEngine::ThreadPrivate::startFunc (arg=0x9ddfdc8) at
>> Thread.cpp:514
>> #8  0x005fc73b in start_thread () from /lib/libpthread.so.0
>> #9  0x00551cfe in clone () from /lib/libc.so.6
>> The work condition is SIP-to-SIP calls in G.729 with a very simple regex
>> routing.
>>  Anyone into the same problem?
>> Any advise?
>>  Alfred
>>
>
>



Hello Diana,
 
my test is done in a dedicated 100Mb network where are running 3 PC:
 
1. Call generator
2. Yate server on CentOS 5.4
3. Call answer.
 
To generate and to answer the calls I use sipp.
 
In my test there are 500 active calls generated with a rate of 4 calls per second.
 
In each call is played a pcap audio file in G.729 format of 140 seconds (the RTP is only in one direction "calling to called").
 
The regex routing is one line like:
 
.*=sip/sip:@targetIP
 
Yate crashes in few hours.
 
I'm using Yate 2.2 where I have addes the G.729 codecs based on Intel IPP.
 
Regards,
 
Alfred

 
On Mon, Apr 26, 2010 at 3:20 PM, Diana Cionoiu <diana-liste@v...> wrote:
Hello Alfred,

This sounds like a memory coruption.
Can you provide more informations like how many calls, on which system, which g729?

Regards,
Diana


Alfred Stainer wrote:
Hi,
I'm testing yate to put it in a production environment but it crashes a lot.
I'm using linux CentOS 5.4 and Yate 2.2
I use only a subset of yate modules and this is the start up log:
 Yate (11482) is starting Mon Apr 26 09:48:26 2010
Loaded module OpenSSL - based on OpenSSL 0.9.8e-fips-rhel5 01 Jul 2008
Loaded module RegexRoute
Loaded module iLBC - based on iLBC library
Loaded module WaveFile
Loaded module YSOCKS
Loaded module G.729a - based on Intel IPP
Loaded module CdrBuild
Loaded module ToneDetector
Loaded module ToneGen
Loaded module SIP Channel
Loaded module YRTP
Loaded module Sangoma TDM
Loaded module Registration from file
Loaded module Wanpipe
Loaded module Signalling Channel
Initializing plugins
Initializing module Wanpipe
Initializing module Sangoma TDM
Initializing module YSOCKS
Initializing module OpenSSL
Initializing module RegexRoute
Initializing module WaveFile
Initializing module CdrBuild
Initializing module ToneDetector
Initializing module ToneGen
Initializing module SIP Channel
Initializing module YRTP
Initializing module Register for file
Initializing module Signalling Channel
Initialization complete
Yate engine is initialized and starting up on localhost.localdomain
The hardware is an HP pc with a Core 2 Quad, 4Gb ram.
 The problem is that yate crashes and generate a core dump on segmentation fault.
 Here the backtrace:  #0  0x004e7860 in malloc_consolidate () from /lib/libc.so.6
#1  0x004e9ce3 in _int_malloc () from /lib/libc.so.6
#2  0x004ebd87 in malloc () from /lib/libc.so.6
#3  0x05ca6ab7 in operator new () from /usr/lib/libstdc++.so.6
#4  0x006df081 in incoming (this=0x9de0fa0, e=0xb7ce40a8, t=0xb7b8b4c0) at ysipchan.cpp:1323
#5  0x006e0574 in run (this=0x9de0fa0) at ysipchan.cpp:1241
#6  0x00b0057e in TelEngine::ThreadPrivate::run (this=0x9ddfdc8) at Thread.cpp:344
#7  0x00b005cd in TelEngine::ThreadPrivate::startFunc (arg=0x9ddfdc8) at Thread.cpp:514
#8  0x005fc73b in start_thread () from /lib/libpthread.so.0
#9  0x00551cfe in clone () from /lib/libc.so.6
The work condition is SIP-to-SIP calls in G.729 with a very simple regex routing.
 Anyone into the same problem?
Any advise?
 Alfred