Displaying 20 results from an estimated 30000 matches similar to: "How to avoid "Avoiding deadlock...""
2006 Apr 10
0
How to avoid "Avoiding initial deadlock...."
An Asterisk box at customer site shows these messages pretty regularly. This
causes one way voice, the called party cannot hear the calling party.
Apr 7 11:59:44 WARNING[18406] channel.c: Avoided initial deadlock for
'0x817b790', 10 retries!
Apr 7 14:47:46 WARNING[18406] channel.c: Avoided initial deadlock for
'0x81a4380', 10 retries!
Apr 7 14:58:53 WARNING[18406] channel.c:
2006 Feb 08
1
channel.c: Avoided deadlock for '0x91a8b20', 10 retries!
Dear users,
Couple of days ago I have updated my * to 1.2.4 with ZAP 1.2.3
Since the upgrade I am having these problems:
Feb 7 16:21:18 WARNING[387] channel.c: Avoided deadlock for '0x91a8b20', 10
retries!$
Feb 7 16:23:16 WARNING[16176] channel.c: Avoided deadlock for '0x91a8b20',
10 retries!$
Feb 7 16:23:28 WARNING[16176] channel.c: Avoided deadlock for '0x91a8b20',
2006 Mar 29
1
Avoiding initial deadlock on iax?
Hi,
My asterisk sometimes stop responding to iax calls.
In the log, I've found this:
Mar 29 13:35:45 DEBUG[8386] channel.c: Avoiding initial deadlock for
'IAX2/trunkjstpcn-3'
Mar 29 13:35:45 DEBUG[13002] chan_sip.c: update_call_counter(1409) -
decrement call limit counter
Mar 29 13:35:45 DEBUG[8386] channel.c: Avoiding initial deadlock for
'IAX2/trunkjstpcn-3'
Mar 29
2006 Nov 22
0
channel_find_locked: Avoided deadlock ... messages - What to do?
What are these?
Nov 22 09:35:23 WARNING[7127]: channel.c:787 channel_find_locked:
Avoided deadlock for '0xf6c06778', 10 retries!
Nov 22 09:35:24 WARNING[7127]: channel.c:787 channel_find_locked:
Avoided deadlock for '0xf6c06778', 10 retries!
Nov 22 09:35:24 WARNING[7127]: channel.c:787 channel_find_locked:
Avoided deadlock for '0xf6c06778', 10 retries!
Nov 22 09:35:25
2010 Nov 24
2
Avoided deadlock Error
My Asterisk is Asterisk 1.2.30.2 currently running on viciserver the problem
is :
Nov 24 06:45:01 WARNING[3335]: channel.c:780 channel_find_locked: Avoided
deadlock for '0x861f6d8', 9 retries!
Nov 24 06:45:01 WARNING[3335]: channel.c:780 channel_find_locked: Avoided
deadlock for '0x85a6420', 9 retries!
Nov 24 06:45:01 WARNING[3335]: channel.c:780 channel_find_locked: Avoided
2006 May 16
4
WARNING[4033]: Avoided initial deadlock for 'Zap/63-1', 10 retries! ... + Kernel Panic!
Hi!
We have an Asterisk Bussines Edition ABE-A.1-6 on a PowerEdge 2850 with 4Gb
RAM. It was working 24/7 without any for a month, but for not related causes I
rebooted it a week ago. Yesterday the machine suddenly stop working, with a
kernel panic. We was watching logs, and found in /var/log/asterisk just
before the machine hung the messages posted avobe(is the first time we see
it).
Anyone
2006 Mar 28
1
Redirect problem/bug/feature
I have a major problem with SIP redirects, or maybe just do not understand
how they are supposed to work. We are using Cisco 7940s and 7960s with SIP
version 6.3. Asterisk 1.2.5.
A call come in to extension 944 over the IAX trunk. Extension 944 has
forward all to extension 904 set on the phone. According to the dialplan.
extension 904 should ring for 90 seconds, then ring another extension, and
2010 Feb 25
1
Deadlock while using MGCP on Asterisk
Hello all,
I'm running Asterisk 1.2.35 with chan_mgcp activated.
The process host around 2,4K users.
Along the day I've got some debug reports like :
Feb 24 22:25:42 DEBUG[28546] channel.c: Avoiding deadlock for
'MGCP/aaln/1 at 028421223635-1'
Feb 24 22:29:04 DEBUG[28670] channel.c: Avoiding initial deadlock for
'MGCP/aaln/1 at 028421223635-1'
Then, at
2007 Aug 30
0
WARNING[22292]: channel.c:780 channel_find_locked: Avoided initial deadlock for '0x82f2fe0', 9 retries!
Hello!
I clear remarks in Makefile:
DEBUG_THREADS = -DDEBUG_THREADS -DDETECT_DEADLOCKS
But same things in CLI:
Aug 30 18:16:31 WARNING[22292]: channel.c:780 channel_find_locked:
Avoided initial deadlock for '0x82f2fe0', 9 retries!
-- Zap/32-1 is proceeding passing it to Zap/31-1
-- Zap/32-1 is ringing
-- Accepting call from '2177' to '7141278' on channel
2011 Jan 14
2
DEBUG[27654] channel.c: Avoiding deadlock for channel '0x114af2c0'
Hello list,
today I experienced the following for the first time :
[Jan 14 11:26:18] DEBUG[27654] channel.c: Avoiding deadlock for channel
'0x114af2c0'
[Jan 14 11:26:18] DEBUG[27654] channel.c: Avoiding deadlock for channel
'0x114af2c0'
[Jan 14 11:26:18] DEBUG[27654] channel.c: Avoiding deadlock for channel
'0x114af2c0'
[Jan 14 11:26:18] DEBUG[27654] channel.c:
2005 May 26
1
deadlock
All out of the blue I get these errors?
Any Ideas why
Please help
May 26 09:54:28 WARNING[3964]: channel.c:507 ast_channel_walk_locked:
Avoided initial deadlock for 'SIP/301-b9d0', 10 retries!
May 26 09:54:30 WARNING[3964]: channel.c:507 ast_channel_walk_locked:
Avoided initial deadlock for 'SIP/301-b9d0', 10 retries!
May 26 09:54:33 WARNING[3964]: channel.c:507
2007 Jan 10
1
VIA EPIA DeadLock Issues
Greetings,
I've been having a large number of deadlock issues lately on chan_sip occurring only on VIA EPIA ML6000 boards. I'm curious if anyone else is having similar issues.
My Config (have multiple systems all running the same hardware with the same problem)
VIA EPIA ML6000
1GB RAM
80GB HDD
Various Digium Cards (T1 and TDM cards)
Trixbox 1.2.2 (though running stock asterisk code)
2004 Dec 01
6
Avoided deadlock
Dec 1 12:08:43 WARNING[6189]: channel.c:495 ast_channel_walk_locked:
Avoided deadlock for 'SIP/2502-6303', 10 retries!
Dec 1 12:08:44 WARNING[6189]: channel.c:495 ast_channel_walk_locked:
Avoided deadlock for 'SIP/2502-6303', 10 retries!
Dec 1 12:08:44 WARNING[6189]: channel.c:495 ast_channel_walk_locked:
Avoided deadlock for 'SIP/2502-6303', 10 retries!
what does this
2008 Jan 09
1
Help! channel_find_deadlocked: Avoided initial deadlock for ...
Hope someone can help.
I have a situation where asterisk is sending a SIP CANCEL message before the Dial() timeout has hit. It doesn't always do it.
Normally, we send an INVITE to the ITSP. They respond with a 100 Trying, then a 180 Ringing, or 183 Session Progress. It seems to be at this point that Asterisk starts the dial timer. Normally, when no more replies have been received by the dial
2007 Jun 28
0
Avoided deadlock for '0x864e70', 10 retries!
Hi
iam using 1.2.X SVN
iam keep getting the below message
Jun 28 23:07:31 WARNING[2692]: channel.c:785 channel_find_locked: Avoided
deadlock for '0x864e70', 10 retries!
any help
ram
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://lists.digium.com/pipermail/asterisk-users/attachments/20070628/6b5382fc/attachment.htm
2007 Jan 27
1
Via EPIA channel_find_locked: Avoided initial deadlock
In asterisk 1.2 branch SVN 51363
zaptel svn 1980
libpri svn 393
addons svn 332
My equipment is a Via EPIA minit-itx CN10000 1.2ghz, 1gb ram and a
tdm400p (4fxo).
A call comes from zap, a SIP ulaw receives the call, talks for a while
and when SIP users tries to park the call, then dozens of...
WARNING[3853]: channel.c:781 channel_find_locked: Avoided initial
deadlock for '0x91bb840', 10
2007 May 29
2
channel_find_locked: Avoided deadlock
Hi
i have 20 people calling agents calling
when ever they calling i get this below error
May 30 00:46:57 WARNING[2840]: channel.c:785 channel_find_locked: Avoided
deadlock for '0x8b2f50', 10 retries!
and the voice go choppy, and voice breakages
iam using Latest SVN, any suggestion to come over this problem
ram
-------------- next part --------------
An HTML attachment was scrubbed...
2005 Jan 20
2
Chan_Capi initial deadlock
Hello,
I am using chan_capi 0.3.5 and Asterisk CVS-v1-0-12/29/04-15:32:48 on a SuSE
Linux 9.0 with Kernel 2.4.21-99-default
In the system is a AVM C4 with one port connected to PSTN at PTP BRI and
another one to an ISDN PBX with an PMP BRI.
The system is running fine, but I have regualary this error, and then
chan_capi is not working anymore.
Jan 18 15:29:46 WARNING[2919]: Avoided initial
2006 Jan 10
1
avoided deadlock/channel already in use
Hello!
After upgrading my production machine to 1.2.1(used to be 1.2.0) on friday
i experienced strange behaviour yesterday, i received
deadlock-avoided-messages and channels refusing to hangup on span1(used
for inbound calls), both messages in all cases paired:
Jan 9 17:40:01 WARNING[30003] chan_zap.c: Ring requested on channel 0/17
already in use on span 1. Hanging up owner.
Jan 9 17:40:01
2009 Sep 08
2
1.2 AGI Deadlock
I am running 1.2.34 (also tried on 1.2.32) and whenever I launch an AGI, I
get the "avoided deadlock" message below.
*CLI> == Spawn extension (CONTEXT3, 6080, 8) exited non-zero on
'SIP/3211-1-081c40a8'
-- Executing NoOp("SIP/3211-1-081c40a8", "") in new stack
-- Executing AGI("SIP/3211-1-081c40a8", "diallocal.agi") in new