Summary:	ASTERISK-26136: pjsip deadlock after a while when a transport config is wrong
Reporter:	Ludovic Gasc (Eyepea) (gmludo)	Labels:
Date Opened:	2016-06-21 17:20:06	Date Closed:	2020-01-14 11:14:02.000-0600
Priority:	Major	Regression?
Status:	Closed/Complete	Components:	Resources/res_pjsip
Versions:	13.9.1	Frequency of Occurrence	Constant
Related Issues:
Environment:	Debian 8.5 64bits	Attachments:
Description:	To reproduce the bug: # You must have several transports. Create a wrong transport section. For example, add *send_pai=yes* in transport. # Configure an endpoint that uses this wrong transport # Configure another endpoint that use a good transport # Restart asterisk # In logs, you'll have: in aco_process_var: Could not find option suitable for category 'XXXX' named 'send_pai' # Now, with the endpoint you have, try to call several times and reload several times configuration with *pjsip reload* during 15 minutes # After a moment, it will be impossible to call and *pjsip reload* won't work anymore # You must use kill -9 to stop asterisk It gives you an idea for the issue, or need to recompile Asterisk to have more debug details ? Have a nice day.
Comments:	By: Asterisk Team (asteriskteam) 2016-06-21 17:20:07.188-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-21 19:11:42.916-0500 Thank you for taking the time to report this bug and helping to make Asterisk better. Unfortunately, we cannot work on this bug because your description did not include enough information. Please read over the Asterisk Issue Guidelines [1] which discusses the information necessary for your issue to be resolved and the format that information needs to be in. We would be grateful if you would then provide a more complete description of the problem. At a minimum, we need: 1. The specific steps or actions you took that caused you to encounter the problem. 2. The behavior you expected and the location of documentation that led you to that expectation. 3. The behavior you actually encountered. To demonstrate the issue in detail, please include Asterisk log files generated per the instructions on the wiki [2]. If applicable, please ensure that protocol-level trace debugging is enabled, e.g., 'sip set debug on' if the issue involves chan_sip, and configuration information such as dialplan and channel configuration. Thanks! [1] https://wiki.asterisk.org/wiki/display/AST/Asterisk+Issue+Guidelines [2] https://wiki.asterisk.org/wiki/display/AST/Collecting+Debug+Information In this case the log files and output would be useful. You can also use the instructions at https://wiki.asterisk.org/wiki/display/AST/Getting+a+Backtrace#GettingaBacktrace-GettingInformationForADeadlock to get the deadlock info needed. By: Ludovic Gasc (Eyepea) (gmludo) 2016-06-22 01:25:27.137-0500 Ok, thanks for the links, we'll do that. By: Ludovic Gasc (Eyepea) (gmludo) 2016-06-22 01:41:12.220-0500 Could you reattribute again the issue ? I didn't know that the assignee will change automatically after a comment. By: Asterisk Team (asteriskteam) 2016-07-06 12:00:01.449-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