Compiling Dahdi (Can’t Read Private Key)

Home » Asterisk Users » Compiling Dahdi (Can’t Read Private Key)
Asterisk Users 2 Comments

Since a couple versions back I keep getting these messages when compiling Dahdi:

make[2]: Entering directory `/usr/src/kernels/3.10.0-327.13.1.el7.x86_64′
INSTALL
/usr/src/dahdi-linux-complete-2.11.1+2.11.1/linux/drivers/dahdi/dahdi.ko Can’t read private key
INSTALL
/usr/src/dahdi-linux-complete-2.11.1+2.11.1/linux/drivers/dahdi/dahdi_dynamic.ko Can’t read private key
INSTALL
/usr/src/dahdi-linux-complete-2.11.1+2.11.1/linux/drivers/dahdi/dahdi_dynamic_eth.ko Can’t read private key
INSTALL
/usr/src/dahdi-linux-complete-2.11.1+2.11.1/linux/drivers/dahdi/dahdi_dynamic_ethmf.ko Can’t read private key
INSTALL
/usr/src/dahdi-linux-complete-2.11.1+2.11.1/linux/drivers/dahdi/dahdi_dynamic_loc.ko Can’t read private key
INSTALL
/usr/src/dahdi-linux-complete-2.11.1+2.11.1/linux/drivers/dahdi/dahdi_echocan_jpah.ko Can’t read private key
INSTALL
/usr/src/dahdi-linux-complete-2.11.1+2.11.1/linux/drivers/dahdi/dahdi_echocan_kb1.ko Can’t read private key
INSTALL
/usr/src/dahdi-linux-complete-2.11.1+2.11.1/linux/drivers/dahdi/dahdi_echocan_mg2.ko Can’t read private key
INSTALL
/usr/src/dahdi-linux-complete-2.11.1+2.11.1/linux/drivers/dahdi/dahdi_echocan_sec.ko Can’t read private key
INSTALL
/usr/src/dahdi-linux-complete-2.11.1+2.11.1/linux/drivers/dahdi/dahdi_echocan_sec2.ko Can’t read private key

Anyone know what they are about?


Telecomunicaciones Abiertas de México S.A. de C.V. Carlos Chávez
+52 (55)9116-91161

2 thoughts on - Compiling Dahdi (Can’t Read Private Key)

  • You can ignore this. I guess your system is CentOS 7. I used to know what the reason was, but forgot it. I guess when you google the message, you’ll find an answer.

    jg

  • I guess this is related to CentOS 7 wanting signed kernel modules then. Seems they work anyway. Now the only remaining problem is that after doing “make config” the make file is not installing any startup script. I did it several times and nothing happened. I had to manually copy dahdi.init to /etc/init.d/dahdi and then enable the service. This script can still start dahdi but can no longer stop it, at least the kernel modules are no longer unloaded when you do a “service dahdi stop”. Seems systemd finally got the better of the old startup scripts. Has anyone made some systemd native scripts for dahdi and asterisk?