[Home]

Summary:ASTERISK-24638: Crash after destroying a stasis bridge
Reporter:John Bigelow (jbigelow)Labels:
Date Opened:2014-12-22 16:17:56.000-0600Date Closed:2018-01-02 08:38:47.000-0600
Priority:MajorRegression?
Status:Closed/CompleteComponents:Resources/res_ari_bridges Resources/res_ari_channels
Versions:SVN 13.1.0 Frequency of
Occurrence		Constant
Related
Issues:
Environment:Asterisk branch 13 r429984, Testsuite trunk r6133Attachments:( 0) backtrace_15622.txt
( 1) extensions.conf
( 2) full-asterisk.txt
( 3) full-asterisk-rb925-r6-patch.txt
( 4) full-testsuite.txt
( 5) full-testsuite-rb925-r6-patch.txt
( 6) test-config.yaml
Description:During the development of a testsuite test, the attached test-config.yaml constantly crashes Asterisk. It may have something to do with the order in which ARI requests/AMI actions are executed.
Comments:By: John Bigelow (jbigelow) 2015-01-06 14:50:12.553-0600

To check if a patch for ASTERISK-24560 resolves this problem, I applied the patch and replaced the file {{test-config.yaml}} with the attached file under {{tests/rest_api/external_interaction/bridge_app/stasis_bridge/}} and executed the test. Asterisk no longer crashes but many *FRACK* messages occur and the test fails. I noticed there are also many backtraces within the Asterisk full log file. The testsuite full log shows additional info for the FRACK messages such as the function name and line number.

I've attached the following from the test execution with the patch applied:
* full-asterisk-rb925-r6-patch.txt
** Get FRACK, backtrace, ARI errors, and other error messages:
{code}
awk '/FRACK|backtrace|logger.c: #|ari_model_validators.c/ {print;}
/Response validation failed for/ {print; for(i=1; i<=7; i++) {getline; print}}' full-asterisk-rb925-r6-patch.txt | less
{code}
* full-testsuite-rb925-r6-patch.txt
** Get FRACK messages and ARI error responses:
{code}
awk '/FRACK/ {print;}
/ERROR.*response 500 {/ {print; for(i=1; i<=2; i++) {getline; print}}' full-testsuite-rb925-r6-patch.txt | less
{code}
By: John Bigelow (jbigelow) 2015-01-06 14:50:25.243-0600

*It's been determined that this crash differs from the one reported on ASTERISK-24560.*
By: Corey Farrell (coreyfarrell) 2017-12-14 12:11:37.850-0600

It looks like the attached test-config.yaml no longer causes a crash but it still fails.  Could you take another look to see if this indicates an error in the test or a bug in Asterisk?
By: Asterisk Team (asteriskteam) 2018-01-02 08:38:47.236-0600

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