[Home]

Summary:ASTERISK-28503: Asterisk sudden crashes with segmentation fault
Reporter:Cyril Ramière (Cyril.r)Labels:pjsip webrtc
Date Opened:2019-08-13 03:43:38Date Closed:2019-08-16 10:23:44
Priority:MajorRegression?
Status:Closed/CompleteComponents:. I did not set the category correctly.
Versions:15.4.0 Frequency of
Occurrence
Occasional
Related
Issues:
Environment:Ubuntu Linux 16.04 ( kernel 4.4.0-1077-aws)Attachments:( 0) kern.log
( 1) messages.log
Description:Hello everyone,

I am badly needing help about an issue with our asterisk.

We are on asterisk 15.4.0, we made no changes on the system or the configuration (asterisk.conf, pjsip.conf...) and we tend to get occasional crashes with segmentation faults.

I'm really strugling to know what happends because there are no "warning signs" before a crash happen, it works and then it just dies.

There are nothing useful in the system logs (just the line telling that there was a segmentation fault).

We are using asterisk in realtime mode for all of our calls with MySQL, and everything is handled through the ARI interface (no static dialplans) connected to our application.

I attached the logs (messages), kern log, and the crash dump.

I know that asterisk is compiled without debug flags and is optimized, this is a critical, production machine.

I am unable to reproduce the issue, it just happened twice il a month causing huge troubles for us (there were more than 800 channels active, recordings on some, moh, webrtc sessions...).

Running asterisk without optimizations & with better traces seems not an option since it sucks so much more ressources, I'm 100% sure that our hardware couldn't handle it.

I'm begging for help, anything where I can start ?
Is there something I can do?

Best regards.

Comments:By: Asterisk Team (asteriskteam) 2019-08-13 03:43:40.229-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].

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.

By: Cyril Ramière (Cyril.r) 2019-08-13 03:46:35.455-0500

Hello, please find attached the logs.

The asterisk crash dump is too big to be uploaded here, I put it on wetransfer inside a .zip file to save some space:  https://wetransfer.com/downloads/056ea2a4c0b7e4ac741289a90dee2d4320190813084303/123d19dee8e62d2de70cf1fbaa1cf2fe20190813084303/01fc21

By: Joshua C. Colp (jcolp) 2019-08-13 04:44:33.893-0500

Per the Asterisk versions page [1], the maintenance (bug fix) support for the Asterisk branch you are using has ended. For continued maintenance support please move to a supported branch of Asterisk. After testing with a supported branch, if you find this problem has not been resolved, please open a new issue against the latest version of that Asterisk branch.

Thanks!

[1] https://wiki.asterisk.org/wiki/display/AST/Asterisk+Versions



By: Cyril Ramière (Cyril.r) 2019-08-13 06:15:55.700-0500

Hello,

Thanks for your feedback, I see that last version on branch 15.x is 15.7.3.

If we install this version and still have the issue, is this version supported ?

Best regards.

By: Kevin Harwell (kharwell) 2019-08-13 09:42:30.995-0500

If you look at the version lifetime table on the page that [~jcolp] linked above [1] you'll note that Asterisk 15 is in security fix only mode (means it only receives updates for security issues, no bug fixes), and reaches end of life in October.

I would highly recommend moving away from that branch and upgrading to a supported version like Asterisk 16, which will continue to receive bug fixes until Oct. 2022.

[1] https://wiki.asterisk.org/wiki/display/AST/Asterisk+Versions

By: Cyril Ramière (Cyril.r) 2019-08-16 10:23:12.122-0500

Hello,

Well, that's sad news for me :)

I will look into asterisk 16

By: Cyril Ramière (Cyril.r) 2019-08-16 10:23:45.081-0500

EOL reached on branch 15.x