[asterisk-bugs] [Asterisk 0012603]: Asterisk locks up and cannot process incoming SIP messages on 1.4.20-rc1

[noreply at bugs.digium.com]

A NOTE has been added to this issue. 
====================================================================== 
http://bugs.digium.com/view.php?id=12603 
====================================================================== 
Reported By:                jyap
Assigned To:                
====================================================================== 
Project:                    Asterisk
Issue ID:                   12603
Category:                   Channels/chan_sip/General
Reproducibility:            always
Severity:                   minor
Priority:                   normal
Status:                     feedback
Asterisk Version:           1.4.20 
SVN Branch (only for SVN checkouts, not tarball releases): N/A 
SVN Revision (number only!):  
Disclaimer on File?:        N/A 
Request Review:              
====================================================================== 
Date Submitted:             05-07-2008 15:53 CDT
Last Modified:              05-28-2008 15:58 CDT
====================================================================== 
Summary:                    Asterisk locks up and cannot process incoming SIP
messages on 1.4.20-rc1
Description: 
This may be related to: http://bugs.digium.com/view.php?id=12584 or
http://bugs.digium.com/view.php?id=12596

Filing this bug separately as I'm not sure.

Attached will be outputs from 'core show locks'.

======================================================================
Relationships       ID      Summary
----------------------------------------------------------------------
related to          0012584 Lock errors on the CLI
====================================================================== 

---------------------------------------------------------------------- 
 putnopvut - 05-28-08 15:58  
---------------------------------------------------------------------- 
Gotcha. Okay, from the backtrace you provided, Asterisk is not attempting
to acquire any locks, so it's no surprise that the core show locks output
is empty. As for what's causing the holdup, I'm not sure just yet as all
threads involved are in states that seem normal.

The one exception is thread 101 (the topmost thread in the backtrace
provided). It's either "stuck" in the fork() system call (or your backtrace
just happened to be taken as the thread was forking). I'd be interested to
know if after waiting a few seconds that thread is still attempting to
fork. If so, it would appear that something is happening within the fork
system call that is causing it not to complete. I did some quick Googling
and cannot seem to find a condition by which fork() would fail to return.

I could, of course, be chasing a red herring with this fork() idea, but if
the problem occurs again, it would be interesting to see if after waiting
several seconds between grabbing backtraces, the thread is still stuck
forking.

---
By the way, this problem you're experiencing is not related to the
original bug reported here. I suggest opening a new bug report and
attaching the backtrace from here to there. I'll copy the main text of this
note to the new bug as well. Thanks! 

Issue History 
Date Modified   Username       Field                    Change               
====================================================================== 
05-28-08 15:58  putnopvut      Note Added: 0087467                          
======================================================================