[asterisk-bugs] [JIRA] (ASTERISK-25370) res_corosync segfaults at startup with corosync version > 2.x

[Matt Jordan (JIRA)]

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

Matt Jordan commented on ASTERISK-25370:
----------------------------------------

Not that it is surprising, but I confirmed as well that 1.4.7 still works:

{code}
*CLI> corosync show members

=============================================================
=== Cluster members =========================================
=============================================================
===
=== Node 1
=== --> Group: asterisk
=== --> Address 1: 192.168.0.102
=== Node 2
=== --> Group: asterisk
=== --> Address 1: 192.168.0.105
===
=============================================================
{code}

Hilarious that 1.4.7 is still the default package on CentOS 6.7. Oh well... people in glass houses and what-not.

> res_corosync segfaults at startup with corosync version > 2.x
> -------------------------------------------------------------
>
>                 Key: ASTERISK-25370
>                 URL: https://issues.asterisk.org/jira/browse/ASTERISK-25370
>             Project: Asterisk
>          Issue Type: Bug
>      Security Level: None
>          Components: Resources/res_corosync
>    Affects Versions: 11.19.0
>         Environment: linux 64bit
> kernel 3.10.17
> distro slackware64 14.1
> corosync 2.3.5
>            Reporter: mdu113
>            Assignee: Unassigned
>         Attachments: backtrace2.txt, backtrace.txt, menuselect.makeopts, valgrind.txt
>
>
> Asterisk crashes at startup when trying to load res_corosync.so. The content of res_corosync.conf doesn't matter. As long as file exists (even empty one) asterisk segfaults. 
> The issue seems identical to the one described in ASTERISK-24343, but since that issue was closed due to no feedback, I'm opening a new one.
> Backtrace is attached.
> I've also tested it in asterisk 13.5.0 and got the same result - asterisk segfaults. The backtrace is taken from 11.19.0 though as that one I'm currently using.
> Thanks



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