[asterisk-bugs] [JIRA] (ASTERISK-27321) Asterisk Crashing with FRACK Errors and Serious Network Trouble

[Steven Sedory (JIRA)]

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

Steven Sedory commented on ASTERISK-27321:
------------------------------------------

I recently made this post on the asterisk forums, after no success of freepbx forums. There's a bit more info on this link at the asterisk forums: https://community.asterisk.org/t/asterisk-freepbx-crashing-and-frack-errors/72159

There are also some links to crash dumps, and backtraces on the above url.

Also, I think that the "Serious Network Trouble" errors are what cause the FRACK errors, which then cause asterisk to crash.

> Asterisk Crashing with FRACK Errors and Serious Network Trouble
> ---------------------------------------------------------------
>
>                 Key: ASTERISK-27321
>                 URL: https://issues.asterisk.org/jira/browse/ASTERISK-27321
>             Project: Asterisk
>          Issue Type: Bug
>      Security Level: None
>          Components: Channels/chan_sip/General
>    Affects Versions: 13.17.0
>         Environment: FreePBX 13.0.192.16 and Asterisk 13.17.0, proxmox 4.4 on Dell R720, local RAID volume. Using TCP and obscure port for SIP. UDP 5060 still open/enabled, but firewalled to only allow Anveo Direct servers.
>            Reporter: Steven Sedory
>            Severity: Critical
>
> Recently used the "warm spare" method to move to a new server (new VM on KVM/proxmox)
> The server has about 120 remote extension, and had no real problems before.
> I posted about this crash issue yesterday here, but my hypothesis was off: https://community.freepbx.org/t/media-index-c-failed-to-stat/43645
> Today we had a ton of users call and say their phones weren't working. Funny thing is, they show OK with IP address in peers list when running "sip show peers" in cli.
> So we did a fwconsole restart, and things started working again.
> This crash has happened three times this week already. Sunday morning, yesterday morning, and today.
> I starting digging through the logs, and these are the errors that may or may not be the cause. I'm hoping someone can give me some insight. Here are some error examples:
> These ones show all over the logs, way before, way after, and right around the crash time:
> [2017-08-22 09:30:59] ERROR[32499][C-00000028] pbx_functions.c: Function PJSIP_HEADER not registered
> These ones yesterday were fairly close to before the crash, but there were none today before the crash:
> [2017-08-22 09:38:08] ERROR[1488] netsock2.c: getaddrinfo("2605:e000:6045:3a00:20b:82ff:feac:c151:13312", "(null)", ...): Name or service not known
> [2017-08-22 09:38:08] WARNING[1488] chan_sip.c: Could not resolve socket address for '2605:e000:6045:3a00:20b:82ff:feac:c151:13312'
> These existing on all three instances:
> Line 33144: [2017-08-20 10:34:38] ERROR[30555] chan_sip.c: Serious Network Trouble; __sip_xmit returns error for pkt data
> And finally, these ones look the like the most likely culprit, but didn't show on Yesterday's crash (just today and Sunday's):
> *note that the difference between Today's and Sunday's, vs Yesterday's, is that the former showed all endpoints "OK", though they truly weren't, the latter showed only about half of them
> [2017-08-23 13:42:49] ERROR[26004] astobj2.c: FRACK!, Failed assertion bad magic number 0x0 for object 0x3de7430 (0)
> So all that to say, I hope someone can help us find the root cause of all this.
> Again, this server was a fresh v13 FreePBX server that we just "warm spare" copied to from an existing server. The existing was running on an ESXi host, fully updated to ....66-21. We fully updated the fresh VM to 66-21 as well before running the backup/restore. The new server is a VM on KVM/proxmox.



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