Summary:	ASTERISK-27416: Can't load res_corosync.so module on Asterisk 13.18.2
Reporter:	Anton Mosin (amsn)	Labels:
Date Opened:	2017-11-14 00:19:01.000-0600	Date Closed:	2017-11-16 06:52:13.000-0600
Priority:	Major	Regression?
Status:	Closed/Complete	Components:	Resources/res_corosync
Versions:	13.18.2	Frequency of Occurrence
Related Issues:
Environment:	CentOS Linux release 7.4.1708 (Core) corosync.x86_64 2.4.0-9.el7_4.2 corosynclib.x86_64 2.4.0-9.el7_4.2	Attachments:
Description:	{code} asterisk*CLI> module load res_corosync.so Unable to load module res_corosync.so Command 'module load res_corosync.so ' failed. [2017-11-14 10:03:34] WARNING[1260]: loader.c:573 load_dynamic_module: Error loading module 'res_corosync.so': /usr/lib64/asterisk/modules/res_corosync.so: undefined symbol: corosync_cfg_fd_get [2017-11-14 10:03:34] WARNING[1260]: loader.c:1054 load_resource: Module 'res_corosync.so' could not be loaded. {code}
Comments:	By: Asterisk Team (asteriskteam) 2017-11-14 00:19:01.542-0600 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]. By: Richard Mudgett (rmudgett) 2017-11-14 17:34:04.063-0600 res_corosync is extended support [1] and supported by the community.  Support times will reflect that.  For this issue you may get more help from the community site [2]. [1] https://wiki.asterisk.org/wiki/display/AST/Asterisk+Module+Support+States [2] https://community.asterisk.org/ By: Matt Jordan (mjordan) 2017-11-15 07:49:01.722-0600 [~amsn]: There's a chance that a recent commit to the 13 branch ([0a11097a2|https://github.com/asterisk/asterisk/commit/0a11097a229100a590b401b4b007b038bef26f72]) will fix this. Can you test with the 13 branch and see if it resolves your issue? By: Anton Mosin (amsn) 2017-11-16 00:46:04.253-0600 Yes, this patch resolved the issue. By: Isaac McDonald (imcdona) 2017-12-04 12:31:46.684-0600 This issue is still present in Asterisk 13.18.3. [~amsn]: Was the commit you referenced (below) not included in 13.18.3? https://github.com/asterisk/asterisk/commit/0a11097a229100a590b401b4b007b038bef26f72 Same environment as the original submitter: CentOS Linux release 7.4.1708 (Core) corosync.x86_64 2.4.0-9.el7_4.2 corosynclib.x86_64 2.4.0-9.el7_4.2 By: Joshua C. Colp (jcolp) 2017-12-04 12:34:26.665-0600 [~imcdona] That was a security fix. It did not receive bug fixes. A release has not yet gone out including this. By: Isaac McDonald (imcdona) 2017-12-04 13:18:48.404-0600 Anyone needing this fix prior to the official release can obtain the 13 branch that includes this fix by cloning the branch. Clone the 13 branch and compile as usual: git clone -b 13 https://github.com/asterisk/asterisk.git