asterisk users - Apr 2004 - Avoiding IAX destroy deadlock

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
to do a service asterisk restart now to get it back into service again.

Ideas?

> 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 to do a service asterisk restart now to get it 
> back into service again.
> 
> Ideas?
I am seeing a very similar thing. Ideas?

Sep  8 12:17:46 NOTICE[-1137718352]: chan_iax2.c:1271 iax2_destroy: 
Avoiding IAX destroy deadlock

Fedora Core 1, Asterisk CVS-03/30/04-16:59:11. Asterisk is stuck in a 
select call. Here is a backtrace:

(gdb) bt
#0  0x0048dc32 in _dl_sysinfo_int80 () from /lib/ld-linux.so.2
#1  0x00579b21 in ___newselect_nocancel () from /lib/tls/libc.so.6
#2  0x08087384 in main (argc=0, argv=0x0) at channel.h:798

I'm not experienced with multi-threaded debugging, so I don't know what
any of the other threads were doing. I'm assuming that one of them was
responsible for the iax2_destroy call, but I didn't know how to get a
backtrace on the thread. I had to restart Asterisk so that phone calls
could go through.

# ps -C asterisk
  PID TTY          TIME CMD
 8356 ?        00:10:26 asterisk

# strace -p 8356
Process 8356 attached - interrupt to quit
select(0, NULL, NULL, NULL, NULL

# uname -a
Linux server 2.4.22-1.2115.nptl #1 Wed Oct 29 15:42:51 EST 2003 i686 i686 
i386 GNU/Linux

# grep -c "destroy deadlock" /var/log/asterisk/messages 
848934

# ls -l /var/log/asterisk/messages 
-rw-r--r--  1 root root 57236862 Sep  8 12:58 /var/log/asterisk/messages

Other log entries from the 7th (surrounding the start of these 
error messages) There are no other entries from the 6th or 8th.

Sep  7 14:06:46 WARNING[-1232168016]: Timeout, but no rule 't' in
context
'from-sip'
Sep  7 14:07:17 WARNING[-1232168016]: Timeout, but no rule 't' in
context
'from-sip'
Sep  7 15:03:54 WARNING[-1232168016]: Unable to read password
Sep  7 17:53:30 WARNING[-1232168016]: Invalid extension, but no rule 'i'
in context 'from-sip'
Sep  7 17:53:57 WARNING[-1232168016]: Timeout, but no rule 't' in
context
'from-sip'

Dustin

I just recently started to get this message in my asterisk log and am hoping
that someone can tell me what it means, and how I can get rid of it.

I am running IAX (trunk but not using iax trunk because of timing issues)
between two Asterisk boxes. One box is for external registration, and the
other is the PSTN GW.

Any ideas or things to considered would be greatly appreciated.

Regards to all,
Joe