[asterisk-bugs] [Asterisk 0017988]: Random deadlock in res_config_mysql
Asterisk Bug Tracker
noreply at bugs.digium.com
Tue Sep 14 15:04:09 CDT 2010
A NOTE has been added to this issue.
======================================================================
https://issues.asterisk.org/view.php?id=17988
======================================================================
Reported By: ricardolandim
Assigned To:
======================================================================
Project: Asterisk
Issue ID: 17988
Category: Addons/res_config_mysql
Reproducibility: sometimes
Severity: minor
Priority: normal
Status: acknowledged
Asterisk Version: 1.4.34
JIRA: SWP-2204
Regression: No
Reviewboard Link:
SVN Branch (only for SVN checkouts, not tarball releases): N/A
SVN Revision (number only!):
Request Review:
======================================================================
Date Submitted: 2010-09-14 08:36 CDT
Last Modified: 2010-09-14 15:04 CDT
======================================================================
Summary: Random deadlock in res_config_mysql
Description:
Asterisk randomly stops processing SIP calls. I cannot find a pattern of
external events triggering it. I have around 700 registers in realtime....
Asterisk version 1.4.32
I have compiled asterisk with DEBUG_THREADS. When this happers 'core show
locks' presents this... I am reporting 4 events (core show locks)...
I believe this bug is the same issue
https://issues.asterisk.org/view.php?id=15090 (fixed for 1.6.x but not fixed
for 1.4.x)
======================================================================
Relationships ID Summary
----------------------------------------------------------------------
related to 0015090 [patch] chan_sip random deadlock
======================================================================
----------------------------------------------------------------------
(0126957) lmadsen (administrator) - 2010-09-14 15:04
https://issues.asterisk.org/view.php?id=17988#c126957
----------------------------------------------------------------------
No, acknowledged just means debugging information has been provided. The
lock information may be enough, but I'm being proactive about asking for
additional information that may be required.
Issue History
Date Modified Username Field Change
======================================================================
2010-09-14 15:04 lmadsen Note Added: 0126957
======================================================================
More information about the asterisk-bugs
mailing list