[asterisk-bugs] [Asterisk 0010318]: chan_sip hangs with big number of sip channels

[noreply at bugs.digium.com]

A NOTE has been added to this issue. 
====================================================================== 
http://bugs.digium.com/view.php?id=10318 
====================================================================== 
Reported By:                IgorG
Assigned To:                
====================================================================== 
Project:                    Asterisk
Issue ID:                   10318
Category:                   Channels/chan_sip/General
Reproducibility:            sometimes
Severity:                   major
Priority:                   normal
Status:                     feedback
Asterisk Version:            1.2.22  
SVN Branch (only for SVN checkouts, not tarball releases):  1.2  
SVN Revision (number only!):  
Disclaimer on File?:        N/A 
Request Review:              
====================================================================== 
Date Submitted:             07-27-2007 02:01 CDT
Last Modified:              07-31-2007 22:39 CDT
====================================================================== 
Summary:                    chan_sip hangs with big number of sip channels
Description: 
After two days on production system (4 ISDN lines) SIP phones can't
register and make calls. mISDN channel seems work (on console I see
incoming calls).

'sip show channels' show 91 active(!) channels

'show channels' show only 9 active channels

command 'restart now' do not restart asterisk


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

---------------------------------------------------------------------- 
 murf - 07-31-07 22:39  
---------------------------------------------------------------------- 
I looked at the core, but I see nothing helpful there concerning a
deadlock... (anyone else see something I don't?).

But, recently we discovered that gcore related mechanisms don't yield as
readable a core file as you would get if the process crashed and dumped
core. So, while I've made recent modes to ast_grab_core, I suggest you try
this again, and repeat these steps by hand:

1. find the pid (process id) of the asterisk process. you can follow
ast_grab_core for ways to do this; you can use ps, or look for the lock
file...

2. as root, issue the command "kill -11 <pid>" where <pid> is the process
id you dug up. Asterisk will die, and dump a core, usually "core.<pid>";
it's in whatever directory that asterisk was started in (commonly /tmp, if
you use safe_asterisk).

3. run "gdb asterisk <path to the core.<pid> file"

4. tell gdb to "thread apply all bt full"

5. collect the results and post them to this bug. If all goes well, there
will be much more detail in the backtrace! 

Issue History 
Date Modified   Username       Field                    Change               
====================================================================== 
07-31-07 22:39  murf           Note Added: 0068181                          
======================================================================