[asterisk-bugs] [JIRA] (DAHLIN-349) Installation fails

[PowerPBX (JIRA)]

     [ https://issues.asterisk.org/jira/browse/DAHLIN-349?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

PowerPBX updated DAHLIN-349:
----------------------------

    Description: 
I have never had an issue installing Dahdi before now.  This affects v2.11.1.  May affect previous versions but not sure.

I reverted to an older version (2.10.0.1) I know works and it installed without issue with no other changes to my install environment.  Not sure why 2.11.1 doesn't show up in your ticketing system as a current stable version even though that is what gets downloaded when I use dahid-linux-complete-current.tar.gz

Unless there is a new prerequesite I am not aware of I think there is an issue on this latest release.

My install procedure was as follows

wget http://downloads.asterisk.org/pub/telephony/dahdi-linux-complete/dahdi-linux-complete-current.tar.gz

tar zxvf dahdi-linux-complete*
cd /usr/src/dahdi-linux-complete*/
make all && make install && make config

Everything appears to compile and install correctly, however there is no /etc/dahdi/system.conf and no /etc/init/d/dahdi created.  It may just be make config step that fails although I do not see any errors.  If I manually create those files it fails to start so there must be several steps in the install that are not completed

If I follow the exact same install procedure on v2.10.0.1 it installs and runs as expected with no other changes made.


  was:
I have never had an issue installing Dahdi before now.  This affects v2.11.1.  May affect previous versions but not sure.

I reverted to an older version (2.10.0.1) I know works and it installed without issue with no other changes to my install environment.  Not sure why 2.11.1 doesn't show up in your ticketing system as a current stable version even though that is what gets downloaded when I use dahid-linux-complete-current.tar.gz

Unless there is a new prerequesite I am not aware of I think there is an issue on this latest release.

My install procedure was as follows

wget http://downloads.asterisk.org/pub/telephony/dahdi-linux-complete/dahdi-linux-complete-current.tar.gz

tar zxvf dahdi-linux-complete*
cd /usr/src/dahdi-linux-complete*/
make all && make install && make config

Everything appears to compile and install correctly, however there is no /etc/dahdi/system.conf and no /etc/init/d/dahdi created.  It may just be make config step that fails although I do not see any errors.

If I follow the exact same install procedure on v2.10.0.1 it installs and runs as expected with no other changes made.



> Installation fails
> ------------------
>
>                 Key: DAHLIN-349
>                 URL: https://issues.asterisk.org/jira/browse/DAHLIN-349
>             Project: DAHDI-Linux
>          Issue Type: Bug
>      Security Level: None
>          Components: dahdi (the module)
>    Affects Versions: 2.10.0.1
>         Environment: CentOS v6
>            Reporter: PowerPBX
>            Assignee: Wendell Thompson
>
> I have never had an issue installing Dahdi before now.  This affects v2.11.1.  May affect previous versions but not sure.
> I reverted to an older version (2.10.0.1) I know works and it installed without issue with no other changes to my install environment.  Not sure why 2.11.1 doesn't show up in your ticketing system as a current stable version even though that is what gets downloaded when I use dahid-linux-complete-current.tar.gz
> Unless there is a new prerequesite I am not aware of I think there is an issue on this latest release.
> My install procedure was as follows
> wget http://downloads.asterisk.org/pub/telephony/dahdi-linux-complete/dahdi-linux-complete-current.tar.gz
> tar zxvf dahdi-linux-complete*
> cd /usr/src/dahdi-linux-complete*/
> make all && make install && make config
> Everything appears to compile and install correctly, however there is no /etc/dahdi/system.conf and no /etc/init/d/dahdi created.  It may just be make config step that fails although I do not see any errors.  If I manually create those files it fails to start so there must be several steps in the install that are not completed
> If I follow the exact same install procedure on v2.10.0.1 it installs and runs as expected with no other changes made.



--
This message was sent by Atlassian JIRA
(v6.2#6252)