[asterisk-bugs] [JIRA] (ASTERISK-27590) res_corosync doesn't load in builds after version 13.17.1

Asterisk Team (JIRA) noreply at issues.asterisk.org
Tue Jan 16 11:02:49 CST 2018


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

Asterisk Team commented on ASTERISK-27590:
------------------------------------------

Thanks for creating a report! The issue has entered the triage process. That means the issue will wait in this status until a Bug Marshal has an opportunity to review the issue. Once the issue has been reviewed you will receive comments regarding the next steps towards resolution.

A good first step is for you to review the [Asterisk Issue Guidelines|https://wiki.asterisk.org/wiki/display/AST/Asterisk+Issue+Guidelines] if you haven't already. The guidelines detail what is expected from an Asterisk issue report.

Then, if you are submitting a patch, please review the [Patch Contribution Process|https://wiki.asterisk.org/wiki/display/AST/Patch+Contribution+Process].

> res_corosync doesn't load in builds after version 13.17.1
> ---------------------------------------------------------
>
>                 Key: ASTERISK-27590
>                 URL: https://issues.asterisk.org/jira/browse/ASTERISK-27590
>             Project: Asterisk
>          Issue Type: Bug
>      Security Level: None
>          Components: Resources/res_corosync
>    Affects Versions: 13.17.2, 13.18.0, 13.18.1, 13.18.2, 13.18.3, 13.18.4, 13.18.5
>         Environment: CentOS Linux release 7.4.1708 (Core)
> Corosync Cluster Engine, version '2.4.0'
>            Reporter: Isaac McDonald
>
> Something changed after Asterisk 13.17.1 that broke res_corosync. I've installed the latest version 13.19.0 and corosync is still broken. This is especially frustrating seeing as how the corosync module was recently fixed after being broke for 2 years only to be broken again after a couple builds.
> I think this commit may have something to do with it:
> 2017-10-06 10:51 +0000 [0a11097a22]  Matt Jordan <mjordan at digium.com>
> 	* res_corosync: Fix linking issue with Corosync 2.x
> 	  At some point in time in the history of Corosync (certainly within the
> 	  2.x branch), the corosync_cfg_state_track function was removed.
> 	  Unfortunately, the cfg library is only linked if this function is
> 	  present. Without the cfg library being linked to res_corosync, loading
> 	  of res_corosync will fail.
> 	  This patch makes it so that detecting corosync's core libraries,
> 	  determined by the COROSYNC external library checks, links both the cpg
> 	  and cfg libraries with res_corosync.
> 	  Change-Id: I674e9e1c8fea11c3bf81154aaa7c1fd43f945465
> Here's the error that's produced in the log when trying to load the module:
> loader.c: Error loading module 'res_corosync.so': /usr/lib/asterisk/modules/res_corosync.so: undefined symbol: corosync_cfg_fd_get
> Here is the ticket for the corosync module that was resolved several months ago along with the patches and other info if it helps.
> https://issues.asterisk.org/jira/browse/ASTERISK-25370 
> https://github.com/corosync/corosync/issues/57
> https://gerrit.asterisk.org/#/c/5858/
> https://gerrit.asterisk.org/5859
> https://gerrit.asterisk.org/5857
> If I can provide any additional details or logs please let me know.



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



More information about the asterisk-bugs mailing list