[asterisk-bugs] [JIRA] (ASTERISK-28503) Asterisk sudden crashes with segmentation fault

[Kevin Harwell (JIRA)]

    [ https://issues.asterisk.org/jira/browse/ASTERISK-28503?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=247759#comment-247759 ] 

Kevin Harwell commented on ASTERISK-28503:
------------------------------------------

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

> Asterisk sudden crashes with segmentation fault
> -----------------------------------------------
>
>                 Key: ASTERISK-28503
>                 URL: https://issues.asterisk.org/jira/browse/ASTERISK-28503
>             Project: Asterisk
>          Issue Type: Bug
>      Security Level: None
>          Components: . I did not set the category correctly.
>    Affects Versions: 15.4.0
>         Environment: Ubuntu Linux 16.04 ( kernel 4.4.0-1077-aws)
>            Reporter: Cyril Ramière
>            Assignee: Unassigned
>              Labels: pjsip, webrtc
>         Attachments: kern.log, messages.log
>
>
> 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.



--
This message was sent by Atlassian JIRA
(v6.2#6252)