I have this problem after update to Asterisk 11.16.0:
module load chan_dahdi.so
Unable to load module chan_dahdi.so
Command ‘module load chan_dahdi.so’ failed.
[2015-02-27 11:49:37] WARNING[8486]: loader.c:439 load_dynamic_module: Error loading module ‘chan_dahdi.so’: libwat.so.1.0.24: cannot open shared object file: No such file or directory
[2015-02-27 11:49:37] WARNING[8486]: loader.c:918 load_resource: Module ‘chan_dahdi.so’ could not be loaded.
Resolved with:
cd/usr/lib64
cp libwat.so.1.0.25 libwat.so.1.0.24
atcom
(atcomsystems.ca)
May 14, 2015, 7:55pm
3
Just used this method to recover dahdi on a system:
cp /usr/lib/libwat.so /usr/lib/libwat.so.1.0.24
GSnover
(GSnover)
May 18, 2015, 3:23pm
4
cp /usr/lib64/libwat.so /usr/lib64/libwat.so.1.0.24
for 64-Bit systems - Why is this still coming up? I updated a box this weekend and this bug came up again - even though it was reported back in February?
What version of the Distro are you using @GSnover . Based on your other thread its a very old version of the Distro which is not supported in years.
GSnover
(GSnover)
May 18, 2015, 4:10pm
6
Absolutely latest version of the Distro achieved with the System Admin Pro and running all upgrade scripts to current:
PBX Firmware: 6.12.65-27
PBX Service Pack: 1.0.0.0
What version of Asterisk?
GSnover
(GSnover)
May 18, 2015, 5:44pm
8
Connected to Asterisk 11.17.1 currently running on localhost (pid = 12102)
localhost*CLI>
GSnover
(GSnover)
May 18, 2015, 6:25pm
9
I didn’t mean to, but I think I have two threads going on the same topic - We should close this one and look here:
Continuing the discussion from DAHDI module not loading (SOLVED, but a bug) :
I think this needs to be relooked at - I did all the updates on this box this weekend with System Admin Pro and still ended up with this problem - so something in the scripts is missing this bug also.
Don’t know how to link them.
Please do a yum update. This has been resolved with the latest Asterisk RPMs we built.
GSnover
(GSnover)
May 20, 2015, 7:12pm
11
Yup - Updates worked fine on another box last night - no problems with libwat now.
Thanks!