Channel.c: Avoided deadlock error

Asterisk Asterisk Support
1

Hello I am using asterisk 1.2.27 with vicidialnow 1.1 for out bound dialing.

from last few days my server load average suddenly shoot up and system become unresponsive. On diagnosing I found very frequent message of

Mar 25 10:34:30 WARNING[22869] channel.c: Avoided deadlock for '0x9683728', 9 retries!
Mar 25 10:34:30 WARNING[22869] channel.c: Avoided deadlock for '0x9639a98', 9 retries!
Mar 25 10:34:30 WARNING[22869] channel.c: Avoided deadlock for '0x98cc6d8', 9 retries!
Mar 25 10:34:30 WARNING[22869] channel.c: Avoided deadlock for '0x964de40', 9 retries!
Mar 25 10:34:30 WARNING[22869] channel.c: Avoided deadlock for '0x933e148', 9 retries!
Mar 25 10:34:30 WARNING[22869] channel.c: Avoided deadlock for '0x95245e0', 9 retries!
Mar 25 10:34:30 WARNING[22869] channel.c: Avoided deadlock for '0x95d5c98', 9 retries!
Mar 25 10:34:30 WARNING[22869] channel.c: Avoided deadlock for '0x9912378', 9 retries!
Mar 25 10:34:30 WARNING[22869] channel.c: Avoided deadlock for '0x990cee0', 9 retries!
Mar 25 10:34:30 WARNING[22869] channel.c: Avoided deadlock for '0x938d7d8', 9 retries!
Mar 25 10:34:30 WARNING[22869] channel.c: Avoided deadlock for '0x96f7d58', 9 retries!
Mar 25 10:34:30 WARNING[22869] channel.c: Avoided deadlock for '0xb2a2c9c0', 9 retries!
Mar 25 10:34:30 WARNING[22869] channel.c: Avoided deadlock for '0x9889db0', 9 retries!
Mar 25 10:34:30 WARNING[22869] channel.c: Avoided deadlock for '0x93e02e8', 9 retries!
Mar 25 10:34:30 WARNING[22869] channel.c: Avoided deadlock for '0x95c37b8', 9 retries!
Mar 25 10:34:30 WARNING[22869] channel.c: Avoided deadlock for '0x93f5128', 9 retries!
Mar 25 10:34:30 WARNING[22869] channel.c: Avoided deadlock for '0x94e4e98', 9 retries!
Mar 25 10:34:30 WARNING[22869] channel.c: Avoided deadlock for '0x94354c0', 9 retries!

What is that error ? and how can be removed

2

This is a warning, not an error, and it is only a problem if it never manages to get the lock.

What you need to do is to upgrade to a supported version, and if you still get the error, compile it with the DEBUG_THREADS option and use “core show locks”. to find out where the locking conflict is occurring.