| Summary: | ASTERISK-13903: Random Coredumps with IAX2 load | ||
| Reporter: | Lorenz Barth (bartpbx) | Labels: | |
| Date Opened: | 2009-04-06 10:32:49 | Date Closed: | 2009-04-08 11:25:27 |
| Priority: | Critical | Regression? | No |
| Status: | Closed/Complete | Components: | Channels/chan_iax2 |
| Versions: | Frequency of Occurrence | ||
| Related Issues: | |||
| Environment: | Attachments: | ||
| Description: | I've updated one of our IAX Servers to 1.4.24.1 and today I see random coredumps on this maschine. The mashine is primary handling IAX2 Traffic and converts to SIP. The maschine is configured with realtime and odbc. BT + BT Full says: #0 0x409c6592 in register_verify (callno=11818, sin=0x40c42dd4, ies=Variable "ies" is not available. ) at chan_iax2.c:5775 5775 ast_string_field_set(iaxs[callno], peer, peer); (gdb) bt #0 0x409c6592 in register_verify (callno=11818, sin=0x40c42dd4, ies=Variable "ies" is not available. ) at chan_iax2.c:5775 #1 0x409cc7b6 in socket_process (thread=0x82039f8) at chan_iax2.c:8424 #2 0x409d3709 in iax2_process_thread (data=0x82039f8) at chan_iax2.c:7031 #3 0x0810dcd5 in dummy_start (data=0x40c3ea14) at utils.c:856 #4 0x4002ee31 in pthread_start_thread () from /lib/i686/libpthread.so.0 ASTERISK-1 0x401ad59a in clone () from /lib/i686/libc.so.6 (gdb) bt full #0 0x409c6592 in register_verify (callno=11818, sin=0x40c42dd4, ies=Variable "ies" is not available. ) at chan_iax2.c:5775 __zz__ = Variable "__zz__" is not available. | ||
| Comments: | By: Leif Madsen (lmadsen) 2009-04-06 10:37:22 Assigning to dvossel to review and determine if this is something from some previous changes to solve IAX2 storms. By: David Vossel (dvossel) 2009-04-06 15:45:47 what version did you update from? By: Lorenz Barth (bartpbx) 2009-04-07 00:38:30 I Updated from asterisk-1.4.21.2 By: Lorenz Barth (bartpbx) 2009-04-08 10:42:54 do you need any more infos from me concerning this issue By: Russell Bryant (russell) 2009-04-08 11:25:27 I came across this crash a little while back when doing some load testing and fixed it. It is fixed in the 1.4 branch as of rev 183559. It will be in the next 1.4.X release. | ||