Re: [Astlinux-users] 0.7.1 DAHDI Asterisk crash
Tom, The firmware should be in /lib/firmware. Other dahdi firmware is in that location. Is it possible that the 0.7.0 release had it, but 0.7.1 does not? Darrick Tom Chadwin wrote: > Exactly. Can anyone find where vpmadt032.bin (or whatever) should live > in a 2.2.1 install? Does anyone else have this hw module? > > Tom > > > > On 7 Apr 2010, at 22:24, Darrick Hartman > wrote: > >> Lonnie, >> >> He has a hardware echo canceller. Tom does not need to specify an >> echo >> canceller in the system.conf file when using a hardware EC. It is >> entirely possible that the EC is part of the cause, especially if the >> firmware files are not there. >> >> Darrick >> >> Lonnie Abelbeck wrote: >>> On Apr 7, 2010, at 9:45 AM, Tom Chadwin wrote: >>> You are getting an explicit timing-related error, but I don't seem to. For info, here are my DAHDI configs: ingrampbx ~ # cat /mnt/kd/dahdi/system.conf fxsks=1-2 loadzone=uk defaultzone=uk >>> Tom, >>> >>> Shouldn't you have "echocanceller" defined in /mnt/kd/dahdi/ >>> system.conf ? >>> >>> Doubt that is causing your problems though. >>> >>> Lonnie >>> >>> >>> --- >>> --- >>> --- >>> - >>> 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 >>> Astlinux-users@lists.sourceforge.net >>> https://lists.sourceforge.net/lists/listinfo/astlinux-users >>> >>> Donations to support AstLinux are graciously accepted via PayPal to >>> pay...@krisk.org >>> . >> --- >> --- >> --- >> - >> 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 >> Astlinux-users@lists.sourceforge.net >> https://lists.sourceforge.net/lists/listinfo/astlinux-users >> >> Donations to support AstLinux are graciously accepted via PayPal to >> pay...@krisk.org >> . > > -- > 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 > Astlinux-users@lists.sourceforge.net > https://lists.sourceforge.net/lists/listinfo/astlinux-users > > Donations to support AstLinux are graciously accepted via PayPal to > pay...@krisk.org. -- 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 Astlinux-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/astlinux-users Donations to support AstLinux are graciously accepted via PayPal to pay...@krisk.org.
Re: [Astlinux-users] 0.7.1 DAHDI Asterisk crash
Exactly. Can anyone find where vpmadt032.bin (or whatever) should live in a 2.2.1 install? Does anyone else have this hw module? Tom On 7 Apr 2010, at 22:24, Darrick Hartman wrote: > Lonnie, > > He has a hardware echo canceller. Tom does not need to specify an > echo > canceller in the system.conf file when using a hardware EC. It is > entirely possible that the EC is part of the cause, especially if the > firmware files are not there. > > Darrick > > Lonnie Abelbeck wrote: >> On Apr 7, 2010, at 9:45 AM, Tom Chadwin wrote: >> >>> You are getting an explicit timing-related error, but I don't seem >>> to. For >>> info, here are my DAHDI configs: >>> >>> ingrampbx ~ # cat /mnt/kd/dahdi/system.conf >>> fxsks=1-2 >>> loadzone=uk >>> defaultzone=uk >>> >> >> Tom, >> >> Shouldn't you have "echocanceller" defined in /mnt/kd/dahdi/ >> system.conf ? >> >> Doubt that is causing your problems though. >> >> Lonnie >> >> >> --- >> --- >> --- >> - >> 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 >> Astlinux-users@lists.sourceforge.net >> https://lists.sourceforge.net/lists/listinfo/astlinux-users >> >> Donations to support AstLinux are graciously accepted via PayPal to >> pay...@krisk.org >> . > > --- > --- > --- > - > 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 > Astlinux-users@lists.sourceforge.net > https://lists.sourceforge.net/lists/listinfo/astlinux-users > > Donations to support AstLinux are graciously accepted via PayPal to > pay...@krisk.org > . -- 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 Astlinux-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/astlinux-users Donations to support AstLinux are graciously accepted via PayPal to pay...@krisk.org.
Re: [Astlinux-users] 0.7.1 DAHDI Asterisk crash
Lonnie, He has a hardware echo canceller. Tom does not need to specify an echo canceller in the system.conf file when using a hardware EC. It is entirely possible that the EC is part of the cause, especially if the firmware files are not there. Darrick Lonnie Abelbeck wrote: > On Apr 7, 2010, at 9:45 AM, Tom Chadwin wrote: > >> You are getting an explicit timing-related error, but I don't seem to. For >> info, here are my DAHDI configs: >> >> ingrampbx ~ # cat /mnt/kd/dahdi/system.conf >> fxsks=1-2 >> loadzone=uk >> defaultzone=uk >> > > Tom, > > Shouldn't you have "echocanceller" defined in /mnt/kd/dahdi/system.conf ? > > Doubt that is causing your problems though. > > Lonnie > > > -- > 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 > Astlinux-users@lists.sourceforge.net > https://lists.sourceforge.net/lists/listinfo/astlinux-users > > Donations to support AstLinux are graciously accepted via PayPal to > pay...@krisk.org. -- 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 Astlinux-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/astlinux-users Donations to support AstLinux are graciously accepted via PayPal to pay...@krisk.org.
Re: [Astlinux-users] 0.7.1 DAHDI Asterisk crash
On Apr 7, 2010, at 9:45 AM, Tom Chadwin wrote: > You are getting an explicit timing-related error, but I don't seem to. For > info, here are my DAHDI configs: > > ingrampbx ~ # cat /mnt/kd/dahdi/system.conf > fxsks=1-2 > loadzone=uk > defaultzone=uk > Tom, Shouldn't you have "echocanceller" defined in /mnt/kd/dahdi/system.conf ? Doubt that is causing your problems though. Lonnie -- 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 Astlinux-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/astlinux-users Donations to support AstLinux are graciously accepted via PayPal to pay...@krisk.org.
Re: [Astlinux-users] 0.7.1 DAHDI Asterisk crash
On Apr 7, 2010, at 1:05 PM, Michael Keuter wrote: >> For fun, try "modprobe dahdi_dummy" then "service asterisk start" as >> Michael suggested, and see if asterisk starts. >> >> Lonnie > > BTW: How can I setup multiple modules in DAHDIMODS? > I need "zaphfc dahdi_transcode dahdi_dummy" and in exactly this order. > > Michael DAHDIMODS="zaphfc dahdi_transcode dahdi_dummy" ie, space separate them. Lonnie -- 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 Astlinux-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/astlinux-users Donations to support AstLinux are graciously accepted via PayPal to pay...@krisk.org.
Re: [Astlinux-users] 0.7.1 DAHDI Asterisk crash
>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 BTW: How can I setup multiple modules in DAHDIMODS? I need "zaphfc dahdi_transcode dahdi_dummy" and in exactly this order. Michael http://www.mksolutions.info -- 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 Astlinux-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/astlinux-users Donations to support AstLinux are graciously accepted via PayPal to pay...@krisk.org.
Re: [Astlinux-users] 0.7.1 DAHDI Asterisk crash
Physically? I'd have to drive 60 miles to answer that question. Obviously, since it's hardware, I've got no easy way to disable it in the config. I suppose I could ditch the VPMADT032 firmware file, though I don't see it in /lib/firmware any more. Is it no longer in userspace? Tom > -Original Message- > From: Darrick Hartman [mailto:dhart...@djhsolutions.com] > Sent: 07 April 2010 18:22 > To: Tom Chadwin; AstLinux Users Mailing List > Subject: Re: [Astlinux-users] 0.7.1 DAHDI Asterisk crash > > Just to narrow this down, what happens if you pull the echo > module off the card? > > On 04/07/2010 12:15 PM, Tom Chadwin wrote: > >>> 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. > >> > >> This is related to "/dev/dahdi/timer" in DAHDI. The > calling code in > >> asterisk.c is below. > >> > >> What is your variable DAHDIMODS set to? > > > > haltwhistlepbx ~ # cat /mnt/kd/rc.conf.d/user.conf |grep DAHDI > > DAHDIMODS="wctdm24xxp" > > > >> What is "cat /etc/rc.modules" ? > > > > haltwhistlepbx ~ # cat /etc/rc.modules # These modules get > modprobe'd > > when the system starts up. > > rtc > > #Comment out the modules you don't need, and change the > order to #move > > eth0 to eth1, etc. > > #Ethernet support > > #10/100 first, then Gigabit > > #3c59x > > #typhoon > > #tulip > > #eepro100 > > #natsemi > > via-rhine > > #forcedeth > > #8139cp > > #8139too > > #pcnet32 > > #acenic > > #e1000 > > #ns83820 > > #r8169 > > #tg3 > > #padlock > > geode-aes > > geode-rng > > geodewdt > > cryptodev > > cryptosoft > > > > I think this is an unmodified net5501 image. > > > >> Are you dong any modprobes in a rc.local or such? > > > > Nope. I do seem to have a /mnt/kd/rc.elocal, but it's empty. > > > >> For fun, try "modprobe dahdi_dummy" then "service asterisk > start" as > >> Michael suggested, and see if asterisk starts. > > > > haltwhistlepbx ~ # modprobe dahdi_dummy haltwhistlepbx ~ # asterisk > > -vvvc > > Asterisk 1.4.30, Copyright (C) 1999 - 2010 Digium, Inc. and others. > > Created by Mark Spencer Asterisk comes with > > ABSOLUTELY NO WARRANTY; type 'core show warranty' for details. > > This is free software, with components licensed under the > GNU General > > Public License version 2 and other licenses; you are welcome to > > redistribute it under certain conditions. Type 'core show > license' for > > details. > > > == > === > >== Parsing '/etc/asterisk/asterisk.conf': Found > >== Parsing '/etc/asterisk/extconfig.conf': Found > >== Parsing '/etc/asterisk/logger.conf': Found Asterisk > Event Logger > > Started /var/log/asterisk/event_log [Apr 7 18:13:08] ERROR[2375]: > > 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. > > haltwhistlepbx ~ # service asterisk start Starting Asterisk... > > > > WARNING WARNING WARNING > > > > YOU STILL HAVE NOT CHANGED YOUR ASTERISK MANAGER PASSWORD > ANYONE THAT > > KNOWS YOU ARE USING ASTLINUX CAN DESTROY YOUR SYSTEM. PLEASE CHANGE > > THIS IN /etc/asterisk/manager.conf IMMEDIATELY! > > > > WARNING WARNING WARNING > > > > haltwhistlepbx ~ # asterisk -rc > > Asterisk 1.4.30, Copyright (C) 1999 - 2010 Digium, Inc. and others. > > Created by Mark Spencer Asterisk comes with > > ABSOLUTELY NO WARRANTY; type 'core show warranty' for details. > > This is free software, with components licensed under the > GNU General > > Public License version 2 and other licenses; you are welcome to > > redistribute it under certain conditions. Type 'core show > license' for >
Re: [Astlinux-users] 0.7.1 DAHDI Asterisk crash
Just to narrow this down, what happens if you pull the echo module off
the card?
On 04/07/2010 12:15 PM, Tom Chadwin wrote:
>>> 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.
>>
>> This is related to "/dev/dahdi/timer" in DAHDI. The calling
>> code in asterisk.c is below.
>>
>> What is your variable DAHDIMODS set to?
>
> haltwhistlepbx ~ # cat /mnt/kd/rc.conf.d/user.conf |grep DAHDI
> DAHDIMODS="wctdm24xxp"
>
>> What is "cat /etc/rc.modules" ?
>
> haltwhistlepbx ~ # cat /etc/rc.modules
> # These modules get modprobe'd when the system starts up.
> rtc
> #Comment out the modules you don't need, and change the order to
> #move eth0 to eth1, etc.
> #Ethernet support
> #10/100 first, then Gigabit
> #3c59x
> #typhoon
> #tulip
> #eepro100
> #natsemi
> via-rhine
> #forcedeth
> #8139cp
> #8139too
> #pcnet32
> #acenic
> #e1000
> #ns83820
> #r8169
> #tg3
> #padlock
> geode-aes
> geode-rng
> geodewdt
> cryptodev
> cryptosoft
>
> I think this is an unmodified net5501 image.
>
>> Are you dong any modprobes in a rc.local or such?
>
> Nope. I do seem to have a /mnt/kd/rc.elocal, but it's empty.
>
>> For fun, try "modprobe dahdi_dummy" then "service asterisk
>> start" as Michael suggested, and see if asterisk starts.
>
> haltwhistlepbx ~ # modprobe dahdi_dummy
> haltwhistlepbx ~ # asterisk -vvvc
> Asterisk 1.4.30, Copyright (C) 1999 - 2010 Digium, Inc. and others.
> Created by Mark Spencer
> Asterisk comes with ABSOLUTELY NO WARRANTY; type 'core show warranty' for
> details.
> This is free software, with components licensed under the GNU General Public
> License version 2 and other licenses; you are welcome to redistribute it
> under
> certain conditions. Type 'core show license' for details.
> =
>== Parsing '/etc/asterisk/asterisk.conf': Found
>== Parsing '/etc/asterisk/extconfig.conf': Found
>== Parsing '/etc/asterisk/logger.conf': Found
> Asterisk Event Logger Started /var/log/asterisk/event_log
> [Apr 7 18:13:08] ERROR[2375]: 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.
> haltwhistlepbx ~ # service asterisk start
> Starting Asterisk...
>
> WARNING WARNING WARNING
>
> YOU STILL HAVE NOT CHANGED YOUR ASTERISK MANAGER PASSWORD
> ANYONE THAT KNOWS YOU ARE USING ASTLINUX CAN DESTROY YOUR
> SYSTEM. PLEASE CHANGE THIS IN /etc/asterisk/manager.conf
> IMMEDIATELY!
>
> WARNING WARNING WARNING
>
> haltwhistlepbx ~ # asterisk -rc
> Asterisk 1.4.30, Copyright (C) 1999 - 2010 Digium, Inc. and others.
> Created by Mark Spencer
> Asterisk comes with ABSOLUTELY NO WARRANTY; type 'core show warranty' for
> details.
> This is free software, with components licensed under the GNU General Public
> License version 2 and other licenses; you are welcome to redistribute it
> under
> certain conditions. Type 'core show license' for details.
> =
>== Parsing '/etc/asterisk/asterisk.conf': Found
>== Parsing '/etc/asterisk/extconfig.conf': Found
> Unable to connect to remote asterisk (does /var/run/asterisk/asterisk.ctl
> exist?)
>
> Seems the same to me.
>
> Tom
>
>
>
>
>> #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_T
Re: [Astlinux-users] 0.7.1 DAHDI Asterisk crash
> > 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.
>
> This is related to "/dev/dahdi/timer" in DAHDI. The calling
> code in asterisk.c is below.
>
> What is your variable DAHDIMODS set to?
haltwhistlepbx ~ # cat /mnt/kd/rc.conf.d/user.conf |grep DAHDI
DAHDIMODS="wctdm24xxp"
> What is "cat /etc/rc.modules" ?
haltwhistlepbx ~ # cat /etc/rc.modules
# These modules get modprobe'd when the system starts up.
rtc
#Comment out the modules you don't need, and change the order to
#move eth0 to eth1, etc.
#Ethernet support
#10/100 first, then Gigabit
#3c59x
#typhoon
#tulip
#eepro100
#natsemi
via-rhine
#forcedeth
#8139cp
#8139too
#pcnet32
#acenic
#e1000
#ns83820
#r8169
#tg3
#padlock
geode-aes
geode-rng
geodewdt
cryptodev
cryptosoft
I think this is an unmodified net5501 image.
> Are you dong any modprobes in a rc.local or such?
Nope. I do seem to have a /mnt/kd/rc.elocal, but it's empty.
> For fun, try "modprobe dahdi_dummy" then "service asterisk
> start" as Michael suggested, and see if asterisk starts.
haltwhistlepbx ~ # modprobe dahdi_dummy
haltwhistlepbx ~ # asterisk -vvvc
Asterisk 1.4.30, Copyright (C) 1999 - 2010 Digium, Inc. and others.
Created by Mark Spencer
Asterisk comes with ABSOLUTELY NO WARRANTY; type 'core show warranty' for
details.
This is free software, with components licensed under the GNU General Public
License version 2 and other licenses; you are welcome to redistribute it
under
certain conditions. Type 'core show license' for details.
=
== Parsing '/etc/asterisk/asterisk.conf': Found
== Parsing '/etc/asterisk/extconfig.conf': Found
== Parsing '/etc/asterisk/logger.conf': Found
Asterisk Event Logger Started /var/log/asterisk/event_log
[Apr 7 18:13:08] ERROR[2375]: 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.
haltwhistlepbx ~ # service asterisk start
Starting Asterisk...
WARNING WARNING WARNING
YOU STILL HAVE NOT CHANGED YOUR ASTERISK MANAGER PASSWORD
ANYONE THAT KNOWS YOU ARE USING ASTLINUX CAN DESTROY YOUR
SYSTEM. PLEASE CHANGE THIS IN /etc/asterisk/manager.conf
IMMEDIATELY!
WARNING WARNING WARNING
haltwhistlepbx ~ # asterisk -rc
Asterisk 1.4.30, Copyright (C) 1999 - 2010 Digium, Inc. and others.
Created by Mark Spencer
Asterisk comes with ABSOLUTELY NO WARRANTY; type 'core show warranty' for
details.
This is free software, with components licensed under the GNU General Public
License version 2 and other licenses; you are welcome to redistribute it
under
certain conditions. Type 'core show license' for details.
=
== Parsing '/etc/asterisk/asterisk.conf': Found
== Parsing '/etc/asterisk/extconfig.conf': Found
Unable to connect to remote asterisk (does /var/run/asterisk/asterisk.ctl
exist?)
Seems the same to me.
Tom
> #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
Re: [Astlinux-users] 0.7.1 DAHDI Asterisk crash
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
Astlinux-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/astlinux-users
Donations to support AstLinux are graciously accepted via PayPal to
pay...@krisk.org.
Re: [Astlinux-users] 0.7.1 DAHDI Asterisk crash
Happy to try a 2.2.1.1 image. I've added notes to: https://issues.asterisk.org/view.php?id=16814 Any opinion from anyone who, you know, has the faintest idea of what they're talking about, as to whether this could be the same issue? Tom > -Original Message- > From: Darrick Hartman [mailto:dhart...@djhsolutions.com] > Sent: 07 April 2010 16:45 > To: AstLinux Users Mailing List > Subject: Re: [Astlinux-users] 0.7.1 DAHDI Asterisk crash > > On 04/07/2010 10:39 AM, Darrick Hartman wrote: > > On 04/07/2010 09:50 AM, Tom Chadwin wrote: > > >> So it's evidently a DAHDI 2.2.1 issue. But what? > >> > >> Tom > > > > 2.2.1.1 may > > > > (...cause you to press send before finishing writing the email) > > Anyway, we can bump dahdi to 2.2.1.1 and build a test image > to see if you see the same behavior. I don't see anything in > the changelog for > 2.2.1.1 that would indicate that it would fix anything, but > it is possible. > > Here's the changelog: > > http://downloads.asterisk.org/pub/telephony/dahdi-linux/Change > Log-2.2.1.1 > > Darrick > -- > Darrick Hartman > DJH Solutions, LLC > http://www.djhsolutions.com > > -- > > 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 > Astlinux-users@lists.sourceforge.net > https://lists.sourceforge.net/lists/listinfo/astlinux-users > > Donations to support AstLinux are graciously accepted via > PayPal to pay...@krisk.org. > -- 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 Astlinux-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/astlinux-users Donations to support AstLinux are graciously accepted via PayPal to pay...@krisk.org.
Re: [Astlinux-users] 0.7.1 DAHDI Asterisk crash
On 04/07/2010 10:39 AM, Darrick Hartman wrote: > On 04/07/2010 09:50 AM, Tom Chadwin wrote: >> So it's evidently a DAHDI 2.2.1 issue. But what? >> >> Tom > > 2.2.1.1 may > (...cause you to press send before finishing writing the email) Anyway, we can bump dahdi to 2.2.1.1 and build a test image to see if you see the same behavior. I don't see anything in the changelog for 2.2.1.1 that would indicate that it would fix anything, but it is possible. Here's the changelog: http://downloads.asterisk.org/pub/telephony/dahdi-linux/ChangeLog-2.2.1.1 Darrick -- Darrick Hartman DJH Solutions, LLC http://www.djhsolutions.com -- 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 Astlinux-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/astlinux-users Donations to support AstLinux are graciously accepted via PayPal to pay...@krisk.org.
Re: [Astlinux-users] 0.7.1 DAHDI Asterisk crash
On 04/07/2010 09:50 AM, Tom Chadwin wrote: > Oh, and reverting to 0.7.0 with no changes to dahdi/system.conf or > chan_dahdi.conf brings the boxes back up. dmesg here gives: > > dahdi: Telephony Interface Registered on major 196 > dahdi: Version: 2.2.0.2 > Port 1: Installed -- AUTO FXO (FCC mode) > wctdm24xxp0: Missed interrupt. Increasing latency to 4 ms in order to > compensate. > wctdm24xxp0: Restarting board initialization after increasing latency. > wctdm24xxp0: Missed interrupt. Increasing latency to 5 ms in order to > compensate. > Port 1: Installed -- AUTO FXO (FCC mode) > wctdm24xxp0: Missed interrupt. Increasing latency to 6 ms in order to > compensate. > wctdm24xxp0: Restarting board initialization after increasing latency. > wctdm24xxp0: Missed interrupt. Increasing latency to 7 ms in order to > compensate. > Port 1: Installed -- AUTO FXO (FCC mode) > wctdm24xxp0: Missed interrupt. Increasing latency to 8 ms in order to > compensate. > wctdm24xxp0: Restarting board initialization after increasing latency. > wctdm24xxp0: Missed interrupt. Increasing latency to 9 ms in order to > compensate. > Port 1: Installed -- AUTO FXO (FCC mode) > wctdm24xxp0: Missed interrupt. Increasing latency to 10 ms in order to > compensate. > wctdm24xxp0: Restarting board initialization after increasing latency. > wctdm24xxp0: Missed interrupt. Increasing latency to 11 ms in order to > compensate. > Port 1: Installed -- AUTO FXO (FCC mode) > wctdm24xxp0: Missed interrupt. Increasing latency to 12 ms in order to > compensate. > wctdm24xxp0: Restarting board initialization after increasing latency. > wctdm24xxp0: Missed interrupt. Increasing latency to 13 ms in order to > compensate. > Port 1: Installed -- AUTO FXO (FCC mode) > wctdm24xxp0: Missed interrupt. Increasing latency to 14 ms in order to > compensate. > wctdm24xxp0: Restarting board initialization after increasing latency. > wctdm24xxp0: Missed interrupt. Increasing latency to 15 ms in order to > compensate. > Port 1: Installed -- AUTO FXO (FCC mode) > wctdm24xxp0: Missed interrupt. Increasing latency to 16 ms in order to > compensate. > wctdm24xxp0: Restarting board initialization after increasing latency. > wctdm24xxp0: Missed interrupt. Increasing latency to 17 ms in order to > compensate. > Port 1: Installed -- AUTO FXO (FCC mode) > wctdm24xxp0: Missed interrupt. Increasing latency to 18 ms in order to > compensate. > wctdm24xxp0: Restarting board initialization after increasing latency. > wctdm24xxp0: Missed interrupt. Increasing latency to 19 ms in order to > compensate. > Port 1: Installed -- AUTO FXO (FCC mode) > wctdm24xxp0: Missed interrupt. Increasing latency to 20 ms in order to > compensate. > wctdm24xxp0: Restarting board initialization after increasing latency. > wctdm24xxp0: Missed interrupt. Increasing latency to 21 ms in order to > compensate. > Port 1: Installed -- AUTO FXO (FCC mode) > wctdm24xxp0: Missed interrupt. Increasing latency to 22 ms in order to > compensate. > wctdm24xxp0: Restarting board initialization after increasing latency. > wctdm24xxp0: Missed interrupt. Increasing latency to 23 ms in order to > compensate. > Port 1: Installed -- AUTO FXO (FCC mode) > wctdm24xxp0: Missed interrupt. Increasing latency to 24 ms in order to > compensate. > wctdm24xxp0: Restarting board initialization after increasing latency. > wctdm24xxp0: Missed interrupt. Increasing latency to 25 ms in order to > compensate. > Port 1: Installed -- AUTO FXO (FCC mode) > Port 2: Not installed > Port 3: Not installed > Port 4: Not installed > VPM100: Not Present > Booting VPMADT032 > VPMADT032: Present and operational (Firmware version 117) > wctdm24xxp0: Missed interrupt. Increasing latency to 26 ms in order to > compensate. > Found a Wildcard TDM: Wildcard TDM410P (4 modules) > wctdm24xxp0: Missed interrupt. Increasing latency to 27 ms in order to > compensate. > dahdi: Registered tone zone 4 (United Kingdom) > wctdm24xxp0: Missed interrupt. Increasing latency to 28 ms in order to > compensate. > wctdm24xxp0: Missed interrupt. Increasing latency to 29 ms in order to > compensate. > wctdm24xxp0: Missed interrupt. Increasing latency to 30 ms in order to > compensate. > > So it's evidently a DAHDI 2.2.1 issue. But what? > > Tom 2.2.1.1 may DJH Solutions, LLC http://www.djhsolutions.com -- 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 Astlinux-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/astlinux-users Donations to support AstLinux are graciously accepted via PayPal to pay...@krisk.org.
Re: [Astlinux-users] 0.7.1 DAHDI Asterisk crash
Oh, and reverting to 0.7.0 with no changes to dahdi/system.conf or chan_dahdi.conf brings the boxes back up. dmesg here gives: dahdi: Telephony Interface Registered on major 196 dahdi: Version: 2.2.0.2 Port 1: Installed -- AUTO FXO (FCC mode) wctdm24xxp0: Missed interrupt. Increasing latency to 4 ms in order to compensate. wctdm24xxp0: Restarting board initialization after increasing latency. wctdm24xxp0: Missed interrupt. Increasing latency to 5 ms in order to compensate. Port 1: Installed -- AUTO FXO (FCC mode) wctdm24xxp0: Missed interrupt. Increasing latency to 6 ms in order to compensate. wctdm24xxp0: Restarting board initialization after increasing latency. wctdm24xxp0: Missed interrupt. Increasing latency to 7 ms in order to compensate. Port 1: Installed -- AUTO FXO (FCC mode) wctdm24xxp0: Missed interrupt. Increasing latency to 8 ms in order to compensate. wctdm24xxp0: Restarting board initialization after increasing latency. wctdm24xxp0: Missed interrupt. Increasing latency to 9 ms in order to compensate. Port 1: Installed -- AUTO FXO (FCC mode) wctdm24xxp0: Missed interrupt. Increasing latency to 10 ms in order to compensate. wctdm24xxp0: Restarting board initialization after increasing latency. wctdm24xxp0: Missed interrupt. Increasing latency to 11 ms in order to compensate. Port 1: Installed -- AUTO FXO (FCC mode) wctdm24xxp0: Missed interrupt. Increasing latency to 12 ms in order to compensate. wctdm24xxp0: Restarting board initialization after increasing latency. wctdm24xxp0: Missed interrupt. Increasing latency to 13 ms in order to compensate. Port 1: Installed -- AUTO FXO (FCC mode) wctdm24xxp0: Missed interrupt. Increasing latency to 14 ms in order to compensate. wctdm24xxp0: Restarting board initialization after increasing latency. wctdm24xxp0: Missed interrupt. Increasing latency to 15 ms in order to compensate. Port 1: Installed -- AUTO FXO (FCC mode) wctdm24xxp0: Missed interrupt. Increasing latency to 16 ms in order to compensate. wctdm24xxp0: Restarting board initialization after increasing latency. wctdm24xxp0: Missed interrupt. Increasing latency to 17 ms in order to compensate. Port 1: Installed -- AUTO FXO (FCC mode) wctdm24xxp0: Missed interrupt. Increasing latency to 18 ms in order to compensate. wctdm24xxp0: Restarting board initialization after increasing latency. wctdm24xxp0: Missed interrupt. Increasing latency to 19 ms in order to compensate. Port 1: Installed -- AUTO FXO (FCC mode) wctdm24xxp0: Missed interrupt. Increasing latency to 20 ms in order to compensate. wctdm24xxp0: Restarting board initialization after increasing latency. wctdm24xxp0: Missed interrupt. Increasing latency to 21 ms in order to compensate. Port 1: Installed -- AUTO FXO (FCC mode) wctdm24xxp0: Missed interrupt. Increasing latency to 22 ms in order to compensate. wctdm24xxp0: Restarting board initialization after increasing latency. wctdm24xxp0: Missed interrupt. Increasing latency to 23 ms in order to compensate. Port 1: Installed -- AUTO FXO (FCC mode) wctdm24xxp0: Missed interrupt. Increasing latency to 24 ms in order to compensate. wctdm24xxp0: Restarting board initialization after increasing latency. wctdm24xxp0: Missed interrupt. Increasing latency to 25 ms in order to compensate. Port 1: Installed -- AUTO FXO (FCC mode) Port 2: Not installed Port 3: Not installed Port 4: Not installed VPM100: Not Present Booting VPMADT032 VPMADT032: Present and operational (Firmware version 117) wctdm24xxp0: Missed interrupt. Increasing latency to 26 ms in order to compensate. Found a Wildcard TDM: Wildcard TDM410P (4 modules) wctdm24xxp0: Missed interrupt. Increasing latency to 27 ms in order to compensate. dahdi: Registered tone zone 4 (United Kingdom) wctdm24xxp0: Missed interrupt. Increasing latency to 28 ms in order to compensate. wctdm24xxp0: Missed interrupt. Increasing latency to 29 ms in order to compensate. wctdm24xxp0: Missed interrupt. Increasing latency to 30 ms in order to compensate. So it's evidently a DAHDI 2.2.1 issue. But what? Tom > -Original Message- > From: Tom Chadwin [mailto:nnpait.servi...@googlemail.com] > Sent: 07 April 2010 15:45 > To: 'AstLinux Users Mailing List' > Subject: RE: [Astlinux-users] 0.7.1 DAHDI Asterisk crash > > You are getting an explicit timing-related error, but I don't > seem to. For info, here are my DAHDI configs: > > ingrampbx ~ # cat /mnt/kd/dahdi/system.conf > fxsks=1-2 > loadzone=uk > defaultzone=uk > > ingrampbx ~ # cat /mnt/kd/asterisk/chan_dahdi.conf > > ; snipping a lot of content here... > > usecallerid=yes > hidecallerid=no > callwaiting=no > threewaycalling=no > transfer=yes > echocancel=yes > cidsignalling=v23 > cidstart=polarity > callerid=asreceived > restrictcid=no > sendcalleridafter=2 > > rxgain=2.0 > txgain=2.0 > > context=zap1 > signalling=fxs_ks > group=1 > channel => 1 > context=zap2 > channel => 2 > > Anyone see anything wrong with this? dmesg gives this: > > dahdi: Telephony Interface Registered on major 196 > da
Re: [Astlinux-users] 0.7.1 DAHDI Asterisk crash
You are getting an explicit timing-related error, but I don't seem to. For info, here are my DAHDI configs: ingrampbx ~ # cat /mnt/kd/dahdi/system.conf fxsks=1-2 loadzone=uk defaultzone=uk ingrampbx ~ # cat /mnt/kd/asterisk/chan_dahdi.conf ; snipping a lot of content here... usecallerid=yes hidecallerid=no callwaiting=no threewaycalling=no transfer=yes echocancel=yes cidsignalling=v23 cidstart=polarity callerid=asreceived restrictcid=no sendcalleridafter=2 rxgain=2.0 txgain=2.0 context=zap1 signalling=fxs_ks group=1 channel => 1 context=zap2 channel => 2 Anyone see anything wrong with this? dmesg gives this: dahdi: Telephony Interface Registered on major 196 dahdi: Version: 2.2.1 Port 1: Installed -- AUTO FXO (FCC mode) Port 2: Not installed Port 3: Not installed Port 4: Not installed VPM100: Not Present wctdm24xxp :00:0e.0: Booting VPMADT032 VPMADT032: Present and operational (Firmware version 120) Found a Wildcard TDM: Wildcard TDM410P (4 modules) dahdi: Registered tone zone 4 (United Kingdom) wctdm24xxp :00:0e.0: Missed interrupt. Increasing latency to 9 ms in order to compensate. wctdm24xxp :00:0e.0: Host failed to service card interrupt within 128 ms which is a hardunderun. wctdm24xxp :00:0e.0: Missed interrupt. Increasing latency to 15 ms in order to compensate. wctdm24xxp :00:0e.0: Missed interrupt. Increasing latency to 21 ms in order to compensate. This is similar to what I have seen in a working system, but I don't remember reference to "hardunderun". Any ideas? Thanks Tom > -Original Message- > From: Michael Keuter [mailto:li...@mksolutions.info] > Sent: 07 April 2010 14:28 > To: tom.chad...@nnpa.org.uk; AstLinux Users Mailing List > Subject: Re: [Astlinux-users] 0.7.1 DAHDI Asterisk crash > > >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 > > I don't know if it's related, but I tested the vzaphfc driver > (community driver for single port HFC ISDN cards) with DAHDI > 2.2.1 in trunk with Asterisk 1.6 .2.6 recently and got > similar messages: > > > Apr 7 15:17:31 net4801 local0.err asterisk[1497]: ERROR[1491]: > res_timing_dahdi.c:172 in dahdi_test_timer: 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 > suppor > Apr 7 15:17:31 net4801 local0.warn asterisk[1497]: WARNING[1491]: > chan_dahdi.c:17050 in process_dahdi: Ignoring any changes to > 'userbase' (on reload) at line 23. > Apr 7 15:17:31 net4801 local0.warn asterisk[1497]: WARNING[1491]: > chan_dahdi.c:17050 in process_dahdi: Ignoring any changes to > 'vmsecret' (on reload) at line 31. > Apr 7 15:17:31 net4801 local0.warn asterisk[1497]: WARNING[1491]: > chan_dahdi.c:17050 in process_dahdi: Ignoring any changes to 'hassip' > (on reload) at line 35. > Apr 7 15:17:31 net4801 local0.warn asterisk[1497]: WARNING[1491]: > chan_dahdi.c:17050 in process_dahdi: Ignoring any changes to 'hasiax' > (on reload) at line 39. > Apr 7 15:17:31 net4801 local0.warn asterisk[1497]: WARNING[1491]: > chan_dahdi.c:17050 in process_dahdi: Ignoring any changes to > 'hasmanager' (on reload) at line 47. > Apr 7 15:17:31 net4801 local0.err asterisk[1497]: ERROR[1491]: > codec_dahdi.c:620 in find_transcoders: Failed to open > /dev/dahdi/transcode: No such file or directory Apr 7 > 15:17:32 net4801 user.info kernel: vzaphfc: card 0: chan B1 > opened as ZTHFC1/0/1. > Apr 7 15:17:32 net4801 user.info kernel: vzaphfc: card 0: > chan B2 opened as ZTHFC1/0/2. > Apr 7 15:17:32 net4801 user.info kernel: vzaphfc: card 0: > chan D opened as ZTHFC1/0/3. > Apr 7 15:17:32 net4801 user.warn kernel: vzaphfc: card 0: > chan D: TX FIFO has become empty > --- > > But in my case it could also be a configuration issue, I > never used DAHDI or that driver before with Astlinux. > What I found out was, that "dahdi_transcode" is also needed > and "dahdi_dummy" must be loaded after all the drivers. > > Michael > > http://www.mksolutions.info > > ---
Re: [Astlinux-users] 0.7.1 DAHDI Asterisk crash
>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 I don't know if it's related, but I tested the vzaphfc driver (community driver for single port HFC ISDN cards) with DAHDI 2.2.1 in trunk with Asterisk 1.6 .2.6 recently and got similar messages: Apr 7 15:17:31 net4801 local0.err asterisk[1497]: ERROR[1491]: res_timing_dahdi.c:172 in dahdi_test_timer: 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 suppor Apr 7 15:17:31 net4801 local0.warn asterisk[1497]: WARNING[1491]: chan_dahdi.c:17050 in process_dahdi: Ignoring any changes to 'userbase' (on reload) at line 23. Apr 7 15:17:31 net4801 local0.warn asterisk[1497]: WARNING[1491]: chan_dahdi.c:17050 in process_dahdi: Ignoring any changes to 'vmsecret' (on reload) at line 31. Apr 7 15:17:31 net4801 local0.warn asterisk[1497]: WARNING[1491]: chan_dahdi.c:17050 in process_dahdi: Ignoring any changes to 'hassip' (on reload) at line 35. Apr 7 15:17:31 net4801 local0.warn asterisk[1497]: WARNING[1491]: chan_dahdi.c:17050 in process_dahdi: Ignoring any changes to 'hasiax' (on reload) at line 39. Apr 7 15:17:31 net4801 local0.warn asterisk[1497]: WARNING[1491]: chan_dahdi.c:17050 in process_dahdi: Ignoring any changes to 'hasmanager' (on reload) at line 47. Apr 7 15:17:31 net4801 local0.err asterisk[1497]: ERROR[1491]: codec_dahdi.c:620 in find_transcoders: Failed to open /dev/dahdi/transcode: No such file or directory Apr 7 15:17:32 net4801 user.info kernel: vzaphfc: card 0: chan B1 opened as ZTHFC1/0/1. Apr 7 15:17:32 net4801 user.info kernel: vzaphfc: card 0: chan B2 opened as ZTHFC1/0/2. Apr 7 15:17:32 net4801 user.info kernel: vzaphfc: card 0: chan D opened as ZTHFC1/0/3. Apr 7 15:17:32 net4801 user.warn kernel: vzaphfc: card 0: chan D: TX FIFO has become empty --- But in my case it could also be a configuration issue, I never used DAHDI or that driver before with Astlinux. What I found out was, that "dahdi_transcode" is also needed and "dahdi_dummy" must be loaded after all the drivers. Michael http://www.mksolutions.info -- 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 Astlinux-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/astlinux-users Donations to support AstLinux are graciously accepted via PayPal to pay...@krisk.org.
Re: [Astlinux-users] 0.7.1 DAHDI Asterisk crash
Hi Darrick They both have TDM410s (plus hw e/c), using wctdm24xxp. Is there anything I should check? Looking around this morning, I can find two possibilities: 1. Config is wrong - is there any way in which a DAHDI config which worked in 0.7.0 would crash Asterisk out in 0.7.1? Did 0.7.1 bump DAHDI? 2. I see references to timing sources relating to that CLI error. Does this point us toward a cause? Thanks Tom > -Original Message- > From: Darrick Hartman [mailto:dhart...@djhsolutions.com] > Sent: 07 April 2010 13:33 > To: tom.chad...@nnpa.org.uk; AstLinux Users Mailing List > Subject: Re: [Astlinux-users] 0.7.1 DAHDI Asterisk crash > > Tom, > > I have several 0.7.1 boxes running DAHDI (mostly with Rhino cards). > What cards are you using? > > Darrick > > On 04/07/2010 03: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 > -- > Darrick Hartman > DJH Solutions, LLC > http://www.djhsolutions.com > > -- > > 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 > Astlinux-users@lists.sourceforge.net > https://lists.sourceforge.net/lists/listinfo/astlinux-users > > Donations to support AstLinux are graciously accepted via > PayPal to pay...@krisk.org. > -- 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 Astlinux-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/astlinux-users Donations to support AstLinux are graciously accepted via PayPal to pay...@krisk.org.
Re: [Astlinux-users] 0.7.1 DAHDI Asterisk crash
Tom, I have several 0.7.1 boxes running DAHDI (mostly with Rhino cards). What cards are you using? Darrick On 04/07/2010 03: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 -- Darrick Hartman DJH Solutions, LLC http://www.djhsolutions.com -- 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 Astlinux-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/astlinux-users Donations to support AstLinux are graciously accepted via PayPal to pay...@krisk.org.
[Astlinux-users] 0.7.1 DAHDI Asterisk crash
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 -- 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 Astlinux-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/astlinux-users Donations to support AstLinux are graciously accepted via PayPal to pay...@krisk.org.
