[asterisk-bugs] [Asterisk 0013886]: CPU Usage Increases and then Asterisk Crashes

[Asterisk Bug Tracker]

A NOTE has been added to this issue. 
====================================================================== 
http://bugs.digium.com/view.php?id=13886 
====================================================================== 
Reported By:                nasirq
Assigned To:                file
====================================================================== 
Project:                    Asterisk
Issue ID:                   13886
Category:                   General
Reproducibility:            random
Severity:                   crash
Priority:                   normal
Status:                     feedback
Asterisk Version:           1.4.22 
Regression:                 No 
SVN Branch (only for SVN checkouts, not tarball releases): N/A 
SVN Revision (number only!):  
Request Review:              
====================================================================== 
Date Submitted:             2008-11-12 08:45 CST
Last Modified:              2009-04-01 01:34 CDT
====================================================================== 
Summary:                    CPU Usage Increases and then Asterisk Crashes
Description: 
I am using Asterisk in a Call Center Environment. I am using
AgentCallbackLogin for Agents. The Agents are on SIP phones (Polycom). 

I am using the Asterisk::Manager perl api for connection to the manager
interface for CTI. One perl script runs (using Asterisk::Manager) and does
two things. First it send Action: Status every 500 ms to get the list of
currently active channels and populates them in a MySQL table. Secondly it
reads a directory for files, which if created consists Managers Actions. It
reads the file, sends the actions to Asterisk and deletes the file. This
way I can send many Managers actions while having only one manager
connection to the Asterisk. 

I have used this approach to reduce the load on Asterisk if many clients
need to read the Events or send actions.

The problem I am facing is that sometimes (and I am unable to find the
steps to reproduce) when sending actions, this interface seems to hang. No
more actions get processed and the CPU usage starts to climb up. Using top
I have seen more than two and sometimes five to six asterisk threads using
a lot of CPU. Some times new calls go through and sometimes not. Sometimes
after the active calls are hanged up everything gets back to normal and
some times it gets worst. Using soft hangup on CLI does not work and even
using restart now does not do anything. The only option left is using
killall -9 asterisk. 

At this stage of this issue, I need expert guidance to enable me to
further dig in to find out what could be wrong when this occurs. 

Please help me out.


====================================================================== 

---------------------------------------------------------------------- 
 (0102524) nasirq (reporter) - 2009-04-01 01:34
 http://bugs.digium.com/view.php?id=13886#c102524 
---------------------------------------------------------------------- 
Today we again faced this problem and I was not doing any thing (sending
actions) that I stated when I started this report.

First I was able to do a "show channels" and get results, and then I did
the gdb thing. After that the show channels was not working (output of
asterisk CLI and gdb attached). I did gdb again. (both outputs attached).
Asterisk process was using a lot of CPU
  PID USER      PR  NI  VIRT  RES  SHR S %CPU %MEM    TIME+  COMMAND
 3283 root      20   0  608m  16m 7284 S 83.8  0.2 128:21.42 asterisk


My asterisk is only compiled with DONT_OPTIMIZE. I am recompiling it to
your specs, and will do the change over on the weekend. I did'nt ready the
post carefully so was not able to do core show locks. Will remember it next
time as well. 

Issue History 
Date Modified    Username       Field                    Change               
====================================================================== 
2009-04-01 01:34 nasirq         Note Added: 0102524                          
======================================================================