Summary: | ASTERISK-25651: Error loading several modules in Fedora 23 with 'undefined symbol' - is modules.conf missing dependencies? | ||
Reporter: | Sean Darcy (seandarcy) | Labels: | |
Date Opened: | 2015-12-30 16:41:15.000-0600 | Date Closed: | 2020-01-14 11:14:11.000-0600 |
Priority: | Major | Regression? | |
Status: | Closed/Complete | Components: | General |
Versions: | 11.21.0 | Frequency of Occurrence | Constant |
Related Issues: | |||
Environment: | Fedora 23. | Attachments: | |
Description: | Upgraded the server today to Fedora 23, gcc-5.3.1.
Had been running 11.21.0-rc1 on fedora 22. I rebuilt asterisk after the upgrade. {noformat} [Dec 30 16:04:59] WARNING[2914]: loader.c:463 load_dynamic_module: Error loading module 'res_calendar_ews.so': /usr/lib64/asterisk/modules/res_calendar_ews.so: undefined symbol: ast_calendar_register [Dec 30 16:04:59] WARNING[2914]: loader.c:463 load_dynamic_module: Error loading module 'chan_motif.so': /usr/lib64/asterisk/modules/chan_motif.so: undefined symbol: ast_xmpp_client_send_message [Dec 30 16:04:59] WARNING[2914]: loader.c:463 load_dynamic_module: Error loading module 'res_agi.so': /usr/lib64/asterisk/modules/res_agi.so: undefined symbol: ast_speech_change [Dec 30 16:04:59] WARNING[2914]: loader.c:463 load_dynamic_module: Error loading module 'res_calendar_caldav.so': /usr/lib64/asterisk/modules/res_calendar_caldav.so: undefined symbol: ast_calendar_event_container_alloc [Dec 30 16:04:59] WARNING[2914]: loader.c:463 load_dynamic_module: Error loading module 'app_speech_utils.so': /usr/lib64/asterisk/modules/app_speech_utils.so: undefined symbol: ast_speech_dtmf [Dec 30 16:04:59] WARNING[2914]: loader.c:463 load_dynamic_module: Error loading module 'res_calendar_icalendar.so': /usr/lib64/asterisk/modules/res_calendar_icalendar.so: undefined symbol: ast_calendar_register {noformat} "preload" ing xmpp solved the motif issue. grep -v \; modules.conf {noformat} [modules] autoload=yes preload => res_xmpp.so noload => pbx_gtkconsole.so load => res_musiconhold.so noload => chan_alsa.so noload => chan_console.so noload => app_directory_imap.so noload => app_voicemail_imap.so noload => app_directory_odbc.so noload => app_voicemail_odbc.so {noformat} | ||
Comments: | By: Asterisk Team (asteriskteam) 2015-12-30 16:41:17.454-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: Sean Darcy (seandarcy) 2015-12-30 16:43:43.348-0600 Just to be clear, 11.21.0-rc1 did _not_ have this issue before the upgrade and the rebuilding. Maybe some quirk with the new gcc version ? By: Rusty Newton (rnewton) 2015-12-31 09:30:13.012-0600 Perhaps some modules didn't get rebuilt? Did you try to 'make uninstall-all' before building from a fresh tarball? Obviously backup your configs. :) I have a Fedora 23 VM so I'll upgrade it and see if I get any goofiness when building Asterisk. By: Rusty Newton (rnewton) 2015-12-31 10:28:58.267-0600 In my build I'm running into: {noformat} gcc: error: /usr/lib/rpm/redhat/redhat-hardened-ld: No such file or directory /root/asterisk/asterisk-11.21.0-rc1/Makefile.rules:170: recipe for target 'res_calendar_icalendar.so' failed make[1]: *** [res_calendar_icalendar.so] Error 1 Makefile:394: recipe for target 'res' failed make: *** [res] Error 2 {noformat} I see the same issue for a few of the modules that didn't load for you. Did you run into this same issue ? By: Sean Darcy (seandarcy) 2016-01-09 12:24:18.899-0600 No , I didn't have any problems with the build. Simply preloading xmpp worked, using the same installation. That is, I installed the rebuilt rpm, and got the error. Then added preload xmpp to modules.conf. Did not rebuild, simply restarted asterisk, and all's well. I didn't bother "preload"ing res_calendar since I don't use it, but it seems to have built correctly: rpm -qif /usr/lib64/asterisk/modules/res_calendar_icalendar.so Name : asterisk11 Version : 11.21.0 Release : 0.rc1.fc23 Architecture: x86_64 Install Date: Wed 30 Dec 2015 04:04:15 PM EST Group : Sound Size : 198059685 By: Rusty Newton (rnewton) 2016-01-26 09:31:07.180-0600 I finally had time to get back to this. I figured out what my issue was: ASTERISK-25726 Now I'll see if I can reproduce your issue again. By: Rusty Newton (rnewton) 2016-01-26 09:54:52.727-0600 In 11.21 installed on Fedora 23 I only get issues with the following {noformat} [Jan 26 09:44:03] WARNING[21364] loader.c: Error loading module 'res_calendar_exchange.so': /usr/lib/asterisk/modules/res_calendar_exchange.so: undefined symbol: ast_calendar_register [Jan 26 09:44:03] WARNING[21364] loader.c: Error loading module 'res_calendar_caldav.so': /usr/lib/asterisk/modules/res_calendar_caldav.so: undefined symbol: ast_calendar_event_container_alloc {noformat} For res_agi and the others (even chan_motif) I don't get an issue and I didn't need to preload res_xmpp.. I wonder what is different? What options did you use when configuring and building? Did you initially get those module loading errors with the default modules.conf? Note: I'm also using gcc version 5.3.1 20151207 (Red Hat 5.3.1-2) (GCC) By: Asterisk Team (asteriskteam) 2016-02-09 12:00:19.188-0600 Suspended due to lack of activity. This issue will be automatically re-opened if the reporter posts a comment. If you are not the reporter and would like this re-opened please create a new issue instead. If the new issue is related to this one a link will be created during the triage process. Further information on issue tracker usage can be found in the Asterisk Issue Guidlines [1]. [1] https://wiki.asterisk.org/wiki/display/AST/Asterisk+Issue+Guidelines |