<tt><font size=2>Are you using a VPM module? The dahdi changelog mentions
some recent work related to VPM modules and HDLC aborts.</font></tt>
<br>
<br><a href="https://issues.asterisk.org/view.php?id=15498"><tt><font size=2>https://issues.asterisk.org/view.php?id=15498</font></tt></a>
<br><a href="https://issues.asterisk.org/view.php?id=15529"><tt><font size=2>https://issues.asterisk.org/view.php?id=15529</font></tt></a>
<br>
<br>
<br><tt><font size=2>I just rebuilt a server this weekend for the same
problem on a single span card with a VPM. I usually have to restart asterisk
to fix it, but I just noticed an instance in the logs where it recovered
on its own a minute later:</font></tt>
<br>
<br><tt><font size=2>[2009-09-29 01:12:20] NOTICE[5290] chan_dahdi.c: PRI
got event: HDLC Abort (6) on Primary D-channel of span 1</font></tt>
<br><tt><font size=2>[2009-09-29 01:19:31] ERROR[5290] chan_dahdi.c: No
more room in scheduler</font></tt>
<br><tt><font size=2>[2009-09-29 01:19:31] ERROR[5290] chan_dahdi.c: Asked
to delete sched id -1???</font></tt>
<br><tt><font size=2>[2009-09-29 01:19:31] ERROR[5290] chan_dahdi.c: No
more room in scheduler</font></tt>
<br><tt><font size=2>--snip--</font></tt>
<br><tt><font size=2>[2009-09-29 01:20:25] ERROR[5290] chan_dahdi.c: No
more room in scheduler</font></tt>
<br><tt><font size=2>[2009-09-29 01:20:25] VERBOSE[5290] logger.c:
== Primary D-Channel on span 1 down</font></tt>
<br><tt><font size=2>[2009-09-29 01:20:25] WARNING[5290] chan_dahdi.c:
No D-channels available! Using Primary channel 24 as D-channel anyway!</font></tt>
<br><tt><font size=2>[2009-09-29 01:20:25] VERBOSE[5290] logger.c:
== Primary D-Channel on span 1 up</font></tt>
<br><tt><font size=2>[2009-09-29 01:20:25] ERROR[5290] chan_dahdi.c: !!
Got a UA, but i'm in state 7</font></tt>
<br><tt><font size=2>[2009-09-29 01:20:26] VERBOSE[5290] logger.c:
== Primary D-Channel on span 1 down</font></tt>
<br><tt><font size=2>[2009-09-29 01:20:26] WARNING[5290] chan_dahdi.c:
No D-channels available! Using Primary channel 24 as D-channel anyway!</font></tt>
<br><tt><font size=2>[2009-09-29 01:20:26] ERROR[5290] chan_dahdi.c: !!
Got S-frame while link down</font></tt>
<br><tt><font size=2>[2009-09-29 01:20:26] ERROR[5290] chan_dahdi.c: !!
Got S-frame while link down</font></tt>
<br><tt><font size=2>[2009-09-29 01:20:26] ERROR[5290] chan_dahdi.c: !!
Got S-frame while link down</font></tt>
<br><tt><font size=2>[2009-09-29 01:20:26] ERROR[5290] chan_dahdi.c: !!
Got S-frame while link down</font></tt>
<br><tt><font size=2>[2009-09-29 01:20:26] VERBOSE[5290] logger.c:
== Primary D-Channel on span 1 up</font></tt>
<br>
<br>
<br><tt><font size=2>I also spotted some similar log entries the day before,
but surprisingly without a crash afterward:</font></tt>
<br>
<br><tt><font size=2>[2009-09-28 01:21:59] NOTICE[5290] chan_dahdi.c: PRI
got event: HDLC Abort (6) on Primary D-channel of span 1</font></tt>
<br><tt><font size=2>[2009-09-28 01:22:01] ERROR[5290] chan_dahdi.c: ACK
received for '0' outside of window of '20' to '21', restarting</font></tt>
<br><tt><font size=2>[2009-09-28 01:22:01] VERBOSE[5290] logger.c:
== Primary D-Channel on span 1 down</font></tt>
<br><tt><font size=2>[2009-09-28 01:22:01] WARNING[5290] chan_dahdi.c:
No D-channels available! Using Primary channel 24 as D-channel anyway!</font></tt>
<br><tt><font size=2>[2009-09-28 01:22:01] VERBOSE[5290] logger.c:
== Primary D-Channel on span 1 up</font></tt>
<br><tt><font size=2>[2009-09-28 01:22:01] ERROR[5290] chan_dahdi.c: !!
Got a UA, but i'm in state 7</font></tt>
<br>
<br>
<br><tt><font size=2>I get the crash in asterisk 1.6.0.15 and 1.6.1.6 with
dahdi 2.2.0.2, asterisk 1.4.26.2 with zaptel, on Centos 4.8 and Centos
5.3. It always happens around the same time (probably the telco running
tests as you mentioned), and I always get 99% on dahdi_test.</font></tt>
<br>
<br><tt><font size=2>I'm scheduling a nightly restart for now, but I'm
also considering ditching the VPM for a while.</font></tt>
<br>
<br>
<br><tt><font size=2>Marc Smith wrote on 09/18/2009 01:33:11 PM:<br>
> <br>
> Hi,<br>
> <br>
> I running into the following problem on my Asterisk setup:<br>
> <br>
> --snip--<br>
> [Sep 3 01:40:59] NOTICE[9170] chan_dahdi.c: PRI got event: HDLC
Abort<br>
> (6) on Primary D-channel of span 3<br>
> [Sep 3 01:47:07] ERROR[9170] chan_dahdi.c: No more room in scheduler<br>
> [Sep 3 01:47:07] ERROR[9170] chan_dahdi.c: Asked to delete sched
id -1???<br>
> [Sep 3 01:47:07] ERROR[9170] chan_dahdi.c: No more room in scheduler<br>
> [Sep 3 01:47:08] ERROR[9170] chan_dahdi.c: No more room in scheduler<br>
> [Sep 3 01:47:08] ERROR[9170] chan_dahdi.c: Asked to delete sched
id -1???<br>
> [Sep 3 01:47:08] ERROR[9170] chan_dahdi.c: No more room in scheduler<br>
> [Sep 3 01:47:08] ERROR[9170] chan_dahdi.c: Asked to delete sched
id -1???<br>
> [Sep 3 01:47:08] ERROR[9170] chan_dahdi.c: No more room in scheduler<br>
> [Sep 3 01:47:08] ERROR[9170] chan_dahdi.c: Asked to delete sched
id -1???<br>
> [Sep 3 01:47:08] ERROR[9170] chan_dahdi.c: No more room in scheduler<br>
> [Sep 3 01:47:08] ERROR[9170] chan_dahdi.c: No more room in scheduler<br>
> [Sep 3 01:47:08] ERROR[9170] chan_dahdi.c: Asked to delete sched
id -1???<br>
> [Sep 3 01:47:08] ERROR[9170] chan_dahdi.c: No more room in scheduler<br>
> [Sep 3 01:47:09] ERROR[9170] chan_dahdi.c: No more room in scheduler<br>
> [Sep 3 01:47:09] ERROR[9170] chan_dahdi.c: Asked to delete sched
id -1???<br>
> [Sep 3 01:47:09] ERROR[9170] chan_dahdi.c: No more room in scheduler<br>
> [Sep 3 01:47:09] ERROR[9170] chan_dahdi.c: Asked to delete sched
id -1???<br>
> --snip--<br>
> <br>
> This happens once a week, at same about the same time (give or take
a<br>
> couple minutes). Always from "span 3" too.<br>
> <br>
> It just continually spits out those messages until I restart Asterisk.<br>
> I've seen others post about this, but haven't seen a real answer.<br>
> <br>
> Someone said to run a 'dahdi_test -v' when this happens; I did and
I<br>
> get 99% every time.<br>
> <br>
> Someone else said this is usually caused by the telco. running some<br>
> type of test on the line, and I would agree since it happens every<br>
> week at pretty much the same time and same day. So, yes, lets say
the<br>
> telco. is sending some type of signal that freaks out Asterisk/DAHDI.<br>
> I could call them and ask them to stop, but it would seem more<br>
> appropriate for Asterisk/DAHDI to just "handle" this and
not cry.<br>
> <br>
> A short term fix would be to just have a cron run around 2:00 a.m.<br>
> weekly that will restart Asterisk.<br>
> <br>
> Should I open a bug for this?<br>
> <br>
> asterisk-1.6.1.1<br>
> dahdi-linux-2.2.0.2<br>
> dahdi-tools-2.2.0<br>
> <br>
> Linux jekyll.mcc.edu 2.6.18-128.1.1.el5 #1 SMP Mon Jan 26 13:58:24
EST<br>
> 2009 x86_64 x86_64 x86_64 GNU/Linux<br>
> Red Hat Enterprise Linux Server release 5.3 (Tikanga)<br>
> <br>
> Dell PowerEdge 2950<br>
> (2) Wildcard TE220 (4th Gen)<br>
> <br>
> [root@jekyll ~]# cat /etc/dahdi/system.conf<br>
> # 20090801 MAS<br>
> # Span 1<br>
> span=1,1,0,esf,b8zs<br>
> bchan=1-23<br>
> dchan=24<br>
> echocanceller=mg2,1-23<br>
> # Span 2<br>
> span=2,2,0,esf,b8zs<br>
> bchan=25-47<br>
> dchan=48<br>
> echocanceller=mg2,25-47<br>
> # Span 3<br>
> span=3,3,0,esf,b8zs<br>
> bchan=49-71<br>
> dchan=72<br>
> echocanceller=mg2,49-71<br>
> # Span 4<br>
> span=4,4,0,esf,b8zs<br>
> bchan=73-95<br>
> dchan=96<br>
> echocanceller=mg2,73-95<br>
> # Global<br>
> loadzone = us<br>
> defaultzone = us<br>
> <br>
> [root@jekyll ~]# cat /etc/asterisk/chan_dahdi.conf<br>
> [general]<br>
> <br>
> [channels]<br>
> ; Span 1<br>
> group = 1<br>
> context = from_pstn<br>
> switchtype = qsig<br>
> signalling = pri_net<br>
> channel => 1-23<br>
> context = default<br>
> ; Span 2<br>
> group = 2<br>
> context = from_avaya<br>
> switchtype = qsig<br>
> signalling = pri_net<br>
> channel => 25-47<br>
> context = default<br>
> ; Span 3<br>
> group = 7<br>
> context = from_pstn<br>
> switchtype = qsig<br>
> signalling = pri_cpe<br>
> channel => 49-71<br>
> context = default<br>
> ; Span 4<br>
> group = 7<br>
> context = from_pstn<br>
> switchtype = qsig<br>
> signalling = pri_cpe<br>
> channel => 73-95<br>
> context = default<br>
> <br>
> [root@jekyll ~]# cat /etc/dahdi/modules<br>
> # 20090801 MAS<br>
> wct4xxp<br>
> wctc4xxp<br>
> <br>
> <br>
> Let me know if any more information is needed.<br>
> Any help is greatly appreciated!<br>
> <br>
> <br>
> Thanks,<br>
> <br>
> Marc<br>
> <br>
> _______________________________________________<br>
> -- Bandwidth and Colocation Provided by </font></tt><a href="http://www.api-digital.com/"><tt><font size=2>http://www.api-digital.com</font></tt></a><tt><font size=2>
--<br>
> <br>
> AstriCon 2009 - October 13 - 15 Phoenix, Arizona<br>
> Register Now: </font></tt><a href=http://www.astricon.net/><tt><font size=2>http://www.astricon.net</font></tt></a><tt><font size=2><br>
> <br>
> asterisk-users mailing list<br>
> To UNSUBSCRIBE or update options visit:<br>
> </font></tt><a href="http://lists.digium.com/mailman/listinfo/asterisk-users"><tt><font size=2>http://lists.digium.com/mailman/listinfo/asterisk-users</font></tt></a><tt><font size=2><br>
</font></tt>