[asterisk-bugs] [Asterisk 0013365]: Asterisk fails to start

[Asterisk Bug Tracker]

A NOTE has been added to this issue. 
====================================================================== 
http://bugs.digium.com/view.php?id=13365 
====================================================================== 
Reported By:                mthomasslo
Assigned To:                
====================================================================== 
Project:                    Asterisk
Issue ID:                   13365
Category:                   General
Reproducibility:            always
Severity:                   minor
Priority:                   normal
Status:                     feedback
Asterisk Version:           1.4.20.1 
SVN Branch (only for SVN checkouts, not tarball releases):  1.4  
SVN Revision (number only!): 135058 
Disclaimer on File?:        N/A 
Request Review:              
====================================================================== 
Date Submitted:             2008-08-22 19:06 CDT
Last Modified:              2008-09-02 12:44 CDT
====================================================================== 
Summary:                    Asterisk fails to start
Description: 
Asterisk fails to start with the message "asterisk.c:2966 main: Asterisk
has detected a problem with your Zaptel configuration and will shutdown for
your protection."  If I stop Zaptel it starts and runs fine, except for the
functions that require ztdummy.  Zttool shows the ztdummy running fine.
====================================================================== 

---------------------------------------------------------------------- 
 (0091976) mthomasslo (reporter) - 2008-09-02 12:44
 http://bugs.digium.com/view.php?id=13365#c91976 
---------------------------------------------------------------------- 
This appears to be hardware related,  I set up the exact same system in a
different PC and it works fine (Kernel = 2.6.18-8 in each case) Centos 5.0
(x86_64) Same build, same zapata.conf and zaptel.conf etc.  Unless you are
interested in determining a cause, I'd say close the issue, and I'll use
the machine that it runs ok on. 

Issue History 
Date Modified    Username       Field                    Change               
====================================================================== 
2008-09-02 12:44 mthomasslo     Note Added: 0091976                          
======================================================================