Summary:	ASTERISK-30501: Frack assertion error in while loop in stasis.c
Reporter:	Abhay Gupta (agupta)	Labels:
Date Opened:	2023-04-24 02:50:44	Date Closed:	2023-04-24 06:03:22
Priority:	Minor	Regression?
Status:	Closed/Complete	Components:	Resources/res_stasis
Versions:	18.17.0	Frequency of Occurrence	Frequent
Related Issues:	is related to ASTERISK-30445 stasis: Off-nominal channel leave causes bridge to be destroyed
Environment:	Ubuntu 22 with asterisk 18.xx using ARI	Attachments:	( 0) log1.txt ( 1) log2.txt
Description:	stasis.c: FRACK!, Failed assertion bad magic number 0x0 for object 0x7f80280018f0 (0) Got 16 backtrace records # 0: asterisk(__ao2_trylock+0x1de) [0x5568e5e2d1ae] # 1: asterisk(stasis_forward_all+0x15a) [0x5568e5f5ec1a] # 2: /usr/lib/asterisk/modules/res_stasis.so(+0x12f66) [0x7f827de0ff66] # 3: /usr/lib/asterisk/modules/res_stasis.so(+0x1795e) [0x7f827de1495e] # 4: /usr/lib/asterisk/modules/res_stasis.so(+0x1526b) [0x7f827de1226b] # 5: /usr/lib/asterisk/modules/res_stasis.so(+0x184c0) [0x7f827de154c0] # 6: /usr/lib/asterisk/modules/res_stasis.so(stasis_app_exec+0x4a0) [0x7f827de0a600] # 7: /usr/lib/asterisk/modules/app_stasis.so(+0x13c9) [0x7f827dbe03c9] # 8: asterisk(pbx_exec+0xdc) [0x5568e5f0fdcc] # 9: /usr/lib/asterisk/modules/pbx_realtime.so(+0x3a90) [0x7f827dd49a90] #10: asterisk(+0x144158) [0x5568e5f04158] #11: asterisk(+0x145f82) [0x5568e5f05f82] #12: asterisk(+0x147651) [0x5568e5f07651] #13: asterisk(+0x1cf348) [0x5568e5f8f348] #14: /lib/x86_64-linux-gnu/libpthread.so.0(+0x8609) [0x7f82817ae609] #15: /lib/x86_64-linux-gnu/libc.so.6(clone+0x43) [0x7f828152e133]
Comments:	By: Asterisk Team (asteriskteam) 2023-04-24 02:50:47.489-0500 WARNING JIRA will be going read-only at the end of April, 2023. We will be starting fresh on Github at https://github.com/asterisk/asterisk at that time. No issues or patches will be copied to Github. If you file an issue on JIRA at this time you will need to recreate it on Github after this date. The same applies if you have a patch. WARNING 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. Please note that log messages and other files should not be sent to the Sangoma Asterisk Team unless explicitly asked for. All files should be placed on this issue in a sanitized fashion as needed. 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]. Please note that once your issue enters an open state it has been accepted. As Asterisk is an open source project there is no guarantee or timeframe on when your issue will be looked into. If you need expedient resolution you will need to find and pay a suitable developer. Asking for an update on your issue will not yield any progress on it and will not result in a response. All updates are posted to the issue when they occur. Please note that by submitting data, code, or documentation to Sangoma through JIRA, you accept the Terms of Use present at [https://www.asterisk.org/terms-of-use/|https://www.asterisk.org/terms-of-use/]. By: Abhay Gupta (agupta) 2023-04-24 02:52:32.757-0500 Even the bigger issue is that this assertion error comes in topic_lock_both where we have a permanent while loop while (ao2_trylock(topic2)) so asterisk gets stuck and keep printing the same error . By: Joshua C. Colp (jcolp) 2023-04-24 04:44:56.062-0500 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: Abhay Gupta (agupta) 2023-04-24 05:11:44.503-0500 Full debug log of 2 crash instances By: Joshua C. Colp (jcolp) 2023-04-24 05:20:50.162-0500 This is not a full debug log with all the information. You will also need to give details about your usage of ARI. I'm asking because an issue recently came in[1] which could be the same as this. You have also given the wrong version on this issue, as your log shows you are using 18.9 certified. This version will NOT receive any fixes as a result of this unless you are a support agreement customer. If you are a support agreement customer then you will need to contact support. [1] https://issues.asterisk.org/jira/browse/ASTERISK-30445 By: Abhay Gupta (agupta) 2023-04-24 05:55:24.176-0500 Incoming calls comes in STASIS , we are using add bridge , add channel to bridge , delete channel from bridge and delete bridge command . Also for outgoing call we use create channel and dial , move stasis is also used . By: Joshua C. Colp (jcolp) 2023-04-24 05:58:55.816-0500 Then it is most likely the already existing and open ASTERISK-30445 issue.