[asterisk-bugs] [Asterisk 0018595]: Asterisk SVN 1.8 running at 99% CPU

[Asterisk Bug Tracker]

A NOTE has been added to this issue. 
====================================================================== 
https://issues.asterisk.org/view.php?id=18595 
====================================================================== 
Reported By:                zeero
Assigned To:                
====================================================================== 
Project:                    Asterisk
Issue ID:                   18595
Category:                   Core/General
Reproducibility:            random
Severity:                   major
Priority:                   normal
Status:                     feedback
Asterisk Version:           SVN 
JIRA:                        
Regression:                 No 
Reviewboard Link:            
SVN Branch (only for SVN checkouts, not tarball releases): 1.8 
SVN Revision (number only!): 299449 
Request Review:              
====================================================================== 
Date Submitted:             2011-01-10 21:45 CST
Last Modified:              2011-01-13 03:43 CST
====================================================================== 
Summary:                    Asterisk SVN 1.8 running at 99% CPU
Description: 
Asterisk (SVN-branch-1.8-r299449) process is processing calls (10 per
minute) but running at 99% CPU utilisation. The asterisk process runs at
low CPU utilisation for approximately 2 weeks before pegging at 99%
utilisation.
Have tried several asterisk releases with the same issue. 
====================================================================== 

---------------------------------------------------------------------- 
 (0130444) schmidts (manager) - 2011-01-13 03:43
 https://issues.asterisk.org/view.php?id=18595#c130444 
---------------------------------------------------------------------- 
your snmp looks like you have cached a deadlock but not bad enough to kill
the whole system.

why do you use the do not fork option -f? any special reason for this?

you should try to use safe_asterisk then IMHO gdb will not kill the
process.

if this happens again try to catch the core show locks in the console not
with a cron job, cause every minute will not be often enough.

thx

stefan 

Issue History 
Date Modified    Username       Field                    Change               
====================================================================== 
2011-01-13 03:43 schmidts       Note Added: 0130444                          
======================================================================