Bug 85655 – Asterisk 1.0.6 emerges fine but fails to run (/usr/lib/asterisk/modules/res_features.so: undefined symbol: adsi_available)

• Product: Gentoo Linux
• Status: RESOLVED FIXED

[Description Vincenzo Romano 2005-03-17 08:39:56 UTC]

I've emerged asterisk-1.0.6 with no error or warning at all.
But when run it fails to start leaving the mpg123 in the background.
I've activated a "full" logger that says:
WARNING[29061]: /usr/lib/asterisk/modules/res_features.so: undefined symbol: adsi_available
WARNING[29061]: Loading module res_features.so failed!


Reproducible: Always
Steps to Reproduce:
1. ACCEPT_KEYWORD="~x86" emerge asterisk
2. /etc/init,d/asterisk start


Actual Results:  
The asterisk process itself is not running at all, while a orphan
mpg123 process is left running

Expected Results:  
The daemon asterisk should at least remain running or dying with some cfg error
message.

[Comment 1 Vincenzo Romano 2005-03-17 08:42:13 UTC]

Created attachment 53707 [details]
emerge --info output

[Comment 2 Remco Barendse 2005-03-20 01:56:51 UTC]

I have the same problem. Actually there are 2 problems here.

The first being that zaptel is installed but it is *not* executing ztcfg before asterisk is started at boot time. When you run ztcfg -v manually you will see that your zaptel card is initalized and if you then zap asterisk and start it everything will be ok.

Then the second problem mpg123. This is due to the ancient version of mpg123 that asterisk likes is not in portage and also due to bugs in asterisk. Once you stop asterisk (and stopping due to not starting fully counts too) you are left with stale mpg123 processes. Just kill them will killall -9 mpg123. I do this regularly and it should be solved in * sometime.

[Comment 3 Remco Barendse 2005-03-20 02:51:25 UTC]

OK, I got a little further. I added a -v to ztcfg in the start section to see if anything is happeing. In the default script when I do zaptel start, nothing happens. However when I comment out these lines in the start section:
        #checkconfig || exit 1

        #if [ ! -d /dev/zap ] && [ "$ZAP_FORCE_CREATE" != "no" ]; then
        #       einfo "Creating zaptel device nodes"
        #       create_devices
        #fi

Zaptel does start!!

I haven't got a clue why it is getting killed on these lines but it's not correct. When I do /etc/init.d/zaptel start I see the channels being created properly.

[Comment 4 Stefan Knoblich (RETIRED) 2005-07-29 13:08:01 UTC]

see #100697 for details, fixed in cvs (1.0.8 and 1.0.9)