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. [Nov 15 14:20:01] DEBUG[21740] channel.c: Avoiding deadlock for channel '0x9f17c88' [Nov 15 14:20:01] DEBUG[21740] channel.c: Avoiding deadlock for channel '0x9f17c88' [Nov 15 14:20:01] DEBUG[21740] channel.c: Avoiding deadlock for channel '0x9f17c88' [Nov 15 14:20:01] DEBUG[21740] channel.c: Avoiding deadlock for channel '0x9f17c88' [Nov 15 14:20:01] DEBUG[21740] channel.c: Avoiding deadlock for channel '0x9f17c88' [Nov 15 14:20:01] DEBUG[21740] channel.c: Avoiding deadlock for channel '0x9f17c88' [Nov 15 14:20:01] DEBUG[21740] channel.c: Avoiding deadlock for channel '0x9f17c88' [Nov 15 14:20:01] DEBUG[21740] channel.c: Avoiding deadlock for channel '0x9f17c88' [Nov 15 14:20:01] DEBUG[21740] channel.c: Avoiding deadlock for channel '0x9f17c88' [Nov 15 14:20:01] DEBUG[21740] channel.c: Avoiding deadlock for channel '0x9f17c88' [Nov 15 14:20:01] DEBUG[21740] channel.c: Avoiding deadlock for channel '0x9f17c88' [Nov 15 14:20:01] DEBUG[21740] channel.c: Avoiding deadlock for channel '0x9f17c88' [Nov 15 14:20:01] DEBUG[21740] channel.c: Avoiding deadlock for channel '0x9f17c88' Asterisk: 1.4.33.1 DAHDI: dahdi-2.3.0.1-3 Regards, Vilius. -------------- next part -------------- An HTML attachment was scrubbed... URL: http://lists.digium.com/pipermail/asterisk-users/attachments/20101116/0414b322/attachment.htm
On Tuesday 16 November 2010 08:08:45 Vilius Adamkavicius wrote:> 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. > > [Nov 15 14:20:01] DEBUG[21740] channel.c: Avoiding deadlock for channel > '0x9f17c88'You can safely ignore these messages, if you are not trying to fix a broader problem. Generally speaking, any messages that are at a DEBUG level are considered to be okay to ignore, unless you're working on tracking down a specific problem, in which case they may be helpful in determining a problem; however, they do not, in themselves, indicate any problem. -- Tilghman Lesher Digium, Inc. | Senior Software Developer twitter: Corydon76 | IRC: Corydon76-dig (Freenode) Check us out at: www.digium.com & www.asterisk.org
On Tue, 16 Nov 2010 14:08:45 +0000 Vilius Adamkavicius <vilius.adamkavicius at invade.net> wrote:> 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. > > [Nov 15 14:20:01] DEBUG[21740] channel.c: Avoiding deadlock for > channel '0x9f17c88'Turn off debugging. On the asterisk CLI, run this command: core set debug 0 Also, check the command line in your init script, or however you run asterisk, and if there is a -d option, remove it. Otherwise, debugging will come back on next time you restart asterisk.