[asterisk-bugs] [JIRA] (ASTERISK-28384) segfault in res_xmpp when distribute_events=yes and res_mwi_devstate loads
Asterisk Team (JIRA)
noreply at issues.asterisk.org
Sun Apr 14 14:51:47 CDT 2019
[ https://issues.asterisk.org/jira/browse/ASTERISK-28384?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=246891#comment-246891 ]
Asterisk Team commented on ASTERISK-28384:
------------------------------------------
Thanks for creating a report! The issue has entered the triage process. That means the issue will wait in this status until a Bug Marshal has an opportunity to review the issue. Once the issue has been reviewed you will receive comments regarding the next steps towards resolution.
A good first step is for you to review the [Asterisk Issue Guidelines|https://wiki.asterisk.org/wiki/display/AST/Asterisk+Issue+Guidelines] if you haven't already. The guidelines detail what is expected from an Asterisk issue report.
Then, if you are submitting a patch, please review the [Patch Contribution Process|https://wiki.asterisk.org/wiki/display/AST/Patch+Contribution+Process].
Please note that once your issue enters an open state it has been accepted. As Asterisk is an open source project there is no guarantee or timeframe on when your issue will be looked into. If you need expedient resolution you will need to find and pay a suitable developer. Asking for an update on your issue will not yield any progress on it and will not result in a response. All updates are posted to the issue when they occur.
> segfault in res_xmpp when distribute_events=yes and res_mwi_devstate loads
> --------------------------------------------------------------------------
>
> Key: ASTERISK-28384
> URL: https://issues.asterisk.org/jira/browse/ASTERISK-28384
> Project: Asterisk
> Issue Type: Bug
> Security Level: None
> Components: Resources/NewFeature, Resources/res_xmpp
> Affects Versions: 13.26.0, 16.3.0
> Environment: AstLinux 1.3.x development
> Linux 3.16.64 x86_64
> XMPP server via prosody 0.10.3
> Reporter: abelbeck
>
> When Asterisk starts, typically every 2-20 times it will either segfault:
> {noformat}
> asterisk[2408]: segfault at 2b6ce0021000 ip 00002b6cc88b8f91 sp 00002b6ccababb70 error 4 in libssl.so.1.0.0[2b6cc8892000+57000]
> {noformat}
> or generate a syslog:
> {noformat}
> WARNING[3061]: res_xmpp.c:3870 in xmpp_client_thread: [asterisk] Socket read error
> {noformat}
> *What I know:*
> Only effects Asterisk 13.26.0 / 16.3.0 with res_mwi_devstate.so allowed to load *and* res_xmpp.so configured with "distribute_events=yes". If either "noload=>res_mwi_devstate.so" or "distribute_events=no" the crash never occurs.
> *What I suspect:*
> Looking at this code:
> {noformat}
> res_xmpp.c: xmpp_init_event_distribution()
> res_mwi_devstate.c: load_module()
> {noformat}
> There may be some startup race condition or interaction that causes the problem.
> I tested using this shell command on our system:
> {noformat}
> while true; do service asterisk stop ; sleep 2 ; rm /var/log/asterisk/full ; service asterisk init ; sleep 4 ; grep 'asterisk.*seg' /var/log/messages; done
> {noformat}
> A crash will occur within a minute or two with the above test script.
> *What I can do:*
> If you have a patch to test, I'll be happy to give it a try, given how hard it may be to reproduce this given the XMPP pubsub environment.
> *What I can't do:*
> Sorry, with our stripped binary embedded system, I can't offer any 'gdb' backtrace help.
--
This message was sent by Atlassian JIRA
(v6.2#6252)
More information about the asterisk-bugs
mailing list