[asterisk-bugs] [Asterisk 0014648]: Asterisk becomes unresponsive and seems to be locked waiting on a mutex
Asterisk Bug Tracker
noreply at bugs.digium.com
Wed Mar 11 22:50:49 CDT 2009
The following issue has been SUBMITTED.
======================================================================
http://bugs.digium.com/view.php?id=14648
======================================================================
Reported By: tomsullivan
Assigned To:
======================================================================
Project: Asterisk
Issue ID: 14648
Category: General
Reproducibility: have not tried
Severity: block
Priority: normal
Status: new
Asterisk Version: 1.4.23
Regression: No
SVN Branch (only for SVN checkouts, not tarball releases): N/A
SVN Revision (number only!):
Request Review:
======================================================================
Date Submitted: 2009-03-11 22:50 CDT
Last Modified: 2009-03-11 22:50 CDT
======================================================================
Summary: Asterisk becomes unresponsive and seems to be locked
waiting on a mutex
Description:
After a restart, Asterisk became unresponsive. The Asterisk console still
worked, but no calls could be made. After a period, Asterisk was killed,
and a coredump generated.
The coredump shows that there were 1034 threads, 1015 of which were in
__lll_mutex_lock_wait () (/lib/libpthread.so.0). Below is a full backtrace
for one of these threads. All the waiting threads refer to the same lock
(lock_addr=0x6650f0).
Below is also a listing of the logs for the period during which it was
unresponsive.
======================================================================
Issue History
Date Modified Username Field Change
======================================================================
2009-03-11 22:50 tomsullivan New Issue
2009-03-11 22:50 tomsullivan Asterisk Version => 1.4.23
2009-03-11 22:50 tomsullivan Regression => No
2009-03-11 22:50 tomsullivan SVN Branch (only for SVN checkouts, not tarball
releases) => N/A
======================================================================
More information about the asterisk-bugs
mailing list