Hi, I running into the following problem on my Asterisk setup:
--snip-- [Sep 3 01:40:59] NOTICE[9170] chan_dahdi.c: PRI got event: HDLC Abort (6) on Primary D-channel of span 3 [Sep 3 01:47:07] ERROR[9170] chan_dahdi.c: No more room in scheduler [Sep 3 01:47:07] ERROR[9170] chan_dahdi.c: Asked to delete sched id -1??? [Sep 3 01:47:07] ERROR[9170] chan_dahdi.c: No more room in scheduler [Sep 3 01:47:08] ERROR[9170] chan_dahdi.c: No more room in scheduler [Sep 3 01:47:08] ERROR[9170] chan_dahdi.c: Asked to delete sched id -1??? [Sep 3 01:47:08] ERROR[9170] chan_dahdi.c: No more room in scheduler [Sep 3 01:47:08] ERROR[9170] chan_dahdi.c: Asked to delete sched id -1??? [Sep 3 01:47:08] ERROR[9170] chan_dahdi.c: No more room in scheduler [Sep 3 01:47:08] ERROR[9170] chan_dahdi.c: Asked to delete sched id -1??? [Sep 3 01:47:08] ERROR[9170] chan_dahdi.c: No more room in scheduler [Sep 3 01:47:08] ERROR[9170] chan_dahdi.c: No more room in scheduler [Sep 3 01:47:08] ERROR[9170] chan_dahdi.c: Asked to delete sched id -1??? [Sep 3 01:47:08] ERROR[9170] chan_dahdi.c: No more room in scheduler [Sep 3 01:47:09] ERROR[9170] chan_dahdi.c: No more room in scheduler [Sep 3 01:47:09] ERROR[9170] chan_dahdi.c: Asked to delete sched id -1??? [Sep 3 01:47:09] ERROR[9170] chan_dahdi.c: No more room in scheduler [Sep 3 01:47:09] ERROR[9170] chan_dahdi.c: Asked to delete sched id -1??? --snip-- This happens once a week, at same about the same time (give or take a couple minutes). Always from "span 3" too. It just continually spits out those messages until I restart Asterisk. I've seen others post about this, but haven't seen a real answer. Someone said to run a 'dahdi_test -v' when this happens; I did and I get 99% every time. Someone else said this is usually caused by the telco. running some type of test on the line, and I would agree since it happens every week at pretty much the same time and same day. So, yes, lets say the telco. is sending some type of signal that freaks out Asterisk/DAHDI. I could call them and ask them to stop, but it would seem more appropriate for Asterisk/DAHDI to just "handle" this and not cry. A short term fix would be to just have a cron run around 2:00 a.m. weekly that will restart Asterisk. Should I open a bug for this? asterisk-1.6.1.1 dahdi-linux-2.2.0.2 dahdi-tools-2.2.0 Linux jekyll.mcc.edu 2.6.18-128.1.1.el5 #1 SMP Mon Jan 26 13:58:24 EST 2009 x86_64 x86_64 x86_64 GNU/Linux Red Hat Enterprise Linux Server release 5.3 (Tikanga) Dell PowerEdge 2950 (2) Wildcard TE220 (4th Gen) [r...@jekyll ~]# cat /etc/dahdi/system.conf # 20090801 MAS # Span 1 span=1,1,0,esf,b8zs bchan=1-23 dchan=24 echocanceller=mg2,1-23 # Span 2 span=2,2,0,esf,b8zs bchan=25-47 dchan=48 echocanceller=mg2,25-47 # Span 3 span=3,3,0,esf,b8zs bchan=49-71 dchan=72 echocanceller=mg2,49-71 # Span 4 span=4,4,0,esf,b8zs bchan=73-95 dchan=96 echocanceller=mg2,73-95 # Global loadzone = us defaultzone = us [r...@jekyll ~]# cat /etc/asterisk/chan_dahdi.conf [general] [channels] ; Span 1 group = 1 context = from_pstn switchtype = qsig signalling = pri_net channel => 1-23 context = default ; Span 2 group = 2 context = from_avaya switchtype = qsig signalling = pri_net channel => 25-47 context = default ; Span 3 group = 7 context = from_pstn switchtype = qsig signalling = pri_cpe channel => 49-71 context = default ; Span 4 group = 7 context = from_pstn switchtype = qsig signalling = pri_cpe channel => 73-95 context = default [r...@jekyll ~]# cat /etc/dahdi/modules # 20090801 MAS wct4xxp wctc4xxp Let me know if any more information is needed. Any help is greatly appreciated! Thanks, Marc _______________________________________________ -- Bandwidth and Colocation Provided by http://www.api-digital.com -- AstriCon 2009 - October 13 - 15 Phoenix, Arizona Register Now: http://www.astricon.net asterisk-users mailing list To UNSUBSCRIBE or update options visit: http://lists.digium.com/mailman/listinfo/asterisk-users
