[asterisk-bugs] [Asterisk 0016156]: Asterisk core-dumps if used as loadgenerator using callfiles

Asterisk Bug Tracker noreply at bugs.digium.com
Wed Nov 11 14:51:50 CST 2009


The following issue requires your FEEDBACK. 
====================================================================== 
https://issues.asterisk.org/view.php?id=16156 
====================================================================== 
Reported By:                bt047265
Assigned To:                tilghman
====================================================================== 
Project:                    Asterisk
Issue ID:                   16156
Category:                   Resources/res_timing_pthread
Reproducibility:            always
Severity:                   minor
Priority:                   normal
Status:                     feedback
Target Version:             1.6.1.11
Asterisk Version:           SVN 
JIRA:                       SWP-329 
Regression:                 No 
Reviewboard Link:            
SVN Branch (only for SVN checkouts, not tarball releases): N/A 
SVN Revision (number only!):  
Request Review:              
====================================================================== 
Date Submitted:             2009-10-29 17:48 CDT
Last Modified:              2009-11-11 14:51 CST
====================================================================== 
Summary:                    Asterisk core-dumps if used as loadgenerator using
callfiles
Description: 
A perl script is used to generate asterisk call files. 1500 "Asterisk
Clients" are connected to another SIP-Softswitch.

A calls B and on both ends RTP will be played. Call files are written with
"modify" time, this allows to limit the calls per second.

./load_generator.pl -f numbers.txt -cmax 250 -cps 10

Asterisk restarts with about 300 active calls:

/usr/sbin/safe_asterisk: line 146: 15582 Segmentation fault      (core
dumped) nice -n $PRIORITY ${ASTSBINDIR}/asterisk -f ${CLIARGS} ${ASTARGS}
>/dev/${TTY} 2>&1 </dev/${TTY}
Asterisk ended with exit status 139
Asterisk exited on signal EXITSTATUS-128.

System and Version:

1. SVN revision number ("svn info")
   
Connected to Asterisk SVN-branch-1.6.1-r226386 currently running on
b-lab-asterisk-load (pid = 17093)
     
2. Platform (O/S)
  
Linux b-lab-asterisk-load 2.6.18-164.el5
https://issues.asterisk.org/view.php?id=1 SMP Thu Sep 3 03:33:56 EDT
2009 i686 i686 i386 GNU/Linux


Attached Symptoms:

- CLI log
- gdb backtrace
====================================================================== 

---------------------------------------------------------------------- 
 (0113680) tilghman (administrator) - 2009-11-11 14:51
 https://issues.asterisk.org/view.php?id=16156#c113680 
---------------------------------------------------------------------- 
It doesn't seem to be an Asterisk issue; rather, the "@plt" string in gdb
indicates that the PLT in the linker is at fault.  Quite simply, the linker
cannot find the ao2_unlock function.  This is rather strange because the
PLT is used for lazy linking of symbols, which is not the linking type
requested for ao2_unlock() in our Makefile and may point to other
problems.

You need to report this error to your distribution vendor, as a problem in
their linker tools. 

Issue History 
Date Modified    Username       Field                    Change               
====================================================================== 
2009-11-11 14:51 tilghman       Note Added: 0113680                          
2009-11-11 14:51 tilghman       Status                   assigned => feedback
======================================================================




More information about the asterisk-bugs mailing list