Summary:ASTERISK-17142: Asterisk 1.4.38, and 1.8.1 with debug flags crashes on load test
Reporter:postas (postas)Labels:
Date Opened:2010-12-21 09:22:21.000-0600Date Closed:2015-03-13 18:09:23
Versions:Frequency of
Environment:Attachments:( 0) call.xml
( 1) issue18510.txt
Description:I'm was trying to debug a deadlock on asterisk 1.4.38 and activated all the following debug flags:

DONT_OPTIMIZE                                                                   DEBUG_THREADS                                                                   LOADABLE_MODULES                                                                DEBUG_FD_LEAKS                                                                  DEBUG_CHANNEL_LOCKS                                                             MALLOC_DEBUG                                                                    

Then started a 30 call per second load test using SIPp with audio (plays a ALAW pcap and RFC2833 DTMF's).
Asterisk extensions.conf has the following config:

;exten => _.,1,InAsteriskApp()
exten => _19196,1,Playback(/var/lib/asterisk/welcome)
exten => h,1,Hangup

Logger.conf has the following config:

;debug => debug
console => notice,warning,error,verbose,debug
;console => notice,warning,error
messages => notice,warning,error
;full => notice,warning,error,debug,verbose

I'm Running asterisk with the command 'asterisk -vvvgdc'.

I've tried all this test with the most recent versions of asterisk 1.4, 1.6 and 1.8 branches and get the same error after ~300 calls.

Can anyone help me? Thanks

Comments:By: Stefan Schmidt (schmidts) 2010-12-21 09:55:08.000-0600

i have removed the logs from the description and append it separate. please recognize for the future to also do this.


By: Stefan Schmidt (schmidts) 2010-12-21 09:57:08.000-0600

could you please try disabling the messages in your logger.conf cause i have done load tests with 590 calls per second up to 2000 concurrant calls without this problem but i never use the messages file.

By: postas (postas) 2010-12-21 10:42:18.000-0600


thanks for the prompt reply!

I've tried you sugestion setting up logger.conf as:

;debug => debug
;console => notice,warning,error,verbose,debug
console => notice,warning,error
;messages => notice,warning,error
;full => notice,warning,error,debug,verbose

And still get a segmentation fault. I only get this problem after enabling all the debug compilation flags and when SIPp sends audio. I imagine that the requests start getting delays and precipitate the fault. I'm attaching my SIPp script without the pcap (too big)

By: postas (postas) 2010-12-21 10:45:51.000-0600

This is the sipp command:

./sipp -sf call.xml -inf users.csv -rp 1000 -t u1 -i -r 30 -m 1000000 -l 1000 -p 16060 -d 5000 -nd

By: Stefan Schmidt (schmidts) 2010-12-22 06:40:03.000-0600

thats a lot of sipp options :D

i have not tried this but could you please try sipp without the -nd option and take a look if you still got the segfault.

and if possible try this from another host not localhost. by 30 cps and 5 sec long calls you will have 150 concurrent calls which would be around 13 mbit of rtp traffic that should not be a problem for a normal switch.

By: postas (postas) 2010-12-22 12:18:57.000-0600

I removed -nd and at the same time moved the sipp to another server and set up a <pause milliseconds="10000"/> session with 30 cps. It blew up after 253 calls. It seems to be the DEBUG_* doing damages.

By: Rusty Newton (rnewton) 2015-03-13 18:09:23.281-0500

I'm going to close this issue out. This issue is getting a bit old, we don't have anyone else reporting the issue and it was reported against versions that are not longer supported at this time.

If anyone can reproduce this issue or something similar, please file a new issue (against the newer versions of Asterisk) and include all the appropriate debug as usual.

By: Joshua C. Colp (jcolp) 2015-03-13 18:12:39.377-0500

I'll also add that attempting to do any sort of load test with those debug flags enabled will yield horrible results. They can seriously hinder it.