Summary:	ASTERISK-26726: Call app.Dial with "d" option from lua dialplan freezes asterisk until kill the process of asterisk
Reporter:	Yuriy Gorlichenko (ovoshlook)	Labels:
Date Opened:	2017-01-18 04:42:51.000-0600	Date Closed:
Priority:	Major	Regression?
Status:	Open/New	Components:	Applications/app_dial PBX/pbx_lua
Versions:	11.25.0 13.10.0	Frequency of Occurrence	Constant
Related Issues:
Environment:	Ubuntu 16.04,14.04	Attachments:	( 0) core-show-locks.txt ( 1) debug.txt
Description:	I  calling app.Dial from extesnions.lua I have context. Presume it named main {noformat} ["main"]={   ["_XXXX"]=simpleDial,   ["0"]=app.NoOp("Works!") } function simpleDial(context,extension)     app.Answer()     app.Dial("SIP/"..extension,"10","d") end {noformat} After press 0 while extension ringing at the debug watch only  (at the asterisk 13.10) {noformat} pbx_lua.c:1480 lua_find_extension: Looking up 0@main:1 {noformat} Then asterisk freezes while I not kill the process I checked other versions of 13 asterisk, but there was not updates of pbx_lua module. In 14 asterisk updates also was not include nothing for this module so i suppose tha tthis issue will happen at the 14 asterisk also. But i will check.
Comments:	By: Asterisk Team (asteriskteam) 2017-01-18 04:42:53.944-0600 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: Rusty Newton (rnewton) 2017-01-18 09:25:34.519-0600 We require additional debug to continue with triage of your issue. Please follow the instructions on the wiki [1] for how to collect debugging information from Asterisk. For expediency, where possible, attach the debug with a '.txt' file extension so that the debug will be usable for further analysis. Thanks! [1] https://wiki.asterisk.org/wiki/display/AST/Collecting+Debug+Information By: Rusty Newton (rnewton) 2017-01-18 09:26:22.728-0600 Thanks for the report. In addition to the debug requested in the previous comment, please provide a trace and locks output as described in the following wiki section: https://wiki.asterisk.org/wiki/display/AST/Getting+a+Backtrace#GettingaBacktrace-GettingInformationForADeadlock By: Yuriy Gorlichenko (ovoshlook) 2017-01-18 13:30:29.570-0600 Added debug Will make trace and will post there soon By: Yuriy Gorlichenko (ovoshlook) 2017-01-18 13:33:44.599-0600 Added debug at the comment above. This message only for changing status By: Yuriy Gorlichenko (ovoshlook) 2017-01-18 13:44:52.655-0600 regarding locks I suppose that it can be impossible to run this command after issue will be setted asterisk -rx "core show locks" > /tmp/core-show-locks.txt Because asterisk have no any reaction on cli commands after issue It freezes as i said before until I will restart machine By: Yuriy Gorlichenko (ovoshlook) 2017-01-19 15:03:03.753-0600 Hi. Any updates regarding this issue? Also may be i needto provide some other logs? Or need some traces with different situations. you can use me as testing server) I will try to response ASAP By: Joshua C. Colp (jcolp) 2017-01-19 15:09:38.148-0600 Any updates will be posted on this issue including requests for more information. As well you should be aware that pbx_lua is in extended support, this means support is provided by the community and there is currently no active maintainer. It may take quite awhile for anyone to look at this issue and there is no guarantee on when it will. By: Rusty Newton (rnewton) 2017-01-19 15:26:26.946-0600 {quote} regarding locks I suppose that it can be impossible to run this command after issue will be setted asterisk -rx "core show locks" > /tmp/core-show-locks.txt Because asterisk have no any reaction on cli commands after issue It freezes as i said before until I will restart machine {quote} I understand. In that case you should get the backtrace as described in the article I linked. Here it is again: https://wiki.asterisk.org/wiki/display/AST/Getting+a+Backtrace#GettingaBacktrace-GettingInformationForADeadlock By: Yuriy Gorlichenko (ovoshlook) 2017-01-20 14:25:34.003-0600 Core show locks By: Rusty Newton (rnewton) 2017-01-20 17:11:16.672-0600 Thanks, if you can provide the backtrace in addition it may help as well. I've opened up the issue.