[Home]

Summary:ASTERISK-27940: asterisk crash randomly
Reporter:pasandev (pasandev)Labels:pjsip
Date Opened:2018-06-25 02:36:02Date Closed:2020-01-14 11:14:01.000-0600
Priority:MajorRegression?
Status:Closed/CompleteComponents:.Release/Targets
Versions:13.21.0 Frequency of
Occurrence		Frequent
Related
Issues:
Environment:os: Debian stretch 9.4 cpu: Architecture: x86_64 CPU op-mode(s): 32-bit, 64-bit Byte Order: Little Endian CPU(s): 6 On-line CPU(s) list: 0-5 Thread(s) per core: 1 Core(s) per socket: 6 Socket(s): 1 NUMA node(s): 1 Vendor ID: GenuineIntel CPU family: 6 Model: 44 Model name: Westmere E56xx/L56xx/X56xx (Nehalem-C) Stepping: 1 CPU MHz: 2933.612 BogoMIPS: 5867.22 Hypervisor vendor: KVM Virtualization type: full L1d cache: 32K L1i cache: 32K L2 cache: 4096K L3 cache: 16384K NUMA node0 CPU(s): 0-5 Flags: fpu vme de pse tsc msr pae mce cx8 apic sep mtrr pge mca cmov pat pse36 clflush mmx fxsr sse sse2 ss ht syscall nx pdpe1gb rdtscp lm constant_tsc rep_good nopl xtopology pni pclmulqdq ssse3 cx16 pcid sse4_1 sse4_2 x2apic popcnt tsc_deadline_timer aes hypervisor lahf_lm kaiser tsc_adjust arat Attachments:( 0) core-brief.txt
( 1) core-full.txt
( 2) core-locks.txt
( 3) core-thread1.txt
Description:We have asterisk gateway with simple dialplan and using chan_pjsip as the sip channel driver. We dial our upstream carrier for calls that are send from our main sip server.

outgoing path
customer -> sip server -> asterisk gw -> supplier gw

incoming path
customer <- sip server <- asterisk gw <- supplier gw



Since upgrade to 13.21.1 with chan_pjsip. asterisk crash randomly.
Comments:By: Asterisk Team (asteriskteam) 2018-06-25 02:36:04.794-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.

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].
By: pasandev (pasandev) 2018-06-25 02:39:09.777-0500

This is the ast_coredumper generated core files.
By: Richard Mudgett (rmudgett) 2018-06-25 10:56:43.015-0500

Thank you for the crash report. However, we need more information to investigate the crash. Please provide:

1. A backtrace generated from a core dump using the instructions provided on the Asterisk wiki [1].
2. Specific steps taken that lead to the crash.
3. All configuration information necesary to reproduce the crash.

Thanks!

[1]: https://wiki.asterisk.org/wiki/display/AST/Getting+a+Backtrace

The backtrace you supplied has *no* symbol information so we cannot see what happened.
By: pasandev (pasandev) 2018-06-25 20:42:13.041-0500

Hi Richard,

I'll get back to you with proper backtrace. We need to recompile asterisk with betterbacktraces on.
By: pasandev (pasandev) 2018-06-27 21:05:58.846-0500

Hi Guys,

I still couldn't reproduce the crash :/. I'll get back to you as soon as I get it reproduce.
By: Asterisk Team (asteriskteam) 2018-07-12 12:00:01.110-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