Summary:ASTERISK-09577: Asterisk restart with segmentation fault while IAX peer is registered
Reporter:warlock52 (warlock52)Labels:
Date Opened:2007-06-03 13:23:16Date Closed:2007-06-06 09:32:48
Versions:Frequency of
Environment:Attachments:( 0) bt.txt
( 1) bt-full.txt
Description:I have 1.4.4 installed on Centos 4.4 and a2b and am getting the following segmentation fault when asterisk is restarted while an IAX peer is registered:
 == Registered custom function IAXPEER
 == Registered application 'IAX2Provision'
 == Manager registered action IAXpeers
 == Manager registered action IAXnetstats
 == Parsing '/etc/asterisk/iax.conf': Found
 == Parsing '/etc/asterisk/additional_a2billing_iax.conf': Found
 == Using TOS bits 0
 == Binding IAX2 to default address
 == Parsing '/etc/asterisk/users.conf': Found
 == Parsing '/etc/asterisk/additional_a2billing_sip.conf': Found
 == Parsing '/etc/asterisk/additional_a2billing_iax.conf': Found
   -- Seeding '3xxxx82944' at xxx.xxx.xxx.xxx:61006 for 60
   -- Seeding '3xxxx82944' at xxx.xxx.xxx.xxx:61006 for 60
Segmentation fault

The only way to be able to restart Asterisk is comenting out the peer definition  for the peer "3xxxx82944" in iax.conf. After this Asterisk comes back with the a message that the IAX peer has been UNREGISTERED. After this I can uncomment the peer definition and everything starts working again.

Comments:By: Joshua C. Colp (jcolp) 2007-06-04 06:38:34

Can you please provide a backtrace with this? Instructions can be found in doc/backtrace.txt - Thanks!

By: warlock52 (warlock52) 2007-06-04 10:22:51

bt and bt-full attached.

By: timrobbins (timrobbins) 2007-06-05 08:50:49

Looks like the issue that was fixed in 1.4 branch rev 63830.


By: Nic Bellamy (nic_bellamy) 2007-06-05 15:47:35

I reported http://bugs.digium.com/view.php?id=9709 which is the one fixed in rev 63830 referenced by timrobbins. The backtrace looks identical to me, so I'd say it's the same bug - try updating to the latest 1.4 SVN and see how you go.

By: Russell Bryant (russell) 2007-06-06 09:32:47

This issue has already been fixed.  Update to the latest code from the 1.4 branch and if you still have a problem, please let us know.  Thanks!