Undefined symbol: ast_aes_set_encrypt_key

Hi;

I installed Asterisk on an Ubuntu 12.10 server and I get this in my /var/log/asterisk/messages when Asterisk starts:

[Nov 27 17:59:01] NOTICE[24813] cdr.c: CDR simple logging enabled.
[Nov 27 17:59:01] NOTICE[24813] loader.c: 219 modules will be loaded.
[Nov 27 17:59:01] WARNING[24813] loader.c: Error loading module ‘pbx_dundi.so’: /usr/lib/asterisk/modules/pbx_dundi.so: undefined symbol: ast_aes_set_encrypt_key
[Nov 27 17:59:01] WARNING[24813] loader.c: Error loading module ‘pbx_ael.so’: /usr/lib/asterisk/modules/pbx_ael.so: undefined symbol: ael2_parse
[Nov 27 17:59:01] WARNING[24813] loader.c: Error loading module ‘res_calendar_caldav.so’: /usr/lib/asterisk/modules/res_calendar_caldav.so: undefined symbol: ast_calendar_event_container_alloc
[Nov 27 17:59:01] WARNING[24813] loader.c: Error loading module ‘res_calendar_exchange.so’: /usr/lib/asterisk/modules/res_calendar_exchange.so: undefined symbol: ast_calendar_register
[Nov 27 17:59:01] WARNING[24813] loader.c: Error loading module ‘chan_gtalk.so’: /usr/lib/asterisk/modules/chan_gtalk.so: undefined symbol: ast_aji_buddy_destroy
[Nov 27 17:59:01] WARNING[24813] loader.c: Error loading module ‘app_stack.so’: /usr/lib/asterisk/modules/app_stack.so: undefined symbol: ast_agi_unregister
[Nov 27 17:59:01] WARNING[24813] loader.c: Error loading module ‘app_voicemail.so’: /usr/lib/asterisk/modules/app_voicemail.so: undefined symbol: ast_smdi_mwi_set
[Nov 27 17:59:01] WARNING[24813] loader.c: Error loading module ‘chan_jingle.so’: /usr/lib/asterisk/modules/chan_jingle.so: undefined symbol: ast_aji_buddy_destroy
[Nov 27 17:59:01] WARNING[24813] loader.c: Error loading module ‘res_calendar_icalendar.so’: /usr/lib/asterisk/modules/res_calendar_icalendar.so: undefined symbol: ast_calendar_register
[Nov 27 17:59:01] WARNING[24813] loader.c: Error loading module ‘cel_odbc.so’: /usr/lib/asterisk/modules/cel_odbc.so: undefined symbol: SQLColumns
[Nov 27 17:59:01] WARNING[24813] loader.c: Error loading module ‘cdr_odbc.so’: /usr/lib/asterisk/modules/cdr_odbc.so: undefined symbol: SQLRowCount
[Nov 27 17:59:01] WARNING[24813] loader.c: Error loading module ‘func_aes.so’: /usr/lib/asterisk/modules/func_aes.so: undefined symbol: ast_aes_set_encrypt_key
[Nov 27 17:59:01] WARNING[24813] loader.c: Error loading module ‘func_odbc.so’: /usr/lib/asterisk/modules/func_odbc.so: undefined symbol: SQLRowCount
[Nov 27 17:59:01] WARNING[24813] loader.c: Error loading module ‘cdr_adaptive_odbc.so’: /usr/lib/asterisk/modules/cdr_adaptive_odbc.so: undefined symbol: SQLColumns
[Nov 27 17:59:01] WARNING[24813] loader.c: Error loading module ‘res_calendar_ews.so’: /usr/lib/asterisk/modules/res_calendar_ews.so: undefined symbol: ast_calendar_register
[Nov 27 17:59:01] NOTICE[24813] res_odbc.c: res_odbc loaded.
[Nov 27 17:59:01] NOTICE[24813] res_smdi.c: No SMDI interfaces are available to listen on, not starting SMDI listener.
[Nov 27 17:59:01] NOTICE[24813] res_config_ldap.c: No directory user found, anonymous binding as default.
[Nov 27 17:59:01] ERROR[24813] res_config_ldap.c: No directory URL or host found.
[Nov 27 17:59:01] ERROR[24813] res_config_ldap.c: Cannot load LDAP RealTime driver.
[Nov 27 17:59:01] NOTICE[24813] config.c: Registered Config Engine sqlite
[Nov 27 17:59:01] NOTICE[24813] config.c: Registered Config Engine curl
[Nov 27 17:59:01] NOTICE[24813] chan_skinny.c: Configuring skinny from skinny.conf
[Nov 27 17:59:01] NOTICE[24813] cel_tds.c: cel_tds has no global category, nothing to configure.
[Nov 27 17:59:01] WARNING[24813] cel_tds.c: cel_tds module had config problems; declining load
[Nov 27 17:59:01] WARNING[24813] cel_pgsql.c: CEL pgsql config file missing global section.
[Nov 27 17:59:01] NOTICE[24813] cdr_pgsql.c: cdr_pgsql configuration contains no global section, skipping module load.
[Nov 27 17:59:01] ERROR[24813] ais/clm.c: Could not initialize cluster membership service: Try Again
[Nov 27 17:59:02] ERROR[24813] chan_vpb.cc: No Voicetronix cards detected
[Nov 27 17:59:02] NOTICE[24813] pbx_ael.c: Starting AEL load process.
[Nov 27 17:59:02] NOTICE[24813] pbx_ael.c: AEL load process: parsed config file name ‘/etc/asterisk/extensions.ael’.
[Nov 27 17:59:02] NOTICE[24813] pbx_ael.c: AEL load process: checked config file name ‘/etc/asterisk/extensions.ael’.
[Nov 27 17:59:02] NOTICE[24813] pbx_ael.c: AEL load process: compiled config file name ‘/etc/asterisk/extensions.ael’.
[Nov 27 17:59:02] NOTICE[24813] pbx_ael.c: AEL load process: merged config file name ‘/etc/asterisk/extensions.ael’.
[Nov 27 17:59:02] NOTICE[24813] pbx_ael.c: AEL load process: verified config file name ‘/etc/asterisk/extensions.ael’.

I believe it has been there right from the beginning (above is cut and paste from the top of my file). I’m a newb and was tweaking my sip, logger, extensions files and then noticed this log. My phones work okay (but I’m not done my voicemail or Google talk and I see those are affected here). I am trying to troubleshoot at least the warnings out. I tried searching Google and this forum for the first undefined symbol but didn’t find anything to help me.

I did a:
sudo apt-get purge asterisk-config
and then reinstalled with:
sudo apt-get install asterisk
I get the exact same log with the default .conf files.

Can someone please help me understand the warnings and help clean up my initialization? In the best case I would like to quiet the notices as well.

Thanks!

Kev

You have Asterisk modules installed that weren’t compiled against your Asterisk binary?

Hi Malcolm;

Sorry, I don’t understand your question… I think (newb again). Since I used apt-get, I would guess that my binaries are whatever was in the repository (or whatever the defaults are that were used when it was placed there). I have auto-load=yes. So for example, pbx_dundi.so is trying to load but it was not compiled into the binary?

Even if I misunderstand, my guess is that the fix is to download the source and build it myself, correct?

Is sudo apt-get purge asterisk-config (and apt-get autoremove) the best way to remove it?

Thanks!

Kev

[quote=“calgarykev”]Hi Malcolm;

Sorry, I don’t understand your question… I think (newb again). Since I used apt-get, I would guess that my binaries are whatever was in the repository (or whatever the defaults are that were used when it was placed there). I have auto-load=yes. So for example, pbx_dundi.so is trying to load but it was not compiled into the binary?

Even if I misunderstand, my guess is that the fix is to download the source and build it myself, correct?

Is sudo apt-get purge asterisk-config (and apt-get autoremove) the best way to remove it?

Thanks!

Kev[/quote]

Downloading from source and building yourself should do the trick. I’m afraid I don’t know what all asterisk related packages may have been pulled in; just have dpkg --get-selections tell you and purge them all first.

Hi Malcolm;

Thanks for the dpkg tip. I am just familiarizing myself with the build process in the O’Rileys manual. Let you know how it goes.

Originally I typed sudo apt-get install asterisk on a lark. I went in and worked. I didn’t think anything of it til I saw my logs.

Thanks!

Yeah, the stuff you’re seeing in there being problematic, at least for the log you pasted, isn’t something used by every installation; so, it might not be the end of the world unless you needed one of those modules.

Thanks Malcolm;

I reinstalled from source and it is much better. Just so you know, neither the O’riley’s manual nor your Quick Start Manual worked for me. The first make failed in the O’Riley’s procedure and the quick start has some syntax problems (which I don’t recall) and is missing sudo make config - which I think enables the autostart from the messages I saw. I pieced it together from both but I don’t know if I did it right or missed anything.

Here’s my log now:

[2012-11-29 17:00:09] NOTICE[25298] cdr.c: CDR simple logging enabled.
[2012-11-29 17:00:09] NOTICE[25298] loader.c: 180 modules will be loaded.
[2012-11-29 17:00:09] NOTICE[25298] res_smdi.c: No SMDI interfaces are available to listen on, not starting SMDI listener.
[2012-11-29 17:00:11] NOTICE[25298] chan_skinny.c: Configuring skinny from skinny.conf
[2012-11-29 17:00:11] NOTICE[25298] pbx_ael.c: Starting AEL load process.
[2012-11-29 17:00:11] NOTICE[25298] pbx_ael.c: AEL load process: parsed config file name ‘/etc/asterisk/extensions.ael’.
[2012-11-29 17:00:11] NOTICE[25298] pbx_ael.c: AEL load process: checked config file name ‘/etc/asterisk/extensions.ael’.
[2012-11-29 17:00:11] NOTICE[25298] pbx_ael.c: AEL load process: compiled config file name ‘/etc/asterisk/extensions.ael’.
[2012-11-29 17:00:11] NOTICE[25298] pbx_ael.c: AEL load process: merged config file name ‘/etc/asterisk/extensions.ael’.
[2012-11-29 17:00:11] NOTICE[25298] pbx_ael.c: AEL load process: verified config file name ‘/etc/asterisk/extensions.ael’.

I’m guessing I should be okay with this. I will do some reading to see if I can quiet it down some more (for example, it looks like I should be able to get rid of SMDI message). If you see anything I should be addressing please let me know.

Thanks for the help!

Kev

Hi Malcolm;

Sorry this is probably a newb question again but I can’t find an answer with Google.

My new installation does not buffer the CLI so I can’t scroll back to previous commands. Is there a setting for this?

Thanks!

Kev

Not that I recall; never had a problem with that.

The logging (as against commands and command responses) are written to the CLI as a special case of the general logging capability, configured in logger.conf. There should be copies of the normal logging there, although you may have to make adjustments to log debug level stuff.

The Linux local console driver supports the use of shift-page up and -page down, to scroll backwards through several screenfuls, a half page at a time.

The console input facility has readine type functions, which means you can use the up and down arrows to recall previous commands (and can edit and re-submit them).

I suspect a lot of people access Asterisk through ssh, and would use scrollback in their terminal emulator.

Played with it some more. Sorry my first question was not correct. It does buffer my current session. But if I exit it loses the buffer when I re-enter.

My previous installation remembered the buffer even if I restarted the core or shut down the computer. That was much handier that what I have now.

Kev