[asterisk-bugs] [JIRA] (ASTERISK-29296) stasis.c: FRACK!, Failed assertion bad magic number 0x0 for object

BJ Weschke (JIRA) noreply at issues.asterisk.org
Wed Jul 7 13:35:33 CDT 2021


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

BJ Weschke commented on ASTERISK-29296:
---------------------------------------

scratch that. It would appear that one of our support folks restarted the server instance prior to us getting a capture of the core dump of the running process that was unhealthy. It happened on June 22 and again today with 18.4, so presumably, it'll happen again and hopefully we can actually get a useful core dump the next time around. Please let us know where you'd like for us to send it up to once we get it. 

> stasis.c: FRACK!, Failed assertion bad magic number 0x0 for object
> ------------------------------------------------------------------
>
>                 Key: ASTERISK-29296
>                 URL: https://issues.asterisk.org/jira/browse/ASTERISK-29296
>             Project: Asterisk
>          Issue Type: Bug
>      Security Level: None
>          Components: Resources/res_stasis
>    Affects Versions: 18.2.0, 18.4.0
>         Environment: Ubuntu 18
>            Reporter: BJ Weschke
>         Attachments: asterisk-frack.log.bz2
>
>
> Upon trying to add a channel to a bridge while testing Asterisk 18.2 in our QA environment, we started seeing these messages (see in attached log beginning at 14:09:42) in the full log, and after that point, anything related to the channel or the bridge in question seems to stream these errors into the log. The testers than gracefully shut down the Asterisk instance to clear the issue. We've not been able to reproduce this by doing the same use case that caused the issue in the first place. 



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



More information about the asterisk-bugs mailing list