[Home]

Summary:DAHTOOL-00073: /etc/init.d/dahd.d not found version 2.11
Reporter:Trent Creekmore (tcreek)Labels:
Date Opened:2016-02-24 00:17:06.000-0600Date Closed:2018-09-20 13:10:11
Priority:BlockerRegression?No
Status:Closed/CompleteComponents:General
Versions:2.10.0 Frequency of
Occurrence		Constant
Related
Issues:
Environment:CentOS 6.7 Dual Core Atom D2500 1.8GhzAttachments:
Description:Obtained dahdi-linux-complete-2.11.0+2.11.0 via...
http://downloads.asterisk.org/pub/telephony/dahdi-linux-complete/dahdi-linux-complete-current.tar.gz

Then entered the following commands:

   make
   make install
   make config

Completes without any errors.

Then I enter  "service dahdi start" which returns:
"dahdi: unrecognized service"

Also try "/etc/init.d/dahd.d" which returns:
"-bash: /etc/init.d/dahd.d: No such file or directory"


I also tried following the steps at https://wiki.asterisk.org/wiki/display/DAHDI/Quick+Start+From+Source

No errors in the steps, then I get to this point:

"cat /etc/dahdi/modules" which shows:

   Autogenerated by /usr/sbin/dahdi_genconf (Dahdi::Config::Gen::Modules) on Tue Feb 23 12:55:53 2016
   If you edit this file and execute /usr/sbin/dahdi_genconf again, your manual change
   wanpipe

However once I get to the "dahdi_genconf system"
I get : "Empty configuration -- no spans"

After completion:
 "service dahdi start" &  "/etc/init.d/dahd.d" returns the same as above






Comments:By: Trent Creekmore (tcreek) 2016-02-24 01:26:46.465-0600

I should note I was able to successfully get 2.10 compiled and functioning.
By: Shaun Ruffell (sruffell) 2016-02-25 23:40:16.997-0600

With wanpipe listed in the output of dahdi_genconf, you must have a Sangoma board installed and wanpipe isn't shipped as part of DAHDI.  Have you contacted them for help?  I'm guessing this is a system that had wanpipe installed on it before and I can't be certain what changes that makes since I've not used wanpipe before.

Otherwise, I recommend removing the sangoma card, and reinstalling a fresh distribution and installing DAHDI without any hardware.  DAHDI is tested regularly against Centos 6.7 and you should be able to see something like below:

{code}
[sruffell@asterisk dahdi-linux-complete-2.11.0+2.11.0]$ sudo asterisk -rx 'timing test'
Attempting to test a timer with 50 ticks per second.
Using the 'DAHDI' timing module for this test.
It has been 1019 milliseconds, and we got 51 timer ticks
[sruffell@asterisk dahdi-linux-complete-2.11.0+2.11.0]$ sudo dahdi_cfg -tv                                                                                
DAHDI Tools Version - 2.11.0

DAHDI Version: 2.11.0
Echo Canceller(s):
Configuration
======================


0 channels to configure.

[sruffell@asterisk dahdi-linux-complete-2.11.0+2.11.0]$ cat /etc/centos-release
CentOS release 6.7 (Final)
{code}

By: Trent Creekmore (tcreek) 2016-02-27 01:46:49.823-0600

This is a new fresh install of of CentOS 6.7

I started with LibPri then on to DAHDI even before I started with the Wanpipe install.


By: Shaun Ruffell (sruffell) 2016-03-02 15:26:45.988-0600

I spoke about this with [~wthompson], and it appears that there may have been an inadvertent change in 2.11.0.  Specifically, the {{make config}} target in dahdi-tools doesn't do anything anymore but was changed to {{make install-config}}.  

So...in the interim, do if you go to the tools directory and run {{make install-config}} do you then get the behavior you expect?
By: Keith Morgan (kmorgan) 2018-09-20 13:05:33.950-0500

I changed the Makefile.legacy to match the needed command.  It says make install-config now instead of make config.