Summary:	ASTERISK-29979: app_chanisavail: Crash when requesting PJSIP channel
Reporter:	Rustam Fayzullin (Rustik665)	Labels:
Date Opened:	2022-03-22 08:18:18	Date Closed:
Priority:	Minor	Regression?
Status:	Open/New	Components:	Applications/app_chanisavail Channels/chan_pjsip Core/General
Versions:	18.4.0 18.10.1	Frequency of Occurrence	Frequent
Related Issues:
Environment:	Centos 7 (3.10.0-1062.18.1.el7.x86_64) on vmware virtualization	Attachments:	( 0) core-asterisk-2022-03-22T08-34-42Z-brief.txt ( 1) core-asterisk-2022-03-22T08-34-42Z-full.txt ( 2) core-asterisk-2022-03-22T08-34-42Z-info_scrubbed.txt ( 3) core-asterisk-2022-03-22T08-34-42Z-locks.txt ( 4) core-asterisk-2022-03-22T08-34-42Z-thread1.txt ( 5) core-asterisk-2022-04-18T05-05-01Z-brief.txt ( 6) core-asterisk-2022-04-18T05-05-01Z-full.txt ( 7) core-asterisk-2022-04-18T05-05-01Z-info.txt ( 8) core-asterisk-2022-04-18T05-05-01Z-locks.txt ( 9) core-asterisk-2022-04-18T05-05-01Z-thread1.txt (10) docker_container_config.txt (11) segfault_asterisk_full_log_cleared.txt
Description:	Asterisk randomly crashes with segmentation fault. Sometimes once a month, sometimes 2-3 times a week. We have over a 100 VMs with asterisk and the most loaded of them fall most often. Nothing suspicious was found in asterisk logs. Also we couldn't reproduce the crash.
Comments:	By: Asterisk Team (asteriskteam) 2022-03-22 08:18:19.529-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. 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: Rustam Fayzullin (Rustik665) 2022-03-22 08:19:08.104-0500 Here are backtrace By: Joshua C. Colp (jcolp) 2022-03-22 08:21:12.292-0500 It appears the bug you have submitted is against a rather old version of a supported branch of Asterisk. There have been many issues fixed between the version you are using and the current version of your branch. Please test with the latest version in your Asterisk branch and report whether the issue persists. Please see the Asterisk Versions [1] wiki page for info on which versions of Asterisk are supported. [1] https://wiki.asterisk.org/wiki/display/AST/Asterisk+Versions By: Joshua C. Colp (jcolp) 2022-03-22 08:25:52.825-0500 Asterisk 18 is supported. Asterisk 18.4.0 is almost a year old, and there have been 6 releases since then with bug fixes. Supporting 18.4.0 would mean going through over a year of changes to see if any change was done that could have fixed or resolved this. You're free to do that if you wish, but as a project we can't sink time into supporting such things when they may have already been fixed and resolved. By: Rustam Fayzullin (Rustik665) 2022-03-22 08:28:13.988-0500 Thanks, we'll try! By: Asterisk Team (asteriskteam) 2022-04-05 12:00:01.235-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 By: Rustam Fayzullin (Rustik665) 2022-04-18 01:50:40.780-0500 Hello! We updated to 18.10.1 and unfortunately it didn't help. The same problem. I will attach new files. By: Asterisk Team (asteriskteam) 2022-04-18 01:50:41.325-0500 This issue has been reopened as a result of your commenting on it as the reporter. It will be triaged once again as applicable. By: Rustam Fayzullin (Rustik665) 2022-04-18 01:54:00.445-0500 Core dumps By: Benjamin Keith Ford (bford) 2022-04-18 11:26:49.490-0500 Unfortunately there's no obvious sign as to what's causing the crash in the thread1 file, and the other files that would have the thread information don't have anything in them. If it's possible to get logs leading up to the crash, that would be nice to have (although I know these can get rather large over time). If it crashes again, save the core dump itself just in case we end up needing to take a look at that. Is this a system used in production, or a test system that would be possible to make changes to if needed to debug the issue? By: Rustam Fayzullin (Rustik665) 2022-04-18 23:49:38.474-0500 Full log before asterisk was crashed By: Rustam Fayzullin (Rustik665) 2022-04-18 23:57:39.326-0500 Core dump is now enabled, at least for the near future. The system is used in production. We have multiple asterisk instances with this issue. I'll add that asterisks are used in docker containers, so I'll attach container config, if it matters. By: Rustam Fayzullin (Rustik665) 2022-04-18 23:57:58.971-0500 asterisk container info By: Rustam Fayzullin (Rustik665) 2022-07-24 23:23:13.001-0500 Hello! Have you found out something? By: Joshua C. Colp (jcolp) 2022-07-25 03:56:41.877-0500 This issue is open and unassigned, noone is actively working on it. If there are any comments they will be posted here.