[asterisk-bugs] [JIRA] (ASTERISK-28337) Regular segmentation faults

[Benjamin Keith Ford (JIRA)]

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

Benjamin Keith Ford edited comment on ASTERISK-28337 at 3/18/19 12:57 PM:
--------------------------------------------------------------------------

None of these should be causing segfaults, just spitting out error messages and warnings and moving on. "ast_func_read" is getting nothing back when trying to lookup a custom function, hence the "Function ___ not registered" error. "func_read_header" either cannot find the channel, or the channel in question is not a PJSIP channel since it checks for "PJSIP/" at the start of the channel name, hence the "This function requires a PJSIP channel" error message. As for the taskprocessor, this one in particular is dealing with subscriptions to topics, and reaching the number to trigger a high volume message is something that can be expected in high load systems. Hopefully that clears up those messages for you.
As for the segfault itself, can you attach some log files so we can see what's going on with Asterisk? If you know the time when the crash occurred, this can also help. Also, if you know what route your channels are taking in your dialplan, providing that information (extensions.conf and the path the channel takes through it) would help too.


was (Author: bford):
None of these should be causing segfaults, just spitting out error messages and warnings and moving on. "ast_func_read" is getting nothing back when trying to lookup a custom function, hence the "Function ___ not registered" error. "func_read_header" either cannot find the channel, or the channel in question is not a PJSIP channel since it checks for "PJSIP/" at the start of the channel name, hence the "This function requires a PJSIP channel" error message. As for the taskprocessor, this one in particular is dealing with subscriptions to topics, and reaching the maximum number is something that can be expected in larger environments. Hopefully that clears up those messages for you.
As for the segfault itself, can you attach some log files so we can see what's going on with Asterisk? If you know the time when the crash occurred, this can also help. Also, if you know what route your channels are taking in your dialplan, providing that information (extensions.conf and the path the channel takes through it) would help too.

> Regular segmentation faults
> ---------------------------
>
>                 Key: ASTERISK-28337
>                 URL: https://issues.asterisk.org/jira/browse/ASTERISK-28337
>             Project: Asterisk
>          Issue Type: Bug
>      Security Level: None
>          Components: Core/General
>    Affects Versions: 13.22.0
>         Environment: OS: Red Hat Enterprise Linux 7.5-0.11
> Asterisk 13.22.0
> PJSIP: 2.7.2
> RAM: 6Gb
> VMware 4 cores
>            Reporter: Jeroen Hermans
>            Assignee: Jeroen Hermans
>              Labels: pjsip
>         Attachments: core.plusovpbx3.danego.net-2019-03-15T09-15-29+0100-brief.txt, core.plusovpbx3.danego.net-2019-03-15T09-15-29+0100-full.txt, core.plusovpbx3.danego.net-2019-03-15T09-15-29+0100-locks.txt, core.plusovpbx3.danego.net-2019-03-15T09-15-29+0100-thread1.txt
>
>
> The Asterisk process keeps producing a segmentation fault a few times a day. I have attached the coredump information of one of the segmentation faults.



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