Fixed: PIAF 1.7.5.5.4 hangs on Dahdi

[amygrant]

Grabbed the latest 64 bit piaf last night (PIAF1.7.5.5.4-CentOS-5.5-64bit)

http://sourceforge.net/projects/pbxinaflash/files/PIAF-1.7.5.5.4-CentOS-5.5-64bit/

During the install of purple, it gets up to the point of compiling dahdi and then hangs. I let it sit for about 2 hours before I did a soft reboot and it froze in the same spot again.

Added dahdi info to the registry
<<D>> Compiling Dahdi Proceeding
Processing make all

... then it hangs

This is going on a comp that was successfully running an older version of PIAF and I figured I'll upgrade it so I know the computer is functioning fine. Network connection is fine.

I guess it could somehow be a bad image download or so I'm going to try to re-download the image and see if that fixes it.

 

[amygrant]

I have re-downloaded the image and burned a new cd. The install hangs in the exact same spot.

I don't see how it would be relevant but just in case, this is going in an Acer Aspire Revo

 

[darmock]

so what do the logs say? look in var log

Since you did not say which version of PIAF you are installing gold/silver/bronze/purple look for install-put your color here.log and start looking thru it till you get to dahdi. Then see what it is failing on

Tom

 

[amygrant]

My bad, thought I mentioned it was purple.

Here is the beginning of the dahdi package install

Resolving downloads.digium.com... 76.164.171.232, 2001:470:e0d4::e8
Connecting to downloads.digium.com|76.164.171.232|:80... connected.
HTTP request sent, awaiting response... 200 OK
Length: 149360 (146K) [application/x-gzip]
Saving to: `dahdi-fwload-vpmadt032-1.25.0.tar.gz'

     0K .......... .......... .......... .......... .......... 34%  154K 1s
    50K .......... .......... .......... .......... .......... 68%  596K 0s
   100K .......... .......... .......... .......... .....     100%  569K=0.5s

2009-01-01 15:07:17 (298 KB/s) - `dahdi-fwload-vpmadt032-1.25.0.tar.gz' saved [149360/149360]

tar: drivers/dahdi/vpmadt032_loader/vpmadt032_x86_64.o_shipped: time stamp 2010-07-14 23:18:57 is 48323500 s in the future
tar: drivers/dahdi/vpmadt032_loader/vpmadt032_x86_32.o_shipped: time stamp 2010-07-14 23:18:57 is 48323500 s in the future
tar: drivers/dahdi/vpmadt032_loader/vpmadt032_loader.h: time stamp 2010-07-14 23:18:57 is 48323500 s in the future
tar: drivers/dahdi/vpmadt032_loader: time stamp 2010-07-14 23:18:57 is 48323500 s in the future
tar: drivers/dahdi: time stamp 2010-07-14 23:18:57 is 48323500 s in the future
tar: drivers: time stamp 2010-07-14 23:18:57 is 48323500 s in the future
make[2]: warning:  Clock skew detected.  Your build may be incomplete.  
make[2]: Leaving directory `/usr/src/dahdi/linux/drivers/dahdi/firmware'
make -C /lib/modules/2.6.18-194.26.1.el5/build SUBDIRS=/usr/src/dahdi/linux/drivers/dahdi DAHDI_INCLUDE=/usr/src/dahdi/linux/include DAHDI_MODULES_EXTRA=" "
make[2]: Entering directory `/usr/src/kernels/2.6.18-194.26.1.el5-x86_64'
make[2]: Warning: File `/usr/src/kernels/2.6.18-194.26.1.el5-x86_64/arch/x86_64/Makefile' has modification time 5.8e+07 s in the future
make[3]: Warning: File `/usr/src/dahdi/linux/drivers/dahdi/Kbuild' has modification time 4.3e+07 s in the future

then after a bit it kicks this out

configure: *** dahdi-tools build successfully configured ***
make -C tools all
make[1]: Entering directory `/usr/src/dahdi/tools'
make[1]: Warning: File `Makefile' has modification time 3.9e+07 s in the future
CC="" CXX="g++" LD="" AR="" RANLIB="" CFLAGS="" make -C menuselect CONFIGURE_SILENT="--silent" makeopts
make[2]: Entering directory `/usr/src/dahdi/tools/menuselect'
make[2]: Warning: File `autoconfig.h.in' has modification time 5.2e+07 s in the future
Package xau was not found in the pkg-config search path.
Perhaps you should add the directory containing `xau.pc'
to the PKG_CONFIG_PATH environment variable
Package 'xau', required by 'X11', not found
make[2]: warning:  Clock skew detected.  Your build may be incomplete.
make[2]: Leaving directory `/usr/src/dahdi/tools/menuselect'
CC="" CXX="g++" LD="" AR="" RANLIB="" CFLAGS="" make -C menuselect CONFIGURE_SILENT="--silent" menuselect
make[2]: Entering directory `/usr/src/dahdi/tools/menuselect'
make[2]: Warning: File `autoconfig.h.in' has modification time 5.2e+07 s in the future
Package xau was not found in the pkg-config search path.
Perhaps you should add the directory containing `xau.pc'
to the PKG_CONFIG_PATH environment variable
Package 'xau', required by 'X11', not found
make[2]: Leaving directory `/usr/src/dahdi/tools/menuselect'
make[2]: Entering directory `/usr/src/dahdi/tools/menuselect'
make[2]: Warning: File `autoconfig.h.in' has modification time 5.2e+07 s in the future
Package xau was not found in the pkg-config search path.
Perhaps you should add the directory containing `xau.pc'
to the PKG_CONFIG_PATH environment variable

This repeats ad-infinitum:

Package xau was not found in the pkg-config search path.
Perhaps you should add the directory containing `xau.pc'
to the PKG_CONFIG_PATH environment variable
Package 'xau', required by 'X11', not found
make[2]: Leaving directory `/usr/src/dahdi/tools/menuselect'
make[2]: Entering directory `/usr/src/dahdi/tools/menuselect'
make[2]: Warning: File `autoconfig.h.in' has modification time 5.2e+07 s in the future

I know my clock is set right and after reading some other threads I am assuming this is related to the problems others have reported that have been traced to asterisk 1.81

 

[darmock]

yep asterisk 1.8.0 is back out there now. All works.

btw I fixed the problem with 1.8.1 however I can't duplicate the time error at all. Not sure what was the root cause of this.

Tom

 

[amygrant]

Did a reinstall and everything is kosher.

Regarding the clock, I think that was user error on my part. I had tunnel vision and saw the time was correct but missed the that the date was wrong.

Corrected that, did a re-install which grabbed asterisk 1.8.0 and all is good.

Thanks

 

[amygrant]

Mysql Unpopulated

Well I spoke too soon.. everything did install fine but the mysql tables in the asterisk database were not populated by the various data points you guys include.. such as the extensions in the 700 range, sample trunks, etc.

I did a dump on the entire asterisk database and attached it to this post so you can see which tables are populated and with what.

I then figured I would check the log files but I am not certain where I should see a data population nor how it would appear in a log file. I did a

grep "mysql" /var/log/*

I have attached the result of that as grep.zip

The only thing that stuck out in that grep was the entry

usr/src/freepbx/SQL/cdr_mysql_table.sql

However that file does not exist. I would *assume* it is a temporary file that gets deleted after piaf is installed.

Eyes are burning, sleep time for me. I will try doing a reinstall tomorrow in case it is isolated to something going wonky on me.

Figured, however, I'd give you a heads up on the unlikely chance that the latest piaf purple does not autopopulate the asterisk database

 

[amygrant]

Reinstalled and the tables were populated and everything is fine now.

Case closed.