[asterisk-bugs] [Asterisk 0018619]: Asterisk deadlocks with no errors
Asterisk Bug Tracker
noreply at bugs.digium.com
Fri Jan 14 09:14:34 CST 2011
A NOTE has been added to this issue.
======================================================================
https://issues.asterisk.org/view.php?id=18619
======================================================================
Reported By: wufan
Assigned To:
======================================================================
Project: Asterisk
Issue ID: 18619
Category: Core/General
Reproducibility: random
Severity: minor
Priority: normal
Status: new
Asterisk Version: 1.6.2.15
JIRA:
Regression: No
Reviewboard Link:
SVN Branch (only for SVN checkouts, not tarball releases): N/A
SVN Revision (number only!):
Request Review:
======================================================================
Date Submitted: 2011-01-14 07:57 CST
Last Modified: 2011-01-14 09:14 CST
======================================================================
Summary: Asterisk deadlocks with no errors
Description:
Hi,
we have every https://issues.asterisk.org/view.php?id=5#c1-2 weeks a deadlock.
Max 10 cc. About 40 users.
Never get any error message or warning.
Last time it happend 2010-12-21 (with version 1.6.2.13) the console
outputs some sip destroying packets and the peers go offline about 5
minutes later availible again and so on.. the asterisk didnt answered to
the sip packets or answered after a few seconds.
This time it happened (1 hour ago) (with version 1.6.2.15) there are no
such errors .. only nothing :)
When i wrote "sip show peers" it showed me the peers
but console dial 50 at context did nothing.
======================================================================
----------------------------------------------------------------------
(0130498) davidw (reporter) - 2011-01-14 09:14
https://issues.asterisk.org/view.php?id=18619#c130498
----------------------------------------------------------------------
That version of Linux is too recent for the problem, as well. (There is a
problem in some versions of Linux were an interrupt latency problem can
cause an HPET wrap round in the RTC simulation. Typically that wrap round
takes about 300 seconds, during which an Asterisk relying on dahdi-dummy
has no internal timing. Dahdi 2.4.0 no longer uses the RTC and later
versions of Linux handle the RTC simulation safely. Your mention of 5
minutes made me wonder if you had this problem.)
Issue History
Date Modified Username Field Change
======================================================================
2011-01-14 09:14 davidw Note Added: 0130498
======================================================================
More information about the asterisk-bugs
mailing list