|Summary:||ASTERISK-12190: Asterisk fails to start|
|Reporter:||David Woolley (davidw)||Labels:|
|Date Opened:||2008-06-13 12:22:07||Date Closed:||2011-06-07 14:00:40|
|Environment:||Attachments:||( 0) fulllogtail.txt|
( 1) typescript.txt
|Description:||I replaced 184.108.40.206 with 1.4 latest (122609), to test whether another issue was completely fixed. Using safe_asterisk, it looped on continually starting, mentioning exit code 1. There were no core dumps. Also running the executable directly with -c, it exited during intialisation.|
****** ADDITIONAL INFORMATION ******
There also appears to be a lack of newlines in the log file.
|Comments:||By: David Woolley (davidw) 2008-06-13 12:41:46|
The problem seems to relate to dahdi. It's also poisoned the modules directory for 220.127.116.11, so I couldn't revert. Removing
-rwxr-xr-x 1 root root 146303 Jun 13 18:11 app_dahdibarge.so
-rwxr-xr-x 1 root root 148816 Jun 13 18:11 app_dahdiscan.so
-rwxr-xr-x 1 root root 150869 Jun 13 18:11 app_dahdiras.so
-rwxr-xr-x 1 root root 144580 Jun 13 18:11 codec_dahdi.so
from the modules directory got me back 18.104.22.168.
By: David Woolley (davidw) 2008-06-13 12:57:30
Removing all the dahdi stuff and:
rm: remove regular file `app_zapbarge.so'? y
rm: remove regular file `app_zapras.so'? y
rm: remove regular file `app_zapscan.so'? y
rm: remove regular file `chan_zap.so'? y
rm: remove regular file `codec_zap.so'? y
allows it to start. I'm not sure if it was just the zap stuff that was actually breaking it, and as we only have ztdummy, that isn't important to followup.
By: Tilghman Lesher (tilghman) 2008-06-13 13:07:10
This may already be fixed; please see bug ASTERISK-12184
By: David Woolley (davidw) 2008-06-13 13:26:25
I was going to say that too. As disabling dahdi cleared our problem, and we are normally using the tagged 1.4 versions, I'm happy for this to be closed.