On Apr 7, 2010, at 3:42 AM, Tom Chadwin wrote:
> Hello all
>
> A major issue with 0.7.1 seems to have transpired. I upgraded six or so
> boxes last week, two of which use DAHDI. Asterisk seems to have failed to
> run. When I try to start it from the command line, I get:
>
> [Apr 7 09:40:18] ERROR[2705]: asterisk.c:3099 main: Asterisk has detected a
> problem with your DAHDI configuration and will shutdown for your protection.
> You have options:
> 1. You only have to compile DAHDI support into Asterisk if you need
> it. One option is to recompile without DAHDI support.
> 2. You only have to load DAHDI drivers if you want to take advantage
> of DAHDI services. One option is to unload DAHDI modules if you don't need
> them.
> 3. If you need Zaptel services, you must correctly configure DAHDI.
>
> DAHDI was working on these boxes in 0.7.0, and Zaptel on them in 0.6.
>
> Can anyone help?
>
> Tom
This is related to "/dev/dahdi/timer" in DAHDI. The calling code in asterisk.c
is below.
What is your variable DAHDIMODS set to?
What is "cat /etc/rc.modules" ?
Are you dong any modprobes in a rc.local or such?
For fun, try "modprobe dahdi_dummy" then "service asterisk start" as Michael
suggested, and see if asterisk starts.
Lonnie
#ifdef HAVE_DAHDI
{
int fd;
int x = 160;
fd = open(DAHDI_FILE_TIMER, O_RDWR);
if (fd >= 0) {
if (ioctl(fd, DAHDI_TIMERCONFIG, &x)) {
ast_log(LOG_ERROR, "You have " DAHDI_NAME
" built and drivers loaded, but
the "
DAHDI_NAME " timer test failed
to set DAHDI_TIMERCONFIG to %d.\n", x);
exit(1);
}
if ((x = ast_wait_for_input(fd, 300)) < 0) {
ast_log(LOG_ERROR, "You have " DAHDI_NAME
"built and drivers loaded, but
the "
DAHDI_NAME " timer could not be
polled during the "
DAHDI_NAME " timer test.\n");
exit(1);
}
if (!x) {
const char dahdi_timer_error[] = {
"Asterisk has detected a problem with
your " DAHDI_NAME
" configuration and will
shutdown for your protection. You have options:"
"\n\t1. You only have to compile "
DAHDI_NAME
" support into Asterisk if you
need it. One option is to recompile without "
DAHDI_NAME " support."
"\n\t2. You only have to load "
DAHDI_NAME " drivers if you want to take advantage of "
DAHDI_NAME " services. One
option is to unload "
DAHDI_NAME " modules if you
don't need them."
"\n\t3. If you need Zaptel services,
you must correctly configure " DAHDI_NAME "."
};
ast_log(LOG_ERROR, "%s\n", dahdi_timer_error);
exit(1);
}
close(fd);
}
}
#endif
------------------------------------------------------------------------------
Download Intel® Parallel Studio Eval
Try the new software tools for yourself. Speed compiling, find bugs
proactively, and fine-tune applications for parallel performance.
See why Intel Parallel Studio got high marks during beta.
http://p.sf.net/sfu/intel-sw-dev
_______________________________________________
Astlinux-users mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/astlinux-users
Donations to support AstLinux are graciously accepted via PayPal to
[email protected].
