I had the problem below:
I solved it by adding a bunch of noload’s in the modules.conf for each individual .so file that was having problem (mostly related to “ast_load” file.
Any ideas why i was getting these errors? Something seems wrong that i had so many config issues.
When I type asterisk -r I get this error:
Unable to connect to remote asterisk (does /var/run/asterisk.ctl exist?)
asterisk -vvvvc gives me this:
[pbx_wilcalu.so]Mar 12 05:53:38 WARNING: loader.c:325 __load_resource: / usr/lib/asterisk/modules/pbx_wilcalu.so: undefined symbol: ast_pthread_create
Mar 12 05:53:38 WARNING: loader.c:554 load_modules: Loading module pbx_wi lcalu.so failed!
I am running Ubuntu 5.10. This is a new install of Asterisk 1.2.5
My modules.conf does not load “pbx_wilcalu.so” - it is right here:
; Asterisk configuration file
; Module Loader configuration file
; Any modules that need to be loaded before the Asterisk core has been
; initialized (just after the logger has been initialized) can be loaded
; using ‘preload’. This will frequently be needed if you wish to map all
; module configuration files into Realtime storage, since the Realtime
; driver will need to be loaded before the modules using those configuration
; files are initialized.
; An example of loading ODBC support would be:
noload => res_odbc.so ;preload
noload => res_config_odbc.so
; If you want, load the GTK console right away.
; Don’t load the KDE console since
; it’s not as sophisticated right now.
noload => pbx_gtkconsole.so
;load => pbx_gtkconsole.so
noload => pbx_kdeconsole.so
; Intercom application is obsoleted by
; chan_oss. Don’t load it.
noload => app_intercom.so
; The ‘modem’ channel driver and its subdrivers are
; obsolete, don’t load them.
noload => chan_modem.so
noload => chan_modem_aopen.so
noload => chan_modem_bestdata.so
noload => chan_modem_i4l.so
load => res_musiconhold.so
; Load either OSS or ALSA, not both
; By default, load OSS only (automatically) and do not load ALSA
noload => chan_alsa.so
noload => chan_oss.so
; Module names listed in “global” section will have symbols globally
; exported to modules loaded after them.