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

[Cyril Ramière (JIRA)]

     [ https://issues.asterisk.org/jira/browse/ASTERISK-28503?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Cyril Ramière updated ASTERISK-28503:
-------------------------------------

    Attachment: messages.log
                kern.log

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

> 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
>              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)