| Summary: | ASTERISK-30148: 18.12.1 Crash / Sigabrt On Pjsip Transaction Destroy Under Load | ||||
| Reporter: | Joshua Elson (joshelson) | Labels: | |||
| Date Opened: | 2022-07-21 00:20:04 | Date Closed: | 2022-07-21 13:38:11 | ||
| Priority: | Minor | Regression? | |||
| Status: | Closed/Complete | Components: | Resources/res_pjsip | ||
| Versions: | 18.12.1 | Frequency of Occurrence | |||
| Related Issues: |
| ||||
| Environment: | Attachments: | ( 0) core-asterisk-2022-07-21T00-16-27Z-brief.txt ( 1) core-asterisk-2022-07-21T00-16-27Z-full.txt ( 2) core-asterisk-2022-07-21T00-16-27Z-info.txt ( 3) core-asterisk-2022-07-21T00-16-27Z-locks.txt ( 4) core-asterisk-2022-07-21T00-16-27Z-thread1.txt | |||
| Description: | Have been seeing a crash under load recently on Asterisk 18.12.1. This only seems to happen under significant system load.
Dialplan output immediately preceding the crash looks like this: [Jul 20 18:16:26] VERBOSE[16861] res_pjsip_registrar.c: Removed contact 'sip:mfd5bvlm@127.0.0.1:33282;transport=WS' from AOR '2127' due to shutdown [Jul 20 18:16:26] VERBOSE[62200] res_pjsip/pjsip_options.c: Contact 2127/sip:mfd5bvlm@127.0.0.1:33282;transport=WS has been deleted [Jul 20 18:16:26] VERBOSE[57198] res_pjsip_registrar.c: Attempted to remove non-existent contact 'sip:mfd5bvlm@127.0.0.1:33282;transport=WS' from AOR '2127' by request [Jul 20 18:16:26] WARNING[61845][C-00001f97] channel.c: Exceptionally long voice queue length queuing to CBAnn/2108-00000cf3;1 [Jul 20 18:16:26] WARNING[66942][C-0000230a] channel.c: Exceptionally long voice queue length queuing to CBAnn/2185-00000ea6;1 [Jul 20 18:16:29] Asterisk 18.12.1 built by root @ polaris on a x86_64 running Linux on 2022-05-24 06:25:08 UTC | ||||
| Comments: | By: Asterisk Team (asteriskteam) 2022-07-21 00:20:05.121-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: Joshua Elson (joshelson) 2022-07-21 00:23:29.422-0500 Attaching BT info. By: Joshua C. Colp (jcolp) 2022-07-21 03:48:08.385-0500 I believe based on the backtrace this is the same underlying issue as ASTERISK-28689, except that timing differences result in it occurring at a slightly different point. By: Joshua Elson (joshelson) 2022-07-21 12:57:27.838-0500 So in this setup, we are not using Asterisk realtime, but the path does look similar. We are able to reproduce this with some frequency. Any new thoughts on additional debugging or info we can provide to help? Or any other workarounds here? By: Asterisk Team (asteriskteam) 2022-07-21 12:57:28.476-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: Joshua C. Colp (jcolp) 2022-07-21 13:00:36.818-0500 Any thoughts/etc would be present on the other issue. The other issue already has backtraces and logging, so until someone investigates the issue deeply there's nothing really to add. By: Aaron An (aaron) 2022-09-09 02:58:11.883-0500 Hi Joshua， do you have any additional information about the crash of pjsip registor_aor when using realtime endpoints? By: Joshua C. Colp (jcolp) 2022-09-09 03:58:40.401-0500 I am not actively working on it. When someone starts, it will be assigned on the linked issue. Any further comments will also be placed there. | ||||