[Home]

Summary:ASTERISK-26161: chan_sip: Channels remain
Reporter:Pragash Thiagarajan (pragash)Labels:
Date Opened:2016-06-29 09:20:26Date Closed:2020-01-14 11:13:46.000-0600
Priority:MajorRegression?
Status:Closed/CompleteComponents:Channels/chan_sip/General
Versions:11.22.0 Frequency of
Occurrence		Frequent
Related
Issues:
Environment:Intel(R) Xeon(R) CPU X5647 @ 2.93GHz / 48 GB RAM - CentOS 7 with Asterisk 11.22.0Attachments:( 0) coreshotlocks.png
( 1) Use_GDB_to_collect_a_backtrace.png
Description:We have recently deployed Phone Server with Asterisk 11.22.0 & FreePBX 12. Currently we are getting "Warning: Autodestruct on dialog with owner in place (Method: BYE). Rescheduling destruction for 10000 ms" error frequently (every 3 Seconds). Currently this server is in Production. Also we found that once in while call not initiated as per our code. But we don't have any issues with the Asterisk 1.8.25 & 11.17.1 version.

Please advice, is there any latest patch to fix this issue or we need to downgrade this version.

Thanks in advance.
Comments:By: Asterisk Team (asteriskteam) 2016-06-29 09:20:27.259-0500

Thanks for creating a report! The issue has entered the triage process. That means the issue will wait in this status until a Bug Marshal has an opportunity to review the issue. Once the issue has been reviewed you will receive comments regarding the next steps towards resolution.

A good first step is for you to review the [Asterisk Issue Guidelines|https://wiki.asterisk.org/wiki/display/AST/Asterisk+Issue+Guidelines] if you haven't already. The guidelines detail what is expected from an Asterisk issue report.

Then, if you are submitting a patch, please review the [Patch Contribution Process|https://wiki.asterisk.org/wiki/display/AST/Patch+Contribution+Process].
By: Joshua C. Colp (jcolp) 2016-06-30 05:50:45.975-0500

Please follow the instructions on the wiki[1] for getting a backtrace as a result of a deadlock. Please also provide the console output and a description of the call flow and environment.

[1] https://wiki.asterisk.org/wiki/display/AST/Getting+a+Backtrace#GettingaBacktrace-GettingInformationForADeadlock
By: Pragash Thiagarajan (pragash) 2016-06-30 06:06:57.782-0500

I got attached screenshot error, not able to get any deadlock
By: Joshua C. Colp (jcolp) 2016-06-30 06:07:05.527-0500

These need to be attached as text files. As well you will only have the "core show locks" command when Asterisk is built with DEBUG_THREADS. As for the inability of gdb to get a backtrace, was Asterisk actually running and not shutting down? What kind of environment are you in?
By: Pragash Thiagarajan (pragash) 2016-06-30 06:23:09.851-0500

Asterisk running only. But if we execute this command "core show locks", we got "No such command 'core show locks' (type 'core show help core show locks' for other possible commands)". What will be next step?


By: Joshua C. Colp (jcolp) 2016-06-30 06:27:25.450-0500

In order to have "core show locks" you have to rebuild Asterisk itself with DEBUG_THREADS enabled in menuselect. The wiki[1] has the specific flags to enable documented. It's in the big yellow box.

[1] https://wiki.asterisk.org/wiki/display/AST/Getting+a+Backtrace#GettingaBacktrace-GettingInformationForADeadlock
By: Pragash Thiagarajan (pragash) 2016-06-30 06:32:15.228-0500

Okay. I will do the same and attach the same by today EOD
By: Asterisk Team (asteriskteam) 2016-07-14 12:00:01.240-0500

Suspended due to lack of activity. This issue will be automatically re-opened if the reporter posts a comment. If you are not the reporter and would like this re-opened please create a new issue instead. If the new issue is related to this one a link will be created during the triage process. Further information on issue tracker usage can be found in the Asterisk Issue Guidlines [1].

[1] https://wiki.asterisk.org/wiki/display/AST/Asterisk+Issue+Guidelines