[asterisk-bugs] [JIRA] (ASTERISK-29882) Occasional segfaults in production

[William ML Leslie (JIRA)]

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

William ML Leslie updated ASTERISK-29882:
-----------------------------------------

    Attachment: asterisk-chan-save.patch

A patch, implementing my second idea by moving a single line of code, made available under the same license as asterisk.  Instead of crashing the system, the attempt to add a snoop channel will receive a 500 error with body {"message":"Snoop channel could not be created"}.  We could try to detect this case and return a 404 to match the other case where the parent channel has gone away if desired.

I have run the repro code for many hours without a crash and am now running my load tests (we test asterisk with thousands of concurrent calls), and will let you know if we discover any issues.

FWIW ASTERISK-29604 appears to also be this bug.  It contains a suggested fix, but I think this patch is a better ARI experience overall as it describes both channels involved.

> Occasional segfaults in production
> ----------------------------------
>
>                 Key: ASTERISK-29882
>                 URL: https://issues.asterisk.org/jira/browse/ASTERISK-29882
>             Project: Asterisk
>          Issue Type: Bug
>      Security Level: None
>          Components: General
>    Affects Versions: 18.8.0
>         Environment: Debian Stretch in Docker
>            Reporter: Duncan
>            Assignee: Unassigned
>              Labels: patch
>         Attachments: asterisk-chan-save.patch, coreFile-thread1.txt, Screenshot from 2021-12-20 09-09-29.png, slow-snoop.zip
>
>
> Hi team,
> We are seeing Asterisk instances occasionally segfault in production. This happens in our voicemail handling stasis app, which includes playing media to the caller, and then recording the caller, managed through ARI. We don't know what the steps are to reproduce the issue as we have never reproduced it ourselves, but suspect it is probably some kind of race condition.
> I have attached coreFile-thread1.txt from the core dump. We have all the other core dump *.txt files but would prefer not to post these publicly in case they could contain any sensitive data. I would be happy to provide these directly to a maintainer via email. We’re happy to assist debugging this issue if at all possible, and have some C experience but no experience working on Asterisk. Please get in touch if we can do anything to help troubleshoot further.
> Many thanks



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