[asterisk-bugs] [JIRA] (ASTERISK-27300) Asterisk crashes randomly (FRACK!, chan_sip)

Kevin Harwell (JIRA) noreply at issues.asterisk.org
Thu Oct 26 15:20:21 CDT 2017


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

Kevin Harwell commented on ASTERISK-27300:
------------------------------------------

Looks like the peer goes away. You can see in Thread 323 that there is a FRACK on the peer, and then when it tries to use a reference from it....crash.

What else is happening on the system at the time? For instance is the system reloading? Since this happens a couple times a week would it be possible to bump up debugging and attach a debug log? If the log ends up being large we won't need the entire log. Just up to a few minutes before the crash.

Once it does crash again with debugging turned on attach both the log and a new backtrace to the issue.

> Asterisk crashes randomly (FRACK!, chan_sip)
> --------------------------------------------
>
>                 Key: ASTERISK-27300
>                 URL: https://issues.asterisk.org/jira/browse/ASTERISK-27300
>             Project: Asterisk
>          Issue Type: Bug
>      Security Level: None
>          Components: Channels/chan_sip/General
>    Affects Versions: 13.13.0
>         Environment: 3.16.0-4-amd64 #1 SMP Debian 3.16.43-2+deb8u3 (2017-08-15) x86_64
> OpenSSL 1.0.1t
> 1032 sip peers (chan_sip with TLS/SRTP only)
>            Reporter: Alex A. Welzl
>            Assignee: Unassigned
>         Attachments: backtrace.txt
>
>
> Asterisk crashes randomly (currently 1-2 times per week). Any idea if this is the same issue like ASTERISK-26699? If not, upgrading to another version makes no sense.
> {noformat}
> [2017-09-27 19:48:13] ERROR[11520] astobj2.c: FRACK!, Failed assertion bad magic number 0x0 for object 0x45f6410 (0)
> [2017-09-27 19:48:13] VERBOSE[11520] logger.c: Got 16 backtrace records
> [2017-09-27 19:48:13] VERBOSE[11520] logger.c: #0: [0x45b777] /usr/sbin/asterisk(__ao2_ref+0x1a7) [0x45b777]
> [2017-09-27 19:48:13] VERBOSE[11520] logger.c: #1: [0x45da2a] /usr/sbin/asterisk() [0x45da2a]
> [2017-09-27 19:48:13] VERBOSE[11520] logger.c: #2: [0x45e4a2] /usr/sbin/asterisk(__ao2_callback_data+0x12) [0x45e4a2]
> [2017-09-27 19:48:13] VERBOSE[11520] logger.c: #3: [0x7f6dbeb5a163] /usr/lib/asterisk/modules/chan_sip.so(+0x68163) [0x7f6dbeb5a163]
> [2017-09-27 19:48:13] VERBOSE[11520] logger.c: #4: [0x7f6dbeb5ad95] /usr/lib/asterisk/modules/chan_sip.so(+0x68d95) [0x7f6dbeb5ad95]
> [2017-09-27 19:48:13] VERBOSE[11520] logger.c: #5: [0x7f6dbeb87911] /usr/lib/asterisk/modules/chan_sip.so(+0x95911) [0x7f6dbeb87911]
> [2017-09-27 19:48:13] VERBOSE[11520] logger.c: #6: [0x7f6dbeb8a1cc]
> {noformat}



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



More information about the asterisk-bugs mailing list