[Home]

Summary:ASTERISK-19307: When a jabber server is configured as type=component, asterisk crashes with segmentation fault.
Reporter:Robert Dailey (rdailey)Labels:
Date Opened:2012-02-07 20:50:27.000-0600Date Closed:2012-02-09 16:53:23.000-0600
Priority:MajorRegression?
Status:Closed/CompleteComponents:Resources/res_jabber
Versions:1.8.9.1 Frequency of
Occurrence		Constant
Related
Issues:
Environment:Linux i686Attachments:
Description:When a jabber server is configured as type=component, asterisk crashes with segmentation fault as soon as res_jabber is loaded.  When starting asterisk from cold, asterisk does not come up fully before seg fault.  When asterisk has been started without res_jabber, asterisk comes up fully, but if res_jabber is loaded with a configured component, it will seg fault at that time.  If the component is commented out or removed from jabber.conf leaving only clients, asterisk does not crash when res_jabber is loaded.  This problem did not exist in Asterisk 1.8.8.0.
Comments:By: Paul Belanger (pabelanger) 2012-02-07 21:53:18.980-0600

Thank you for your bug report. In order to move your issue forward, we require a backtrace[1] from the core file produced after the crash. Also, be sure you have DONT_OPTIMIZE enabled in menuselect within the Compiler Flags section, then:

make install

After enabling, reproduce the crash, and then execute the backtrace[1] instructions. When complete, attach that file to this issue report.

[1] https://wiki.asterisk.org/wiki/display/AST/Getting+a+Backtrace


By: Robert Dailey (rdailey) 2012-02-08 10:59:45.326-0600

No core file is dumped.  Asterisk was started with "asterisk -c -dddddddd -g -vvvv" and there is no core file created in the current working directory (root's home) nor asterisk's home directory.  "Don't optimize" is enabled (see below).

MENUSELECT_CFLAGS=DONT_OPTIMIZE LOADABLE_MODULES


By: Matt Jordan (mjordan) 2012-02-09 16:53:23.231-0600

I'm unable to reproduce this crash.  Using the latest in the 1.8 branch, with a type=component, I'm able to start Asterisk, as well as unload/load res_jabber.


*CLI> module unload res_jabber
Unloaded res_jabber
*CLI>   == Unregistered application 'JabberSend'
 == Unregistered application 'JabberSendGroup'
 == Unregistered application 'JabberStatus'
 == Unregistered application 'JabberJoin'
 == Unregistered application 'JabberLeave'
 == Manager unregistered action JabberSend
 == Unregistered custom function JABBER_STATUS
 == Unregistered custom function JABBER_RECEIVE
module load res_jabber
 == Parsing '/etc/asterisk/jabber.conf':   == Found
 == Manager registered action JabberSend
 == Registered application 'JabberSend'
 == Registered application 'JabberSendGroup'
 == Registered application 'JabberStatus'
 == Registered application 'JabberJoin'
 == Registered application 'JabberLeave'
 == Registered custom function 'JABBER_STATUS'
 == Registered custom function 'JABBER_RECEIVE'
Loaded res_jabber

It's possible that there is another configuration issue at work here, but its impossible to tell without a backtrace.  Even so, res_jabber is a community supported module, so the response time for issues may reflect that.