[Home]

Summary:ASTERISK-23414: chan_sip stops responding after a about 5-20 minutes
Reporter:Dennis DeDonatis (dennisd)Labels:
Date Opened:2014-03-04 13:19:17.000-0600Date Closed:2014-03-04 15:58:07.000-0600
Priority:MajorRegression?Yes
Status:Closed/CompleteComponents:Channels/chan_sip/TCP-TLS
Versions:11.6.0 11.6.1 11.7.0 11.8.0 Frequency of
Occurrence
Constant
Related
Issues:
is duplicated byASTERISK-22851 Asterisk/SIP+RTP stops responding when compiled with DEBUG_THREADS
Environment:x86_64 Fedora 19 3.13.5-101Attachments:( 0) example1.txt
( 1) example2.txt
Description:11.5.1 works with no issues.  Any version (I did not try 12) after that will eventually deadlock after 5-20 minutes.

I'm GUESSING it may have to do with using TCP for signaling (as most people aren't doing that).
Comments:By: Matt Jordan (mjordan) 2014-03-04 13:31:39.297-0600

This may sound odd, but do you run into any problems when {{DEBUG_THREADS}} is not enabled?

By: Dennis DeDonatis (dennisd) 2014-03-04 14:27:39.494-0600

Well, it's been running 11.8.0, with no changes except not setting DEBUG_THREADS, for almost 30 minutes now...

By: Dennis DeDonatis (dennisd) 2014-03-04 15:52:03.931-0600

Still up with no issues - almost 2 hours, so whatever you are thinking with regard to DEBUG_THREADS seems to be correct.  There is almost no possible way it wouldn't have a locking issue by now.

By: Matt Jordan (mjordan) 2014-03-04 15:58:07.129-0600

I'm going to go ahead and close this out as a duplicate of ASTERISK-22851 (which was the issue I suspected it was).

{{DEBUG_THREADS}} is a bit wonky right now and cause some odd locking issues. Unless you have an active deadlock - and other than one involving {{pbx_realtime}}, there aren't a lot floating around out there - I wouldn't run with {{DEBUG_THREADS}}.

It's a performance killer anyway...