[Home]

Summary:ASTERISK-30005: res_pjsip: Crash when retrieving session due to destroyed dialog
Reporter:LA (learbia)Labels:
Date Opened:2022-04-01 13:17:25Date Closed:
Priority:MajorRegression?
Status:Open/NewComponents:Resources/res_pjsip
Versions:18.10.0 18.11.3 18.13.0 Frequency of
Occurrence
Related
Issues:
Environment:Attachments:( 0) core-asterisk-2022-04-01T16-41-10Z-brief.txt
( 1) core-asterisk-2022-04-01T16-41-10Z-full.txt
( 2) core-asterisk-2022-04-01T16-41-10Z-info.txt
( 3) core-asterisk-2022-04-01T16-41-10Z-locks.txt
( 4) core-asterisk-2022-04-01T16-41-10Z-thread1.txt
( 5) core-asterisk-2022-04-06T16-28-11Z-brief.txt
( 6) core-asterisk-2022-04-06T16-28-11Z-full.txt
( 7) core-asterisk-2022-04-06T16-28-11Z-info.txt
( 8) core-asterisk-2022-04-06T16-28-11Z-locks.txt
( 9) core-asterisk-2022-04-06T16-28-11Z-thread1.txt
Description:Asterisk crash many times

The incidence is increased when have netwok  connectivity problem
Comments:By: Asterisk Team (asteriskteam) 2022-04-01 13:17:25.939-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: LA (learbia) 2022-04-01 13:18:37.994-0500

Dump Files
By: Joshua C. Colp (jcolp) 2022-04-01 13:24:37.838-0500

Was Asterisk built without optimizations so that the backtrace is fully useful? What was going on at the time (please provide an accompanying Asterisk log)? Did this just start happening? Was it not occurring in a previous version (if so what version)? You say "many times" - how often is that actually?
By: Joshua C. Colp (jcolp) 2022-04-01 13:26:12.902-0500

And I assume this is after the other patch was applied fixing the other issue? Is it crashing the same amount as before?
By: LA (learbia) 2022-04-01 13:32:22.418-0500

This happen 4 a 6 times per week.
aways happen when a have a higth traffic calls in  server

I started asterisk with asterisk -g and after crash he generate a core file
By: LA (learbia) 2022-04-01 13:33:49.704-0500

This happen in other versions too
By: Joshua C. Colp (jcolp) 2022-04-01 13:40:10.295-0500

Was Asterisk built according to the instructions[1]? That is, with the DONT_OPTIMIZE option set?

[1] https://wiki.asterisk.org/wiki/display/AST/Getting+a+Backtrace
By: LA (learbia) 2022-04-01 13:48:23.508-0500

Yes, my all  opened issues I  generate  files with from documentation method
By: LA (learbia) 2022-04-01 13:49:10.164-0500

I have a full core and I can put in my drive if necessary
By: Joshua C. Colp (jcolp) 2022-04-01 13:53:13.901-0500

Can you also provide a debug log[1] so I can see the progression of things?

[1] https://wiki.asterisk.org/wiki/display/AST/Collecting+Debug+Information
By: LA (learbia) 2022-04-01 14:11:02.371-0500

OK, so

1) I enable debug_log_123456 => notice,warning,error,debug,verbose,dtmf
2) I start asterisk with "asterisk -vvvvvg -c"

3) When happen crash I get core dump

Its Ok ?


By: Joshua C. Colp (jcolp) 2022-04-01 14:49:28.942-0500

Yes.
By: LA (learbia) 2022-04-01 15:08:30.584-0500

Ok I will make do it, and post results here.
By: LA (learbia) 2022-04-06 14:28:20.138-0500

Done,
By: LA (learbia) 2022-04-06 14:28:38.465-0500

Done
By: Joshua C. Colp (jcolp) 2022-04-07 03:54:17.632-0500

It doesn't appear as though you attached the debug log so that the events leading up to this can be seen.
By: LA (learbia) 2022-04-07 09:01:03.769-0500

This a full log:

https://drive.google.com/file/d/1y-SMRShjNJnLHUJIeXtRUTnWvG52qUU6/view?usp=sharing

By: Joshua C. Colp (jcolp) 2022-04-07 09:32:37.950-0500

That's a core dump and the associated libraries, which is fine, but I was actually referring to the Asterisk full log.
By: Joshua C. Colp (jcolp) 2022-04-07 09:45:02.920-0500

Are you commercially distributing this?
By: LA (learbia) 2022-04-07 09:52:29.316-0500

We use in our base, we have a 30k endpoints, in various servers
By: Joshua C. Colp (jcolp) 2022-04-07 09:57:56.920-0500

Are you selling the software or hardware with it and if so, are you providing the source code for Asterisk?
By: Joshua C. Colp (jcolp) 2022-04-07 10:05:23.353-0500

I've also accepted this issue, but an Asterisk debug log would be good to see the progression up to the crash.
By: LA (learbia) 2022-04-07 10:33:15.702-0500

We salling hardware with asterisk embed
By: Joshua C. Colp (jcolp) 2022-04-07 10:43:03.147-0500

Are you making the source code of Asterisk available to customers on request?
By: LA (learbia) 2022-04-07 11:36:54.165-0500

No, we make install by default in all machines
By: LA (learbia) 2022-04-07 14:37:48.312-0500

This a Link with full log.

https://drive.google.com/file/d/1msEfDLDsADyC3N_gPoN99-lEFE6Usdj3/view?usp=sharing

By: LA (learbia) 2022-04-07 14:43:50.935-0500

The time of crash is between 13:28 and 13:29
By: LA (learbia) 2022-05-03 11:46:48.212-0500

This crash generate:

traps: asterisk[37738] general protection ip:45edfc sp:7f1d8613b3a0 error:0 in asterisk[400000+2f0000]

in kernel
By: LA (learbia) 2022-05-19 07:28:00.739-0500

Other Information.

When I use a internal DNS in Linux, the incidents decrease