[asterisk-bugs] [Asterisk 0011080]: SIP channel stops processing calls, but no apparent deadlock
noreply at bugs.digium.com
noreply at bugs.digium.com
Thu Dec 27 08:15:03 CST 2007
A NOTE has been added to this issue.
======================================================================
http://bugs.digium.com/view.php?id=11080
======================================================================
Reported By: callguy
Assigned To: russell
======================================================================
Project: Asterisk
Issue ID: 11080
Category: Channels/chan_sip/General
Reproducibility: always
Severity: block
Priority: normal
Status: assigned
Asterisk Version: 1.4.13
SVN Branch (only for SVN checkouts, not tarball releases): N/A
SVN Revision (number only!):
Disclaimer on File?: N/A
Request Review:
======================================================================
Date Submitted: 10-24-2007 15:58 CDT
Last Modified: 12-27-2007 08:15 CST
======================================================================
Summary: SIP channel stops processing calls, but no apparent
deadlock
Description:
Approximately once per week we are seeing asterisk stop processing SIP
calls. The behavior is the same as a deadlock, but core show locks does not
show any evidence that there is a deadlock.
The only way to resolve is to restart asterisk.
output of:
core show locks
info thread
thread apply all bt
from the running process is attached.
======================================================================
Relationships ID Summary
----------------------------------------------------------------------
related to 0011165 Deadlock in channel.c
======================================================================
----------------------------------------------------------------------
callguy - 12-27-07 08:15
----------------------------------------------------------------------
we just had another deadlock, looks similar but slightly different than the
previous two. we are getting these every few hours on recent builds, with
1.4.16 it was every couple of weeks on any given machine. It appears from
what I can see that manager logon/logoff at the same time as a phone
changing state and hints updating (sometimes with a reload thrown in) at
least appears to be one trigger.
russell - if you need access just let me know, we have the core files from
each of these generated as well.
Issue History
Date Modified Username Field Change
======================================================================
12-27-07 08:15 callguy Note Added: 0076015
======================================================================
More information about the asterisk-bugs
mailing list