[Home]

Summary:ASTERISK-16038: getting warning message every 4 seconds
Reporter:jmls (jmls)Labels:
Date Opened:2010-04-30 17:05:22Date Closed:2010-11-11 20:46:07.000-0600
Priority:TrivialRegression?No
Status:Closed/CompleteComponents:Channels/chan_dahdi
Versions:Frequency of
Occurrence
Related
Issues:
Environment:Attachments:
Description:I have a 4-span EuroISDN span, with

#1 connected to telecoms provider
#2 looped to #3
#3 looped to #2
#4 unplugged

Upgraded libpri and zaptel to latest versions

zaptel: URL: http://svn.digium.com/svn/zaptel/branches/1.4 Revision: 4696
libpri: URL: http://svn.digium.com/svn/libpri/branches/1.4 Revision: 1684

before this upgrade, I was getting _no_ warning messages, now I am getting a

"WARNING[2659]: chan_dahdi.c:2790 pri_find_dchan: No D-channels available!  Using Primary channel 109 as D-channel anyway!"

message every 4 seconds

If I remove the definition of the 4th span from zapata.conf, the message goes away

****** ADDITIONAL INFORMATION ******

we have 10 channels on span 1, spans 2&3 are looped, span 4 is disconnected

zapata.conf
context=isdnspan1
pridialplan=unknown
group=1,1
signalling=pri_cpe
switchtype=euroisdn
channel => 1-10

context=isdnspan2
pridialplan=unknown
group=2,2
signalling=pri_cpe
switchtype=euroisdn
channel => 32-46,48-62

context=isdnspan3
pridialplan=unknown
group=3,5
signalling=pri_net
switchtype=euroisdn
channel => 63-77,79-93

context=isdnspan4
pridialplan=unknown
group=4,4
signalling=pri_cpe
switchtype=euroisdn
channel => 94-108,110-124

[root@foxtrot zaptel]# ztcfg -vvvvvvvvvvvvvv

Zaptel Version: SVN-branch-1.4-r4692
Echo Canceller: MG2
Configuration
======================

SPAN 1: CCS/HDB3 Build-out: 0 db (CSU)/0-133 feet (DSX-1)
SPAN 2: CCS/HDB3 Build-out: 0 db (CSU)/0-133 feet (DSX-1)
SPAN 3: CCS/HDB3 Build-out: 0 db (CSU)/0-133 feet (DSX-1)
SPAN 4: CCS/HDB3 Build-out: 0 db (CSU)/0-133 feet (DSX-1)

Channel map:

Channel 01: Clear channel (Default) (Slaves: 01)
...
Channel 09: Clear channel (Default) (Slaves: 09)
Channel 10: Clear channel (Default) (Slaves: 10)
Channel 16: D-channel (Default) (Slaves: 16)

Channel 32: Clear channel (Default) (Slaves: 32)
...
Channel 46: Clear channel (Default) (Slaves: 46)
Channel 47: D-channel (Default) (Slaves: 47)
Channel 48: Clear channel (Default) (Slaves: 48)
...
Channel 77: Clear channel (Default) (Slaves: 77)
Channel 78: D-channel (Default) (Slaves: 78)
Channel 79: Clear channel (Default) (Slaves: 79)
...
Channel 108: Clear channel (Default) (Slaves: 108)
Channel 109: D-channel (Default) (Slaves: 109)
Channel 110: Clear channel (Default) (Slaves: 110)
...
Channel 124: Clear channel (Default) (Slaves: 124)

104 channels to configure.

[root@foxtrot zaptel]#

get the following in the console:

[Apr 30 22:58:49] WARNING[2659]: chan_dahdi.c:2790 pri_find_dchan: No D-channels available!  Using Primary channel 109 as D-channel anyway!
[Apr 30 22:58:53] WARNING[2659]: chan_dahdi.c:2790 pri_find_dchan: No D-channels available!  Using Primary channel 109 as D-channel anyway!
[Apr 30 22:58:57] WARNING[2659]: chan_dahdi.c:2790 pri_find_dchan: No D-channels available!  Using Primary channel 109 as D-channel anyway!
[Apr 30 22:59:01] WARNING[2659]: chan_dahdi.c:2790 pri_find_dchan: No D-channels available!  Using Primary channel 109 as D-channel anyway!
[Apr 30 22:59:05] WARNING[2659]: chan_dahdi.c:2790 pri_find_dchan: No D-channels available!  Using Primary channel 109 as D-channel anyway!
[Apr 30 22:59:09] WARNING[2659]: chan_dahdi.c:2790 pri_find_dchan: No D-channels available!  Using Primary channel 109 as D-channel anyway!

...
...
...
Comments:By: Paul Belanger (pabelanger) 2010-05-03 09:20:06

I'm not sure what the issue is, you have stated you start Asterisk with the 4th span configured, but no cable. Why?  If you are not using the span, just disable it.
By: Leif Madsen (lmadsen) 2010-05-07 10:18:36

We had a conversation on IRC about this in that he needed to disconnect the span sometimes for some forgotten reason that made sense. I think being warned every 4 seconds is a bit excessive regardless.
By: Jared Smith (jsmith) 2010-05-07 16:24:45

I tend to agree with lmadsen here.  It's *very* common on development boxes (and even on some production boxes) to have spans configured and ready for traffic, without actually having anything plugged into them.

Getting a notice like this every four seconds is just plain overkill.

I think it should alert you on startup, and any time the alarm goes into or comes out of an different alarm state.
By: Paul Belanger (pabelanger) 2010-05-08 13:35:14

It should be noted, this code has changed in trunk.  Could you confirm it is still a problem?  If not, one solutions would be to back-port changes.
By: Leif Madsen (lmadsen) 2010-05-11 10:35:24

Just noticed this is against Zaptel -- is this an issue with DAHDI?
By: Leif Madsen (lmadsen) 2010-05-25 15:06:57

I'm suspending this issue for now. If this is an issue with DAHDI then please reopen this issue. Thanks!
By: Tzafrir Cohen (tzafrir) 2010-06-22 06:32:24

Confirmed in recent trunk.

I recall having this behaviour in old 1.4 (and in bristuff), and vaguely recall it fixed at around 1.6.0. It is plain annoying.
By: andrea lanza (lanzaandrea) 2010-07-02 03:21:40

Ok, I am here again...
I opened issue 17481 as a duplicate of this.
Anyway I was told the problem was my version, 1.6.1.20,
which reached end of life status.

So I migrated all my asterisk servers to the new release 1.6.2.9
The problem is still there, using chan_dahdi and getting error every 4 seconds.

I re-patched my chan_dahdi.c commenting out lines 4160-4161

This is really annoyng.... I would suggest to remove this warnig or to provide a configuration parameter in order to suppress this warning
By: David Brillert (aragon) 2010-07-28 09:35:48

Same problem here.
I have many installed servers with 4 span PRI cards where not all spans are connected to carrier.  Upgrading these boxes starts spewing the warning.
Wasn't a problem in 1.4.32 but is a problem since 1.4.34
Now I have to disable my ports/configs on any system which is upgraded.  Sounds like a regression to me...

I agree with jsmith's comments
"I tend to agree with lmadsen here. It's *very* common on development boxes (and even on some production boxes) to have spans configured and ready for traffic, without actually having anything plugged into them.

Getting a notice like this every four seconds is just plain overkill.

I think it should alert you on startup, and any time the alarm goes into or comes out of an different alarm state."
By: Joel Vandal (jvandal) 2010-07-28 09:47:32

Also have this issue, so for now I changed the loglevel from WARNING to DEBUG.
By: ibercom (ibercom) 2010-08-15 13:56:45

Also I have this issue.

I have 3 installed servers with 4 span PRI cards each one where one server is the 'standby server' and not all spans are connected. Before, the config was the same in servers and now I have to disable my ports/configs. Sounds like a regression...

I agree with jsmith's and aragon's comments.

Getting a notice like this every four seconds is just plain overkill. The log gets full.
By: Anthony H (ahave) 2010-08-27 10:50:34

I have the same issue with B410P card.
I downgrade the libpri version to 1.4.9.

These messages don't appear since I installed libpri 1.4.9
By: ph (ph) 2010-09-03 04:05:10

Same thing for me with asterisk 1.6.2.11 and libpri 1.4.11.
Sounds like a regression in libpri ...
By: Andrew Thomas (raffles) 2010-09-13 04:34:54

Same annoying issue here!  I have a four port BRI card that is used for development.  Can't do anything with these constant messages filling up my console:

[Sep 13 10:29:13] WARNING[5350]: chan_dahdi.c:4160 pri_find_dchan: No D-channels available!  Using Primary channel 3 as D-channel anyway!
[Sep 13 10:29:13] WARNING[5351]: chan_dahdi.c:4160 pri_find_dchan: No D-channels available!  Using Primary channel 6 as D-channel anyway!
[Sep 13 10:29:13] WARNING[5353]: chan_dahdi.c:4160 pri_find_dchan: No D-channels available!  Using Primary channel 12 as D-channel anyway!
[Sep 13 10:29:13] WARNING[5352]: chan_dahdi.c:4160 pri_find_dchan: No D-channels available!  Using Primary channel 9 as D-channel anyway!


Asterisk: 1.6.2.11
Libpri: 1.4.11.4
Dahdi (complete): 2.4.0 + 2.4.0

Digium 4-port BRI card: B410P
Dahdi driver: wcb4xxp

I'll regress Libpri - and see if that cures it...

EDIT : Libpri 1.4.12-beta2 still has this problem btw.

EDIT: EDIT: Problem NOT there in Libpri 1.4.10.1


By: Anthony H (ahave) 2010-09-14 07:47:52

I think that is a similar issue than :
https://issues.asterisk.org/view.php?id=14031

With BRI card in ptmp TE mode, telco (in europe for example) use power saving on D-channel.

This issue appear when the telco try to put the d-channel in idle mode.
My question is: How is it possible to use power saving with dahdi and/or libpri?
By: Andrew Thomas (raffles) 2010-09-15 13:27:55

JFYI - the 'power saving' D-channel isn't the problem with my set-up.  This has been proved with a Trend tester as well as a genuine ISDN2e

Something has changed in Libpri.
By: Anthony H (ahave) 2010-09-15 13:35:43

Raffles: I'm ok with you, something has changed in Libpri.
Raffles, where do you live?
In your configuration, your D-channels is always UP?
By: Andrew Thomas (raffles) 2010-09-15 13:55:22

I'm in the UK.  I know that some UK telco's do, indeed, drop layer 1 in to power save - but not on my test rig.  I have it connected to a genuine ISDN2e, a S0 bus off another switch (Siemens Hi-path that doesn't drop L1) and a Trend tester (that drops nothing).

So, in my configuration - my layer 1 is always on.  

Just to repeat - libpri v1.4.10.1 and 1.4.10.2 don't seem to have this problem - it only appeared from 1.4.11 onwards.

I only wish I knew enough about C to help out with the programming...
By: Anthony H (ahave) 2010-09-15 14:07:29

In my test, my telco shutdown D-channel... With Dahdi and libpri < 1.4.11, my D-channel is always UP.
With libpri > 1.4.10.2 I have these "strange" logs

Currently, I analyse libpri and dahdi in order to try to use power saving with my telco...
By: Leif Madsen (lmadsen) 2010-10-04 10:07:37

Yes, the issue does seem to be confirmed to exist in versions greater than 1.4.10.2. What we need is someone to look at the code and submit a patch. It has been prioritized by Digium so will be looked at as time and resources permit, but if someone from the community would like this fixed sooner, then someone will need to spend the time doing some coding. Thanks!
By: Digium Subversion (svnbot) 2010-11-11 20:31:27.000-0600

Repository: libpri
Revision: 2113

U   branches/1.4/pri_internal.h
U   branches/1.4/pri_q921.h
U   branches/1.4/q921.c

------------------------------------------------------------------------
r2113 | rmudgett | 2010-11-11 20:31:26 -0600 (Thu, 11 Nov 2010) | 16 lines

Asterisk is getting a "No D-channels available!" warning message every 4 seconds.

For PTP links, libpri generated the PRI_EVENT_DCHAN_DOWN event every time
it failed to bring layer 2 up because the physical layer is down.

For PTP links, made generate the PRI_EVENT_DCHAN_UP/PRI_EVENT_DCHAN_DOWN
only when it enters/exits the Q.921 superstate consisting of states
7(Q921_MULTI_FRAME_ESTABLISHED) and 8(Q921_TIMER_RECOVERY).

Also changed the PTP link restart delay to be link specific instead of D
channel specific because the GR-303 PTP switch types have more than one
Q.921 link.

(closes issue ASTERISK-16038)
Reported by: jmls

------------------------------------------------------------------------

http://svn.digium.com/view/libpri?view=rev&revision=2113
By: Digium Subversion (svnbot) 2010-11-11 20:41:15.000-0600

Repository: asterisk
Revision: 294821

U   branches/1.4/channels/chan_dahdi.c

------------------------------------------------------------------------
r294821 | rmudgett | 2010-11-11 20:41:14 -0600 (Thu, 11 Nov 2010) | 11 lines

Asterisk is getting a "No D-channels available!" warning message every 4 seconds.

Asterisk is just whining too much with this message: "No D-channels
available!  Using Primary channel XXX as D-channel anyway!".

Filtered the message so it only comes out once if there is no D channel
available without an intervening D channel available period.

(closes issue ASTERISK-16038)
Reported by: jmls

------------------------------------------------------------------------

http://svn.digium.com/view/asterisk?view=rev&revision=294821
By: Digium Subversion (svnbot) 2010-11-11 20:44:13.000-0600

Repository: asterisk
Revision: 294822

_U  branches/1.6.2/
U   branches/1.6.2/channels/chan_dahdi.c

------------------------------------------------------------------------
r294822 | rmudgett | 2010-11-11 20:44:13 -0600 (Thu, 11 Nov 2010) | 18 lines

Merged revisions 294821 via svnmerge from
https://origsvn.digium.com/svn/asterisk/branches/1.4

........
 r294821 | rmudgett | 2010-11-11 20:41:13 -0600 (Thu, 11 Nov 2010) | 11 lines
 
 Asterisk is getting a "No D-channels available!" warning message every 4 seconds.
 
 Asterisk is just whining too much with this message: "No D-channels
 available!  Using Primary channel XXX as D-channel anyway!".
 
 Filtered the message so it only comes out once if there is no D channel
 available without an intervening D channel available period.
 
 (closes issue ASTERISK-16038)
 Reported by: jmls
........

------------------------------------------------------------------------

http://svn.digium.com/view/asterisk?view=rev&revision=294822
By: Digium Subversion (svnbot) 2010-11-11 20:45:24.000-0600

Repository: asterisk
Revision: 294823

_U  branches/1.8/
U   branches/1.8/channels/sig_pri.c
U   branches/1.8/channels/sig_pri.h

------------------------------------------------------------------------
r294823 | rmudgett | 2010-11-11 20:45:23 -0600 (Thu, 11 Nov 2010) | 25 lines

Merged revisions 294822 via svnmerge from
https://origsvn.digium.com/svn/asterisk/branches/1.6.2

................
 r294822 | rmudgett | 2010-11-11 20:44:12 -0600 (Thu, 11 Nov 2010) | 18 lines
 
 Merged revisions 294821 via svnmerge from
 https://origsvn.digium.com/svn/asterisk/branches/1.4
 
 ........
   r294821 | rmudgett | 2010-11-11 20:41:13 -0600 (Thu, 11 Nov 2010) | 11 lines
   
   Asterisk is getting a "No D-channels available!" warning message every 4 seconds.
   
   Asterisk is just whining too much with this message: "No D-channels
   available!  Using Primary channel XXX as D-channel anyway!".
   
   Filtered the message so it only comes out once if there is no D channel
   available without an intervening D channel available period.
   
   (closes issue ASTERISK-16038)
   Reported by: jmls
 ........
................

------------------------------------------------------------------------

http://svn.digium.com/view/asterisk?view=rev&revision=294823
By: Digium Subversion (svnbot) 2010-11-11 20:46:04.000-0600

Repository: asterisk
Revision: 294824

_U  trunk/
U   trunk/channels/sig_pri.c
U   trunk/channels/sig_pri.h

------------------------------------------------------------------------
r294824 | rmudgett | 2010-11-11 20:46:03 -0600 (Thu, 11 Nov 2010) | 32 lines

Merged revisions 294823 via svnmerge from
https://origsvn.digium.com/svn/asterisk/branches/1.8

................
 r294823 | rmudgett | 2010-11-11 20:45:22 -0600 (Thu, 11 Nov 2010) | 25 lines
 
 Merged revisions 294822 via svnmerge from
 https://origsvn.digium.com/svn/asterisk/branches/1.6.2
 
 ................
   r294822 | rmudgett | 2010-11-11 20:44:12 -0600 (Thu, 11 Nov 2010) | 18 lines
   
   Merged revisions 294821 via svnmerge from
   https://origsvn.digium.com/svn/asterisk/branches/1.4
   
   ........
     r294821 | rmudgett | 2010-11-11 20:41:13 -0600 (Thu, 11 Nov 2010) | 11 lines
     
     Asterisk is getting a "No D-channels available!" warning message every 4 seconds.
     
     Asterisk is just whining too much with this message: "No D-channels
     available!  Using Primary channel XXX as D-channel anyway!".
     
     Filtered the message so it only comes out once if there is no D channel
     available without an intervening D channel available period.
     
     (closes issue ASTERISK-16038)
     Reported by: jmls
   ........
 ................
................

------------------------------------------------------------------------

http://svn.digium.com/view/asterisk?view=rev&revision=294824