thr3ads.net - asterisk users - [asterisk-users] asterisk crash on DAHDI error: No more room in scheduler [May 2009]

If this information is useful, please help other people find it:
Share via:

Hose

2009-May-20 14:04 UTC

[asterisk-users] asterisk crash on DAHDI error: No more room in scheduler

Hi,

I'm getting the following error from an asterisk 1.6.0.9 installation:

[May 20 06:07:18] ERROR[18517]: chan_dahdi.c:10515 dahdi_pri_error:
Asked to delete sched id -1???
[May 20 06:07:18] ERROR[18517]: chan_dahdi.c:10515 dahdi_pri_error: No
more room in scheduler

This repeats a few times, then asterisk crashes.  I can't seem to locate
any info on this error at all.  I'm using the latest versions of non-rc
dahdi-linux and -tools (2.1.0.4 and 2.1.0.2).

Nothing weird compiled in, and just a regular Digium TE110P for
hardware.  Asterisk stays up for days before this happens; didn't happen
with 1.4 and chan_zap.

Anyone run into the issue before?

hose

Hose

2009-May-20 20:10 UTC

head link

[asterisk-users] asterisk crash on DAHDI error: No more room in scheduler

What you say...Hose (hose+asterisk at bluemaggottowel.com):
> Hi,
> 
> I'm getting the following error from an asterisk 1.6.0.9 installation:
> 
> [May 20 06:07:18] ERROR[18517]: chan_dahdi.c:10515 dahdi_pri_error:
> Asked to delete sched id -1???
> [May 20 06:07:18] ERROR[18517]: chan_dahdi.c:10515 dahdi_pri_error: No
> more room in scheduler
> 
> This repeats a few times, then asterisk crashes.  I can't seem to
locate
> any info on this error at all.  I'm using the latest versions of non-rc
> dahdi-linux and -tools (2.1.0.4 and 2.1.0.2).
> 
> Nothing weird compiled in, and just a regular Digium TE110P for
> hardware.  Asterisk stays up for days before this happens; didn't
happen
> with 1.4 and chan_zap.
> 
> Anyone run into the issue before?
> 
Apparently it all comes after the following dahdi error:

[May 20 02:35:40] ERROR[18517] chan_dahdi.c: T200 counter expired,
nothing to send...

I'm at a loss...?

hose

Allan Oepping

2009-May-29 16:40 UTC

head link

[asterisk-users] asterisk crash on DAHDI error: No more room in scheduler

I'm not sure if this posting will go to the correct thread or not, as I 
am subscribing to make this post, and don't have a message to reply to. 
Hose, if this does not end up in the thread can you post in in there?

I am getting the same DAHDI error, under Asterisk 1.4.25, libpri-1.4.10 
using a TE420 (TE420P I believe). Only Asterisk does not crash but all 
the channels on the port/group are listed as not busy and no calls get 
received or placed over the span.
It also happened at a time of no use, just after a restart message 
*SHOULD* have appeared in the log for that span, though the span would 
have been nearly 100% busy for more than 8 hours the previous day. I did 
not get a dahdi_test, sorry.

lspci:
05:08.0 Communication controller: Digium, Inc. Unknown device 0420 (rev 02)

Here are the restarts 1 hour before the failure:
[May 29 00:45:22] VERBOSE[19121] logger.c:     -- B-channel 0/1 
successfully restarted on span 1
[May 29 00:45:22] VERBOSE[19121] logger.c:     -- B-channel 0/2 
successfully restarted on span 1
[May 29 00:45:23] VERBOSE[19121] logger.c:     -- B-channel 0/3 
successfully restarted on span 1
[May 29 00:45:23] VERBOSE[19121] logger.c:     -- B-channel 0/4 
successfully restarted on span 1
[May 29 00:45:23] VERBOSE[19121] logger.c:     -- B-channel 0/5 
successfully restarted on span 1
[May 29 00:45:23] VERBOSE[19121] logger.c:     -- B-channel 0/6 
successfully restarted on span 1
[May 29 00:45:23] VERBOSE[19121] logger.c:     -- B-channel 0/7 
successfully restarted on span 1
[May 29 00:45:23] VERBOSE[19121] logger.c:     -- B-channel 0/8 
successfully restarted on span 1
[May 29 00:45:23] VERBOSE[19121] logger.c:     -- B-channel 0/9 
successfully restarted on span 1
[May 29 00:45:23] VERBOSE[19121] logger.c:     -- B-channel 0/10 
successfully restarted on span 1
[May 29 00:45:23] VERBOSE[19121] logger.c:     -- B-channel 0/11 
successfully restarted on span 1
[May 29 00:45:23] VERBOSE[19121] logger.c:     -- B-channel 0/12 
successfully restarted on span 1
[May 29 00:45:23] VERBOSE[19121] logger.c:     -- B-channel 0/13 
successfully restarted on span 1
[May 29 00:45:23] VERBOSE[19121] logger.c:     -- B-channel 0/14 
successfully restarted on span 1
[May 29 00:45:23] VERBOSE[19121] logger.c:     -- B-channel 0/15 
successfully restarted on span 1
[May 29 00:45:23] VERBOSE[19121] logger.c:     -- B-channel 0/16 
successfully restarted on span 1
[May 29 00:45:23] VERBOSE[19121] logger.c:     -- B-channel 0/17 
successfully restarted on span 1
[May 29 00:45:23] VERBOSE[19121] logger.c:     -- B-channel 0/18 
successfully restarted on span 1
[May 29 00:45:23] VERBOSE[19121] logger.c:     -- B-channel 0/19 
successfully restarted on span 1
[May 29 00:45:23] VERBOSE[19121] logger.c:     -- B-channel 0/20 
successfully restarted on span 1
[May 29 00:45:23] VERBOSE[19121] logger.c:     -- B-channel 0/21 
successfully restarted on span 1
[May 29 00:45:23] VERBOSE[19121] logger.c:     -- B-channel 0/22 
successfully restarted on span 1
[May 29 00:45:24] VERBOSE[19121] logger.c:     -- B-channel 0/23 
successfully restarted on span 1
*SNIP*
[May 29 00:45:30] VERBOSE[19122] logger.c:     -- B-channel 0/1 
successfully restarted on span 2
[May 29 00:45:30] VERBOSE[19122] logger.c:     -- B-channel 0/2 
successfully restarted on span 2
[May 29 00:45:30] VERBOSE[19122] logger.c:     -- B-channel 0/3 
successfully restarted on span 2
[May 29 00:45:30] VERBOSE[19122] logger.c:     -- B-channel 0/4 
successfully restarted on span 2
[May 29 00:45:30] VERBOSE[19122] logger.c:     -- B-channel 0/5 
successfully restarted on span 2
[May 29 00:45:30] VERBOSE[19122] logger.c:     -- B-channel 0/6 
successfully restarted on span 2
[May 29 00:45:30] VERBOSE[19122] logger.c:     -- B-channel 0/7 
successfully restarted on span 2
[May 29 00:45:30] VERBOSE[19122] logger.c:     -- B-channel 0/8 
successfully restarted on span 2
[May 29 00:45:30] VERBOSE[19122] logger.c:     -- B-channel 0/9 
successfully restarted on span 2
[May 29 00:45:30] VERBOSE[19122] logger.c:     -- B-channel 0/10 
successfully restarted on span 2
[May 29 00:45:30] VERBOSE[19122] logger.c:     -- B-channel 0/11 
successfully restarted on span 2
[May 29 00:45:30] VERBOSE[19122] logger.c:     -- B-channel 0/12 
successfully restarted on span 2
[May 29 00:45:30] VERBOSE[19122] logger.c:     -- B-channel 0/13 
successfully restarted on span 2
[May 29 00:45:30] VERBOSE[19122] logger.c:     -- B-channel 0/14 
successfully restarted on span 2
[May 29 00:45:30] VERBOSE[19122] logger.c:     -- B-channel 0/15 
successfully restarted on span 2
[May 29 00:45:30] VERBOSE[19122] logger.c:     -- B-channel 0/16 
successfully restarted on span 2
[May 29 00:45:30] VERBOSE[19122] logger.c:     -- B-channel 0/17 
successfully restarted on span 2
[May 29 00:45:31] VERBOSE[19122] logger.c:     -- B-channel 0/18 
successfully restarted on span 2
[May 29 00:45:31] VERBOSE[19122] logger.c:     -- B-channel 0/19 
successfully restarted on span 2
[May 29 00:45:31] VERBOSE[19122] logger.c:     -- B-channel 0/20 
successfully restarted on span 2
[May 29 00:45:31] VERBOSE[19122] logger.c:     -- B-channel 0/21 
successfully restarted on span 2
[May 29 00:45:31] VERBOSE[19122] logger.c:     -- B-channel 0/22 
successfully restarted on span 2
[May 29 00:45:31] VERBOSE[19122] logger.c:     -- B-channel 0/23 
successfully restarted on span 2
*SNIP* Minutes before the error: span 2 restarts bus span 1 does not, 
but has been every hour previously, at least during off hours.
[May 29 01:45:34] VERBOSE[19122] logger.c:     -- B-channel 0/1 
successfully restarted on span 2
[May 29 01:45:34] VERBOSE[19122] logger.c:     -- B-channel 0/2 
successfully restarted on span 2
[May 29 01:45:35] VERBOSE[19122] logger.c:     -- B-channel 0/3 
successfully restarted on span 2
[May 29 01:45:35] VERBOSE[19122] logger.c:     -- B-channel 0/4 
successfully restarted on span 2
[May 29 01:45:35] VERBOSE[19122] logger.c:     -- B-channel 0/5 
successfully restarted on span 2
[May 29 01:45:35] VERBOSE[19122] logger.c:     -- B-channel 0/6 
successfully restarted on span 2
[May 29 01:45:35] VERBOSE[19122] logger.c:     -- B-channel 0/7 
successfully restarted on span 2
[May 29 01:45:35] VERBOSE[19122] logger.c:     -- B-channel 0/8 
successfully restarted on span 2
[May 29 01:45:35] VERBOSE[19122] logger.c:     -- B-channel 0/9 
successfully restarted on span 2
[May 29 01:45:35] VERBOSE[19122] logger.c:     -- B-channel 0/10 
successfully restarted on span 2
[May 29 01:45:35] VERBOSE[19122] logger.c:     -- B-channel 0/11 
successfully restarted on span 2
[May 29 01:45:35] VERBOSE[19122] logger.c:     -- B-channel 0/12 
successfully restarted on span 2
[May 29 01:45:35] VERBOSE[19122] logger.c:     -- B-channel 0/13 
successfully restarted on span 2
[May 29 01:45:35] VERBOSE[19122] logger.c:     -- B-channel 0/14 
successfully restarted on span 2
[May 29 01:45:35] VERBOSE[19122] logger.c:     -- B-channel 0/15 
successfully restarted on span 2
[May 29 01:45:35] VERBOSE[19122] logger.c:     -- B-channel 0/16 
successfully restarted on span 2
[May 29 01:45:35] VERBOSE[19122] logger.c:     -- B-channel 0/17 
successfully restarted on span 2
[May 29 01:45:35] VERBOSE[19122] logger.c:     -- B-channel 0/18 
successfully restarted on span 2
[May 29 01:45:35] VERBOSE[19122] logger.c:     -- B-channel 0/19 
successfully restarted on span 2
[May 29 01:45:35] VERBOSE[19122] logger.c:     -- B-channel 0/20 
successfully restarted on span 2
[May 29 01:45:35] VERBOSE[19122] logger.c:     -- B-channel 0/21 
successfully restarted on span 2
[May 29 01:45:35] VERBOSE[19122] logger.c:     -- B-channel 0/22 
successfully restarted on span 2
[May 29 01:45:36] VERBOSE[19122] logger.c:     -- B-channel 0/23 
successfully restarted on span 2
*SNIP*
[May 29 01:47:41] ERROR[19121] chan_dahdi.c: No more room in scheduler
[May 29 01:47:41] ERROR[19121] chan_dahdi.c: Asked to delete sched id -1???
[May 29 01:47:41] ERROR[19121] chan_dahdi.c: No more room in scheduler
[May 29 01:47:45] ERROR[19121] chan_dahdi.c: No more room in scheduler
[May 29 01:47:45] ERROR[19121] chan_dahdi.c: Asked to delete sched id -1???
[May 29 01:47:45] ERROR[19121] chan_dahdi.c: No more room in scheduler
[May 29 01:47:46] ERROR[19121] chan_dahdi.c: No more room in scheduler
[May 29 01:47:46] ERROR[19121] chan_dahdi.c: Asked to delete sched id -1???
[May 29 01:47:46] ERROR[19121] chan_dahdi.c: No more room in scheduler
[May 29 01:47:46] ERROR[19121] chan_dahdi.c: No more room in scheduler
[May 29 01:47:46] ERROR[19121] chan_dahdi.c: Asked to delete sched id -1???
[May 29 01:47:46] ERROR[19121] chan_dahdi.c: No more room in scheduler

The last messages are repeated over and over. Removing the T1 from the 
port and plugging it back in fixed all the problems(although it was 
plugged into another phone system to test it for 2 minutes).
Asterisk or DAHDI were not restarted.


Here is my chan_dahdi.conf:

; Span 1: TE4/0/1 "T4XXP (PCI) Card 0 Span 1" (MASTER) B8ZS/ESF RED
group=0,11
context=from-pstn
switchtype = national
signalling = pri_cpe
channel => 1-23
context = default
group = 63

; Span 2: TE4/0/2 "T4XXP (PCI) Card 0 Span 2"
group=0,12
context=from-pstn
switchtype = national
signalling = pri_cpe
channel => 25-47
context = default
group = 63

; Span 3: TE4/0/3 "T4XXP (PCI) Card 0 Span 3"
group=0,13
context=from-pstn
switchtype = national
signalling = pri_cpe
channel => 49-71
context = default
group = 63

; Span 4: TE4/0/4 "T4XXP (PCI) Card 0 Span 4"
group=0,14
context=from-pstn
switchtype = national
signalling = pri_cpe
channel => 73-95
context = default
group = 63

dahdi_scan (first 2 ports only):

[1]
active=yes
alarms=OK
description=T4XXP (PCI) Card 0 Span 1
name=TE4/0/1
manufacturer=Digium
devicetype=Wildcard TE420 (4th Gen)
location=Board ID Switch 0
basechan=1
totchans=24
irq=169
type=digital-T1
syncsrc=1
lbo=0 db (CSU)/0-133 feet (DSX-1)
coding_opts=B8ZS,AMI
framing_opts=ESF,D4
coding=B8ZS
framing=ESF
[2]
active=yes
alarms=OK
description=T4XXP (PCI) Card 0 Span 2
name=TE4/0/2
manufacturer=Digium
devicetype=Wildcard TE420 (4th Gen)
location=Board ID Switch 0
basechan=25
totchans=24
irq=169
type=digital-T1
syncsrc=1
lbo=0 db (CSU)/0-133 feet (DSX-1)
coding_opts=B8ZS,AMI
framing_opts=ESF,D4
coding=B8ZS
framing=ESF


using driver wct4xxp.

dahdh/system.conf:

# Autogenerated by /usr/sbin/dahdi_genconf on Fri May  1 17:51:13 2009 
-- do not hand edit
# Dahdi Configuration File
#
# This file is parsed by the Dahdi Configurator, dahdi_cfg
#
# Span 1: TE4/0/1 "T4XXP (PCI) Card 0 Span 1" (MASTER) B8ZS/ESF RED
span=1,1,0,esf,b8zs
# termtype: te
bchan=1-23
dchan=24
echocanceller=mg2,1-23

# Span 2: TE4/0/2 "T4XXP (PCI) Card 0 Span 2"
span=2,2,0,esf,b8zs
# termtype: te
bchan=25-47
dchan=48
echocanceller=mg2,25-47

# Span 3: TE4/0/3 "T4XXP (PCI) Card 0 Span 3"
span=3,3,0,esf,b8zs
# termtype: te
bchan=49-71
dchan=72
echocanceller=mg2,49-71

# Span 4: TE4/0/4 "T4XXP (PCI) Card 0 Span 4"
span=4,4,0,esf,b8zs
# termtype: te
bchan=73-95
dchan=96
echocanceller=mg2,73-95

# Global data

loadzone        = us
defaultzone     = us



Thanks.

Allan

Possibly Parallel Threads

Search for more apparently analagous threads

asterisk users - May 2009 - asterisk crash on DAHDI error: No more room in scheduler

[asterisk-users] asterisk crash on DAHDI error: No more room in scheduler

[asterisk-users] asterisk crash on DAHDI error: No more room in scheduler

[asterisk-users] asterisk crash on DAHDI error: No more room in scheduler

Possibly Parallel Threads