[Home]

Summary:ASTERISK-24359: Deadlock in chan_sip.c when monitoring
Reporter:Kevin Scott Adams (nivek)Labels:
Date Opened:2014-09-26 07:29:28Date Closed:2014-10-14 17:17:31
Priority:MajorRegression?
Status:Closed/CompleteComponents:Channels/chan_sip/General
Versions:1.8.29.0 Frequency of
Occurrence
Occasional
Related
Issues:
Environment:CentOS 5 x86_64 kernel 2.6.18-274.18.1Attachments:( 0) locks_output.txt
Description:Been getting some deadlocks recently and the only thing I can point to is monitoring a channel.  Seems to be a weekly occurrence but no feed back from the users what they were doing at the time.

[Edit by Rusty - large inline debug excerpt removed per the guidelines.]

This locks the entire system asterisk system.

Thanks,

Kev
Comments:By: Rusty Newton (rnewton) 2014-09-30 15:26:49.362-0500

Attaching reporters debug after removing from the description.

By: Rusty Newton (rnewton) 2014-09-30 15:32:17.437-0500

[~nivek] please read through the [Asterisk Issue Guidelines|https://wiki.asterisk.org/wiki/display/AST/Asterisk+Issue+Guidelines] to see how to use the tracker and what we typically need for various issues. Try not to post large chunks of debug into description or comment fields. It ends up making for a lot of scrolling and difficulty reading if the issue gets lengthy.

In this case, can you provide also:

*  An [Asterisk log|https://wiki.asterisk.org/wiki/display/AST/Collecting+Debug+Information] captured up to the time of the deadlock.
* If possible can you recompile with DEBUG_THREADS, DONT_OPTIMIZE and BETTER_BACKTRACES, so that the next lock output and trace you get will include additional information.
* Provide a [Backtrace|https://wiki.asterisk.org/wiki/display/AST/Getting+a+Backtrace#GettingaBacktrace-GettingInformationForADeadlock] and the output of "core show locks" from the CLI.

Be sure the Asterisk log correlates to the particular lock of course.

Thanks a ton!


By: Rusty Newton (rnewton) 2014-10-14 17:17:25.106-0500

Suspended due to lack of activity. Please request a bug marshal in #asterisk-bugs on the IRC network irc.freenode.net to reopen the issue should you have the additional information requested.  Further information can be found at http://www.asterisk.org/developers/bug-guidelines