# Asterisk does not start properly (log files provided) **URL:** \ **Category:** Asterisk General\ **Created:** [August 14, 2007, 11:22am UTC](https://community.asterisk.org/t/asterisk-does-not-start-properly-log-files-provided/16163 "2007-08-14T11:22:59Z")\ **Posts on this page:** 3\ **Page:** 1
**Author:** ![saeed144](https://avatars.discourse-cdn.com/v4/letter/s/db5fbb/32.png) [@saeed144](https://community.asterisk.org/u/saeed144)\ **Post date:** [August 14, 2007, 11:22am UTC](https://community.asterisk.org/t/asterisk-does-not-start-properly-log-files-provided/16163/1 "2007-08-14T11:22:59Z")
Hello, I have CentOS 2.6.9-22.ELsmp; Asterisk 1.2.13; The asterisk used to come up everytime system booted, but somehow it stopped doing so, I ran “genzaptelconf” and it showed this message, Please tell me how can I make sure Asterisk comes up OK everytime system rebooted. Thanks in advance, Saeed ############################## STOPPING ASTERISK STOPPING FOP SERVER Generating '/etc/zaptel.conf’ Generating '/etc/asterisk/zapata-auto.conf’ Unloading zaptel hardware drivers: wctdm24xxp wctdm wcfxo wcte11xp wct1xxp wct4x xp tor2. Removing zaptel module: ERROR: Module zaptel is in use by ztdummy [FAILED] Loading zaptel framework: [OK] Waiting for zap to come online…OK Loading zaptel hardware modules: tor2 wct4xxp wct1xxp wcte11xp wcfxo wctdm wctdm 24xxpRunning ztcfg: [OK] SETTING FILE PERMISSIONS Permissions OK STARTING ASTERISK Asterisk ended with exit status 1 Asterisk died with code 1. Automatically restarting Asterisk. Asterisk ended with exit status 1 Asterisk died with code 1. Automatically restarting Asterisk. * * * ## Asterisk could not start! Use ‘tail /var/log/asterisk/full’ to find out why. Unable to connect to remote asterisk (does /var/run/asterisk/asterisk.ctl exist?) [root@MINA1 /]# tail --lines 20 /var/log/asterisk/full Aug 14 11:51:31 VERBOSE[3392] logger.c: [chan\_skinny.so]Aug 14 11:51:31 VERBOSE[3392] logger.c: [chan\_skinny.so] =\> (Skinny Client Control Protocol (Skinny)) Aug 14 11:51:31 VERBOSE[3392] logger.c: == Parsing ‘/etc/asterisk/skinny.conf’: Aug 14 11:51:31 VERBOSE[3392] logger.c: == Parsing ‘/etc/asterisk/skinny.conf’: Found Aug 14 11:51:31 VERBOSE[3392] logger.c: == Skinny listening on 0.0.0.0:2000 Aug 14 11:51:31 VERBOSE[3392] logger.c: == Registered channel type ‘Skinny’ (Skinny Client Control Protocol (Skinny)) Aug 14 11:51:31 VERBOSE[3392] logger.c: [chan\_features.so]Aug 14 11:51:31 VERBOSE[3392] logger.c: [chan\_features.so] =\> (Feature Proxy Channel) Aug 14 11:51:31 VERBOSE[3392] logger.c: == Registered channel type ‘Feature’ (Feature Proxy Channel Driver) Aug 14 11:51:31 VERBOSE[3392] logger.c: [skipping chan\_oss.so] Aug 14 11:51:31 VERBOSE[3392] logger.c: [chan\_phone.so]Aug 14 11:51:31 VERBOSE[3392] logger.c: [chan\_phone.so] =\> (Linux Telephony API Support) Aug 14 11:51:31 VERBOSE[3392] logger.c: == Parsing ‘/etc/asterisk/phone.conf’: Aug 14 11:51:31 VERBOSE[3392] logger.c: == Parsing ‘/etc/asterisk/phone.conf’: Found Aug 14 11:51:31 VERBOSE[3392] logger.c: == Registered channel type ‘Phone’ (Standard Linux Telephony API Driver) Aug 14 11:51:31 VERBOSE[3392] logger.c: [chan\_zap.so]Aug 14 11:51:31 VERBOSE[3392] logger.c: [chan\_zap.so] =\> (Zapata Telephony w/PRI) Aug 14 11:51:31 VERBOSE[3392] logger.c: == Parsing ‘/etc/asterisk/zapata.conf’: Aug 14 11:51:31 VERBOSE[3392] logger.c: == Parsing ‘/etc/asterisk/zapata.conf’: Found Aug 14 11:51:31 VERBOSE[3392] logger.c: == Parsing ‘/etc/asterisk/zapata-auto.conf’: Aug 14 11:51:31 VERBOSE[3392] logger.c: == Parsing ‘/etc/asterisk/zapata-auto.conf’: Found Aug 14 11:51:31 VERBOSE[3392] logger.c: == Parsing ‘/etc/asterisk/zapata\_additional.conf’: Aug 14 11:51:31 VERBOSE[3392] logger.c: == Parsing ‘/etc/asterisk/zapata\_additional.conf’: Found Aug 14 11:51:31 WARNING[3392] chan\_zap.c: Unable to specify channel 1: Device or resource busy Aug 14 11:51:31 ERROR[3392] chan\_zap.c: Unable to open channel 1: Device or resource busy here = 0, tmp-\>channel = 1, channel = 1 Aug 14 11:51:31 ERROR[3392] chan\_zap.c: Unable to register channel '1’ Aug 14 11:51:31 WARNING[3392] loader.c: chan\_zap.so: load\_module failed, returning -1 Aug 14 11:51:31 WARNING[3392] loader.c: Loading module chan\_zap.so failed! ---
**Author:** ![ianplain](https://sea1.discourse-cdn.com/asterisk/user_avatar/community.asterisk.org/ianplain/32/1776_2.png) [@ianplain](https://community.asterisk.org/u/ianplain)\ **Post date:** [August 14, 2007, 11:24am UTC](https://community.asterisk.org/t/asterisk-does-not-start-properly-log-files-provided/16163/2 "2007-08-14T11:24:36Z")
Hi Somethings not right with your zapata.conf file. Ian ---
**Author:** ![saeed144](https://avatars.discourse-cdn.com/v4/letter/s/db5fbb/32.png) [@saeed144](https://community.asterisk.org/u/saeed144)\ **Post date:** [August 14, 2007, 2:35pm UTC](https://community.asterisk.org/t/asterisk-does-not-start-properly-log-files-provided/16163/3 "2007-08-14T14:35:26Z")
Hi ya, This script solved the problem yet it doesn’t seem to be a solution since it produces zaptel files from scratch. Thanks to Ian, Saeed rebuild\_zaptel Shutdown –r now genzaptelconf Shutdown –r now