similar to: DEBUG[27654] channel.c: Avoiding deadlock for channel '0x114af2c0'

For some reason we are seeing "Avoiding deadlock for channel" in our Asterisk logs, the logs are getting filled up with an amazing speed around 12000 lines a second, and all of them are "Avoiding deadlock". What could be the potential reason for this to be happening? The Asterisk is used as auto dialler, therefore different channel types are involved SIP, DAHDI, Local's.

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

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)

Hello, I have previously open a topic on the mailing list about deadlocking on Asterisk 1.2.35. After upgrading to 1.4.29.1 we still experienced the same problem : Mar 5 12:05:56] DEBUG[8647] channel.c: Avoiding initial deadlock for channel '0xb7689840' [Mar 5 12:06:41] DEBUG[7130] channel.c: Avoiding deadlock for channel '0xb7c04788' [Mar 5 12:06:41] DEBUG[7130]

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

On one of my 3 * servers I get this after 2 or 3 IAX2 calls Apr 22 15:54:39 NOTICE[1150495040]: chan_iax2.c:1271 iax2_destroy: Avoiding IAX destroy deadlock And as if that wasn't enough I get a never ending stream of this error flying off the top of the screen. At which point I can no longer make any calls into or out of the box. Any commands issued at the CLI prompt are ignored so I have

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',

Hi all, Can tell me somebody what meen : channel.c: Avoided initial deadlock Our customer makes calls with our softphone (with IAX2). Sometimes the softphon freezes. The call is ACTIVE but the user cant hang it up. At this time in the log file (asterisk/messages) appear the next line: channel.c: Avoided initial deadlock..... we use: SVN-branch-1.2-r46176M with VoIP channel (ADSL) Can you help

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

Hi I have 3FXO trunks called ZAP-25,ZAP-26 and ZAP-28 and T1 Channnel bank I get this deadlock problem when 2 incoming call from FXO(Here ZAP-28 and then ZAP-26) wants to dial same channel (Here ZAP-1). In this senario ZAP-1 first answer ZAP-28 and thne ZAP-26 wants to call ZAP-1 but it time out and goto voicemail after that ZAP-1 try to reach ZAP-26 call by puting ZAP-28 on HOLD During

Hi guys, First of all, I know that this server must be upgraded asap, I'm just wondering if anyone of you has already faced this problem and , if so, would the upgrade solve my problems... CAPI version 0.6 Asterisk 1.2.5 AGI scripts are being used Main problems: -Dropped Calls - ps aux | grep asterisk shows that asterisk (that is started with safe_asterisk) is generating multiple

Hello! I use FastAGI very frequently [meaning 30 channels IVR is made in it] and sometimes I find, that there is a message like: Jul 29 09:38:55 VERBOSE[896] logger.c: == Auto fallthrough, channel 'Local/1@route-out-eeae,2' status is 'CHANUNAVAIL' Jul 29 09:38:55 VERBOSE[893] logger.c: > Channel Local/1@route-out-eeae,1 was never answered. Jul 29 09:38:55 VERBOSE[896]

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

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

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

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

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

I have a very serious problem with calls between PAP2-NA and a TDM2400 (8 FXO). Almost every call dropped after between 20 and 30 seconds with conversation. I disable the sound card, serial and other things on my server, but the problem still continues. I've changed the RPT Packet Size to .20 on PAP2-NA, but nothing. Here a piece of my log: [Jan 31 07:10:43] DEBUG[3131] channel.c: Hanging up

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:

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: